IETF Logo Mail Archive

Re: [Roll] Last Call: <draft-ietf-roll-trickle-mcast-05.txt> (Multicast Protocol for Low power and Lossy Networks (MPL)) to Proposed Standard

"Ralph Droms (rdroms)" <rdroms@cisco.com> Fri, 25 October 2013 19:56 UTC

Return-Path: <rdroms@cisco.com>
X-Original-To: roll@ietfa.amsl.com
Delivered-To: roll@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 15B6E11E81CF; Fri, 25 Oct 2013 12:56:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level:
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vM3MTXPOvVWj; Fri, 25 Oct 2013 12:56:46 -0700 (PDT)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) by ietfa.amsl.com (Postfix) with ESMTP id 3B01B11E81CB; Fri, 25 Oct 2013 12:56:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2095; q=dns/txt; s=iport; t=1382731003; x=1383940603; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=1LWoRS4K09YN3RZ7H0On+224HuK6MVj3iNgzQKwe+Hk=; b=BqUjDoZx4sOHb3825q6wt3CmmIsgrJjEzuOBm+c0Hm3siaY6vJtYPPSC +QsG+bDMC83+iNKlOQN5zUaRDkiBwmGrgP5UgAie516lLYyDds0Beab7g aJXyzRAfEGQq8YFhOPgl5Do8LpNm6kFrsEIf1QE3N0UK7ByVSWToDwoMM 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgsFAGvMalKtJV2Z/2dsb2JhbABZgweBDL5IgSMWdIImAQEEOjQLEAIBCCIUBQsyJQIEDgUIh3+5VI4bgQUCMQeDH4ENA6oRgWiBPoIq
X-IronPort-AV: E=Sophos;i="4.93,572,1378857600"; d="scan'208";a="273781249"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by rcdn-iport-9.cisco.com with ESMTP; 25 Oct 2013 19:56:42 +0000
Received: from xhc-rcd-x04.cisco.com (xhc-rcd-x04.cisco.com [173.37.183.78]) by rcdn-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id r9PJug6M029987 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 25 Oct 2013 19:56:42 GMT
Received: from xmb-aln-x04.cisco.com ([169.254.9.229]) by xhc-rcd-x04.cisco.com ([fe80::200:5efe:173.37.183.34%12]) with mapi id 14.02.0318.004; Fri, 25 Oct 2013 14:56:42 -0500
From: "Ralph Droms (rdroms)" <rdroms@cisco.com>
To: "ietf@ietf.org list" <ietf@ietf.org>
Thread-Topic: Last Call: <draft-ietf-roll-trickle-mcast-05.txt> (Multicast Protocol for Low power and Lossy Networks (MPL)) to Proposed Standard
Thread-Index: AQHO0bxTB8hb4i6HYEmq/bFuLj8olw==
Date: Fri, 25 Oct 2013 19:56:42 +0000
Message-ID: <4518F39EB578034D8C99A9B7776CDBA301C0651B@xmb-aln-x04.cisco.com>
References: <20131010221713.891.32620.idtracker@ietfa.amsl.com> <B594A37B-51F9-44FD-9E45-56D273657E89@gmail.com>
In-Reply-To: <B594A37B-51F9-44FD-9E45-56D273657E89@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [161.44.68.183]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <7980C149C96C0545807856C9D47B5268@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "roll@ietf.org" <roll@ietf.org>
Subject: Re: [Roll] Last Call: <draft-ietf-roll-trickle-mcast-05.txt> (Multicast Protocol for Low power and Lossy Networks (MPL)) to Proposed Standard
X-BeenThere: roll@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Fri, 25 Oct 2013 19:56:53 -0000

There was a long discussion about this issue on the roll@ietf.org mailing list:

draft-ietf-roll-trickle-mcast-05 and draft-ietf-6man-multicast-scopes-00 are in conflict with each other.

>From draft-ietf-roll-trickle-mcast-05:

  When
  used with MPL, Realm-Local scope is administratively defined and used
  to define the boundaries of multicast message dissemination by MPL.

>From draft-ietf-6man-multicast-scopes-00:

  Realm-Local scope is the largest scope that is automatically
  configured, i.e., automatically derived from physical
  connectivity or other, non-multicast-related configuration.

Specifically, "administratively defined" seems to me to be in direct
conflict with "automatically configured". 

I think I've read consensus in the various discussion threads to make the following change to draft-ietf-roll-trickle-mcast-05:

OLD:

   When
   used with MPL, Realm-Local scope is administratively defined and used
   to define the boundaries of multicast message dissemination by MPL.

NEW:

   When
   used with MPL, Realm-Local scope is defined according to the
   underlying network technology; for example, [cite the
   IP-over-IEEE802.15.4 definition].

where "the IP-over-IEEE802.15.4 definition" is text to be published elsewhere (perhaps draft-ietf-6man-multicast-scopes) that defines scop 3 for IEEE802.15.4 mesh networks.

I read less strong consensus (less discussion) of the following proposed changes:

NEW (to be added immediately following text describing the use of Realm-Local scope):

  Admin-Local scope (scop value 4) can also be used with MPL
  in deployments that use administratively defined scopes that
  cover, for example, multiple subnets based on different
  underlying network technologies.

As a side note, there is a related discussion about draft-ietf-6man-multicast-scopes on the 6man@ietf.org mailing list.  The term "Realm-Local scope" may change (should be changed for consistency with) the final published version of draft-ietf-6man-multicast-scopes.

- Ralph

v2.23.0 | Report a Bug | By Email