Re: [spring] WG Last Call for draft-ietf-spring-segment-routing-msdc-02

"Stefano Previdi (sprevidi)" <sprevidi@cisco.com> Wed, 01 March 2017 14:53 UTC

Return-Path: <sprevidi@cisco.com>
X-Original-To: spring@ietfa.amsl.com
Delivered-To: spring@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B4F51129495 for <spring@ietfa.amsl.com>; Wed, 1 Mar 2017 06:53:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.522
X-Spam-Level:
X-Spam-Status: No, score=-14.522 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, 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 f-L7zvG-Fy7l for <spring@ietfa.amsl.com>; Wed, 1 Mar 2017 06:53:32 -0800 (PST)
Received: from rcdn-iport-7.cisco.com (rcdn-iport-7.cisco.com [173.37.86.78]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3854512946D for <spring@ietf.org>; Wed, 1 Mar 2017 06:53:32 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3398; q=dns/txt; s=iport; t=1488380012; x=1489589612; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=Wzv1O/soO0VLe2cpWiqaoBEvP3rTi4vQJiENncdVhwg=; b=lj82Sfbr4lWNsdL/nRN9JgqXt2eOor28MZFXowbPTymPeCyjpooKxMxg 2PJLG9AmWYhhJ43cHxO+zh7Zcx+tKnVo+OFqVnF3iryRAoJiiafXYuoce 6eGEVvSC+Bi4g7lc6QmyZCGxT/LUKN6Phr64iAbttgLVc9LnYBY1VO6ft w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0ARAQCt37ZY/5pdJa1eGQEBAQEBAQEBAQEBBwEBAQEBg1CBageNXJFmlTWCDYYiAoI4PxgBAgEBAQEBAQFiHQuEcAEBAQMBHVcFBQsCAQgVAQInBzIUEQIEDgWJcQi0FYsiAQEBAQEBAQEBAQEBAQEBAQEBAQEBHYZMggWCaoQmEQEcgzSCMQEEnCgBkjGBe4UhigKTNAEfOHkIVBVPAYY7dYdEgSGBDQEBAQ
X-IronPort-AV: E=Sophos;i="5.35,226,1484006400"; d="scan'208";a="212785716"
Received: from rcdn-core-3.cisco.com ([173.37.93.154]) by rcdn-iport-7.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 01 Mar 2017 14:53:31 +0000
Received: from XCH-RTP-009.cisco.com (xch-rtp-009.cisco.com [64.101.220.149]) by rcdn-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id v21ErUEo013182 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 1 Mar 2017 14:53:31 GMT
Received: from xch-rtp-010.cisco.com (64.101.220.150) by XCH-RTP-009.cisco.com (64.101.220.149) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Wed, 1 Mar 2017 09:53:29 -0500
Received: from xch-rtp-010.cisco.com ([64.101.220.150]) by XCH-RTP-010.cisco.com ([64.101.220.150]) with mapi id 15.00.1210.000; Wed, 1 Mar 2017 09:53:29 -0500
From: "Stefano Previdi (sprevidi)" <sprevidi@cisco.com>
To: "bruno.decraene@orange.com" <bruno.decraene@orange.com>
Thread-Topic: [spring] WG Last Call for draft-ietf-spring-segment-routing-msdc-02
Thread-Index: AQHSkpmn7TsijQsKVEGVSeuJSawao6GAZcoA
Date: Wed, 01 Mar 2017 14:53:29 +0000
Message-ID: <B1C835BC-D7D8-463E-A474-E159D89AC707@cisco.com>
References: <27991_1487670653_58AC0D7D_27991_2292_1_53C29892C857584299CBF5D05346208A1ED7122E@OPEXCLILM21.corporate.adroot.infra.ftgroup> <18673_1487691447_58AC5EB7_18673_4491_1_53C29892C857584299CBF5D05346208A1ED71F65@OPEXCLILM21.corporate.adroot.infra.ftgroup> <A19DD756-D858-4F86-BF76-F6AC94C0D211@cisco.com> <29235_1488379173_58B6DD25_29235_294_1_53C29892C857584299CBF5D05346208A1ED87127@OPEXCLILM21.corporate.adroot.infra.ftgroup>
In-Reply-To: <29235_1488379173_58B6DD25_29235_294_1_53C29892C857584299CBF5D05346208A1ED87127@OPEXCLILM21.corporate.adroot.infra.ftgroup>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.61.101.21]
Content-Type: text/plain; charset="Windows-1252"
Content-ID: <52A6548FE909FA4A9FB49178EDFA0065@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/I5zaiKn4WuYR4O1QuPbDqbmz7rg>
Cc: "spring@ietf.org" <spring@ietf.org>
Subject: Re: [spring] WG Last Call for draft-ietf-spring-segment-routing-msdc-02
X-BeenThere: spring@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "Stacked Tunnels for Source Routing \(STATUS\)." <spring.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spring>, <mailto:spring-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spring/>
List-Post: <mailto:spring@ietf.org>
List-Help: <mailto:spring-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spring>, <mailto:spring-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Mar 2017 14:53:34 -0000

