[spring] One question on E-flag of ABR/ASBR in OSPF SR extension
Chao Fu <chao.fu@ericsson.com> Thu, 18 May 2017 07:50 UTC
Return-Path: <chao.fu@ericsson.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 ED6E812EC00 for <spring@ietfa.amsl.com>; Thu, 18 May 2017 00:50:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.219
X-Spam-Level:
X-Spam-Status: No, score=-4.219 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.onmicrosoft.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 zGz7UHbqBvDP for <spring@ietfa.amsl.com>; Thu, 18 May 2017 00:50:29 -0700 (PDT)
Received: from sesbmg23.ericsson.net (sesbmg23.ericsson.net [193.180.251.37]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4D07712EB5E for <spring@ietf.org>; Thu, 18 May 2017 00:44:53 -0700 (PDT)
X-AuditID: c1b4fb25-35fff700000055fe-ca-591d50f16367
Received: from ESESSHC001.ericsson.se (Unknown_Domain [153.88.183.21]) by sesbmg23.ericsson.net (Symantec Mail Security) with SMTP id 2A.13.22014.1F05D195; Thu, 18 May 2017 09:44:51 +0200 (CEST)
Received: from EUR01-VE1-obe.outbound.protection.outlook.com (153.88.183.145) by oa.msg.ericsson.com (153.88.183.21) with Microsoft SMTP Server (TLS) id 14.3.339.0; Thu, 18 May 2017 09:44:48 +0200
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ericsson.onmicrosoft.com; s=selector1-ericsson-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=R1OQ4yFCtvwO4rgQD62HMgWmXyBrrKZThpZg4m5up4k=; b=ZBKGJe0SW+ABF8bX9YbB6mQ29afCR3XcO690Bomv40tlV3XrfojIZo8p0DaJgHjDOuyCEbpaxYtpeHJ28O/7hXSqkDle0S9du1kkKVCRpAR+G6rvU/5x1YcqA8jP7MAl3v4uOeNzaQc0VrRwQLo40wKRgEXCWNWxf/Q5g590Sv4=
Received: from VI1PR07MB1071.eurprd07.prod.outlook.com (10.163.168.19) by VI1PR07MB1070.eurprd07.prod.outlook.com (10.163.168.18) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1101.8; Thu, 18 May 2017 07:44:47 +0000
Received: from VI1PR07MB1071.eurprd07.prod.outlook.com ([10.163.168.19]) by VI1PR07MB1071.eurprd07.prod.outlook.com ([10.163.168.19]) with mapi id 15.01.1101.011; Thu, 18 May 2017 07:44:47 +0000
From: Chao Fu <chao.fu@ericsson.com>
To: "spring@ietf.org" <spring@ietf.org>
Thread-Topic: One question on E-flag of ABR/ASBR in OSPF SR extension
Thread-Index: AdLPqkMsp7Qw/GF8TGW2zt4btSR+jQ==
Date: Thu, 18 May 2017 07:44:47 +0000
Message-ID: <VI1PR07MB1071503225586B964C69096191E40@VI1PR07MB1071.eurprd07.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=ericsson.com;
x-originating-ip: [106.38.5.68]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; VI1PR07MB1070; 7:cOpQklFfIN7iU6z9PBSTDgeFsGNNjTOg6BxBGIiFZ4WGpTeTnoFoYauYsciHu0xdlFmUmnAluSJBZOooZQmzhoZuLrPLOO9HIBOJGyJaKntIRwIkeViaEn1awEA7uXstwMhhMQWvM8bSdGF6mztKikfdRpQUQzk7p+ZU1koj17yTWR0I6RyydxzcN3ZGG5oVltZU6VhK1aKhIECWA4XbId6joQNdg4d0HvrqprhHYYRvdiFRziX9HOs4l1dwrrQaPwJDI9U+1wxvI1HvvtqQecIrwijGLFC/bpshqNlCgF3/YIr76Njn3VioHHXlrcmCSCWbJiTdHccDpidPyRSZ3w==
x-ms-traffictypediagnostic: VI1PR07MB1070:
x-ms-office365-filtering-correlation-id: d07971a8-cc3b-4e87-cfc0-08d49dc1c1f8
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(2017030254075)(201703131423075)(201703031133081); SRVR:VI1PR07MB1070;
x-microsoft-antispam-prvs: <VI1PR07MB1070097CD64126DD8D87922691E40@VI1PR07MB1070.eurprd07.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(21748063052155);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(100000700036)(100105000095)(100000701036)(100105300095)(100000702036)(100105100095)(6040450)(601004)(2401047)(5005006)(8121501046)(100000703036)(100105400095)(3002001)(10201501046)(93006095)(93001095)(6041248)(20161123560025)(20161123555025)(20161123558100)(201703131423075)(201702281528075)(201703061421075)(201703061406153)(20161123564025)(20161123562025)(6072148)(100000704036)(100105200095)(100000705036)(100105500095); SRVR:VI1PR07MB1070; BCL:0; PCL:0; RULEID:(100000800036)(100110000095)(100000801036)(100110300095)(100000802036)(100110100095)(100000803036)(100110400095)(100000804036)(100110200095)(100000805036)(100110500095); SRVR:VI1PR07MB1070;
x-forefront-prvs: 0311124FA9
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(39410400002)(39400400002)(39860400002)(39840400002)(39850400002)(39450400003)(6306002)(7736002)(54896002)(5660300001)(74316002)(478600001)(7906003)(6116002)(7696004)(55016002)(99286003)(38730400002)(966005)(54356999)(110136004)(2351001)(6916009)(33656002)(9326002)(6436002)(6506006)(3846002)(19609705001)(790700001)(2900100001)(25786009)(606005)(102836003)(77096006)(86362001)(3280700002)(2906002)(8676002)(1730700003)(81166006)(5640700003)(5630700001)(8936002)(122556002)(53936002)(189998001)(50986999)(66066001)(3660700001)(9686003)(236005)(2501003)(5890100001); DIR:OUT; SFP:1101; SCL:1; SRVR:VI1PR07MB1070; H:VI1PR07MB1071.eurprd07.prod.outlook.com; FPR:; SPF:None; MLV:ovrnspm; PTR:InfoNoRecords; LANG:en;
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_VI1PR07MB1071503225586B964C69096191E40VI1PR07MB1071eurp_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-originalarrivaltime: 18 May 2017 07:44:47.2048 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 92e84ceb-fbfd-47ab-be52-080c6b87953f
X-MS-Exchange-Transport-CrossTenantHeadersStamped: VI1PR07MB1070
X-OriginatorOrg: ericsson.com
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprHKsWRmVeSWpSXmKPExsUyM2K7qO7nANlIg82TtS2OX/jN6MDosWTJ T6YAxigum5TUnMyy1CJ9uwSujIYZMxkLDmtVTH/p2cB4S6WLkYNDQsBE4stl9y5GLg4hgSOM EvO+HWCHcE4wSuxc+4UNxGER6GWWuDT7H1RmGpPEwjNvGCGcY4wSe24sYAOZxSagIrFwoSGI KSKgLvHsaHgXIyeHsICDxL8bv5hAbBEBV4nWzz+gbD2Jfx3rwWwWAVWJrS/vsoHYvAIxErNO f2UBsRkFxCS+n1oDVsMsIC5x68l8MFtCQEBiyZ7zzBC2qMTLx/9YQc5hFOhmlPgw7xpUkbzE qVsH2SFsWYlL87vBbpYQ6GGWOPBhPStEQkuiZc9vqEm+EpP7b0M110ms2fEcqjlbonHXLEYI 20qiY+JxVohBh1glJvVPg0rISKyeuQ4q8ZFVYt3Zr6wQ/0tJ3L3SyQhhy0i8uLOXFeKffInJ n6+wTGBUn4XkvVlIUrPAwSEocXLmExaIuI7Egt2f2CBsbYllC18zw9hnDjxmQhZfwMi+ilG0 OLU4KTfdyFgvtSgzubg4P08vL7VkEyMw1Rzc8lt1B+PlN46HGAU4GJV4eHPMZSOFWBPLiitz DzFKcDArifBOtwAK8aYkVlalFuXHF5XmpBYfYpTmYFES53XcdyFCSCA9sSQ1OzW1ILUIJsvE wSnVwOhwfbnTj9qmG/dE7VWt4hp/Tzjhlby+8+3R9T/39r51yp24Symn/N7ifNZ5iS7Wr00l 62oTn/S/vHr6cFfbPIP8Sb6OzTcZNh9P4uA1NnFe7+f0KTFXfurN6Tl85cH6SjeF7+x7zV7w 9Yfx14iaU/Z7HsR43TKzvi+nJ3pZfkfeqQfTw9wXeSixFGckGmoxFxUnAgC87ATrMQMAAA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/-QFjl8tg9MEIW1TOfyOorwmDGDI>
Subject: [spring] One question on E-flag of ABR/ASBR in OSPF SR extension
X-BeenThere: spring@ietf.org
X-Mailman-Version: 2.1.22
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: Thu, 18 May 2017 07:50:33 -0000
Hi, Should we clarify how to set E-flag for ABR/ASBR in OSPF SR extension? In https://www.ietf.org/id/draft-ietf-ospf-segment-routing-extensions-14.txt, the draft describes how to set NP-flag on ABR and ASBR (Section 5 [Page 14]): The NP-Flag (No-PHP) MUST be set for Prefix-SIDs allocated to inter- area prefixes that are originated by the ABR based on intra-area or inter-area reachability between areas. When the inter-area prefix is generated based on a prefix which is directly attached to the ABR, the NP-Flag SHOULD NOT be set. The NP-Flag (No-PHP) MUST be be set for Prefix-SIDs allocated to redistributed prefixes, unless the redistributed prefix is directly attached to the ASBR, in which case the NP-flag SHOULD NOT be set. However, the E-flag (Explicit-Null Flag) is not described. Should we clarify it also? I think E-flag SHOULD NOT be set if the prefix is not directly attached to the ABR or ASBR, and if necessary, it SHOULD be set if the prefix is directly attached to the ABR or ASBR. Regards, Chao Fu