Re: draft-ietf-ipngwg-rfc2553bis-10.txt

2003-01-14 Thread Jack McCann

Itojun,

> minor nit:
> NI_NUMERICSCOPE appears in the text (page 24) but not in section 7.

Thanks for catching that.  The reference to NI_NUMERICSCOPE
on page 24 should be removed, it was part of the stuff
that moved to draft-ietf-ipv6-scope-api-00.txt.

It may be too late to fix this...

- Jack


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]




Re: draft-ietf-ipngwg-rfc2553bis-10.txt

2003-01-25 Thread Pekka Savola
On Tue, 14 Jan 2003, Jack McCann wrote:
> > minor nit:
> > NI_NUMERICSCOPE appears in the text (page 24) but not in section 7.
> 
> Thanks for catching that.  The reference to NI_NUMERICSCOPE
> on page 24 should be removed, it was part of the stuff
> that moved to draft-ietf-ipv6-scope-api-00.txt.
> 
> It may be too late to fix this...

Another minor nit: the Introduction says:

  IPv6 also introduces new features (e.g., traffic class
  and flowlabel), some of which must be made visible to applications via
  the API.

.. but tclass/flowlabel specification was mostly moved off.  I wonder if 
some rewording would be in order?

I believe these kind of editorial nits can be fixed when RFC editor is
done and while at AUTH48 state.

-- 
Pekka Savola "You each name yourselves king, yet the
Netcore Oykingdom bleeds."
Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings



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]