Out of your choices I vote for (b). I also vote for John's notion of "just a
QoS hint".
Also, relax the pseudo-random number requirement of the flow label. Routers
can't really know how good the PRF used by the host is, so no router should
assume the flow label to be a pseudo random number! Also, if the flow label
does not need to be a result of a PRF, usage of "well-known values" becomes
possible, if anyone ever would find a need for that (currently I really
don't see the need for this as the Traffic Class should provide more than
enough tags for aggregates needing specific per-hop-behavior).
Additionally, the flow label should not be mutable in transit, except within
specific "QoS domains", where the flow-label value could temporarily be
changed. I mean that the value seen at the flow label field on "QoS domain"
entry will be restored at the "QoS domain" exit. Whatever signaling etc.
might be needed to effect this is the problem of the "QoS domain".
End-to-end the value should not be changed, except, perhaps as Francis
suggested to allow it to be changed once from all-zero to a non-zero value.
As for routing, the addresses themselves should be sufficient. And isn't
MPLS supposed to live beneath the IP-layer?
Jarno
> -----Original Message-----
> From: ext Brian E Carpenter [mailto:[EMAIL PROTECTED]]
> Sent: 16. elokuuta 2001 16:45
> To: ipng
> Subject: Higher level question about flow label
>
>
> I think the WG needs to decide once and for all whether the
> flow label is
> a) a CATNIP or MPLS-like routing handle
> or b) a QOS hint for intserv only
> or c) a QOS hint for intserv and diffserv
> or d) a waste of bits
>
> We can get back to the details once we have a consensus on this.
>
> Brian
> --------------------------------------------------------------------
> 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]
> --------------------------------------------------------------------
>
--------------------------------------------------------------------
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]
--------------------------------------------------------------------