> On Mar 1, 2017, at 3:39 PM, bruno.decraene@orange.com wrote:
> 
> Hi Stefano,
> 
>> From: Stefano Previdi (sprevidi) [mailto:sprevidi@cisco.com]  > Sent: Tuesday, February 28, 2017 10:16 AM
>> 
>> Hi Bruno,
>> 
>> thanks for the review. I integrated all the comments in the new version I'm going to submit
>> very soon.
> 
> 
> Thanks.
> 
> 
>> One last comment here below:
>> 
>>> On Feb 22, 2017, at 2:00 PM, bruno.decraene@orange.com wrote:
>>> 
>>> 2)      For the document write up, are there any known deployment of draft-ietf-spring-
>> segment-routing-msdc?
>>> 
>>> 
>>> 3)      § 2.1.  Reference design
>>> 
>>> "   o  Each node is its own AS (Node X has AS X)
>>> 
>>>      *  For simple and efficient route propagation filtering, Nodes 5,
>>>         6, 7 and 8 share the same AS, Nodes 3 and 4 share the same AS,
>>>         Nodes 9 and 10 share the same AS.
>>> 
>>>      *  For efficient usage of the scarce 2-byte Private Use AS pool,
>>>         different Tier-3 nodes might share the same AS.
>>> 
>>>      *  Without loss of generality, we will simplify these details in
>>>         this document and assume that each node has its own AS."
>>> 
>>> 
>>> First 2 bullets are contradicting each other's.
>> 
>> 
>> why so ? First bullet refers to tier-1 and tier-2. second bullet refers to tier-3.
> 
> Bullet 1: "Each node is its own AS"
> Bullet 2: "Nodes 5, 6, 7 and 8 share the same AS”


ok sorry, the indent was such that I was confused.


> Looks a priori contradicting.
> Now thinking more about this, and given that on your 5-stage clos topology nodes 5, 6, 7 and 8 are not connected to each other's and any flow has no valid reason to cross two of them, I now see what you mean.
> 
> I would then propose the following change:
> OLD: share the same AS
> NEW: use the same AS number


I agree. I also think that “sharing” has other implications which are not intended here.


> It may look the same, but the two nodes are indeed in different ASes. But they use the same AS number, just like private AS number.
> 
> Or may be it's just me ;-)  So up to you.


no, it’s me too ;-)

s.


> 
> Thanks,
> -- Bruno
>> 
>> thanks.
>> s.
>> 
> 
> 
> _________________________________________________________________________________________________________________________
> 
> Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
> pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
> a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
> Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
> 
> This message and its attachments may contain confidential or privileged information that may be protected by law;
> they should not be distributed, used or copied without authorisation.
> If you have received this email in error, please notify the sender and delete this message and its attachments.
> As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
> Thank you.
>