Doug Barton <do...@dougbarton.us> писал в своём письме Sat, 27 Feb 2010
01:06:09 +0300:
On 02/25/10 18:30, internet-dra...@ietf.org wrote:
A New Internet-Draft is available from the on-line Internet-Drafts
directories.
This draft is a work item of the IPv6 Maintenance Working Group of the
IETF.
Title : A Recommendation for IPv6 Address Text Representation
Author(s) : S. Kawamura, M. Kawashima
Filename : draft-ietf-6man-text-addr-representation-07.txt
Pages : 14
Date : 2010-02-25
At the risk of being redundant I'm including a diff that consists only
of a few minor nits. I'm still supportive of the draft moving forward
with or without these changes.
Regards,
Doug
Since we seem to go over small nits now, I'll submit a couple of my own:
--- draft-ietf-6man-text-addr-representation-07.txt.old 2010-02-26
22:36:32 +0000
+++ draft-ietf-6man-text-addr-representation-07.txt 2010-02-26 22:47:37
+0000
@@ -603,7 +603,7 @@
o 2001:db8::1#80
The situation is not much different in IPv4, but the most ambiguous
- case with IPv6 is the second bullet. This is due to the "::"usage in
+ case with IPv6 is the second bullet. This is due to the usage of "::"
in
IPv6 addresses. This style is NOT RECOMMENDED for its ambiguity.
The [] style as expressed in [RFC3986] SHOULD be employed, and is the
default unless otherwise specified. Other styles are acceptable when
@@ -648,7 +648,7 @@
starting this document. We also would like to thank Brian Carpenter,
Akira Kato, Juergen Schoenwaelder, Antonio Querubin, Dave Thaler,
Brian Haley, Suresh Krishnan, Jerry Huang, Roman Donchenko, Heikki
- Vatiainen ,Dan Wing, and Doug Barton for their input. Also a very
+ Vatiainen, Dan Wing, and Doug Barton for their input. Also a very
special thanks to Ron Bonica, Fred Baker, Brian Haberman, Robert
Hinden, Jari Arkko, and Kurt Lindqvist for their support in bringing
this document to the light of IETF working groups.
@@ -702,7 +702,7 @@
these rules. For example, the usage of getnameinfo() with flags
argument NI_NUMERICHOST in FreeBSD 7.0 will give a conforming output,
except for the special addresses notes in Section 5. The function
- inet_ntop() of FreeBSD7.0 is a good C code reference, but should not
+ inet_ntop() of FreeBSD 7.0 is a good C code reference, but should not
be called directly. See [RFC4038] for details.
Roman.
--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------
