Re: [Gen-art] Russ's Discs on draft-ietf-pim-port [Was: Gen-ART Telechat review of draft-ietf-pim-port-09.txt]

Stig Venaas <stig@venaas.com> Tue, 06 December 2011 06:07 UTC

Return-Path: <stig@venaas.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AC8DB1F0C9A for <gen-art@ietfa.amsl.com>; Mon, 5 Dec 2011 22:07:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level:
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ni4Ddp07Iv79 for <gen-art@ietfa.amsl.com>; Mon, 5 Dec 2011 22:07:23 -0800 (PST)
Received: from ufisa.uninett.no (ufisa.uninett.no [IPv6:2001:700:1:2:158:38:152:126]) by ietfa.amsl.com (Postfix) with ESMTP id 11C791F0C40 for <gen-art@ietf.org>; Mon, 5 Dec 2011 22:07:23 -0800 (PST)
Received: from [10.21.119.5] (128-107-239-233.cisco.com [128.107.239.233]) by ufisa.uninett.no (Postfix) with ESMTPSA id 633687FE2; Tue, 6 Dec 2011 07:07:18 +0100 (CET)
Message-ID: <4EDDB0EB.2000103@venaas.com>
Date: Mon, 05 Dec 2011 22:06:35 -0800
From: Stig Venaas <stig@venaas.com>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: Suresh Krishnan <suresh.krishnan@ericsson.com>
References: <00d401ccabbe$216a6ae0$643f40a0$@olddog.co.uk> <4ED1860F.3080501@ericsson.com> <4ED3CBF1.9050303@cisco.com> <4ED521FE.5080401@ericsson.com> <4ED3DBD8.1070207@cisco.com>
In-Reply-To: <4ED3DBD8.1070207@cisco.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: "adrian@olddog.co.uk" <adrian@olddog.co.uk>, 'General Area Review Team' <gen-art@ietf.org>, "draft-ietf-pim-port.all@tools.ietf.org" <draft-ietf-pim-port.all@tools.ietf.org>
Subject: Re: [Gen-art] Russ's Discs on draft-ietf-pim-port [Was: Gen-ART Telechat review of draft-ietf-pim-port-09.txt]
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Dec 2011 06:07:23 -0000

I think we should be all set then. Can the discuss be cleared then Russ?
See below.

Suresh, maybe you can confirm that you are happy ? At least I think
you are.

Stig

On 28.11.2011 11:07, Stig Venaas wrote:
> On 11/29/2011 10:18 AM, Suresh Krishnan wrote:
>> Hi Stig,
>>
>>
>> On 11/28/2011 12:59 PM, Stig Venaas wrote:
>>>> Please note that the Connection ID AFI in the PORT Hello Option does
>>>> not
>>>> need to match the address family of PIM Hello message that carries it.
>>>> e.g. an IPv6 PIM Hello message could contain a PORT Hello Option with a
>>>> TCP Connection ID AFI of 1 (IPv4).
>>>
>>> While I am OK with this text, wouldn't it be better to add this to 3.1
>>> and 3.2 where we formally define the hello options?
>>>
>>> My proposal would be:
>>>
>>> End of 3.1:
>>>
>>> OLD:
>>> TCP Connection ID AFI: The AFI value to describe the address-family
>>> of the address of the TCP Connection ID field. When this field is
>>> 0, a mechanism outside the scope of this document is used to
>>> obtain the addresses used to establish the TCP connection.
>>>
>>> NEW:
>>> TCP Connection ID AFI: The AFI value to describe the address-family
>>> of the address of the TCP Connection ID field. Note that this
>>> value does not need to match the address-family of the PIM Hello
>>> message that carries it. When this field is 0, a mechanism
>>> outside the scope of this document is used to obtain the
>>> addresses used to establish the TCP connection.
>>>
>>> End of 3.2:
>>>
>>> OLD:
>>> SCTP Connection ID AFI: The AFI value to describe the address-
>>> family of the address of the SCTP Connection ID field. When this
>>> field is 0, a mechanism outside the scope of this document is used
>>> to obtain the addresses used to establish the SCTP connection.
>>>
>>> NEW:
>>> SCTP Connection ID AFI: The AFI value to describe the address-
>>> family of the address of the SCTP Connection ID field. Note that
>>> this value does not need to match the address-family of the PIM
>>> Hello message that carries it. When this field is 0, a mechanism
>>> outside the scope of this document is used to obtain the
>>> addresses used to establish the SCTP connection.
>>>
>>> What do you think?
>>
>> This works great.
>
> Great, I hope we can then just add a note for the editor, and that the
> discuss can be cleared...
>
> Stig
>
>>
>> Thanks
>> Suresh
>