IETF Logo Mail Archive

Re: [spring] [Lsr] Adjacency SID and Passive Interface

"Acee Lindem (acee)" <acee@cisco.com> Fri, 10 May 2019 12:08 UTC

Return-Path: <acee@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 8320A120052; Fri, 10 May 2019 05:08:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.5
X-Spam-Level:
X-Spam-Status: No, score=-14.5 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, 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 header.b=cO6QH4Hn; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=L2hfJcjC
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 DAWdg-PYAAVh; Fri, 10 May 2019 05:08:47 -0700 (PDT)
Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7E85512001B; Fri, 10 May 2019 05:08:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2230; q=dns/txt; s=iport; t=1557490127; x=1558699727; h=from:to:subject:date:message-id:references:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=ETraLbbSJZ/m9qX+Zobk8zOj+cf6TbN5RA3+yEgkI58=; b=cO6QH4Hn5O6KPgErb36vvWy5sgOY8tuC+cE0kfMbpS5jfIjh9bm8L0td B1GG8pxYMGqlMxKeOi5LY9Unc3FEQGH/Tx3Z5WvVioLglU3LQr3R5ZpMW bqI1tjCgHo+Cn61iQ41PwwOz/kecTNVaMuFaIqjC0/EJ12egVyI+7NsKb Y=;
IronPort-PHdr: 9a23:ZP1UsRzgg3UuEgXXCy+N+z0EezQntrPoPwUc9psgjfdUf7+++4j5YRGN/u1j2VnOW4iTq+lJjebbqejBYSQB+t7A+GsHbIQKUhYEjcsMmAl1CcWIBGXwLeXhaGoxG8ERHFI=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0BIAAATadVc/5NdJa1kHAEBAQQBAQcEAQGBUQcBAQsBgT1QA2lVIAQLKAqEB4NHA4RSiixKgg2XJYEugSQDVAkBAQEMAQEYCwoCAQGEQAIXgXQjNAkOAQMBAQQBAQIBBG0cDIVLAQEBAwEBEBERDAEBLAwPAgEIDgoCAiYCAgIlCxUQAgQBEiKDAAGBagMdAQIMohMCgTWIX3GBL4J5AQEFhH8Ygg8DBoELJwGLTheBf4EQKB+CHi4+gmEBAYFhF4JzMoImjV2ZdwkCggmKV4gCG5VpjDGVAwIEAgQFAg4BAQWBTziBV3AVOyoBgkGCDwwXg0yFFIU/coEpjhYBgSABAQ
X-IronPort-AV: E=Sophos;i="5.60,453,1549929600"; d="scan'208";a="546291289"
Received: from rcdn-core-11.cisco.com ([173.37.93.147]) by rcdn-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 10 May 2019 12:08:46 +0000
Received: from XCH-ALN-012.cisco.com (xch-aln-012.cisco.com [173.36.7.22]) by rcdn-core-11.cisco.com (8.15.2/8.15.2) with ESMTPS id x4AC8kOe022516 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Fri, 10 May 2019 12:08:46 GMT
Received: from xhs-rcd-002.cisco.com (173.37.227.247) by XCH-ALN-012.cisco.com (173.36.7.22) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Fri, 10 May 2019 07:08:45 -0500
Received: from xhs-rtp-003.cisco.com (64.101.210.230) by xhs-rcd-002.cisco.com (173.37.227.247) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Fri, 10 May 2019 07:08:45 -0500
Received: from NAM05-DM3-obe.outbound.protection.outlook.com (64.101.32.56) by xhs-rtp-003.cisco.com (64.101.210.230) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Fri, 10 May 2019 08:08:45 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com; s=selector1-cisco-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=ETraLbbSJZ/m9qX+Zobk8zOj+cf6TbN5RA3+yEgkI58=; b=L2hfJcjC9PCMFfxUSdP4M2PUHWULay2Ji/KRyx08+kcjXrCtf9ekApR7j4tLGxvIAsTAMS6Qq2FpZu8IdAX/NdubIOK42qgfDtjaP03PwMRvr3BZqpcH8QXAB9K3KBNDCG3qPhww48oh37M7GMrJ1s8iwMKcRbmfYLgq5zCgghQ=
Received: from SN6PR11MB2845.namprd11.prod.outlook.com (52.135.93.24) by SN6PR11MB3328.namprd11.prod.outlook.com (52.135.111.78) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1856.14; Fri, 10 May 2019 12:08:44 +0000
Received: from SN6PR11MB2845.namprd11.prod.outlook.com ([fe80::5c42:5f15:d194:98f]) by SN6PR11MB2845.namprd11.prod.outlook.com ([fe80::5c42:5f15:d194:98f%5]) with mapi id 15.20.1878.022; Fri, 10 May 2019 12:08:43 +0000
From: "Acee Lindem (acee)" <acee@cisco.com>
To: Christian Franke <chris@opensourcerouting.org>, "olivier.dugeon@orange.com" <olivier.dugeon@orange.com>, SPRING <spring@ietf.org>, LSR <lsr@ietf.org>
Thread-Topic: [Lsr] Adjacency SID and Passive Interface
Thread-Index: AQHVBwZAffHqPG+5Z0mPmlAuYnTM+6ZkCeiA///3NQA=
Date: Fri, 10 May 2019 12:08:43 +0000
Message-ID: <55B16264-3C65-4D4A-B9E1-5BA406FE64FA@cisco.com>
References: <13318_1557475082_5CD52F0A_13318_76_1_e581409b-8272-9b7b-df11-941f4325413d@orange.com> <e78e6735-059c-a563-d657-244696b904ff@opensourcerouting.org>
In-Reply-To: <e78e6735-059c-a563-d657-244696b904ff@opensourcerouting.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=acee@cisco.com;
x-originating-ip: [173.38.117.68]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 14758689-cf1e-442d-1c20-08d6d5403f86
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600141)(711020)(4605104)(2017052603328)(7193020); SRVR:SN6PR11MB3328;
x-ms-traffictypediagnostic: SN6PR11MB3328:
x-ms-exchange-purlcount: 1
x-microsoft-antispam-prvs: <SN6PR11MB33282A5E7A088542E7E2ECCFC20C0@SN6PR11MB3328.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-forefront-prvs: 0033AAD26D
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(136003)(396003)(366004)(39860400002)(346002)(376002)(199004)(189003)(102836004)(2906002)(66066001)(68736007)(6506007)(36756003)(53546011)(76176011)(53936002)(6246003)(5660300002)(229853002)(26005)(76116006)(91956017)(6486002)(64756008)(66556008)(66446008)(66476007)(73956011)(99286004)(6512007)(6306002)(66946007)(2501003)(486006)(86362001)(33656002)(186003)(25786009)(14454004)(7736002)(110136005)(6436002)(256004)(14444005)(478600001)(966005)(81166006)(446003)(82746002)(8936002)(2616005)(476003)(305945005)(71190400001)(71200400001)(11346002)(8676002)(3846002)(6116002)(83716004)(81156014)(316002); DIR:OUT; SFP:1101; SCL:1; SRVR:SN6PR11MB3328; H:SN6PR11MB2845.namprd11.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1;
received-spf: None (protection.outlook.com: cisco.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: gDXyEUOV0MfStAIpqEw+cJEUf2jXx9vaARbSVCSa6gsYPdeZQv1ePRStrDi9kHjuxQw5I4Xh+lq/xwktZ62dDWxaKvxvnptk83+9n6zrRKpwoSLXQ0dtoIINT2YJ/iwcYGsVpHUu/QP4RsYTEiKIdHKasNJ9ky44y4ZJEDqsjW5brXw9Djqd71wNEpUbobsW7zvLSHrU8+BJ4bJfhvEgugK86AmfUhjj8P9rLZANnu0b7qopQaqfpGVgX7B99oViTstzx5u7pqZ/6FkAgKND3CWPuja8NV86DHRMlJ47kHBb5HeaBAA7mNcdIEazefm/7LYqjPYlTOnVNNJv4RLdn7xJUphltqpAUFeL1yPkSuDtP5XBACNfyX6EubEsHnW7HhMe+FYEI1pCgrNavJgdJ3X94yaxPa5VenYrXX9jJiA=
Content-Type: text/plain; charset="utf-8"
Content-ID: <A8827AC556B0E5428F0123F66AB12251@namprd11.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 14758689-cf1e-442d-1c20-08d6d5403f86
X-MS-Exchange-CrossTenant-originalarrivaltime: 10 May 2019 12:08:43.8479 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5ae1af62-9505-4097-a69a-c1553ef7840e
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-Transport-CrossTenantHeadersStamped: SN6PR11MB3328
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.36.7.22, xch-aln-012.cisco.com
X-Outbound-Node: rcdn-core-11.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/j7wEyJE-p3qK6tvLIoBQvDQT7eA>
Subject: Re: [spring] [Lsr] Adjacency SID and Passive Interface
X-BeenThere: spring@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Source Packet Routing in NetworkinG \(SPRING\)" <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: Fri, 10 May 2019 12:08:50 -0000

Hi Chris, Olivier, 

On 5/10/19, 4:41 AM, "Lsr on behalf of Christian Franke" <lsr-bounces@ietf.org on behalf of chris@opensourcerouting.org> wrote:

    On 5/10/19 9:58 AM, olivier.dugeon@orange.com wrote:
    > In the current state of Segment Routing drafts, do you think it is possible to advertise
    > Adjacency SID on such passive or inter-domain interfaces or do we need to specify this behaviour
    > in a new draft ?
    > 
    > For me I don't see anything in the drafts that prohibits this kind of advertisement, but perhaps I'm wrong.
    
    My understanding is that the SID is specific to an adjacency and
    advertised in IS-IS in either TLV 22, 222, 23, 223.
    
    As adjacencies will not be formed on a passive interface, an adjacency
    SID should not be advertised for the passive interface.

I agree with Chris. We shouldn't reuse the existing Adj-SID when there will never be an adjacency and the current semantics require this. If we need advertisement of SIDs for passive interfaces, it would definitely be a new draft that clearly articulates the use case and designates a new type of SID that has different semantics. Also note that while passive interfaces are very useful in order to include a stub network in the topologies, they are not part of the OSPF specifications. I haven't done an exhaustive search on IS-IS. 

Thanks,
Acee

    
    I might also be wrong here, though.
    
    All Best,
    Chris
    
    _______________________________________________
    Lsr mailing list
    Lsr@ietf.org
    https://www.ietf.org/mailman/listinfo/lsr

v2.23.0 | Report a Bug | By Email