Re: [lisp] Mirja Kühlewind's Discuss on draft-ietf-lisp-gpe-05: (with DISCUSS and COMMENT)

"Fabio Maino (fmaino)" <fmaino@cisco.com> Tue, 07 January 2020 23:02 UTC

Return-Path: <fmaino@cisco.com>
X-Original-To: lisp@ietfa.amsl.com
Delivered-To: lisp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CDF751207FE; Tue, 7 Jan 2020 15:02:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.501
X-Spam-Level:
X-Spam-Status: No, score=-14.501 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, 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=C+wVI9QH; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=ojPsE4ym
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 zY2V7iDvNSUC; Tue, 7 Jan 2020 15:02:15 -0800 (PST)
Received: from alln-iport-1.cisco.com (alln-iport-1.cisco.com [173.37.142.88]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 759761201DE; Tue, 7 Jan 2020 15:02:15 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=200886; q=dns/txt; s=iport; t=1578438135; x=1579647735; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=6kEqXrXAr43TVWK+694TZTgxf5eDSqqM/Nr7KesjP6U=; b=C+wVI9QHeWng8E5AVh1gggJpKMmD41siY/olFeGM4zFyuYAPV5qAWOdu Ov6qsSvbPYzZKdnz0nv3O4ZaTfYRc+ofYszPNUTOuyDsyuqn76o8QzV4A MorDJQ5ebVYJMF7ZZw6SZmV3rAduHIYBp42yp6gBsjQvuMJCFAJUXP0XP k=;
X-Files: Diff_ draft-ietf-lisp-gpe-05.txt - draft-ietf-lisp-gpe-13.txt.pdf : 141840
IronPort-PHdr: =?us-ascii?q?9a23=3ASCHAdBb4SKLJcnTUSLfzp6T/LSx94ef9IxIV55?= =?us-ascii?q?w7irlHbqWk+dH4MVfC4el20Q6bRp3VvvRDjeee87vtX2AN+96giDgDa9QNMn?= =?us-ascii?q?1NksAKh0olCc+BB1f8KavkaiU7GsNqX15+9Hb9Ok9QS47z?=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0C2AAAcDRVe/4wNJK1mGgEBAQEBAQE?= =?us-ascii?q?BAQMBAQEBEQEBAQICAQEBAYF8gVRQBWwrLSAECyqECYNGA4sFgjolgQGXDIF?= =?us-ascii?q?CgRADVAIHAQEBCQECAQEjCgIBAYRAAheBUiQ4EwIDDQEBBAEBAQIBBQRthTc?= =?us-ascii?q?MhV4BAQEBAgESER0BAQMmDgEPAgEIGCoCAgIYGBoLAgQBDQUODQeDAAGCRgM?= =?us-ascii?q?OEQ8BAgyhZwKBOIhhdYEygn4BAQWBSUGDBBiCBQcDBoE2gVOKRhqBQT+BESc?= =?us-ascii?q?MFIIXNT6CZAIBAgGBLAESAYMvMoIsjVCCODmFV4ESiFOEE4ESigEKgjaDYYN?= =?us-ascii?q?UhHmITYEhG4JHh32LWYRCg0eLDIFIhwySDQIEAgQFAg4BAQWBaSJnWBEIcBV?= =?us-ascii?q?lATkBggdQGA2NEgwXFYM7hRSFP3QBgSeNIoIyAQE?=
X-IronPort-AV: E=Sophos;i="5.69,407,1571702400"; d="pdf'?scan'208";a="399157532"
Received: from alln-core-7.cisco.com ([173.36.13.140]) by alln-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 07 Jan 2020 23:02:14 +0000
Received: from XCH-RCD-007.cisco.com (xch-rcd-007.cisco.com [173.37.102.17]) by alln-core-7.cisco.com (8.15.2/8.15.2) with ESMTPS id 007N2EWR006471 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 7 Jan 2020 23:02:14 GMT
Received: from xhs-rtp-002.cisco.com (64.101.210.229) by XCH-RCD-007.cisco.com (173.37.102.17) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Tue, 7 Jan 2020 17:02:13 -0600
Received: from xhs-rtp-003.cisco.com (64.101.210.230) by xhs-rtp-002.cisco.com (64.101.210.229) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Tue, 7 Jan 2020 18:02:11 -0500
Received: from NAM10-BN7-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; Tue, 7 Jan 2020 18:02:11 -0500
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=kJlewZMpXg5/fEPzIcDo1cqA/56SmnBlluLP+/KaxB66XV3eXreCExdDygycAObx+Rx/Q7DnPM/rLlFIOYaRm8L5y+UATMKy4hykbjoCjMQ+EjRSYVvAkivP3XQ7Tr3EAVd09MXIDtGbfap5pio3+FmVybWcFP2YTazcnsuG76OiiiGKSh4nBpQmF6Q5YRIyPSSEFuqjmmI3BGkhLOM6W8nT6FJbhhIk1O8w90Kqh3zAATeeTEUX/wwI+XConJjPkma3o5FKAHBqtG6yCjYRGqF5Zl5VBp1ljs3Gpf2inuEEWhoEomla1z3+/dThuonleX4imd5E9E/mk8XtyawC+w==
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=eFLo3ER6VGbaZY/dVUh2dLRWM585sFSt/ZfxzsOxQuM=; b=EB+845T+0u69UzL4DZ7yoUSidmpUdfZ34yF4Bzb6dphIAWuat3Udlfnicp5+ynHRwgVN89MFdqP8fV8Rd6zx22m3QvzifnnqH8n5giXcpDohhByhyu+JmDEfMPZX7uc1lIyf0qghnu5V98L5igZzt5pFymLeC//vFjQyf0I0CIFhwICJl2RH++Ko3SqcaKOvjWYiKYKFRY4ClMaxtO1LYRr5XJZ8q9lR10lzs/7wNhlxvmi2d5s84bOoMjKpy7gCehjj91NaBO/6m8FlBE4TgTtLlprdCqOojqaAfMFhqVQrJp8d1NmBDRPt3KIYF/5hQskRIrD80x5iBfHu5FW+9w==
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=eFLo3ER6VGbaZY/dVUh2dLRWM585sFSt/ZfxzsOxQuM=; b=ojPsE4ymKXvJGYlf9iTlgLyyBHEEqaoMilA/O7/sBYo3qgIjLOBXW2L7/3Ox6gKnKy8FfRlbeEu3zM7bhmocRq4yTwp5mmMQ9q0abICli8qg6PGP6fi0NPFlIHxwOmB5xSfxbwykpxedKxhfgi7geejIKIfOX5Ykq3TSAAcy1+A=
Received: from BY5PR11MB4420.namprd11.prod.outlook.com (52.132.255.20) by BY5PR11MB3928.namprd11.prod.outlook.com (10.255.161.30) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2602.15; Tue, 7 Jan 2020 23:02:10 +0000
Received: from BY5PR11MB4420.namprd11.prod.outlook.com ([fe80::cc2a:491c:a377:bc18]) by BY5PR11MB4420.namprd11.prod.outlook.com ([fe80::cc2a:491c:a377:bc18%7]) with mapi id 15.20.2602.016; Tue, 7 Jan 2020 23:02:10 +0000
From: "Fabio Maino (fmaino)" <fmaino@cisco.com>
To: =?utf-8?B?TWlyamEgS8O8aGxld2luZA==?= <ietf@kuehlewind.net>, The IESG <iesg@ietf.org>
CC: "draft-ietf-lisp-gpe@ietf.org" <draft-ietf-lisp-gpe@ietf.org>, "Luigi Iannone" <ggx@gigix.net>, "lisp-chairs@ietf.org" <lisp-chairs@ietf.org>, "lisp@ietf.org" <lisp@ietf.org>, "BRUNGARD, DEBORAH A (ATTLABS)" <db3546@att.com>, "magnus.westerlund@ericsson.com" <magnus.westerlund@ericsson.com>
Thread-Topic: =?utf-8?B?TWlyamEgS8O8aGxld2luZCdzIERpc2N1c3Mgb24gZHJhZnQtaWV0Zi1saXNw?= =?utf-8?Q?-gpe-05:_(with_DISCUSS_and_COMMENT)?=
Thread-Index: AQHUUFDdrGXy7u5t8UK1eJZx5YzeLqT5fQ2Agui5L4A=
Date: Tue, 7 Jan 2020 23:02:09 +0000
Message-ID: <F07DBBF7-BAEB-4D88-8552-EB3A64AC72C2@cisco.com>
References: <153738612868.21424.5753365080841918983.idtracker@ietfa.amsl.com> <c31f2457-0803-6a98-5970-10acf9782e10@cisco.com>
In-Reply-To: <c31f2457-0803-6a98-5970-10acf9782e10@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/10.20.0.191208
authentication-results: spf=none (sender IP is ) smtp.mailfrom=fmaino@cisco.com;
x-originating-ip: [2001:420:30a:4e05:15c:a22d:632b:c69f]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 9fcb8214-5683-4a5a-a908-08d793c5a020
x-ms-traffictypediagnostic: BY5PR11MB3928:
x-microsoft-antispam-prvs: <BY5PR11MB3928FEDCE7D8AAB176437B2FC23F0@BY5PR11MB3928.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 027578BB13
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(136003)(346002)(396003)(376002)(366004)(39860400002)(199004)(189003)(2906002)(53546011)(6506007)(478600001)(4326008)(66574012)(186003)(5660300002)(33656002)(224303003)(86362001)(54906003)(81166006)(110136005)(8936002)(6512007)(81156014)(316002)(76116006)(36756003)(66476007)(6486002)(66946007)(71200400001)(66616009)(66556008)(966005)(64756008)(66446008)(2616005); DIR:OUT; SFP:1101; SCL:1; SRVR:BY5PR11MB3928; H:BY5PR11MB4420.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: f/PSsgkfOVGIwSWhexGJo6FMzJmnUEbxRGSVyQJBFiX1kU6fi+u4tnj3/Cj/XIGeiXH/9Uh7X/8Gc9DBGM2hfnpT1GGrtXklP2bXFgmNPS8nUwQRb6ciemG193nnvTAAM+xSF7XFRKAbbxgz8h6kad/KVEOtX16v99n3tLWzNS+pB1/tW1Q2SXlFT8qBiKUZVJpayRoXAQIx8vAWeAqMsAoaxx2N+o2HyDkLspli6UtxBZ3hx7ggfM4gP8bHDa7CcOUmOrvp8UjkD07Jb+j1783GcrumSrdTPPdKVB8JfEn6FWO3G872SX+qEFgsgyeetc/aHKK67KoxfsPhgj1AdtiLqPV4UGIzzufT0RaAhSKCbsQcZClnYrG1/kEREnOCYOvOjFvbQ4InoyK29aqgjMEskZet05tnsjuWhZpBb75B+wckMt5VmqnYUoAdpftUgqovq6Qait3VuwkK4fXnD4JiFFlR3HXbWSsA1u+3dIo=
x-ms-exchange-transport-forked: True
Content-Type: multipart/mixed; boundary="_002_F07DBBF7BAEB4D888552EB3A64AC72C2ciscocom_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 9fcb8214-5683-4a5a-a908-08d793c5a020
X-MS-Exchange-CrossTenant-originalarrivaltime: 07 Jan 2020 23:02:09.8750 (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: 123S2/cU4WPhWqim5n/HPO5+YSREKtMcZblP+/qjInTEAqwgKg33lBkcDnEkqqYZMnuXBZyC0M6zaxAXwgpguw==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BY5PR11MB3928
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.37.102.17, xch-rcd-007.cisco.com
X-Outbound-Node: alln-core-7.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/lisp/Cx3iAAEkZoWUiVDvaLWizBW2Fp8>
Subject: Re: [lisp] =?utf-8?q?Mirja_K=C3=BChlewind=27s_Discuss_on_draft-ietf-?= =?utf-8?q?lisp-gpe-05=3A_=28with_DISCUSS_and_COMMENT=29?=
X-BeenThere: lisp@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: List for the discussion of the Locator/ID Separation Protocol <lisp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/lisp>, <mailto:lisp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/lisp/>
List-Post: <mailto:lisp@ietf.org>
List-Help: <mailto:lisp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lisp>, <mailto:lisp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Jan 2020 23:02:18 -0000

Hi Mirja,
It took quite some time, but I think we are finally making progress with the review of draft-ietf-lisp-gpe and the related LISP RFCbis drafts (https://datatracker.ietf.org/doc/draft-ietf-lisp-rfc6830bis/
, https://datatracker.ietf.org/doc/draft-ietf-lisp-rfc6833bis/ ).

Could you please take a look at the latest rev -13 of https://datatracker.ietf.org/doc/draft-ietf-lisp-gpe/, and let us  know if we have addressed your comments?

Wrt lisp-gpe, compared with rev -05 that you last reviewed, we have done two main changes that might help addressing your DISCUSS: 
1.	We have introduced the concept of shim header, along the line of what Mirja suggested in her comment. The chairs thought that the change was significant enough to require a new last call with the WG, that we did after Singapore
2.	 We have introduced section 4 that, following what done in RFC8085 and RFC8086, defines the scope of applicability of LISP-GPE and makes considerations related with congestion control, UDP checksum, and ethernet payload encapsulation. 

Please, let me know if you have any further question or suggestion. 

I have attached a diff from rev -05 that is the one to which your ballot comments were referring to. 

Thanks,
Fabio


On 9/20/18, 1:22 PM, "Fabio Maino" <fmaino@cisco.com> wrote:

    Thanks for your notes Mirja.
    
    I'll publish an updated rev this evening to consolidate the changes that 
    I believe we have agreed upon, and then I'll work on those that are 
    still open.
    
    Please see below.
    
    
    On 9/19/18 12:42 PM, Mirja Kühlewind wrote:
    > Mirja Kühlewind has entered the following ballot position for
    > draft-ietf-lisp-gpe-05: Discuss
    >
    > When responding, please keep the subject line intact and reply to all
    > email addresses included in the To and CC lines. (Feel free to cut this
    > introductory paragraph, however.)
    >
    >
    > Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
    > for more information about IESG DISCUSS and COMMENT positions.
    >
    >
    > The document, along with other ballot positions, can be found here:
    > https://datatracker.ietf.org/doc/draft-ietf-lisp-gpe/
    >
    >
    >
    > ----------------------------------------------------------------------
    > DISCUSS:
    > ----------------------------------------------------------------------
    >
    > Thanks for addressing the TSV-ART review (and Magnus for doing the review)! I
    > assume that the proposed text will be incorporated in the next version. (Would
    > have been even better if those (larger) changes would have been added before
    > the doc was put on the telechat; please update as soon as possible so other AD
    > can review that text as well).
    >
    > However, I think the text still needs to say more about HOW the PCP should be
    > mapped to DSCPs. RFC8325 doesn't provide guidelines but a mapping for 802.11.
    > Is the same mapping applicable here?
    
    Agree. As pointed out by Magnus' latest email there's more investigation 
    needed here. I'll get back on this.
    
    >
    > Also, I'm not an expert for that part, but I guess there also is further
    > guidance needed on HOW to map the VID...?
    
    This is really straightforward, as the VID is a 12-bit field, and the 
    IID is 24-bit. Implementation that I'm aware of typically carve a 
    portion of the IID space to encode the VID.
    
    >
    >
    > ----------------------------------------------------------------------
    > COMMENT:
    > ----------------------------------------------------------------------
    >
    > Given this doc uses the last reserved bit in the lisp header, I would really
    > like to see more discussion how the data plane lisp can still be extended. I
    > think the solution is straight-forward (define a shim layer for the extension
    > and announce this capability in the Map-Reply), however, spelling this out
    > seems to be appropriate for this doc.
    
    Correct, that's the idea. I'll add a sentence that states that a 
    lisp-gpe next protocol header can be used to extend the lisp data-plane 
    functions.
    
    
    Thanks,
    Fabio
    
    >
    >