[PWE3] Re: New Version Notification - draft-ietf-pwe3-iana-allocation-14.txt

Brian E Carpenter <brc@zurich.ibm.com> Mon, 31 October 2005 17:26 UTC

Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EWdQJ-0005iR-N0; Mon, 31 Oct 2005 12:26:19 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EWdQI-0005i9-06; Mon, 31 Oct 2005 12:26:18 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA22134; Mon, 31 Oct 2005 12:25:57 -0500 (EST)
Received: from mtagate4.de.ibm.com ([195.212.29.153]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EWdeV-0002bF-JD; Mon, 31 Oct 2005 12:41:00 -0500
Received: from d12nrmr1607.megacenter.de.ibm.com (d12nrmr1607.megacenter.de.ibm.com [9.149.167.49]) by mtagate4.de.ibm.com (8.12.10/8.12.10) with ESMTP id j9VHQ8ZB178842; Mon, 31 Oct 2005 17:26:08 GMT
Received: from d12av01.megacenter.de.ibm.com (d12av01.megacenter.de.ibm.com [9.149.165.212]) by d12nrmr1607.megacenter.de.ibm.com (8.12.10/NCO/VERS6.7) with ESMTP id j9VHQ89S169676; Mon, 31 Oct 2005 18:26:08 +0100
Received: from d12av01.megacenter.de.ibm.com (loopback [127.0.0.1]) by d12av01.megacenter.de.ibm.com (8.12.11/8.13.3) with ESMTP id j9VHQ7KH024521; Mon, 31 Oct 2005 18:26:08 +0100
Received: from sihl.zurich.ibm.com (sihl.zurich.ibm.com [9.4.16.232]) by d12av01.megacenter.de.ibm.com (8.12.11/8.12.11) with ESMTP id j9VHQ7K7024511; Mon, 31 Oct 2005 18:26:07 +0100
Received: from zurich.ibm.com (sig-9-146-218-19.de.ibm.com [9.146.218.19]) by sihl.zurich.ibm.com (AIX4.3/8.9.3p2/8.9.3) with ESMTP id SAA79538; Mon, 31 Oct 2005 18:26:04 +0100
Message-ID: <436653A3.3010008@zurich.ibm.com>
Date: Mon, 31 Oct 2005 18:25:55 +0100
From: Brian E Carpenter <brc@zurich.ibm.com>
Organization: IBM
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040113
X-Accept-Language: en, fr, de
MIME-Version: 1.0
To: Luca Martini <lmartini@cisco.com>
References: <E1EUrHe-00070H-3A@newodin.ietf.org> <43653577.4020301@zurich.ibm.com> <4365D89C.5060006@cisco.com>
In-Reply-To: <4365D89C.5060006@cisco.com>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d185fa790257f526fedfd5d01ed9c976
Content-Transfer-Encoding: 7bit
Cc: danny@tcb.net, pwe3 <pwe3@ietf.org>, IESG <iesg@ietf.org>, stbryant@cisco.com
Subject: [PWE3] Re: New Version Notification - draft-ietf-pwe3-iana-allocation-14.txt
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

OK, if -15 has those fixes I will be happy. Thanks.

     Brian

Luca Martini wrote:
> Brian,
> 
> I sent the document out , as there where many changes to it , and I 
> wanted to start from a fresh copy of the draft , with most of the 
> changes incorporated. I think that reving a draft is the best way to 
> document the changes , and making sure that we are all on the same page ...
> 
> 
> Brian E Carpenter wrote:
> 
>> Most of my DISCUSS comments are fixed, thanks, but I still have two 
>> points
>> I'm afraid.
>>
>>> 3.3. Interface Parameters Sub-TLV type
>>
>> ...
>>
>>>    For each allocation a length field MUST also be specified in one of
>>>    the following formats:
>>>      - A decimal integer
>>>      - Text as follows:"up to X", where X is a decimal integer
>>>      - Up to 3 different decimal integers.
>>
>>
>>
>> Why is "A decimal integer" listed? It is a subset of "Up to 3 
>> different decimal integers".
> 
> Yes, it is redundant. I will edit it to include only the "Up to 3 
> different decimal integers."
> 
>> Does "up to X" mean "up to and including X"?
> 
> 
> yes. I will edit the text to make it clear by adding the following comment:
> 
> "The text "up to X" is meant to mean up to and including X."
> 
> 
>>
>>> 3.4.1. Attachment Individual Identifier Type
>>
>> ...
>>
>>>    For each allocation a length field MUST also be specified as a
>>>    decimal integer.
>>
>>
>> This is a substantive change since the document was submitted to
>> the IESG, since the -12 version had the same three alternatives
>> as above. Has this change got WG consensus?
>>
>>> 3.4.2. Attachment Group Identifier (AGI) Type
>>
>> ...
>>
>>>    For each allocation a length field MUST also be specified as a
>>>    decimal integer.
>>
>>
>> Ditto.
> 
> I do not believe that there is any question on this point in the WG. The 
>  length was already included in the protocol specification.  The length 
> was omitted from this allocation by an oversight. This has been 
> corrected, and I have not heard any comments on this topic in the WG.
> ( And I CCed the WG )
> Thanks.
> Luca
> 
>>
>>     Brian
> 
> 


_______________________________________________
pwe3 mailing list
pwe3@ietf.org
https://www1.ietf.org/mailman/listinfo/pwe3