Re: [DMM] Intdir telechat review of draft-ietf-dmm-distributed-mobility-anchoring-14

"Eric Vyncke (evyncke)" <evyncke@cisco.com> Sat, 29 February 2020 07:52 UTC

Return-Path: <evyncke@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 C0D4C3A0AFC; Fri, 28 Feb 2020 23:52:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.6
X-Spam-Level:
X-Spam-Status: No, score=-9.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_PASS=-0.001, URIBL_BLOCKED=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=CTlUJVei; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=Auabcxgh
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 d4dTYr0IEeBU; Fri, 28 Feb 2020 23:52:24 -0800 (PST)
Received: from alln-iport-4.cisco.com (alln-iport-4.cisco.com [173.37.142.91]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B5F1F3A0AF5; Fri, 28 Feb 2020 23:52:23 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=5842; q=dns/txt; s=iport; t=1582962744; x=1584172344; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=2b64vtjo2RciqsRcJfom6HxazWGZ/1XdQAcX0DpCGIk=; b=CTlUJVeiRAJWW1Fbrr754szJ126f7FXw2oZu/znONXZeQrQIa9ZkQrra 2tXkqZQ6qEck/EqNJLQ55A6sBz55Y6kKMFLbEcH34SPg034JVn6Z+RTOA emFEy/uYOQIAdpeUi9adNMDdEN5fWCNjzf2Nv5AX5eTMDHcmyJ2IDVhSR E=;
IronPort-PHdr: 9a23:XJFs0xSYS9DPtn0gGFSFOmraQtpsv++ubAcI9poqja5Pea2//pPkeVbS/uhpkESXBdfA8/wRje3QvuigQmEG7Zub+FE6OJ1XH15g640NmhA4RsuMCEn1NvnvOiEkDcJJV1JN9HCgOk8TE8H7NBXf
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0CzAABQF1pe/4oNJK1mGgEBAQEBAQEBAQMBAQEBEQEBAQICAQEBAYF7gVRQBWxYIAQLKoQUg0YDimaCOiWJY44yglIDVAkBAQEMAQEjCgIEAQGEQAIXgXMkOBMCAw0BAQUBAQECAQUEbYVWDIVjAQEBAQMSEREMAQEwBwELBAIBCBEDAQIDAiYCAgIfERUICAIEAQ0FCRIHgwQBgkoDLgEOowcCgTmIYnWBMoJ/AQEFhQwNC4IMCYEOKowlGoFBP4ERJwwUgk0+ghs+CwIBgWSDETKCLIdWhgiDB497jntECoI8ki8EhDIcmzGOcIZ2hDSQHgIEAgQFAg4BAQWBaSKBWHAVZQGCQQlHGA2OHQwXg1CFFIVBdAKBJ45JAQE
X-IronPort-AV: E=Sophos;i="5.70,499,1574121600"; d="scan'208";a="439495205"
Received: from alln-core-5.cisco.com ([173.36.13.138]) by alln-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 29 Feb 2020 07:52:20 +0000
Received: from XCH-ALN-005.cisco.com (xch-aln-005.cisco.com [173.36.7.15]) by alln-core-5.cisco.com (8.15.2/8.15.2) with ESMTPS id 01T7qKDg029542 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Sat, 29 Feb 2020 07:52:20 GMT
Received: from xhs-rcd-003.cisco.com (173.37.227.248) by XCH-ALN-005.cisco.com (173.36.7.15) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Sat, 29 Feb 2020 01:52:20 -0600
Received: from xhs-rtp-001.cisco.com (64.101.210.228) by xhs-rcd-003.cisco.com (173.37.227.248) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Sat, 29 Feb 2020 01:52:19 -0600
Received: from NAM11-BN8-obe.outbound.protection.outlook.com (64.101.32.56) by xhs-rtp-001.cisco.com (64.101.210.228) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Sat, 29 Feb 2020 02:52:19 -0500
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=bl9LvhxXJqMCInz+xLW5J1uYcwi1MFDTrv4oZKaKA+vOXmhIzK3Euv/rE9J74IZW50nbjazAQJp9rW4uf+XPzlW51egnHbiup4bW0YgYJtW0x8hCpXlOnpAD6SyRLcYeYYBYQJbWdA9uCD/xGMqnbPEU9QONGdWizubQlNq6EYkrTHOJqc4COcNv4ym2INBhpfV992U830/HbEcQf9wCae0k1+azVBWtaOZfjBv9H3lfs+HpRMbyRU83PkuigTmR/B1md+oCpMefKgj07dWXLC7wOC1EjaOxO3pyGGMpq7VSsNE8nNJNjCNEAg602AjX9pKMkooPfWME8EbZG9giuw==
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=2b64vtjo2RciqsRcJfom6HxazWGZ/1XdQAcX0DpCGIk=; b=dhEb0fmQkQ1RXJLVeI0nOkRfrQ/cq5zzxIaDz49qfeLFheRDriFimB1SxxksOz7lAXxXdaDxrIjeP1dzfNdzQcxWXeSWL0wvPB0pNQakksaIgeopdldHVbhjbBY2fyg1zKXgTii3A+cQ2Rb5iXwkh+Pkta7W/BdxxOzw5lb2UwLWtAo0ZLA3kLzupe8vRp24eaCRkPgJJPenkdU2jcAlatgcv3YilPCA+MmSahNppdJyYhDAcbgORhmX6YjVzTfeLOEDgJb9mIByNgX9+vg36wnAVH/tt0tXeyN/yf143LncTSDANcgnnm9qRgZ6wY/fzAZs/Drxv/DU251IH+uSwA==
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=2b64vtjo2RciqsRcJfom6HxazWGZ/1XdQAcX0DpCGIk=; b=Auabcxghzt7YdtGCee2d3rTMbB+f/bYATy5uHEG41PnjGMnhAWNv3VHSl/+ahSxrLZxXcsW0asc6pLk4NqwS3KVzEGLuor3XhbOI0NStSKhzYxGYT/QjWPPjT2pbS4haa1sJwo2FGgdW2l2zYfnUYwMSJBBgHMh8jW4dRO1zFWI=
Received: from DM5PR11MB1753.namprd11.prod.outlook.com (2603:10b6:3:10d::13) by DM5PR11MB1788.namprd11.prod.outlook.com (2603:10b6:3:10a::13) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2772.14; Sat, 29 Feb 2020 07:52:05 +0000
Received: from DM5PR11MB1753.namprd11.prod.outlook.com ([fe80::680d:e22e:72d5:67ca]) by DM5PR11MB1753.namprd11.prod.outlook.com ([fe80::680d:e22e:72d5:67ca%3]) with mapi id 15.20.2772.018; Sat, 29 Feb 2020 07:52:05 +0000
From: "Eric Vyncke (evyncke)" <evyncke@cisco.com>
To: "Carlos Pignataro (cpignata)" <cpignata@cisco.com>, "int-dir@ietf.org" <int-dir@ietf.org>
CC: "last-call@ietf.org" <last-call@ietf.org>, "draft-ietf-dmm-distributed-mobility-anchoring.all@ietf.org" <draft-ietf-dmm-distributed-mobility-anchoring.all@ietf.org>, "dmm@ietf.org" <dmm@ietf.org>
Thread-Topic: Intdir telechat review of draft-ietf-dmm-distributed-mobility-anchoring-14
Thread-Index: AQHV7q0pxHZ1JjXiv0umjQlw6BCfsKgx3a6A
Date: Sat, 29 Feb 2020 07:52:05 +0000
Message-ID: <8DC05C7F-FDAC-4744-9D04-C143080D6C5F@cisco.com>
References: <158294551595.19795.13194872695997233791@ietfa.amsl.com>
In-Reply-To: <158294551595.19795.13194872695997233791@ietfa.amsl.com>
Accept-Language: fr-BE, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/10.22.0.200209
authentication-results: spf=none (sender IP is ) smtp.mailfrom=evyncke@cisco.com;
x-originating-ip: [2001:420:c0c1:36:d0c5:7582:dc4a:408a]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 4b23722c-75f3-45b0-2a68-08d7bcec4549
x-ms-traffictypediagnostic: DM5PR11MB1788:
x-ms-exchange-transport-forked: True
x-microsoft-antispam-prvs: <DM5PR11MB17887CE671EA328BD58AC88FA9E90@DM5PR11MB1788.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:5516;
x-forefront-prvs: 03283976A6
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(136003)(39860400002)(396003)(376002)(346002)(366004)(189003)(199004)(36756003)(8676002)(6506007)(2616005)(81166006)(110136005)(86362001)(8936002)(6512007)(54906003)(316002)(33656002)(6486002)(53546011)(450100002)(81156014)(5660300002)(966005)(66574012)(64756008)(76116006)(71200400001)(186003)(66476007)(4326008)(66556008)(91956017)(66446008)(2906002)(478600001)(66946007); DIR:OUT; SFP:1101; SCL:1; SRVR:DM5PR11MB1788; H:DM5PR11MB1753.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: ALNYA36ugR5AphFc4ay6nGGjN91jX0q1SMMzvvb5df6BZv4WX7Qn1Kk16PpMAvQ/FO9vBIM/JfKurXVcc0JAmI/7dP6LSWqfcnSnP/SqKPEaNCitQfTlvIrU8kOYjyWcJloDogvdnvAifsJZpEePP84s/9Ua2NHOmXBeVOKetDbMNnPiGBAjcDEhpaGi2s0yB0cTGi3DICxSjsI3gl3teFUTuaUvAlWGybdKFiwVexZ+7XLT7vfF4h7GKxvXwzuudH1muh2oNJqUUIcPOGt98vuJnEpYVSygZRaXnNRYBetBK5w+ax1QJxGxYx50gKBtfi+oDwPn9Nl46XqSEnLQrC1EJG2bM94REtP8mu+3Q2KcZKx38Ed1wp1DCh8SJol5BvfgRd050bQMid6c+QluRXbMDD/2NBd64DxkLR29M3ndpynBicvK2le+4PBgQAMEvfGJQQHq+v3Avw6bz3jkTlpp4n3Dzmhht7M0mY07m+FOBPVrLhJnlX2fmTEH3c1DGmHTayNHp1sjM7OmOSBJHw==
x-ms-exchange-antispam-messagedata: R+63jNfS+sPH7Igu+oVBQwZLm9jc3ErobntDKu3H+dzfZDygLWDC+QM3bPCm05VcYnF1qltO6r+rko1N/0nNqr4TRiJfQNiaX2dzYvWT0sReMdjmjJA5FVnKQ0rgjBGuGU88v76JsueA+eQK+Q4gu0noYiYQtv2cQKROL9/5xLUcCzqIaEPr+h7PTp6fy9F351DVe1Uvzw3jAZB857RPOA==
Content-Type: text/plain; charset="utf-8"
Content-ID: <9960A7792839D740BB6CA8BB47D1559A@namprd11.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 4b23722c-75f3-45b0-2a68-08d7bcec4549
X-MS-Exchange-CrossTenant-originalarrivaltime: 29 Feb 2020 07:52:05.6441 (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: QBkUot7qEwEyaZHkfjiVRNkBOujjZy+Kc+mZSmqYuK8GNLTg2SdjOhxxTABWiugdMLc1W+Zw42USM7WQUgJELQ==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM5PR11MB1788
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.36.7.15, xch-aln-005.cisco.com
X-Outbound-Node: alln-core-5.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmm/7RRzt0jye8vxzK1oqLlsm_P4UJI>
Subject: Re: [DMM] Intdir telechat review of draft-ietf-dmm-distributed-mobility-anchoring-14
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: Sat, 29 Feb 2020 07:52:35 -0000

Carlos,

Thank you for the review. I will enter your points in my ballot on those 2 DMM documents.

Regards

-éric

-----Original Message-----
From: Carlos Pignataro via Datatracker <noreply@ietf.org>
Reply-To: "Carlos Pignataro (cpignata)" <cpignata@cisco.com>
Date: Saturday, 29 February 2020 at 04:05
To: "int-dir@ietf.org" <int-dir@ietf.org>
Cc: "last-call@ietf.org" <last-call@ietf.org>, "draft-ietf-dmm-distributed-mobility-anchoring.all@ietf.org" <draft-ietf-dmm-distributed-mobility-anchoring.all@ietf.org>, "dmm@ietf.org" <dmm@ietf.org>
Subject: Intdir telechat review of draft-ietf-dmm-distributed-mobility-anchoring-14
Resent-From: <alias-bounces@ietf.org>
Resent-To: <h.a.chan@ieee.org>, <weixinpeng@huawei.com>, <jonghyouk@smu.ac.kr>, <seiljeon@skku.edu>, <cjbc@it.uc3m.es>, <maxpassion@gmail.com>, <sgundave@cisco.com>, <satoru.matsushima@gmail.com>, Suresh Krishnan <suresh@kaloom.com>, <ek.ietf@gmail.com>, Eric Vyncke <evyncke@cisco.com>, Dapeng Liu <maxpassion@gmail.com>
Resent-Date: Saturday, 29 February 2020 at 04:05

    Reviewer: Carlos Pignataro
    Review result: Ready with Nits
    
    I am an assigned INT directorate reviewer for this Internet-Draft.  These
    comments were written primarily for the benefit of the Internet Area Directors.
    Document editors and shepherd(s) should treat these comments just like they
    would treat comments from any other IETF contributors and resolve them along
    with any other Last Call comments that have been received. For more details on
    the INT Directorate, see http://www.ietf.org/iesg/directorate.html.
    
    I hope these comments are clear and useful.
    
    As requested, from the Internet area Directorate review, these two DMM
    documents are being reviewed together:
    * draft-ietf-dmm-distributed-mobility-anchoring-14
    * draft-ietf-dmm-pmipv6-dlif-05
    
    This document defines distributed mobility anchoring, in terms of the
    different configurations and functions to provide IP mobility support,
    including network-based or host-based mobility support.
    
    The intended status is Informational. It is a very well written and
    comprehensive document. It is technically sound.
    
    No major or minor issues.
    
    Nits:
    
    A set of small nits for your consideration.
    
    1.  Introduction
    
       As a Mobile Node (MN) attaches to an access router and establishes a
       link between them, a /64 IPv6 prefix anchored to the router may be
       assigned to the link for exclusive use by the MN [RFC6459].  The MN
       may then configure a global IPv6 address from this prefix and use it
       as the source IP address in a flow to communicate with its
       correspondent node (CN).
    
    Capitalize:
    s/correspondent node/Correspondent Node/
    
    2.  Conventions and Terminology
    
       These include terms such as mobile node (MN), correspondent node
       (CN), home agent (HA), home address (HoA), care-of-address (CoA),
       local mobility anchor (LMA), and mobile access gateway (MAG).
    
    Capitalize “Mobile Node” (as per § 1), “Corespondent Node”, etc.
    
    Similar within this same § 2, “mobile router”, etc.
    Same throughout the document (e.g., “router advertisement (RA)”)
    
    4.3.  Mobility case, anchor relocation
    
       The IP prefix/address anchoring may move without changing the IP
       prefix/address of the flow.  Here the LM and FM functions in Figure 1
       in Section 3.1 are implemented as shown in Figure 7.
    
    “Figure 1 in Section 3.1.1 are implemented”
    
                             Figure 7: Anchor mobility
    
    Should this figure’s label be “Anchor Relocation” instead of ‘Anchor mobility”?
    
    5.  Security Considerations
    
       As stated in [RFC7333], "a DMM solution MUST supportany security
    
    s/supportany/support any/
    
    8.2. Informative References
    
    The relationship of this document and draft-ietf-dmm-deployment-models is
    mostly clear, thank you for that.
    
    I hope you fid these comments useful.
    
    Carlos Pignataro.