IETF Logo Mail Archive

Re: [Lsr] AD Review of draft-ietf-isis-segment-routing-msd-13

"Les Ginsberg (ginsberg)" <ginsberg@cisco.com> Wed, 29 August 2018 23:52 UTC

Return-Path: <ginsberg@cisco.com>
X-Original-To: lsr@ietfa.amsl.com
Delivered-To: lsr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7B30E130DF4; Wed, 29 Aug 2018 16:52:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.51
X-Spam-Level:
X-Spam-Status: No, score=-14.51 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id i0evhR5qBNt8; Wed, 29 Aug 2018 16:52:48 -0700 (PDT)
Received: from rcdn-iport-5.cisco.com (rcdn-iport-5.cisco.com [173.37.86.76]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1F268130DC8; Wed, 29 Aug 2018 16:52:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=16836; q=dns/txt; s=iport; t=1535586768; x=1536796368; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=IkiKJURfEKaRYxnbCsPYVMRnl43guCyVzrnHpxYHHz4=; b=CRYv8bZY6DGtszRuY3+9iBUDimJftkqQxIB57/v/buQG/wdr/+/mIEQk T005GNmIScGPP6WHotva6x2Cg70vOCEkTc1jiW3QmV3WpgbLD5JsHUuDh 2Z9dQt4RWNss7Xz5+mP36Gd8HJlL5TjU+LGHkBc8QGzbI5VDY9Nwkujz8 o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0CbAABTMYdb/4kNJK1ZGQEBAQEBAQEBAQEBAQcBAQEBAYJXeGV/KAqDaIgRjCqCDYhViCCFM4F6C4RsAheCdCE0GAECAQECAQECbSiFNwEBAQQjCkUHEAIBCA4DBAEBKAMCAgIfERQJCAIEAQ0FCIMagR1MAxWkIYEuhy4Ngk6KEBeBQT+EJIJWgl6CS4JXAo0RhVOIKisJAoxhgwgfgT+ENIhejAeHKgIRFIEkHTiBUnAVGoMKkFNvi0yBHAEB
X-IronPort-AV: E=Sophos;i="5.53,305,1531785600"; d="scan'208,217";a="227102762"
Received: from alln-core-4.cisco.com ([173.36.13.137]) by rcdn-iport-5.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 29 Aug 2018 23:52:47 +0000
Received: from XCH-ALN-005.cisco.com (xch-aln-005.cisco.com [173.36.7.15]) by alln-core-4.cisco.com (8.15.2/8.15.2) with ESMTPS id w7TNqlMD023970 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 29 Aug 2018 23:52:47 GMT
Received: from xch-aln-001.cisco.com (173.36.7.11) by XCH-ALN-005.cisco.com (173.36.7.15) with Microsoft SMTP Server (TLS) id 15.0.1367.3; Wed, 29 Aug 2018 18:52:46 -0500
Received: from xch-aln-001.cisco.com ([173.36.7.11]) by XCH-ALN-001.cisco.com ([173.36.7.11]) with mapi id 15.00.1367.000; Wed, 29 Aug 2018 18:52:46 -0500
From: "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>
To: Alvaro Retana <aretana.ietf@gmail.com>, "draft-ietf-isis-segment-routing-msd@ietf.org" <draft-ietf-isis-segment-routing-msd@ietf.org>
CC: "lsr@ietf.org" <lsr@ietf.org>, Christian Hopps <chopps@chopps.org>, "lsr-chairs@ietf.org" <lsr-chairs@ietf.org>
Thread-Topic: AD Review of draft-ietf-isis-segment-routing-msd-13
Thread-Index: AQHUNNoQmHI5FO69m0uobgW9g1VMU6TBXRPAgAecJnCADmNXgIAAH7nQ
Date: Wed, 29 Aug 2018 23:52:46 +0000
Message-ID: <712be60685b44934b40357887c80d8d2@XCH-ALN-001.cisco.com>
References: <CAMMESsxptarNYpLnNHA3mB+QBzb=RV0si1NNScPZdNJw4UyLog@mail.gmail.com> <d2de842b864a4a7a98f646c748828fe6@XCH-ALN-001.cisco.com> <a91d03ee241e4112ab0fe5a638f480fe@XCH-ALN-001.cisco.com> <CAMMESszWgAB6Mh7eSW08Z0=Nrx2XM407j+6kJqWK0ciBAZYS7A@mail.gmail.com>
In-Reply-To: <CAMMESszWgAB6Mh7eSW08Z0=Nrx2XM407j+6kJqWK0ciBAZYS7A@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.24.73.246]
Content-Type: multipart/alternative; boundary="_000_712be60685b44934b40357887c80d8d2XCHALN001ciscocom_"
MIME-Version: 1.0
X-Outbound-SMTP-Client: 173.36.7.15, xch-aln-005.cisco.com
X-Outbound-Node: alln-core-4.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/y-NrQQmMKIkzh73--qP7Jl25PqQ>
Subject: Re: [Lsr] AD Review of draft-ietf-isis-segment-routing-msd-13
X-BeenThere: lsr@ietf.org
X-Mailman-Version: 2.1.27
Precedence: list
List-Id: Link State Routing Working Group <lsr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/lsr>, <mailto:lsr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/lsr/>
List-Post: <mailto:lsr@ietf.org>
List-Help: <mailto:lsr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lsr>, <mailto:lsr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Aug 2018 23:52:51 -0000

Alvaro –

I have posted V15 addressing your comments.

Inline.

From: Alvaro Retana <aretana.ietf@gmail.com>
Sent: Wednesday, August 29, 2018 9:56 AM
To: Les Ginsberg (ginsberg) <ginsberg@cisco.com>; draft-ietf-isis-segment-routing-msd@ietf.org
Cc: lsr@ietf.org; Christian Hopps <chopps@chopps.org>; lsr-chairs@ietf.org
Subject: RE: AD Review of draft-ietf-isis-segment-routing-msd-13

On August 20, 2018 at 2:15:32 PM, Les Ginsberg (ginsberg) (ginsberg@cisco.com<mailto:ginsberg@cisco.com>) wrote:

Les:

Hi!
V14 of the draft has been posted addressing your comments – subject to my responses previously sent.
Please let us know if this is sufficient or you still have concerns which need to be addressed.

I just have one outstanding comment (below).

I think that this comment, along with the ones in my other message on this thread can be addressed while we move the document forward.  I will start the IETF Last Call.

Thanks!!

Alvaro.


From: Alvaro Retana <aretana.ietf@gmail.com<mailto:aretana.ietf@gmail.com>>
Sent: Wednesday, August 15, 2018 1:53 PM

...
239     4.  Using Node and Link MSD Advertisements
[major] After reading this section, I still don't know how to use the advertisements.  What should a receiver do with the values?  Maybe the use is constrained to a controller...maybe the exact operation is out of the scope of this document.  Either way, please say something.
[Les:] The proper use of an MSD type is specific to the type. What this section is discussing is not how to use a particular MSD type – or even MSD types in general – but rather the relationship between Node/Link Advertisements what procedures should be followed when one or both are present.
I changed the title of the section to “Procedures for using Node and Link MSD Advertisements”.
   Les

v2.23.0 | Report a Bug | By Email