IETF Logo Mail Archive

Re: [Sidrops] WG Adoption call for draft-borchert-sidrops-bgpsec-validation-signaling-01 (9/16-9/30)

"Borchert, Oliver (Fed)" <oliver.borchert@nist.gov> Wed, 25 September 2019 15:01 UTC

Return-Path: <oliver.borchert@nist.gov>
X-Original-To: sidrops@ietfa.amsl.com
Delivered-To: sidrops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DBC0D1200C4 for <sidrops@ietfa.amsl.com>; Wed, 25 Sep 2019 08:01:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.002
X-Spam-Level:
X-Spam-Status: No, score=-2.002 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nist.gov
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 twAeg_l8uN-O for <sidrops@ietfa.amsl.com>; Wed, 25 Sep 2019 08:01:01 -0700 (PDT)
Received: from GCC01-CY1-obe.outbound.protection.outlook.com (mail-eopbgr830125.outbound.protection.outlook.com [40.107.83.125]) (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 AB9FA120026 for <sidrops@ietf.org>; Wed, 25 Sep 2019 08:01:01 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=KlnOPM5CxWrKkKpRx39zg43fnoDGorVPQXJxRQ0h91PMd/HRXGxBRcyfOz09xnxEKcMXAtfjK4hxn2k84FSDmYzHdZIMHxg8kegT9u+F3aaZBmWj7C+cIHa6yGMnEvMzhceT4eclGZzT1YHIBT5aUyrx5lJNQ9Oeze8AmLdceIE0Y3bOmmKxkJl8tHGjxL4wFOnJILd5N5wz+8g4hmIBThw4WDQVypKTPVpU7DfmWHbo2nTmSFt7+NLdWI9Z42yK5DiGrqtI8xkW0tES7kT9UFuId6htL/tl0ZEPWjUdLd8l9rxpB4XviIMM970topLmNSMgshGbrHbUorqtPEATtA==
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=bD+UDEaOxKZED64CPu8xL8fAD+tpBnFppKxGVO1Gp9A=; b=hGwrLQgLkVoaa9SwzRswbhRlFIP15dLEzpzuMGCO1zWPBrv0cBQOpqeLl/9l4wrDJQxeuioOcvxOuH+Aqm6BT6sWaGpSmhEDoPAR1G9f50g56c49PWNgfJyjgKdRDVcx9n12ckF4xoIxco0Akxq4cq+1cv1BKSJjjd4YsE5IArzO2RQUI7rAtKA0T8TPfKWx5zR2c9XnZP84fUH8p+kSKbgy+DCljjoTnIRw+dAiIOdYtRfuthwHMgqwRBL414YpBFNeUwod3eS8MHTEQM3DFfRoHzeVFDIn+ux3YCxsxhw9oLW+J4WFEP+e/ONmDyMgubter6t+82V4Jq9/tULSlA==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=nist.gov; dmarc=pass action=none header.from=nist.gov; dkim=pass header.d=nist.gov; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nist.gov; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=bD+UDEaOxKZED64CPu8xL8fAD+tpBnFppKxGVO1Gp9A=; b=cMvQ+JrK71guY28wzWWj5tK5N0x5972zf12Bp9iUGNE6tvh5LIM2/aEl8ts24xfMfnFIf4sSVWu0APlW49hUlMpvAzqKyFIM9nVlw28WV4uYBKHaAuF/t8oqj30c5PQ9OqWnTuWRxnzKk4PlBe504TxT7dHQ14R4gHzWJXUwoAA=
Received: from DM6PR09MB3019.namprd09.prod.outlook.com (20.178.2.203) by DM6PR09MB3082.namprd09.prod.outlook.com (20.178.3.22) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2284.26; Wed, 25 Sep 2019 15:01:00 +0000
Received: from DM6PR09MB3019.namprd09.prod.outlook.com ([fe80::14:3d9:2d38:262]) by DM6PR09MB3019.namprd09.prod.outlook.com ([fe80::14:3d9:2d38:262%7]) with mapi id 15.20.2284.023; Wed, 25 Sep 2019 15:01:00 +0000
From: "Borchert, Oliver (Fed)" <oliver.borchert@nist.gov>
To: "Jakob Heitz (jheitz)" <jheitz@cisco.com>, "Montgomery, Douglas (Fed)" <dougm=40nist.gov@dmarc.ietf.org>, Randy Bush <randy@psg.com>, Keyur Patel <keyur@arrcus.com>
CC: "sidrops@ietf.org" <sidrops@ietf.org>, "Borchert, Oliver (Fed)" <oliver.borchert@nist.gov>
Thread-Topic: [Sidrops] WG Adoption call for draft-borchert-sidrops-bgpsec-validation-signaling-01 (9/16-9/30)
Thread-Index: AQHVbMKiBubipeZ/d0GMV+4UPfWKYKcuza8A///bQYCADJgpcIABQZkA
Date: Wed, 25 Sep 2019 15:01:00 +0000
Message-ID: <DM6PR09MB3019425FBE11F93DF9747CD898870@DM6PR09MB3019.namprd09.prod.outlook.com>
References: <0BBFA8C1-A13D-4CC9-A72D-ABAE797F2E4F@arrcus.com> <m28sqouepr.wl-randy@psg.com> <875A2007-9546-4CE3-AD32-15D4E7F7C29E@nist.gov> <BN8PR11MB3746439C06B460A7BD009758C0840@BN8PR11MB3746.namprd11.prod.outlook.com>
In-Reply-To: <BN8PR11MB3746439C06B460A7BD009758C0840@BN8PR11MB3746.namprd11.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=oliver.borchert@nist.gov;
x-originating-ip: [129.6.140.119]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 889b5dfc-94d2-4905-0167-08d741c92d7a
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(5600167)(711020)(4605104)(1401327)(4618075)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(2017052603328)(7193020); SRVR:DM6PR09MB3082;
x-ms-traffictypediagnostic: DM6PR09MB3082:|DM6PR09MB3082:
x-ms-exchange-purlcount: 1
x-ms-exchange-transport-forked: True
x-microsoft-antispam-prvs: <DM6PR09MB3082D5643254D25399FEFB1798870@DM6PR09MB3082.namprd09.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-forefront-prvs: 01713B2841
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(136003)(39850400004)(396003)(376002)(366004)(346002)(13464003)(189003)(199004)(71190400001)(71200400001)(45080400002)(52536014)(25786009)(14454004)(478600001)(966005)(76176011)(7696005)(99286004)(26005)(6506007)(2906002)(66476007)(66556008)(476003)(486006)(446003)(11346002)(64756008)(9686003)(6306002)(6246003)(5660300002)(4326008)(66066001)(107886003)(55016002)(6436002)(86362001)(186003)(76116006)(66946007)(74316002)(8676002)(81156014)(8936002)(316002)(110136005)(7736002)(305945005)(81166006)(6116002)(3846002)(229853002)(54906003)(66446008)(66574012)(53546011)(102836004)(33656002)(256004); DIR:OUT; SFP:1102; SCL:1; SRVR:DM6PR09MB3082; H:DM6PR09MB3019.namprd09.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: nist.gov does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: wZ12ytOY9W4TJ8iiirr66nNyRztHyYB00PCtsZP6b9voLyYy4c73DyO4/J/0mZu6xtAwaAocO3la3PCl11sil3KBtAqesR7bQv0c09aBh/MvP5iaDsaCy/pmCXTqbd+XAcxmJVckj1fCC4TM515LQFlytKCvH46zhpr1ezCbdvCQRuy9ZrAMLkrBlhtGRq/kwaz/goMsA7Ag1vXmmuPBJ+B8cLExldLIaNjxIyjWnU0HA+Ws6sRBHsfFdM4/wam7CjK8GX51owfDhf+rwcTJojv0gyBjqRl+V58JVNgbaL0V9oeMq9drZVRE6prQR1oOLhvTiZWojjeYZ92Tuahc7lBBhaWYIU4xHZzZXedZuVylAHsiHMyOzwmbrf3S7QexPwrHYUMmL8mM8+1Lkh2JDqhuPCoxPHRO4a/fcs56NY93R+hnMrkyv61pydbzj+Dme4LsMgHQ5j/ADn2V5N25rg==
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: nist.gov
X-MS-Exchange-CrossTenant-Network-Message-Id: 889b5dfc-94d2-4905-0167-08d741c92d7a
X-MS-Exchange-CrossTenant-originalarrivaltime: 25 Sep 2019 15:01:00.1068 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 2ab5d82f-d8fa-4797-a93e-054655c61dec
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: kcOcR+sbhJXP1het7D+N0paz6Jx+2zi4z5G593wDbKgf0Oep4FU85uIP1HzJoTqq5SVTBhMeehbRukPiNdVjkg==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM6PR09MB3082
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidrops/I2bOgVA8antMDQklBIpBLdNC9qU>
Subject: Re: [Sidrops] WG Adoption call for draft-borchert-sidrops-bgpsec-validation-signaling-01 (9/16-9/30)
X-BeenThere: sidrops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: A list for the SIDR Operations WG <sidrops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sidrops>, <mailto:sidrops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sidrops/>
List-Post: <mailto:sidrops@ietf.org>
List-Help: <mailto:sidrops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sidrops>, <mailto:sidrops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 25 Sep 2019 15:01:05 -0000

Jakob, 

I agree, adding the BGPsec information into the RFC 8097 communities "reserved" field 
seems definitely be a good solution and I can easily modify the proposed draft to do that.  

Oliver

-----Original Message-----
From: Sidrops <sidrops-bounces@ietf.org> On Behalf Of Jakob Heitz (jheitz)
Sent: Tuesday, September 24, 2019 3:32 PM
To: Montgomery, Douglas (Fed) <dougm=40nist.gov@dmarc.ietf.org>; Randy Bush <randy@psg.com>; Keyur Patel <keyur@arrcus.com>
Cc: sidrops@ietf.org
Subject: Re: [Sidrops] WG Adoption call for draft-borchert-sidrops-bgpsec-validation-signaling-01 (9/16-9/30)

I would be in favor of carving off another byte from the reserved field.
Redefining the validation state to add the new information instead would confuse older receivers that do not understand the new code points.

In addition, I would add another point to the BGPSec validation state: BGPSec attribute not present or in error.

   +-------+------------------------------+
   | Value | Meaning                      |
   +-------+------------------------------+
   |   0   | Lookup result = "Unverified" |
   |   1   | Lookup result = "Valid"      |
   |   2   | Lookup result = "Not valid"  |
   |   3   | Lookup result = "BGPSec attribute not present or in error"
   +-------+------------------------------+

If it were to use a reserved byte of the RFC8097 community, 0 for unverified would work, I think.

Regards,
Jakob.

-----Original Message-----
From: Sidrops <sidrops-bounces@ietf.org> On Behalf Of Montgomery, Douglas (Fed)
Sent: Monday, September 16, 2019 4:02 PM
To: Randy Bush <randy@psg.com>; Keyur Patel <keyur@arrcus.com>
Cc: sidrops@ietf.org
Subject: Re: [Sidrops] WG Adoption call for draft-borchert-sidrops-bgpsec-validation-signaling-01 (9/16-9/30)

Randy,

Are you suggesting keeping the 0x43 0x00 code point, but redefining its validation state byte with additional values and meanings for path validation?

Or carving off another byte from reserved?

Either of those sounds fine and save bits.   

Clearly there would need to be a new spec that that adds the words to do that.

dougm
--
Doug Montgomery, Manager Internet  & Scalable Systems Research @ NIST
 

On 9/16/19, 5:13 PM, "Sidrops on behalf of Randy Bush" <sidrops-bounces@ietf.org on behalf of randy@psg.com> wrote:

    "This document defines a new BGP non-transitive extended community to
    carry the BGPsec path validation state inside an autonomous system."
    
    given the one in RFC 8097, we need a new one because?
    
    randy
    
    _______________________________________________
 

_______________________________________________
Sidrops mailing list
Sidrops@ietf.org
https://gcc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Fsidrops&amp;data=02%7C01%7Coliver.borchert%40nist.gov%7C43f29b9643dc4705595508d74125f6d5%7C2ab5d82fd8fa4797a93e054655c61dec%7C1%7C1%7C637049503640406944&amp;sdata=N1%2ByCkKcQD4zf6sbr9%2B7e5QnwB6wq%2BRIcaHUvYhSLW4%3D&amp;reserved=0
_______________________________________________
Sidrops mailing list
Sidrops@ietf.org
https://gcc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Fsidrops&amp;data=02%7C01%7Coliver.borchert%40nist.gov%7C43f29b9643dc4705595508d74125f6d5%7C2ab5d82fd8fa4797a93e054655c61dec%7C1%7C1%7C637049503640406944&amp;sdata=N1%2ByCkKcQD4zf6sbr9%2B7e5QnwB6wq%2BRIcaHUvYhSLW4%3D&amp;reserved=0

v2.23.0 | Report a Bug | By Email