Re: [v6ops] draft-ietf-dhc-pd-exclude

jouni korhonen <jouni.nospam@gmail.com> Wed, 14 December 2011 09:22 UTC

Return-Path: <jouni.nospam@gmail.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1401E21F8B24 for <v6ops@ietfa.amsl.com>; Wed, 14 Dec 2011 01:22:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level:
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 YeZpHALVv9g8 for <v6ops@ietfa.amsl.com>; Wed, 14 Dec 2011 01:22:29 -0800 (PST)
Received: from mail-ee0-f44.google.com (mail-ee0-f44.google.com [74.125.83.44]) by ietfa.amsl.com (Postfix) with ESMTP id 607C221F8B1D for <v6ops@ietf.org>; Wed, 14 Dec 2011 01:22:29 -0800 (PST)
Received: by eeke49 with SMTP id e49so525830eek.31 for <v6ops@ietf.org>; Wed, 14 Dec 2011 01:22:28 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=content-type:mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to:x-mailer; bh=2P189mO+y178ZSGWnj534hEkjopVPtBN+JsAhvSGeDM=; b=tSQhZRBcpxLwukRb7YiMFWdXhsDLiQdb4ghuX/cS5Zw4ZDLDxpYogYIEEjg2NoH5F4 PYUSajX8OedqzuRi0mG5Sp4lIlSflVhMlAe+UJu+FKrlus5wi1N/MRhc8iV5bnEE4S8S ihlRs1bhUiMwTdJJVyhWv6gSCFABasMCChamQ=
Received: by 10.213.17.198 with SMTP id t6mr378784eba.13.1323854548489; Wed, 14 Dec 2011 01:22:28 -0800 (PST)
Received: from [10.45.197.110] ([188.238.197.110]) by mx.google.com with ESMTPS id j20sm8013252eej.8.2011.12.14.01.22.23 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 14 Dec 2011 01:22:26 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Apple Message framework v1084)
From: jouni korhonen <jouni.nospam@gmail.com>
In-Reply-To: <CAKD1Yr0ngNaoOYJ86RoozZv+mZfb8dKXyEPP9NhgJHE4VLz=dQ@mail.gmail.com>
Date: Wed, 14 Dec 2011 11:22:19 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <73C15E41-A377-4094-86BD-62B4BD9E8AB6@gmail.com>
References: <CABmgDzR9eVRaUJOAcf_TXcXVJJfWk5kof7JvEMpWmTwcpktxCg@mail.gmail.com> <OF51F6250C.40961A0F-ON85257961.005889C2-85257961.0058C1A7@videotron.com> <5B6B2B64C9FE2A489045EEEADDAFF2C3038291E2@XMB-RCD-109.cisco.com> <20111209162751.GL72014@Space.Net> <5B6B2B64C9FE2A489045EEEADDAFF2C3038291F1@XMB-RCD-109.cisco.com> <20111209163935.GM72014@Space.Net> <5B6B2B64C9FE2A489045EEEADDAFF2C303829251@XMB-RCD-109.cisco.com> <5B6B2B64C9FE2A489045EEEADDAFF2C30382943B@XMB-RCD-109.cisco.com> <CAKD1Yr3Lu9ENa7kuEMgu7e-36OPg4iB3VxD7QvKPN8=Ykvfg6A@mail.gmail.com> <5B6B2B64C9FE2A489045EEEADDAFF2C3038298F6@XMB-RCD-109.cisco.com> <92DE244D-4F26-4CF9-98F0-2DB90CED4A43@steffann.nl> <00F796E0-82BE-4B26-8450-2BB42115B19A@gmail.com> <5B6B2B64C9FE2A489045EEEADDAFF2C3038E528F@XMB-RCD-109.cisco.com> <CAKD1Yr0ngNaoOYJ86RoozZv+mZfb8dKXyEPP9NhgJHE4VLz=dQ@mail.gmail.com>
To: "v6ops@ietf.org Operations" <v6ops@ietf.org>
X-Mailer: Apple Mail (2.1084)
Subject: Re: [v6ops] draft-ietf-dhc-pd-exclude
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Dec 2011 09:22:30 -0000

Using Lorenzo's proposed wording:

"The solution provided in this document is intended for use in networks where each RR is on its own layer 2 domain."

Any better?

- Jouni


On Dec 14, 2011, at 5:43 AM, Lorenzo Colitti wrote:

> On Tue, Dec 13, 2011 at 08:51, Hemant Singh (shemant) <shemant@cisco.com> wrote:
> The semantics definitely include DHCPv6 and the pd-exclude option but it
> may be mistaken that the new option is good for use both in the unicast
> RA and the multicast RA network.  Thus it's best to preserve the keyword
> of "unicast RA".  One document I can find on the unicast RA is rfc6085.
> 
> Hemant, I think you're using the wrong terminology. As Ole says, where you say "multicast RA" you should say "a deployment where multiple CEs are on a shared layer 2 domain" (e.g., the N:1 model) and where you say "unicast RA" you should instead say "with a deployment where each CEs is on its own layer 2 domain".