Re: [Isis-wg] draft-wei-isis-tlv-03 (Purge Originator Id)

lizhenqiang@chinamobile.com Thu, 22 April 2010 10:15 UTC

Return-Path: <lizhenqiang@chinamobile.com>
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 7FA153A6829 for <isis-wg@core3.amsl.com>; Thu, 22 Apr 2010 03:15:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 3.236
X-Spam-Level: ***
X-Spam-Status: No, score=3.236 tagged_above=-999 required=5 tests=[AWL=1.163, BAYES_00=-2.599, MIME_CHARSET_FARAWAY=2.45, RELAY_IS_221=2.222]
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 M3Q6rC7+mepY for <isis-wg@core3.amsl.com>; Thu, 22 Apr 2010 03:15:06 -0700 (PDT)
Received: from cmccmta.chinamobile.com (cmccmta.chinamobile.com [221.130.253.133]) by core3.amsl.com (Postfix) with ESMTP id 465E63A67DB for <isis-wg@ietf.org>; Thu, 22 Apr 2010 03:15:05 -0700 (PDT)
To: Les Ginsberg <ginsberg@cisco.com>, Tony Li <tony.li@tony.li>, Jie Dong <dongjie_dj@huawei.com>, bruno.decraene@orange-ftgroup.co, isis-wg@ietf.org, weifang@chinamobile.com
MIME-Version: 1.0
From: lizhenqiang@chinamobile.com
Date: Thu, 22 Apr 2010 18:14:18 +0800
Message-ID: <OFBBABEC65.1E3AAC83-ON4825770D.00383DB7-4825770D.00383DC0@china.mobile>
X-Mailer: Lotus Domino Web Server Release 6.5.5FP1 April 14, 2006
X-MIMETrack: Serialize by Router on cmccmta/servers/cmcc(Release 6.5.5FP1 | April 14, 2006) at 2010-04-22 18:14:56
MIME-Version: 1.0
Content-Type: text/plain; charset="GB2312"
Content-Transfer-Encoding: quoted-printable
Subject: Re: [Isis-wg] draft-wei-isis-tlv-03 (Purge Originator Id)
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, 22 Apr 2010 10:15:07 -0000

Comment inline, begins with Zhenqiang.

Zhenqiang Li


发件人: Les Ginsberg (ginsberg)
发送时间: 2010-04-22 14:41:46
收件人: Les Ginsberg (ginsberg); Tony Li; lizhenqiang@chinamobile.com; Jie Dong; bruno.decraene@orange-ftgroup.co; isis-wg@ietf.org; weifang@chinamobile.com
抄送: 
主题: RE: [Isis-wg] draft-wei-isis-tlv-03 (Purge Originator Id)

A couple of other comments that come to mind:

We need to define what an implementation SHOULD do when it receives a
purged LSP with the additional TLVs i.e. store it (including the body)
and flood it unchanged.

Zhenqiang: This is the normal processing, isn't it?

If the same purged LSP is received from two different originators, the
choice of which "copy" to flood is a local matter.

   Les

> -----Original Message-----
> From: isis-wg-bounces@ietf.org [mailto:isis-wg-bounces@ietf.org] On
> Behalf Of Les Ginsberg (ginsberg)
> Sent: Wednesday, April 21, 2010 11:25 PM
> To: Tony Li; lizhenqiang@chinamobile.com; Jie Dong;
> bruno.decraene@orange-ftgroup.co; isis-wg@ietf.org;
> weifang@chinamobile.com
> Subject: Re: [Isis-wg] draft-wei-isis-tlv-03 (Purge Originator Id)
> 
> 
> 
>  > -----Original Message-----
>  > From: isis-wg-bounces@ietf.org [mailto:isis-wg-bounces@ietf.org] On
>  > Behalf Of Tony Li
>  > Sent: Wednesday, April 21, 2010 10:55 PM
>  > To: lizhenqiang@chinamobile.com; Jie Dong; bruno.decraene@orange-
>  > ftgroup.co; isis-wg@ietf.org; weifang@chinamobile.com
>  > Subject: Re: [Isis-wg] draft-wei-isis-tlv-03 (Purge Originator Id)
>  >
>  >
>  >
>  >
>  >  > I renamed the draft as draft-ietf-isis-purge-tlv-00.txt and
> submitted
>  >  > it to IETF. Its status is Initial Version Approval Requested.
>  >
>  >
>  > As long as that's stuck in the queue, there's not much point in
>  > submitting a
>  > -01 verison.  So here's the document as an attachment.
> 
> But hopefully we can comment on 01 anyway?? :-)
> 
> ****************
> 
> I don't see the need for Section 3. It was interesting discussion
> material while we were debating the merits of making this a WG
> document,
> but I think it has drawbacks when it is included in what is intended
to
> become a standards document.
> 
> The first three points suggest (no doubt unintentionally) that this
> document may in some way be redefining/clarifying the base spec in
> regards to when it is permissible to purge. I don't think we want to
> even remotely suggest that. If you want to know when it is OK to
purge,
> look at the base spec.
> 
> In the second set of three points, only the first (which documents the
> lamentable purge on checksum error experience) has value. The last two
> are anecdotal and could be translated as "there are some weird bugs
out
> there". Interesting - but unnecessary. The first point could be
> mentioned in the introduction as part of the justification for the
> protocol extensions - but I think even that is unnecessary.
> 
> ********************
> In Section 5 I would like to see language which says "hostname TLV
> SHOULD only be used in addition to the system ID TLV". As every IS
MUST
> have a unique systemID but hostnames are optional I would prefer that
> if
> an implementation chooses to include the extra info in the purge that
> the system ID ALWAYS be there. (This is unenforceable of course)
> 
> *******************
> 
> I think there needs to be language which makes clear that the absence
> or
> presence of this additional information has no impact on the
acceptance
> of a purged LSP as valid i.e. no changes to the operation of the
Update
> process are introduced by this draft.
> 
> Thanx.
> 
>    Les
> 
> 
>  >
>  > Tony
> 
> _______________________________________________
> Isis-wg mailing list
> Isis-wg@ietf.org
> https://www.ietf.org/mailman/listinfo/isis-wg