>>>>> On Mon, 14 Oct 2002 15:46:33 -0400,
>>>>> Thomas Narten <[EMAIL PROTECTED]> said:
> As Jack has completed his updates to RFC 2553, I've put it back on the
> IESG for consideration for publication. That prompted the following
> comment from Bill Fenner.
> Thoughts on how to proceed?
This is a good catch. If I remember correctly, a separate draft
(draft-itojun-ipv6-flowlabel-api-01.txt --I don't know if this is the
latest one) was issued to clarify the API for flow labels. After some
discussions, however, the revise of the draft was suspended, because
the protocol usage of flow labels was still unclear. (And, this was
the reason why the draft was not incorporated into rfc2292bis.)
Thus, I think the best way is
- to remove the paragraph of 2553bis in question, and
- (if necessary) to clarify the detailed usage of sin6_flowinfo is not
defined in 2553bis because the protocol specification of flow labels
is still unclear.
JINMEI, Tatuya
Communication Platform Lab.
Corporate R&D Center, Toshiba Corp.
[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]
--------------------------------------------------------------------
