Re: FlowId and FlowIdOrAny
Dan Grossman <[email protected]> Tue, 21 Jan 2003 11:34:14 -0500
| Newsgroups | gmane.ietf.diffserv,gmane.ietf.rap |
|---|---|
| Message-ID | <[email protected]> |
Um... since you're bringing the Diffserv folks into the middle of the conversation, would it be possible to clue us in as to what we're talking about? Thanks. Juergen Schoenwaelder wrote: > I changed the subject line and fixed the proposed TC. So here is where > I think we are. I have also reduced the CC list and I have added the > diffserv mailing list since diffserv folks should be in the loop I > think. > > FlowId TECTUAL-CONVENTION > DISPLAY-HINT "d" > STATUS current > DESCRIPTION > "The flow identifier in an IPv6 header that may be used to > discriminate traffic flows." > REFERENCE > "RFC 2460" > SYNTAX Integer32 (0..1048575) > > FlowIdOrAny TECTUAL-CONVENTION > DISPLAY-HINT "d" > STATUS current > DESCRIPTION > "The flow identifier in an IPv6 header that may be used to > discriminate traffic flows. The value of -1 is used to > indicate a wildcard, i.e. any value." > REFERENCE > "RFC 2460" > SYNTAX Integer32 (-1 | 0..1048575) > > Open issues: > > - Is the flow identifier the same as the flow label? I guess so. If > this is true, then we should probably use the TC names FlowLabel > and FlowLableOrAny and also change the wordings in the description > clause. > > - The name of the MIB modules which will contain these definitions. > > - Since Fred kind of said that the diffServMultiFieldClfrFlowId > object should have had a wildcard, can we agree that this is > actually a bug in RFC 3289 which will be fixed by using FlowIdOrAny > in the next revision of the DIFFSERV-MIB? > > /js > > -- > Juergen Schoenwaelder <http://www.informatik.uni-osnabrueck.de/schoenw/> > > _______________________________________________ > diffserv mailing list > [email protected] > https://www1.ietf.org/mailman/listinfo/diffserv > Archive: http://www.ietf.org/mail-archive/working-groups/diffserv/current/maillist.html _______________________________________________ diffserv mailing list [email protected] https://www1.ietf.org/mailman/listinfo/diffserv Archive: http://www.ietf.org/mail-archive/working-groups/diffserv/current/maillist.html