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 <svenaas@cisco.com> Tue, 03 January 2012 17:26 UTC

Return-Path: <svenaas@cisco.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 610C421F84AC for <gen-art@ietfa.amsl.com>; Tue, 3 Jan 2012 09:26:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 olTzEahj6YRj for <gen-art@ietfa.amsl.com>; Tue, 3 Jan 2012 09:26:39 -0800 (PST)
Received: from mtv-iport-4.cisco.com (mtv-iport-4.cisco.com [173.36.130.15]) by ietfa.amsl.com (Postfix) with ESMTP id D9BF421F8498 for <gen-art@ietf.org>; Tue, 3 Jan 2012 09:26:39 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=svenaas@cisco.com; l=2502; q=dns/txt; s=iport; t=1325611600; x=1326821200; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=cTieAY7RmDHm2R4PfVHbN+GqSky4QYfktOyPBP8L9hI=; b=lthasHXhiMq3W+jyCLSYWecjc+/0RwjPSkZM+NRmZGGv6f6BjB/s9zN6 EQoReM9ZPHut4TCxU1npBbCaVrYRSlqeYoNNu2ozjs/+8AjhmgzTPQZ4H pkbYfztuBV/pvxLmBlUPjEiaOm0vkdLMG56RMZp7k6YbmcE/dmiYZKnHr Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AmEQAAM6A0+rRDoH/2dsb2JhbABDggWoHoI7gQWBcgEBAQQSASUvEQEQCxgJFgQLCQMCAQIBRQYNAQcBAR6fMAGdeIwPBIg3jEuFT40G
X-IronPort-AV: E=Sophos;i="4.71,450,1320624000"; d="scan'208";a="23520387"
Received: from mtv-core-2.cisco.com ([171.68.58.7]) by mtv-iport-4.cisco.com with ESMTP; 03 Jan 2012 17:26:39 +0000
Received: from [10.33.12.84] ([10.33.12.84]) by mtv-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id q03HQcHT003564; Tue, 3 Jan 2012 17:26:39 GMT
Message-ID: <4F033A4F.9080407@cisco.com>
Date: Tue, 03 Jan 2012 09:26:39 -0800
From: Stig Venaas <svenaas@cisco.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: Russ Housley <housley@vigilsec.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, General Area Review Team <gen-art@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, 03 Jan 2012 17:26:40 -0000

Russ, I've sent 3-4 emails in December asking if your discuss can be
resolved, but no response. I hope you can respond now.

Stig

On 11/28/2011 11:07 AM, Stig Venaas (svenaas) 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
>