Re: [spring] SRv6 Network Programming and Link Local Source Addresses

"Darren Dukes (ddukes)" <ddukes@cisco.com> Fri, 06 December 2019 15:53 UTC

Return-Path: <ddukes@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 E39E6120807 for <spring@ietfa.amsl.com>; Fri, 6 Dec 2019 07:53:31 -0800 (PST)
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=hxZHv8Wl; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=arc//czb
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 h-Aj8SMhsyzF for <spring@ietfa.amsl.com>; Fri, 6 Dec 2019 07:53:29 -0800 (PST)
Received: from alln-iport-6.cisco.com (alln-iport-6.cisco.com [173.37.142.93]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 72A7A120019 for <spring@ietf.org>; Fri, 6 Dec 2019 07:53:28 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=7866; q=dns/txt; s=iport; t=1575647609; x=1576857209; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=hhtF1Mpd/HMX5VRdJqAP8RPhJzu2PQP1y2oaKW/3Gb0=; b=hxZHv8WlgrxEfgmO+NTfvll2GPhys9qzXCAWrywMiRYW8IXvYBP2JgYL +WBAmZepVofeHAgG+AMQ83m3b48NZu6pSvmZs6Exhc2nied3TzKysc54a FrPwoLcu8MbIX5j46m5DAN+isbQWoE0phsJWHYXWwHMagQCnAxQrLeGqW k=;
IronPort-PHdr: 9a23:HcfrlRw/GzfDqnPXCy+N+z0EezQntrPoPwUc9psgjfdUf7+++4j5YR2N/u1j2VnOW4iTq+lJjebbqejBYSQB+t7A1RJKa5lQT1kAgMQSkRYnBZuJBVD4IeXCZC0hF8MEX1hgrDm2
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0BbAQABeepd/4YNJK1kHAEBAQEBBwEBEQEEBAEBgW0EAQELAYFKUAVsWCAECyoKhCGDRgOKfYJfiVuOKYJSA1QJAQEBDAEBGAsKAgEBg3tFAheBfiQ3Bg4CAw0BAQQBAQECAQUEbYU3DIVSAQEBAQIBAQEQEREMAQEsCwEEBwQCAQgRAQMBAQECAiYCAgIfBgsVAgYIAgQOBSKDAAGCRgMOIAECDKIuAoE4iGB1gTKCfgEBBYUTDQuCFwMGgQ4oAYwWGoFBP4ESJiCCHi4+ghtJAQECgWEXgnkygiyNNIJtnWtCCoIukT+EGxuCQYduj3eQD4kSj0wCBAIEBQIOAQEFgWgjgVhwFTsqAYJBUBEUjGYMF4NQhRSFP3QBgSePMAGBDwEB
X-IronPort-AV: E=Sophos;i="5.69,285,1571702400"; d="scan'208";a="396564686"
Received: from alln-core-12.cisco.com ([173.36.13.134]) by alln-iport-6.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 06 Dec 2019 15:53:27 +0000
Received: from XCH-RCD-014.cisco.com (xch-rcd-014.cisco.com [173.37.102.24]) by alln-core-12.cisco.com (8.15.2/8.15.2) with ESMTPS id xB6FrRrr015827 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Fri, 6 Dec 2019 15:53:27 GMT
Received: from xhs-aln-002.cisco.com (173.37.135.119) by XCH-RCD-014.cisco.com (173.37.102.24) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Fri, 6 Dec 2019 09:53:27 -0600
Received: from xhs-aln-003.cisco.com (173.37.135.120) by xhs-aln-002.cisco.com (173.37.135.119) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Fri, 6 Dec 2019 09:53:26 -0600
Received: from NAM12-BN8-obe.outbound.protection.outlook.com (173.37.151.57) by xhs-aln-003.cisco.com (173.37.135.120) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Fri, 6 Dec 2019 09:53:26 -0600
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=dP7edl2TqJGBY2xPSYwv2tGJzorEHWljkL76+QXL2D9i+WucgapK3P33LO49Hu1N0DIccI8ZbD3CPyXoiLuY24jy2JfIhrR4XpYcNXlHWoHRbGIHyjsOz4RMMGEl218BIHdHUdsx50eD5H+WM8HeoXNFpNjPs5fCcMtpoFIWA8YDZBHlUOJqxReDCkRCEdbUAkprIuRfD/kbN6qI5bQNW34RamN2aHfEx0nnj7VXmAKUWVq4cr3zt6t01/ASjekl19l2Bgt153Pr147mTr4v5z1qOfHrYSjJtbvqefTgckhmfIuHX4Fzz+g/UQeRzfKmb4M9oxw1vuNBl5pZ/Gt5Wg==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=hhtF1Mpd/HMX5VRdJqAP8RPhJzu2PQP1y2oaKW/3Gb0=; b=M5j9MF0WicPCP0KpP98xL9JZDkRiAWVaSTtaCr1R5ROu0YgEm9C5+VM7s5AxLuqyQ90qe0gY/Q2xNYWwsxCP7uesBXTfP0ZbcjwzgkkuDWl/lDBfQ6MKM3f4OBG1gvbU7e9O4jxlLiPxBIVv757bP4xkElV6qTSntfI5PmzTumaztMZkAs6Fi1h2rzulKn9ENHVoT2bNvM/FCESwQm+mP5Sb2hvPQZLhb83fS8bDiYMjnF9rlCno1R4TSPMnueu1NuRVMSXsK9EO1neYHCAMqZ3YNLTDJMgdCjh0mG+JFMAkPTkenrQ9NKy8F9pJaCDBBWOXEB/qoyGTWKNy9tk6+g==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=cisco.com; dmarc=pass action=none header.from=cisco.com; dkim=pass header.d=cisco.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com; s=selector2-cisco-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=hhtF1Mpd/HMX5VRdJqAP8RPhJzu2PQP1y2oaKW/3Gb0=; b=arc//czbJD8ecjBkt4qUpNLMs6+aCrM6BI2VZGhOt6w7vUx9UZqu+N5s926b8+dahB6y4pEwGtVlcKWr2mFfAA0y4C0Qu2rGZ3bt9vCa/bPkNnCk0MPTL+10g3KPF/LwhOZXv0729vbndVvsqHj7Hj7z4igAG4dPPXQ5MwU5IuA=
Received: from BN7PR11MB2594.namprd11.prod.outlook.com (52.135.246.159) by BN7PR11MB2609.namprd11.prod.outlook.com (52.135.244.154) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2516.14; Fri, 6 Dec 2019 15:53:25 +0000
Received: from BN7PR11MB2594.namprd11.prod.outlook.com ([fe80::c72:fa12:757e:cca3]) by BN7PR11MB2594.namprd11.prod.outlook.com ([fe80::c72:fa12:757e:cca3%5]) with mapi id 15.20.2516.014; Fri, 6 Dec 2019 15:53:25 +0000
From: "Darren Dukes (ddukes)" <ddukes@cisco.com>
To: Ron Bonica <rbonica=40juniper.net@dmarc.ietf.org>
CC: Bob Hinden <bob.hinden@gmail.com>, SPRING WG <spring@ietf.org>, Mark Smith <markzzzsmith@gmail.com>
Thread-Topic: [spring] SRv6 Network Programming and Link Local Source Addresses
Thread-Index: AdWnvRd0lqtmH80YQu+C6Oz5BkM5rgA0iXcAAAHtYYAAAH2owAAAaB+AACLhNsAAAGgsgAAAEqowAMlT84A=
Date: Fri, 06 Dec 2019 15:53:25 +0000
Message-ID: <DDDAFD08-71A1-462E-8C9A-12EDC357B05A@cisco.com>
References: <BN7PR05MB5699A179E7206F3899564234AE410@BN7PR05MB5699.namprd05.prod.outlook.com> <F42D9CF3-DB62-4402-86B6-B48843959A84@gmail.com> <CAO42Z2zv9D7cncX2EfS=Amkbx9cbqNrRytZPdj5YP+h4DsSMGg@mail.gmail.com> <BN7PR05MB5699616A8A4F8DFD876C8352AE400@BN7PR05MB5699.namprd05.prod.outlook.com> <CBB0837B-C743-46A4-86C1-28C96A336E06@gmail.com> <BN7PR05MB5699F8930082179B3B1A28B3AE430@BN7PR05MB5699.namprd05.prod.outlook.com> <1E03C1DB-980A-4BFE-9DCD-56C26BDC8B77@gmail.com> <BN7PR05MB5699E56B4195DBD06F479FB9AE430@BN7PR05MB5699.namprd05.prod.outlook.com>
In-Reply-To: <BN7PR05MB5699E56B4195DBD06F479FB9AE430@BN7PR05MB5699.namprd05.prod.outlook.com>
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=ddukes@cisco.com;
x-originating-ip: [161.44.213.3]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 0aa96a5a-332f-4b50-38bf-08d77a646ded
x-ms-traffictypediagnostic: BN7PR11MB2609:
x-microsoft-antispam-prvs: <BN7PR11MB2609886C50F5CC9C03C31F09C85F0@BN7PR11MB2609.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-forefront-prvs: 0243E5FD68
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(376002)(136003)(366004)(346002)(396003)(39860400002)(199004)(51444003)(189003)(13464003)(66946007)(66556008)(66476007)(76116006)(5660300002)(33656002)(64756008)(66446008)(6512007)(8936002)(81156014)(966005)(71200400001)(2906002)(305945005)(86362001)(81166006)(26005)(229853002)(6486002)(8676002)(54906003)(76176011)(2616005)(99286004)(4326008)(316002)(186003)(71190400001)(102836004)(36756003)(6506007)(53546011)(478600001); DIR:OUT; SFP:1101; SCL:1; SRVR:BN7PR11MB2609; H:BN7PR11MB2594.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: BCL:0;
x-microsoft-antispam-message-info: QVvoPU/fQ2rk5xAHdhm9D3WkEDUoc9kjg8Bhkiqayv6GMWZoMdJqn0xxsm52JN2N8NEdlCWEYvmUxlhQQaRt4O6vUVFrngHZSXZIU17O8Sm7CzdTD0dvqoU/bJtyCxJRQIMv/NJttjPXmVgX28cGqI7HigIzAsx8FwoqKgJGK1TnUjEycfXLSYr3y9AZ9mCDt75CR4yC/hRMia1Zf0C6J6f+13/BVrxWUd+qMHizR9PMte9W8aWci7BksiB5nbOBXZrLNSDx/BELMECR3wEYUe71WKE8Qb0gh/q/h4Hca5u0I2QnZwiD37W6jV+0ZabmK50sB/9gcOx/SpUr4zAn9Sh9tocH/l1KEz60XgHqmn3QvKMV0DXdmDZU5oT50c8i+2xT+Spye6cxzsxR3AuwgU+PVfWuBS6yU52gbqmfTyQAwpZzMQF+zPsH0UsGrzD7E7+JpmocYVU2koKZeU0cg92JHZXxac1Gkzgnvj5VMKsvhdzPkFDhU2E0LW1J0pIC5ZDF+FRdIzGKD5/CC9n5Awayq4SYluwt8ohdfgoQC15NYiFpyliYeq4poaMdonhf
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="utf-8"
Content-ID: <36F1C772413A7C498E344BC1DADE985F@namprd11.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 0aa96a5a-332f-4b50-38bf-08d77a646ded
X-MS-Exchange-CrossTenant-originalarrivaltime: 06 Dec 2019 15:53:25.4426 (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-CrossTenant-userprincipalname: F8lcy5/LC0PejcAmxAATKYn/PivYl3O+zoMBtlQFASKzFFZNzosPot5HtDyyTgvlToZeq9ZlM5y588rVYGKhUQ==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN7PR11MB2609
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.37.102.24, xch-rcd-014.cisco.com
X-Outbound-Node: alln-core-12.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/d6CdcLDwR20lSOmC-qpHGU0REvo>
Subject: Re: [spring] SRv6 Network Programming and Link Local Source Addresses
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, 06 Dec 2019 15:53:32 -0000

Hi Ron, I agree with Bob here.

Section 4.2 pseudocode simply says an implementation would use a predetermined egress adjacency instead of performing a FIB lookup to find one.  
It specifies the SID processing, not the entire IPv6 data path.

It has no text that would indicate RFC4291 text on link-local addresses and routers would not apply.

As a side note, every routing header currently defined (even those now deprecated) do not re-state the RFC4291 text.

Thanks,
  Darren


> On Dec 2, 2019, at 10:58 AM, Ron Bonica <rbonica=40juniper.net@dmarc.ietf.org> wrote:
> 
> Bob,
> 
> Before we debate presentation too much, we should let Pablo answer the original question. Will the packet be dropped or forwarded?
> 
> If the packet will be dropped, how is the reader of Section 4.2 to know this? Normally, pseudocode is taken literally, and the pseudocode in Section 4.2 suggests that the packet will be forwarded.
> 
> One way to wiggle out of this problem is to include a sentence at the beginning of Section 4 saying, "When the following pseudocode contradicts RFC 4291 or 8200, RFCs 4291 and 8200 take precedence.
> 
>                                                                                                              Ron
> 
> 
> 
> 
> Juniper Business Use Only
> 
> -----Original Message-----
> From: Bob Hinden <bob.hinden@gmail.com> 
> Sent: Monday, December 2, 2019 10:47 AM
> To: Ron Bonica <rbonica@juniper.net>
> Cc: Bob Hinden <bob.hinden@gmail.com>; Mark Smith <markzzzsmith@gmail.com>; SPRING WG <spring@ietf.org>
> Subject: Re: [spring] SRv6 Network Programming and Link Local Source Addresses
> 
> Ron,
> 
>> On Dec 2, 2019, at 7:36 AM, Ron Bonica <rbonica@juniper.net> wrote:
>> 
>> Bob,
>> 
>> Take a look at Section 4.2. The pseudocode is pretty specific.
> 
> Please explain.  I don’t see that.
> 
> Thanks,
> Bob
> 
> 
>> 
>>                                           Ron
>> 
>> 
>> 
>> Juniper Business Use Only
>> 
>> -----Original Message-----
>> From: Bob Hinden <bob.hinden@gmail.com>
>> Sent: Sunday, December 1, 2019 5:56 PM
>> To: Ron Bonica <rbonica@juniper.net>
>> Cc: Bob Hinden <bob.hinden@gmail.com>; Mark Smith <markzzzsmith@gmail.com>; SPRING WG <spring@ietf.org>
>> Subject: Re: [spring] SRv6 Network Programming and Link Local Source Addresses
>> 
>> Ron,
>> 
>>> On Dec 1, 2019, at 2:47 PM, Ron Bonica <rbonica@juniper.net> wrote:
>>> 
>>> Mark, Bob,
>>> 
>>> Yes, I agree that routers should not forward packets with link local source addresses.
>> 
>> or Destination addresses.
>> 
>>> 
>>> Pablo,
>>> 
>>> Maybe we should update section 4.2 of the network programming draft to reflect this?
>> 
>> I was thinking that unless network programming has text that might cause one to think it overrides the defined behavior from rfc4291 for link-local addresses, I am not sure it has to be mentioned.
>> 
>> Bob
>> 
>> 
>>> 
>>>                                                                Ron
>>> 
>>> 
>>> From: Mark Smith <markzzzsmith@gmail.com>
>>> Sent: Sunday, December 1, 2019 5:31 PM
>>> To: Bob Hinden <bob.hinden@gmail.com>
>>> Cc: Ron Bonica <rbonica@juniper.net>; SPRING WG <spring@ietf.org>
>>> Subject: Re: [spring] SRv6 Network Programming and Link Local Source Addresses
>>> 
>>> 
>>> 
>>> On Mon, 2 Dec 2019, 08:35 Bob Hinden, <bob.hinden@gmail.com> wrote:
>>> Ron,
>>> 
>>>> On Nov 30, 2019, at 12:36 PM, Ron Bonica <rbonica=40juniper.net@dmarc.ietf.org> wrote:
>>>> 
>>>> Pablo,
>>>> 
>>>> 
>>>> 
>>>> Consider the packet (SA,DA) (S3, S2, S1; SL) where:
>>>> 
>>>> 
>>>> 
>>>>     • SA is link-local (fe80)
>>>>     • DA, S3, S2, and S1 are all END.X
>>>> 
>>>> 
>>>> Section 4.2 suggests that this packet will be delivered over multiple hops to its destination, regardless of its link-local source address.
>>> 
>>> I would think that RFC2460 Section 2.5.6. "Link-Local IPv6 Unicast Addresses” covers this:
>>> 
>>>  Link-Local addresses are for use on a single link.  Link-Local
>>>  addresses have the following format:
>>> 
>>>  |   10     |
>>>  |  bits    |         54 bits         |          64 bits           |
>>>  +----------+-------------------------+----------------------------+
>>>  |1111111010|           0             |       interface ID         |
>>>  +----------+-------------------------+----------------------------+
>>> 
>>>  Link-Local addresses are designed to be used for addressing on a
>>>  single link for purposes such as automatic address configuration,
>>>  neighbor discovery, or when no routers are present.
>>> 
>>>  Routers must not forward any packets with Link-Local source or
>>>  destination addresses to other links.
>>> 
>>> I think that's RFC4291.
>>> 
>>> RFC4007, "IPv6 Scoped Address Architecture" does too, more generally and probably more formally, in particular section 9, "Forwarding".
>>> 
>>> Regards,
>>> Mark.
>>> 
>>> 
>>> 
>>> Bob
>>> 
>>> 
>>>> 
>>>> 
>>>> 
>>>> Is this the case?
>>>> 
>>>> 
>>>> 
>>>>                                                            Ron
>>>> 
>>>> 
>>>> 
>>>> 
>>>> 
>>>> 
>>>> 
>>>> 
>>>> 
>>>> 
>>>> Juniper Business Use Only
>>>> _______________________________________________
>>>> spring mailing list
>>>> spring@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/spring
>>> 
>>> _______________________________________________
>>> spring mailing list
>>> spring@ietf.org
>>> https://www.ietf.org/mailman/listinfo/spring
>>> 
>>> Juniper Business Use Only
> _______________________________________________
> spring mailing list
> spring@ietf.org
> https://www.ietf.org/mailman/listinfo/spring