Re: [Roll] Brian Haberman's Discuss on draft-ietf-roll-mpl-parameter-configuration-07: (with DISCUSS and COMMENT)
"Alvaro Retana (aretana)" <aretana@cisco.com> Wed, 11 November 2015 11:01 UTC
Return-Path: <aretana@cisco.com>
X-Original-To: roll@ietfa.amsl.com
Delivered-To: roll@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1444D1B3466; Wed, 11 Nov 2015 03:01:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level:
X-Spam-Status: No, score=-14.511 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, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 R5Ph8QEuTPnt; Wed, 11 Nov 2015 03:01:04 -0800 (PST)
Received: from alln-iport-1.cisco.com (alln-iport-1.cisco.com [173.37.142.88]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EEEFB1B3495; Wed, 11 Nov 2015 03:01:03 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3690; q=dns/txt; s=iport; t=1447239664; x=1448449264; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=TvRT7/LChXSgudqx/prB9DLDeX7JOZYYKzv48swz4c0=; b=Ota1G4PkTEReUDBgyx1x0pgQRS8t2pYgoHxsNWUnARSC5CTD2eX8BvjM 2AOpeajVi/8QFx4LZkggXKR1blW4ZyTvjPzUaDSeWundMdcxrm/E0KI5I cuC/1Tt395FT4/rH3eFnDwVtqmhypqMQ8KijdvHnO6KW0hSik9X1xiiJX U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AdAgAQH0NW/4oNJK1egztTbwa+LAENgWUXDIVtAoFFOBQBAQEBAQEBgQqENQEBBAEBATc0CxACAQgYHgULJwslAgQBDQWILg3ELAEBAQEBAQEBAQEBAQEBAQEBAQEBARQEhlQBhH2EKhEBUYQsBYdEiyODYQGFHIgJgVuEQJI4g3EBHwEBQoJEgUByAYQUOoEHAQEB
X-IronPort-AV: E=Sophos;i="5.20,275,1444694400"; d="scan'208";a="207402271"
Received: from alln-core-5.cisco.com ([173.36.13.138]) by alln-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 11 Nov 2015 11:01:03 +0000
Received: from XCH-ALN-002.cisco.com (xch-aln-002.cisco.com [173.36.7.12]) by alln-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id tABB128L013922 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 11 Nov 2015 11:01:02 GMT
Received: from xch-aln-002.cisco.com (173.36.7.12) by XCH-ALN-002.cisco.com (173.36.7.12) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Wed, 11 Nov 2015 05:01:02 -0600
Received: from xch-aln-002.cisco.com ([173.36.7.12]) by XCH-ALN-002.cisco.com ([173.36.7.12]) with mapi id 15.00.1104.000; Wed, 11 Nov 2015 05:01:02 -0600
From: "Alvaro Retana (aretana)" <aretana@cisco.com>
To: Brian Haberman <brian@innovationslab.net>, Yusuke DOI <yusuke.doi@toshiba.co.jp>, "roll@ietf.org" <roll@ietf.org>, "iesg@ietf.org" <iesg@ietf.org>
Thread-Topic: [Roll] Brian Haberman's Discuss on draft-ietf-roll-mpl-parameter-configuration-07: (with DISCUSS and COMMENT)
Thread-Index: AQHQ6w1uG0TVdJl4/UiEUhNQBkKB4Z5U/yiAgAC8EwCAQV/oAA==
Date: Wed, 11 Nov 2015 11:01:02 +0000
Message-ID: <D26889EF.E97A4%aretana@cisco.com>
References: <20150909143959.25684.48803.idtracker@ietfa.amsl.com> <560B72CB.5030305@toshiba.co.jp> <560C1090.4080503@innovationslab.net>
In-Reply-To: <560C1090.4080503@innovationslab.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.117.15.3]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <208CD007565C8B4981DD2452FB1599A5@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/roll/mMYYaBQnhtDV52fGjTKCbAytBaw>
Cc: "roll-chairs@ietf.org" <roll-chairs@ietf.org>, "draft-ietf-roll-mpl-parameter-configuration@ietf.org" <draft-ietf-roll-mpl-parameter-configuration@ietf.org>, "draft-ietf-roll-mpl-parameter-configuration.shepherd@ietf.org" <draft-ietf-roll-mpl-parameter-configuration.shepherd@ietf.org>, "maria.ines.robles@ericsson.com" <maria.ines.robles@ericsson.com>, "draft-ietf-roll-mpl-parameter-configuration.ad@ietf.org" <draft-ietf-roll-mpl-parameter-configuration.ad@ietf.org>
Subject: Re: [Roll] Brian Haberman's Discuss on draft-ietf-roll-mpl-parameter-configuration-07: (with DISCUSS and COMMENT)
X-BeenThere: roll@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: Routing Over Low power and Lossy networks <roll@ietf.org>
List-Id: Routing Over Low power and Lossy networks <roll.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/roll>, <mailto:roll-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/roll/>
List-Post: <mailto:roll@ietf.org>
List-Help: <mailto:roll-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/roll>, <mailto:roll-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 Nov 2015 11:01:06 -0000
On 9/30/15, 11:40 AM, "Brian Haberman" <brian@innovationslab.net> wrote: Brian: Hi! >These changes look good. -08 was posted last week with these changes. When you get a chance, please clear the DISCUSS. Thanks! Alvaro. > >Regards, >Brian > > >On 9/30/15 1:27 AM, Yusuke DOI wrote: >> Hi Brian, >> >> Thank you very much for your review! >> >>> ---------------------------------------------------------------------- >>> DISCUSS: >>> ---------------------------------------------------------------------- >> (snip) >>> 2. In section 2.3 (MPL Forwarder Behavior), there should be a brief >>> discussion of the role of the MPL Domain Address and include a >>>reference >>> to [I-D.ietf-roll-trickle-mcast]. >> (snip) >> >> Does the following text added on Section 2.3 looks good for you? >> >> >> """ >> If a DHCPv6 client requests and receives the MPL Parameter >> Configuration Option, the node SHOULD join the MPL domain given by >> the option and act as an MPL forwarder. Note that there may be cases >> in which a node may fail to join a domain (or domains) due to local >> resource constraints. Each joining node SHOULD configure its MPL >> forwarder with the given parameter set for the MPL domain. >> <added> >> Each MPL domain is defined by an MPL Domain Address given by an MPL >> Parameter Configuration Option. As defined in Section 2 of >> [I-D.ietf-roll-trickle-mcast], an MPL Domain Address is an IPv6 >> multicast address associated to a set of MPL network interfaces >> in an MPL Domain. >> </added> >> """ >> >>> ---------------------------------------------------------------------- >>> COMMENT: >>> ---------------------------------------------------------------------- >>> >>> - Why is the text in Appendix A not in the Operational Considerations >>> section? >> >> It's my another mistake. I'll move it on next revision (already merged >> as operational consideration on my local repo) >> >> Best Regards, >> >> // Yusuke DOI <yusuke.doi@toshiba.co.jp> >> >> On 2015-09-09 23:39, Brian Haberman wrote: >>> Brian Haberman has entered the following ballot position for >>> draft-ietf-roll-mpl-parameter-configuration-07: 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-roll-mpl-parameter-configura >>>tion/ >>> >>> >>> >>> >>> ---------------------------------------------------------------------- >>> DISCUSS: >>> ---------------------------------------------------------------------- >>> >>> Updated for -07... >>> >>> 1. Resolved >>> >>> 2. In section 2.3 (MPL Forwarder Behavior), there should be a brief >>> discussion of the role of the MPL Domain Address and include a >>>reference >>> to [I-D.ietf-roll-trickle-mcast]. >>> >>> 3. Resolved >>> >>> >>> ---------------------------------------------------------------------- >>> COMMENT: >>> ---------------------------------------------------------------------- >>> >>> - Why is the text in Appendix A not in the Operational Considerations >>> section? >>> >>> >>> _______________________________________________ >>> Roll mailing list >>> Roll@ietf.org >>> https://www.ietf.org/mailman/listinfo/roll >>> >> >
- [Roll] Brian Haberman's Discuss on draft-ietf-rol… Brian Haberman
- Re: [Roll] Brian Haberman's Discuss on draft-ietf… Yusuke DOI
- Re: [Roll] Brian Haberman's Discuss on draft-ietf… Brian Haberman
- Re: [Roll] Brian Haberman's Discuss on draft-ietf… Alvaro Retana (aretana)