Re: [DMM] WGLC on draft-ietf-dmm-pmipv6-dlif-03

CARLOS JESUS BERNARDOS CANO <cjbc@it.uc3m.es> Sun, 20 January 2019 12:11 UTC

Return-Path: <cjbc@it.uc3m.es>
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 B7D7813107E for <dmm@ietfa.amsl.com>; Sun, 20 Jan 2019 04:11:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 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_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=it.uc3m.es
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 Z5dyZQI8LFLH for <dmm@ietfa.amsl.com>; Sun, 20 Jan 2019 04:11:48 -0800 (PST)
Received: from mail-wr1-x430.google.com (mail-wr1-x430.google.com [IPv6:2a00:1450:4864:20::430]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EEA08131058 for <dmm@ietf.org>; Sun, 20 Jan 2019 04:11:47 -0800 (PST)
Received: by mail-wr1-x430.google.com with SMTP id p4so20152984wrt.7 for <dmm@ietf.org>; Sun, 20 Jan 2019 04:11:47 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=it.uc3m.es; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=GT+TlpNJlJ9oiL/jkDsGiF42ziW/KieQ7suGcXPng2Y=; b=RAP9p3GSbqzhk688RQ+cGWLbUvivLUHRnAFejIyVQV/65SYGF+SbgacfCBR7isEpuh +jg00Aa6pjTnrzHgOAB2bIkHE1KMZHrVKfoOY7zEhm9dPHOfkgUZdzo9zFPbphaqxI+8 IczJj701vEfKQhERFqQeSnWrHjfjpQ0rWRvggCJZ5NiZ1YryzKUQjad3QLPjMb9Si/EV up0IFPJtSzSXbIO2VtCKXsdyJWN6cUVduNismfhr3tzeCM2THcjVpMJ2ZMUMncshpd31 5ajtslroygPfdR/IZ0EzXru9bIanmGOiVo+P3WT46X1wEWTz++tcfwoETRX3iBiP83Dv L+RQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=GT+TlpNJlJ9oiL/jkDsGiF42ziW/KieQ7suGcXPng2Y=; b=KP6z6NLpIRNKDopckO9OJ71KzUfXtZLcz8BYnCW/VG/pGgtRq1lVmNkt9Fm3wDYUuT w156OQoZutRMP+RdO7cU+XadV/s1kPrLakyveXZhSSXYkA/CrPvJmV6AwDeP/hevZU2W wLUShdzcv1hQTUYCtFFM6bnOiWT2i7eo0CiGZMB80k0PGmASEbO+q9P+UHdw5sAsPDc/ 3Mf4v3UVgWHkqLcbksx8+Kkya052PLKLe7fMUdigDaz4f/Pt1FMgmJyQtZWtBPSh1m+N +9bEY3xWWV3ApMqMGZe5ga/uFxQgWIu8d4baKmHQozS7/CZSimPw3cf6V9yvL6gy6n72 GBsg==
X-Gm-Message-State: AJcUukcqzVzlOLlCSG2KvCGS3p0/pG1DL9LVz60P4MJbkpFwF8PZ11f/ Jwv7AY4zZNT4Tx5bJ/vBBSupMahUHxetFyW7pVto7Q==
X-Google-Smtp-Source: ALg8bN6DscJIBAjUo0uPCWp1q8d2/frPAlsElkSS+T9UpGmIJ7UCgS3w6MuxSB4bCTfpn58zviFuOYbK1LKgqBvNZqM=
X-Received: by 2002:a5d:4586:: with SMTP id p6mr23168920wrq.69.1547986306174; Sun, 20 Jan 2019 04:11:46 -0800 (PST)
MIME-Version: 1.0
References: <D85B80D0.2E3465%sgundave@cisco.com> <FRXPR01MB01346A12396D3EEED39E5949D1820@FRXPR01MB0134.DEUPRD01.PROD.OUTLOOK.DE> <6561EABF52675C45BCDACA1B4D7AA1171FA43B1F@sjceml521-mbs.china.huawei.com>
In-Reply-To: <6561EABF52675C45BCDACA1B4D7AA1171FA43B1F@sjceml521-mbs.china.huawei.com>
From: CARLOS JESUS BERNARDOS CANO <cjbc@it.uc3m.es>
Date: Sun, 20 Jan 2019 13:11:29 +0100
Message-ID: <CALypLp9=UguFf32n12=TG2PR2kkOX-s9CdyNW7fBbyQbU7cajQ@mail.gmail.com>
To: John Kaippallimalil <John.Kaippallimalil@huawei.com>
Cc: "dmm@ietf.org" <dmm@ietf.org>, "sgundave@cisco.com" <sgundave@cisco.com>
Content-Type: multipart/alternative; boundary="000000000000e5aeea057fe2a551"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmm/txUHaIQUAL59dI3aN5cpJnQKWco>
Subject: Re: [DMM] WGLC on draft-ietf-dmm-pmipv6-dlif-03
X-BeenThere: dmm@ietf.org
X-Mailman-Version: 2.1.29
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: Sun, 20 Jan 2019 12:11:52 -0000

Thanks a lot John! We'll address your comments in the next revision.

Carlos

On Sat, Jan 19, 2019 at 6:11 PM John Kaippallimalil <
John.Kaippallimalil@huawei.com> wrote:

> Review and comments on draft-ietf-dmm-pmipv6-dlif-03.
>
>
>
> The text in the draft is clear, and it is ready to move forward in my view.
>
>
>
> A couple of comments below:
>
> (not repeating nits that Dirk has already posted)
>
>
>
> Section 3:
>
> “As another note, the solution described in this document allows
> performing per-prefix anchoring decisions, to support e.g., some flows to
> be anchored at a central Home-DPA (like a traditional LMA)”
>
> Would be good to clarify a bit here: is this a result of the MN requesting
> central anchoring (or not), or the result of the mobility topology (MAARs,
> CMDs).
>
>
>
> Section 3.4:
>
> Does the implementation with parallel operations need to mention something
> about race conditions.
> It is probably fine in practice, but not a completely safe operation
> (e.g., MAAR2 may forward data to MAAR1 before the route update at MAAR1 is
> complete)
>
> Overall – the draft looks really good and ready.
>
>
>
> John
>
>
>
>
>
>
>
> *From:* dmm [mailto:dmm-bounces@ietf.org] *On Behalf Of *
> Dirk.von-Hugo@telekom.de
> *Sent:* Wednesday, January 16, 2019 10:18 AM
> *To:* sgundave@cisco.com
> *Cc:* dmm@ietf.org
> *Subject:* Re: [DMM] WGLC on draft-ietf-dmm-pmipv6-dlif-03
>
>
>
> Hi all,
>
> I agree to forward the mature and very useful document to IESG.
>
>
>
> I just detected 3 very minor nits presumably created during recent
> re-formatting:
>
> P.7
>
> the MN-ID, Pref1 and MAAr1's address as a Proxy-CoA => the MN-ID, Pref1,
> and MAAR1's address as a Proxy-CoA
>
>
>
> 5. MAAR1 stores the BCE described in (1) an unicast a Router Advertisement
> (RA) to the MN with Pref1 => 5. MAAR1 stores the BCE described in (1) and
> unicasts a Router Advertisement (RA) to the MN with Pref1
>
> P.9
>
> Step 6. Is an empty one and SHOULD be deleted
>
> ;-)
>
>
>
> Thanks!
>
> Kind regards
>
> Dirk
>
>
>
> *From:* dmm <dmm-bounces@ietf.org> *On Behalf Of *Sri Gundavelli
> (sgundave)
> *Sent:* Mittwoch, 9. Januar 2019 19:44
> *To:* dmm@ietf.org
> *Subject:* [DMM] WGLC on draft-ietf-dmm-pmipv6-dlif-03
>
>
>
> Folks – As we discussed in the WG meeting at IETF103, we are issuing WGLC
> on https://www.ietf.org/id/draft-ietf-dmm-pmipv6-dlif-03.txt.
>
>
>
> *We have also made one key change to the document status, moving it from
> Standards Track to Experimental Track. We the chairs have talked to the
> authors and they are OK with this change. We are dong this as we are not
> sure about any potential vendor implementations and so we chose to keep
> this on experimental track.*
>
>
>
> The document went through several revisions and there were good amount of
> reviews on this document.  The authors have addressed all the comments and
> there are no open issues that we are tracking at this time. We believe the
> document is ready for IESG reviews and like to confirm the same from the
> working group.
>
>
>
>
>
> The following message commences a two week WGLC for all feedback.
>
>
>
> Document Link:
>
>  https://www.ietf.org/id/draft-ietf-dmm-pmipv6-dlif-03.txt
> <https://www.ietf.org/id/draft-ietf-dmm-pmipv6-dlif-03..txt>
>
>
>
> The target status for this document is “Experimental”.
>
>
>
> Please post any comments/concerns on the draft.
>
>
>
>
>
> Thanks!
>
> Dapeng & Sri
>
>
>
>
>