Re: 6MAN WG Last Call: <draft-ietf-6man-text-addr-representation-01.txt>

Seiichi Kawamura <kawamucho@mesh.ad.jp> Mon, 26 October 2009 01:12 UTC

Return-Path: <kawamucho@mesh.ad.jp>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B906C3A68D0 for <ipv6@core3.amsl.com>; Sun, 25 Oct 2009 18:12:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.51
X-Spam-Level:
X-Spam-Status: No, score=0.51 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, J_CHICKENPOX_34=0.6]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id X3hq+r6IU+N7 for <ipv6@core3.amsl.com>; Sun, 25 Oct 2009 18:12:13 -0700 (PDT)
Received: from tyo201.gate.nec.co.jp (TYO201.gate.nec.co.jp [202.32.8.193]) by core3.amsl.com (Postfix) with ESMTP id 997063A6890 for <ipv6@ietf.org>; Sun, 25 Oct 2009 18:12:13 -0700 (PDT)
Received: from mailgate3.nec.co.jp ([10.7.69.161]) by tyo201.gate.nec.co.jp (8.13.8/8.13.4) with ESMTP id n9Q1CNHE017497; Mon, 26 Oct 2009 10:12:23 +0900 (JST)
Received: (from root@localhost) by mailgate3.nec.co.jp (8.11.7/3.7W-MAILGATE-NEC) id n9Q1CMS23983; Mon, 26 Oct 2009 10:12:22 +0900 (JST)
Received: from bgas200085.sys.biglobe.nec.co.jp (bgas200085.sys.biglobe.nec.co.jp [10.82.141.45]) by mailsv3.nec.co.jp (8.13.8/8.13.4) with ESMTP id n9Q1CMKN014908; Mon, 26 Oct 2009 10:12:22 +0900 (JST)
Received: from bsac29088.sys.biglobe.nec.co.jp (localhost [127.0.0.1]) by bgas200085.sys.biglobe.nec.co.jp (BINGO/BINGO/06101717) with ESMTP id n9Q1CMsF004099; Mon, 26 Oct 2009 10:12:22 +0900
Received: from mail.sys.biglobe.nec.co.jp (bgsx5626.sys.biglobe.nec.co.jp [10.18.151.10]) by bsac29088.sys.biglobe.nec.co.jp (BINGO/BINGO/06101717) with ESMTP id n9Q1CMgg021256; Mon, 26 Oct 2009 10:12:22 +0900
Received: from [127.0.0.1] (edonet065.sys.biglobe.nec.co.jp [10.19.137.65]) (authenticated bits=0) (envelope-from kawamucho@mesh.ad.jp) by mail.sys.biglobe.nec.co.jp (BINGO/BINGO/06101717) with ESMTP id n9Q1CMw1029283 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 26 Oct 2009 10:12:22 +0900
Message-ID: <4AE4F774.1030006@mesh.ad.jp>
Date: Mon, 26 Oct 2009 10:12:20 +0900
From: Seiichi Kawamura <kawamucho@mesh.ad.jp>
User-Agent: Thunderbird 2.0.0.22 (Windows/20090605)
MIME-Version: 1.0
To: Alexandru Petrescu <alexandru.petrescu@gmail.com>
Subject: Re: 6MAN WG Last Call: <draft-ietf-6man-text-addr-representation-01.txt>
References: <501E2743-9EFF-4D9A-A873-003DB8AF0381@gmail.com> <4AE2F6BB.50004@gmail.com>
In-Reply-To: <4AE2F6BB.50004@gmail.com>
X-Enigmail-Version: 0.96.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
Cc: 6man Mailing List <ipv6@ietf.org>, Bob Hinden <bob.hinden@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Oct 2009 01:12:15 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Alex

Thanks for your support and comments.
Please see inline.

Alexandru Petrescu wrote:
> I support it.
> 
> Half-substantive and half-editorial comments follow.
> 
> draft:
>> When the length of the
>>    consecutive 16 bit 0 fields are equal (i.e. 2001:db8:0:0:1:0:0:1),
>>    the former is shortened.
> 
> The "former" when reading it left-to-right western latin style?  Maybe
> better "The most significant if represented in network byte order"?  Or
> similar.

Yes, former as in western latin.

> 
> Is there any intention to suggest this choice of placement of :: to the
> IEEE Unix ("Austin Group") who standardizes what inet_pton and ntop do:
> http://www.opengroup.org/onlinepubs/9699919799/

Appendix A notes that inet_ntop (of FreeBSD7.0) follows Section 4.
Linux implementations that I checked works the same also, but
I've had a few people tell me some do not work this way.
I've not been able to confirm this, but in most cases
inet_ntop already does follow Sec4 placement of ::s

> 
> ?
> 
> Or at least add a reference in the draft about the inet_ntop and pton
> standardization documents, which are IEEE (outside of IETF).
> 
> Finally, is there some implementation prototyping in support of
> recommendation of section 4?  I think there may be already.

inet_ntop :-)
and ipv6calc works very nice too.

Regards,
Seiichi

> 
> Alex
> 
> Bob Hinden a écrit :
>> All,
>>
>> This message starts a 2-week 6MAN Working Group Last Call on advancing:
>>
>>
>>     Title           : A Recommendation for IPv6 Address Text
>> Representation
>>     Author(s)       : S. Kawamura, M. Kawashima
>>     Filename        : draft-ietf-6man-text-addr-representation-01.txt
>>     Pages           : 14
>>     Date            : 2009-10-18
>>
>>
>> as a Proposed Standard.  Substantive comments and statements of
>> support for advancing this document should be directed to the mailing
>> list. Editorial suggestions can be sent to the document editor. 
> 
> Who is the document editor?
> 
> Alex
> 
> 
>  This last
>> call will end on November 5, 2009.
>>
>> Regards,
>> Bob Hinden & Brian Haberman
>> 6MAN Chairs
>> --------------------------------------------------------------------
>> IETF IPv6 working group mailing list
>> ipv6@ietf.org
>> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
>> --------------------------------------------------------------------
>>
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
> 
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)

iEYEARECAAYFAkrk93QACgkQcrhTYfxyMkKcwgCggL/Eupl8hs550DeKdgMuLGJb
+YkAnihKuiSWx6/R0EojiQDdJjNGULRM
=iPHf
-----END PGP SIGNATURE-----