Re: [DMM] Mirja Kühlewind's Discuss on draft-ietf-dmm-mag-multihoming-04: (with DISCUSS and COMMENT)
"Sri Gundavelli (sgundave)" <sgundave@cisco.com> Fri, 18 August 2017 01:08 UTC
Return-Path: <sgundave@cisco.com>
X-Original-To: dmm@ietfa.amsl.com
Delivered-To: dmm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 29E64132707; Thu, 17 Aug 2017 18:08:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.521
X-Spam-Level:
X-Spam-Status: No, score=-14.521 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, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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
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 hC5okEaQZiKA; Thu, 17 Aug 2017 18:08:41 -0700 (PDT)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C05C81243F6; Thu, 17 Aug 2017 18:08:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4378; q=dns/txt; s=iport; t=1503018520; x=1504228120; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=ut5AuSuQURgm/PN2Oy6hhsNevN+BoqoRSqFVAZBnS0A=; b=OeWiP+nbPJ3jJgVsw/TZaD8fAOBPJ2SpBsbFwQbKSLsOFGbAaiO5yKEw p0AOIR/qUmsFwnbPzmznGVa7xJXaE6LOpmiSG+tYg5XYs3J0tb4vaSqnU CM+WSmD622ak8yfV8YUXzbUisSNy3IPMUnCu8MG5j6yrLYP6fQ0sg69nK c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0CfAADIPZZZ/5FdJa1TChkBAQEBAQEBAQEBAQcBAQEBAYNaZIEVB44LkBKTI4RmghKFRwIahD4/GAECAQEBAQEBAWsohRkGIxFFEAIBCBoCJgICAjAVBQsCBA4FijCqC4Imi2YBAQEBAQEBAQEBAQEBAQEBAQEBAQEdgQuCHYICgUyFCoRIgz6CYQWJfhOIa41NApRAghCFYIpsiWiMNAEfOIEKdxWGFYFOdohMgQ8BAQE
X-IronPort-AV: E=Sophos;i="5.41,390,1498521600"; d="scan'208";a="284163497"
Received: from rcdn-core-9.cisco.com ([173.37.93.145]) by rcdn-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 18 Aug 2017 01:08:33 +0000
Received: from XCH-ALN-007.cisco.com (xch-aln-007.cisco.com [173.36.7.17]) by rcdn-core-9.cisco.com (8.14.5/8.14.5) with ESMTP id v7I18X77019253 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Fri, 18 Aug 2017 01:08:33 GMT
Received: from xch-aln-008.cisco.com (173.36.7.18) by XCH-ALN-007.cisco.com (173.36.7.17) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Thu, 17 Aug 2017 20:08:33 -0500
Received: from xch-aln-008.cisco.com ([173.36.7.18]) by XCH-ALN-008.cisco.com ([173.36.7.18]) with mapi id 15.00.1210.000; Thu, 17 Aug 2017 20:08:33 -0500
From: "Sri Gundavelli (sgundave)" <sgundave@cisco.com>
To: "Mirja Kuehlewind (IETF)" <ietf@kuehlewind.net>
CC: The IESG <iesg@ietf.org>, "dmm-chairs@ietf.org" <dmm-chairs@ietf.org>, Jouni Korhonen <jouni.nospam@gmail.com>, "draft-ietf-dmm-mag-multihoming@ietf.org" <draft-ietf-dmm-mag-multihoming@ietf.org>, "dmm@ietf.org" <dmm@ietf.org>
Thread-Topic: Mirja Kühlewind's Discuss on draft-ietf-dmm-mag-multihoming-04: (with DISCUSS and COMMENT)
Thread-Index: AQHTCkbWqTqOB87KxkGk4BHR1eN2MQ==
Date: Fri, 18 Aug 2017 01:08:33 +0000
Message-ID: <D5BB8B17.287E17%sgundave@cisco.com>
References: <150153774387.6368.10402951105593501459.idtracker@ietfa.amsl.com> <D5BA5624.287B9A%sgundave@cisco.com> <89C42C3C-4A49-4CB1-B853-D834900281D8@kuehlewind.net>
In-Reply-To: <89C42C3C-4A49-4CB1-B853-D834900281D8@kuehlewind.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.7.1.161129
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.20.188.62]
Content-Type: text/plain; charset="utf-8"
Content-ID: <1B7F884D2C11ED498255A7A6C41BA3D5@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmm/qZ570j-e5ppvTpdp3EQeNAym8hI>
Subject: Re: [DMM] Mirja Kühlewind's Discuss on draft-ietf-dmm-mag-multihoming-04: (with DISCUSS and COMMENT)
X-BeenThere: dmm@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Distributed Mobility Management Working Group <dmm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmm>, <mailto:dmm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmm/>
List-Post: <mailto:dmm@ietf.org>
List-Help: <mailto:dmm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dmm>, <mailto:dmm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Aug 2017 01:08:43 -0000
Hi Mirja, Thank you for your quick feedback. Please see inline … On 8/17/17, 6:12 AM, "Mirja Kuehlewind (IETF)" <ietf@kuehlewind.net> wrote: <snip> .. keeping only the open issues. > >> >> >> >>> >>> 3) This document does not really normative specify the use of the newly >>> defined >>> options. It only gives an examples but it does not specify normatively >>>any >>> actions that need to performed on receipt of these options. How does >>>the >>> MAG >>> know if the LMA does not support Multipath binding? An LMA that does >>>not >>> implement this spec will not send back an error message. Why are there >>>two >>> different options? What happens if one of the options is present in the >>> Proxy >>> Binding Update but not the other? >>> >> >> >> This is a good point. There is an implicit assumption that the LMA >> behavior is consistent with the behavior when dealing with any unknown >> options. >> We can put a note that the PBU will rejected with error code 128. > >That's good. Are you supposed to resend without the new options if you >received 128? And again what happens if only one option is present? I will take care of this. Will add considerations on both LMA/MAG behavior when there is version incompatibility. Will post a new rev with these considerations. But, thank you; we definitely overlooked this part. > >> >> >> >> >> >>> >>> ---------------------------------------------------------------------- >>> COMMENT: >>> ---------------------------------------------------------------------- >>> >>> Please also clarify the definitions of Interface Label and Binding >>> Identifier >>> as requested by the gen-art review (Thanks Robert!) >>> >> >> Interface label is a static field, Ex: “LTE-Interface”, “my blue >> interface”. Traffic policy is tied to this static label, >> >> HTTP Flow: Use LTE-Interface, if not available, use “WiFI-Interface”. >> Label is tied to a policy; which the MAG and LMA will translate it bind >> the flow to a dynamically created tunnel using the CoA from that >>interface. >> >> Binding identifier is what is dynamically generated and using to >>identify >> a specific binding on the LMA. > >I think this comment was on the way it is described in the draft. Maybe >the wording can be further clarified there. Here is the original text >from the genart review of Robert Sparks: I have looked at both the definitions and I agree it needs to some clarification. I will fix this. > >"* I still find the definitions of Interface Label and Binding Identifier >confusing. > I suspect they _both_ need to be carefully rewritten to make sure they >are > definitions of the terms, and not descriptions of the interactions of >the two > fields. Why is the Interface Label definition talking so much about >binding? > As currently written, that last sentence of the Binding Identifier > definition says the document says the mobile access gateway assigns > a single unique binding identifier for each of its interfaces. „ > > >Thanks! >Mirja > > > >> >> >> >> >>> >> >
- [DMM] Mirja Kühlewind's Discuss on draft-ietf-dmm… Mirja Kühlewind
- Re: [DMM] Mirja Kühlewind's Discuss on draft-ietf… pierrick.seite
- Re: [DMM] Mirja Kühlewind's Discuss on draft-ietf… Behcet Sarikaya
- Re: [DMM] Mirja Kühlewind's Discuss on draft-ietf… Sri Gundavelli (sgundave)
- Re: [DMM] Mirja Kühlewind's Discuss on draft-ietf… Mirja Kuehlewind (IETF)
- Re: [DMM] Mirja Kühlewind's Discuss on draft-ietf… Sri Gundavelli (sgundave)
- Re: [DMM] Mirja Kühlewind's Discuss on draft-ietf… Mirja Kuehlewind (IETF)