IETF Logo Mail Archive

Re: [bess] WG adoption and IP poll for draft-snr-bess-pbb-evpn-isid-cmacflush

"Ali Sajassi (sajassi)" <sajassi@cisco.com> Fri, 04 October 2019 06:37 UTC

Return-Path: <sajassi@cisco.com>
X-Original-To: bess@ietfa.amsl.com
Delivered-To: bess@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CDB611200F6; Thu, 3 Oct 2019 23:37:32 -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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-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=EhrwHkzs; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=iW1AHGow
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 apDl6YdsUhYG; Thu, 3 Oct 2019 23:37:30 -0700 (PDT)
Received: from alln-iport-3.cisco.com (alln-iport-3.cisco.com [173.37.142.90]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 49825120018; Thu, 3 Oct 2019 23:37:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=12909; q=dns/txt; s=iport; t=1570171050; x=1571380650; h=from:to:subject:date:message-id:references:in-reply-to: mime-version; bh=YvZbgigxlYHtiaChGGZisMTbQxZMw/UW2fXmZX41k+E=; b=EhrwHkzs1lUkRrEiXXPwP/LUmQFpDN3FZondlGxgV3opVA6ai8Px5vtP i6ioWk1LZigwJ39NlPNKOUMCdtIWVDKL9gCeLK7bz8O5dr4XXHG2X75SN NeByQQ0blQMfCdJPfcxbeXZELpZZpUqTRSUZiwCwaGzq3VXegIP03820N o=;
IronPort-PHdr: 9a23:W18knRFc06AQFidbErhTU51GYnJ96bzpIg4Y7IYmgLtSc6Oluo7vJ1Hb+e4z1A3SRYuO7fVChqKWqK3mVWEaqbe5+HEZON0pNVcejNkO2QkpAcqLE0r+eeXjbSUhB8VqX15+9Hb9Ok9QS47z
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AbAABL55Zd/5BdJa1lGgEBAQEBAgEBAQEMAgEBAQGBVQMBAQEBCwGBGy9QA21WIAQLKgqEGINHA4pITYIPiWeJMIRhgS4UgRADVAkBAQEMAQElCAIBAYRAAheCLiM2Bw4CAwEDAgMBAQQBAQECAQUEbYUtDIVLAQEBBBIRChMBASwMDwIBCA4DAwECKwICAh8RHQgCBAESIoMAAYEdTQMdAQIMomwCgTiIYXWBMoJ9AQEFgUhBgwINC4IXAwaBNAGMDRiBf4ERJx+CTD6CGkcCAwGBKgESATYJDYJgMoImjHOCeIU1l1tBCoIjhwiKCYQHG4I6h06NWYFfjUALYIgggg2PBAIEAgQFAg4BAQWBWQMvKj1xcBU7KgGCQVAQFIFPDBeDUIUUhT90gSmNXYEiAYEiAQE
X-IronPort-AV: E=Sophos;i="5.67,254,1566864000"; d="scan'208,217";a="350315321"
Received: from rcdn-core-8.cisco.com ([173.37.93.144]) by alln-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 04 Oct 2019 06:37:29 +0000
Received: from XCH-RCD-018.cisco.com (xch-rcd-018.cisco.com [173.37.102.28]) by rcdn-core-8.cisco.com (8.15.2/8.15.2) with ESMTPS id x946bSmE000601 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Fri, 4 Oct 2019 06:37:28 GMT
Received: from xhs-rtp-001.cisco.com (64.101.210.228) by XCH-RCD-018.cisco.com (173.37.102.28) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Fri, 4 Oct 2019 01:37:28 -0500
Received: from xhs-rtp-002.cisco.com (64.101.210.229) by xhs-rtp-001.cisco.com (64.101.210.228) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Fri, 4 Oct 2019 02:37:27 -0400
Received: from NAM02-BL2-obe.outbound.protection.outlook.com (64.101.32.56) by xhs-rtp-002.cisco.com (64.101.210.229) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Fri, 4 Oct 2019 02:37:27 -0400
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=Zi5dTtZqhGKwxHXd29+dE5oIPyL3So+Ax8jdmdtTu+and1lohn/0FgXF5uCVkO2p8xktrl9jD4So+XEouCsuBecXVnJaDhTbKdywr/FBJNZtf+mTaci5XqBtq3OWqUXOPCv8CpWjQHKzqg8Cu4aC6wI2KzTUZDY8YaprdXdgh8gjGgZ9uGJEy34TlpQi1rOJSvjO1dSBkYa69m8LZJGSLtKLzpMzs7+/4pDW2AXgdh5dxNLCChfOh1rVeauKq0/RpoxXDU1+Moq9TDWxwl9Yz1cULzO9LxJe75xIfpap36pvSD4+a8sf3baMFJLfKjeNzGrB+V68xbO7IVPJLZeLaQ==
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=YvZbgigxlYHtiaChGGZisMTbQxZMw/UW2fXmZX41k+E=; b=KZO/o4GL5ug2CDhAOj+0KRegkmzmxyNgFebvJL4o/GUhmVODKlqW1PLPOENn++/BplVDj7hZCt2ha5iVMdQfa9bdO+uuhuJ114uyVhcjDgpi86XuqVlx+mkUzhCq8kj3DhdDkjgsEwyfuntMWLScJJnObvUsJVA5W41JhufQWyCh8BQtQ+8GjH5sqjBRrfNoazO/cXG5KVpNSN9JW9ZbNdOB8OIy8v01J4uk6PWePvMxlt0aJQsOcA6PXX5Xby3oYBa2vNhf+4SqJXCRxVgcTWxAQkbNls4GPEq0qx/KdyJ7/VMTZSWEHelymNxiZsibYuLMzYQIsiX1B7FnwArd5g==
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=YvZbgigxlYHtiaChGGZisMTbQxZMw/UW2fXmZX41k+E=; b=iW1AHGow2Mq8GuphbxuKJK9i48ZNvsapVQSYUAdHhaT5tZHSfrAVLaRB18skQ+N9lfU6IMas3swNFeBWQTL5J/rV8tq8eGYaNx/txECYvlAXUGPNrkyLNriBKcmGMD5UtLonTlOWv9COlT71zShD9sUnEQCLPAg8DYpRgjb+hKI=
Received: from DM6PR11MB3708.namprd11.prod.outlook.com (20.178.231.158) by DM6PR11MB3820.namprd11.prod.outlook.com (20.179.17.28) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2305.20; Fri, 4 Oct 2019 06:37:26 +0000
Received: from DM6PR11MB3708.namprd11.prod.outlook.com ([fe80::f844:816:5069:c9bb]) by DM6PR11MB3708.namprd11.prod.outlook.com ([fe80::f844:816:5069:c9bb%5]) with mapi id 15.20.2305.023; Fri, 4 Oct 2019 06:37:26 +0000
From: "Ali Sajassi (sajassi)" <sajassi@cisco.com>
To: Stephane Litkowski <slitkows.ietf@gmail.com>, "bess@ietf.org" <bess@ietf.org>, "bess-chairs@ietf.org" <bess-chairs@ietf.org>
Thread-Topic: [bess] WG adoption and IP poll for draft-snr-bess-pbb-evpn-isid-cmacflush
Thread-Index: AQHVbsqCH7+ML3N2uE2MOg/K7sBR3qdJqW8A
Date: Fri, 04 Oct 2019 06:37:26 +0000
Message-ID: <CFED628D-F22B-4E39-B512-B3B70674DB07@cisco.com>
References: <CAKVaF1R024G=iK91yErOQ3ucctQt-miYS8SuLGm1OmH6BJrmFA@mail.gmail.com>
In-Reply-To: <CAKVaF1R024G=iK91yErOQ3ucctQt-miYS8SuLGm1OmH6BJrmFA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/10.1d.0.190908
authentication-results: spf=none (sender IP is ) smtp.mailfrom=sajassi@cisco.com;
x-originating-ip: [128.107.241.162]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 462e394f-7ba9-43df-9af0-08d74895525e
x-ms-traffictypediagnostic: DM6PR11MB3820:
x-ms-exchange-purlcount: 1
x-microsoft-antispam-prvs: <DM6PR11MB3820454940AF09118EB1AC46B09E0@DM6PR11MB3820.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-forefront-prvs: 018093A9B5
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(39860400002)(346002)(136003)(376002)(396003)(366004)(189003)(199004)(66066001)(6506007)(6116002)(790700001)(25786009)(7736002)(3846002)(14454004)(966005)(5660300002)(53546011)(71200400001)(478600001)(71190400001)(102836004)(91956017)(110136005)(8936002)(2906002)(58126008)(14444005)(81166006)(81156014)(66556008)(64756008)(256004)(8676002)(66446008)(66476007)(316002)(11346002)(36756003)(606006)(229853002)(6246003)(476003)(33656002)(486006)(2616005)(54896002)(66946007)(26005)(6486002)(446003)(236005)(6436002)(76116006)(2501003)(86362001)(186003)(99286004)(2201001)(76176011)(6306002)(6512007); DIR:OUT; SFP:1101; SCL:1; SRVR:DM6PR11MB3820; H:DM6PR11MB3708.namprd11.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A: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: nNIOUJ+OhmOAnLT2NMDXAzK4OlcQCDkWx7MhDI5EizZ7Jzpfmpn9vGufHvAFLISYaRMbrER5YFtnWBad9+EGEWED9rUcTYEO8XBGwrN/nHZ09De1NVLpvB5Cl9tgoucKoXbQ0qGKY0zWjiyfPnngX3yjjrWXJohUp8FTDhOybS/oBuL7Rrb9ikX8/7iXtQYdqVZHib60NTpx6RNqcnLK57Ja3LRFFUfi2vgAkOBETMb9jFeNAt06VfZFNcXkUQ8xNUT43K3iN05DSuI3iOkdBCmfdwUQUMlL6v5S+UxEVo3Q+2Ut1nDslBo0PkUSWWo6YgA3E0gmivmwLLI4IeVCZVAiizpQQ39OgS1lSBB6Crb3jIKbz7eeJ2U/XuPfg9hdWY81oGCwPZ7zogCsYjGcbXIkO5ZMvsw00RJ7rizAdBiddUhk6b+K4e6fW7kVYyGRCVHc+8z2cQQbS5zI4aI7YQ==
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_CFED628DF22B4E39B512B3B70674DB07ciscocom_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 462e394f-7ba9-43df-9af0-08d74895525e
X-MS-Exchange-CrossTenant-originalarrivaltime: 04 Oct 2019 06:37:26.4114 (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: Cvh71CvJGm8sr18VORiMXq//sBUkjWOuSIIjXZvPfjYpg3Lc1vIMzcNPBxidm/4M0eCEaOg8mrl1nF821wxAZQ==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM6PR11MB3820
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.37.102.28, xch-rcd-018.cisco.com
X-Outbound-Node: rcdn-core-8.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/bess/zb3pIVdpHQxdFk1lJZ1YzHksWj8>
Subject: Re: [bess] WG adoption and IP poll for draft-snr-bess-pbb-evpn-isid-cmacflush
X-BeenThere: bess@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: BGP-Enabled ServiceS working group discussion list <bess.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/bess>, <mailto:bess-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/bess/>
List-Post: <mailto:bess@ietf.org>
List-Help: <mailto:bess-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bess>, <mailto:bess-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Oct 2019 06:37:33 -0000

We already have another ISID flushing mechanism for PBB-EVPN described in section 5.2 of draft-ietf-bess-virtual-eth-segment. Although this draft has already passed WG LC and it is on its way for IESG review, I don’t want to use that as a leverage for pushing the ISID flushing mechanism specified in that draft. But instead I want both of these mechanisms to be reviewed by the authors based on their technical merits and we pick only one. Each of these mechanisms have their own pros/cons. If we decided to go with snr draft, then I will remove ISID flushing procedure from my draft and request for another WG LC. If we decide to go with my draft, then we don’t need to have a WG for this draft. I will schedule a call among the co-authors.

Cheers,
Ali

From: BESS <bess-bounces@ietf.org> on behalf of Stephane Litkowski <slitkows.ietf@gmail.com>
Date: Thursday, September 19, 2019 at 2:13 AM
To: "bess@ietf.org" <bess@ietf.org>, "bess-chairs@ietf.org" <bess-chairs@ietf.org>
Subject: [bess] WG adoption and IP poll for draft-snr-bess-pbb-evpn-isid-cmacflush

Hi,

This email begins a two-weeks WG adoption poll for draft-snr-bess-pbb-evpn-isid-cmacflush [1]
Please review the draft and post any comments to the BESS working group list.

We are also polling for knowledge of any undisclosed IPR that applies to this Document, to ensure that IPR has been disclosed in compliance with IETF IPR rules (see RFCs 3979, 4879, 3669 and 5378 for more details).

If you are listed as an author or a contributor of this document, please respond to this email and indicate whether or not you are aware of any relevant undisclosed IPR, copying the BESS mailing list. The document won't progress without answers from all the authors and contributors.
Currently, there are no IPR disclosures against this document.

If you are not listed as an author or a contributor, then please explicitly respond only if you are aware of any IPR that has not yet been disclosed in conformance with IETF rules.

This poll for adoption closes on 7th October 2019.

Regards,
Stephane and Matthew

[1] https://datatracker.ietf.org/doc/draft-snr-bess-pbb-evpn-isid-cmacflush/

v2.23.0 | Report a Bug | By Email