On Tue, 21 Aug 2001, Jim Bound wrote:
> the traffic class will provide diff serv metric and the flow identifies
> the E2E connection with the src addr.
My intuitive feeling is that if we leverage the end to end properties of
IPv6 in the address space, then we should do likewise, end to end, for an
identifier that allows recognition of unique flows, and thus keep the
field immutable.
> The src addr MUST be a global address.
> Site-Local can be done too but don't want to get into that right now.
We will want to recognise flows on site-level networks at some stage,
so we shouldn't lock that out just yet.
> One can ask if the Ipv6 address is global why have the flow for per
> connection as above. This is a good question and needs discussion.
If we adopt Francis' (reasonable) suggestion that the label can be written
from a non-zero value only once, then it becomes much harder to assert
that the src/label combination represents a unique flow on a fully end
to end basis. Maybe in end-to-end H.323 to a handset you may want to
prioritise the voice udp rtp flow over the video udp rtp flow, where the
source IP is the same.
I think it is quite possible that in the future we will see more systems
where multiple flows will require different QoS handling and packet treatment
per flow, so we should keep options open to enable that. You could use a
different IPv6 source addresses for a similar purpose, but that probably adds
more complexity (see how hard it is now to negotiate H.323 through a
firewall).
tim
--------------------------------------------------------------------
IETF IPng Working Group Mailing List
IPng Home Page: http://playground.sun.com/ipng
FTP archive: ftp://playground.sun.com/pub/ipng
Direct all administrative requests to [EMAIL PROTECTED]
--------------------------------------------------------------------
