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

Tony Li <tony.li@tony.li> Thu, 16 September 2010 16:04 UTC

Return-Path: <tony.li@tony.li>
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 051563A6988 for <isis-wg@core3.amsl.com>; Thu, 16 Sep 2010 09:04:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.306
X-Spam-Level:
X-Spam-Status: No, score=-102.306 tagged_above=-999 required=5 tests=[AWL=0.293, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 Zizhkn+2Eox0 for <isis-wg@core3.amsl.com>; Thu, 16 Sep 2010 09:04:03 -0700 (PDT)
Received: from qmta09.emeryville.ca.mail.comcast.net (qmta09.emeryville.ca.mail.comcast.net [76.96.30.96]) by core3.amsl.com (Postfix) with ESMTP id 80BCB3A688B for <isis-wg@ietf.org>; Thu, 16 Sep 2010 09:04:02 -0700 (PDT)
Received: from omta12.emeryville.ca.mail.comcast.net ([76.96.30.44]) by qmta09.emeryville.ca.mail.comcast.net with comcast id 7RpA1f0040x6nqcA9U4TXX; Thu, 16 Sep 2010 16:04:27 +0000
Received: from sjc-vpn7-442.cisco.com ([128.107.239.233]) by omta12.emeryville.ca.mail.comcast.net with comcast id 7U451f00552qHCY8YU48A8; Thu, 16 Sep 2010 16:04:25 +0000
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: text/plain; charset="us-ascii"
From: Tony Li <tony.li@tony.li>
In-Reply-To: <AA0F3797-4BC4-491A-B25E-93869B73AA4A@castlepoint.net>
Date: Thu, 16 Sep 2010 09:04:05 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <65B1B019-5384-431F-998D-9E15AB0894F0@tony.li>
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>
To: Shane Amante <shane@castlepoint.net>
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: Thu, 16 Sep 2010 16:04:06 -0000

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.


> 3)  In Section 5, there appears to be a placeholder in there that says "NEW TEXT:".  Should those two words be stricken?


<blush>  Whoops.  Yes, text processing error on my part.  </blush>


> 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.


> 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.

Tony