Re: [Isis-wg] WG LC draft-ietf-isis-purge-tlv-03.txt

Shane Amante <shane@castlepoint.net> Fri, 17 September 2010 01:43 UTC

Return-Path: <shane@castlepoint.net>
X-Original-To: isis-wg@core3.amsl.com
Delivered-To: isis-wg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A96663A6AA5 for <isis-wg@core3.amsl.com>; Thu, 16 Sep 2010 18:43:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.022
X-Spam-Level:
X-Spam-Status: No, score=-2.022 tagged_above=-999 required=5 tests=[AWL=0.577, BAYES_00=-2.599]
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 eJ0-kaUNvJUH for <isis-wg@core3.amsl.com>; Thu, 16 Sep 2010 18:43:53 -0700 (PDT)
Received: from dog.tcb.net (dog.tcb.net [64.78.150.133]) by core3.amsl.com (Postfix) with ESMTP id 47A613A69F3 for <isis-wg@ietf.org>; Thu, 16 Sep 2010 18:43:53 -0700 (PDT)
Received: by dog.tcb.net (Postfix, from userid 0) id 2CF85268674; Thu, 16 Sep 2010 19:44:18 -0600 (MDT)
Received: from mbpw.castlepoint.net (174-29-218-177.hlrn.qwest.net [174.29.218.177]) (authenticated-user smtp) (TLSv1/SSLv3 AES128-SHA 128/128) by dog.tcb.net with SMTP; Thu, 16 Sep 2010 19:44:17 -0600 (MDT) (envelope-from shane@castlepoint.net)
X-Avenger: version=0.7.8; receiver=dog.tcb.net; client-ip=174.29.218.177; client-port=64796; syn-fingerprint=65535:56:1:64:M1452,N,W1,N,N,T,S; data-bytes=0
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: text/plain; charset="us-ascii"
From: Shane Amante <shane@castlepoint.net>
In-Reply-To: <65B1B019-5384-431F-998D-9E15AB0894F0@tony.li>
Date: Thu, 16 Sep 2010 19:44:02 -0600
Content-Transfer-Encoding: quoted-printable
Message-Id: <02EDC2E4-7B30-4564-BF07-3A6961FA396A@castlepoint.net>
References: <8E27D05D-D541-4DEC-9800-E22E1927CBC3@juniper.net> <FE38F867-3BC7-4F7D-9ED0-5E70595E9D52@tony.li> <3EB4BF44-1911-4782-A4D7-D1F989B38290@tony.li> <AA0F3797-4BC4-491A-B25E-93869B73AA4A@castlepoint.net> <65B1B019-5384-431F-998D-9E15AB0894F0@tony.li>
To: Tony Li <tony.li@tony.li>
X-Mailer: Apple Mail (2.1081)
Cc: isis mailing list <isis-wg@ietf.org>, "weifang@chinamobile.com" <weifang@chinamobile.com>, Adrian Farrel <Adrian.Farrel@huawei.com>, Christian Hopps <chopps@cisco.com>, ??? <lizhenqiang@chinamobile.com>, "qinyue@chinamobile.com" <qinyue@chinamobile.com>
Subject: Re: [Isis-wg] WG LC draft-ietf-isis-purge-tlv-03.txt
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/isis-wg>, <mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/isis-wg>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/isis-wg>, <mailto:isis-wg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Sep 2010 01:43:54 -0000

Hi Tony,

On Sep 16, 2010, at 10:04 MDT, Tony Li wrote:
> Hi Shane,
> 
> Thanks for your comments.
> 
>> 2)  In Section 4, it is mentioned that the Dynamic Hostname TLV can be included in purges.  When an IS is inserting two System ID's into the Purge TLV (first, of the IS that inserted the Purge TLV and, second, of the IS that the purge was received from), presumably the Dynamic Hostname TLV would only include the former (the IS that inserted the Purge TLV), correct?  Or, is it permitted for this IS that's inserting two System ID's to insert two Dynamic Hostname TLV's, (assuming the Dynamic Hostname of the IS that purge was first recv'd from was available)?
> 
> 
> The intent was that it was only the local hostname that would be inserted.  I'll add some clarifying text.

Sounds good.


[--snip--]

>> 4)  In Section 6, why is there an RFC Editor Note to remove this section?  Shouldn't this section stay "as is"?
> 
> 
> My understanding is that IANA requests are supposed to be removed.  If I'm out of sync here, I'm happy for it to stay.

By way of precedent I could cite a small handful of (random) IS-IS RFC's with IANA Considerations:
http://tools.ietf.org/html/rfc5305#section-5
http://tools.ietf.org/html/rfc5310#section-6
http://tools.ietf.org/html/rfc5304#section-4
http://tools.ietf.org/html/rfc5308
... thus, I'd recommend it stays in.  However, I'll defer to the co-chairs judgement if you're still unsure/uncomfortable.
 


>> Re: draft-li-reg-purge-01
>> 2)  draft-ietf-isis-purge-tlv states that it's acceptable for the Dynamic Hostname TLV to be included in Purges.  Thus, shouldn't draft-li-reg-purge specify, in IANA Considerations, that the Purge Column should be augmented to also include TLV 137, "Dynamic Name"?  Or, perhaps it would be cleaner if in the IANA Considerations of draft-ietf-isis-purge-tlv stated that TLV 137 also have the Purge column say "y", since Dynamic Hostname TLV is mentioned in this draft and isn't talked about at all in draft-li-reg-purge?
> 
> 
> ?
> 
> Section 4, para 2:
>   The 'Purge' column should initially contain a 'y' for TLV type 10
>   (Authentication) and for TLV type 137 (Dynamic hostname).  All other
>   entries in this column should have an 'n'.  Other additions to this
>   registry should explicitly specify their value for this column.

My turn to blush.  Looks good.  :-)

-shane