IETF Logo Mail Archive

Re: [mif] FW: New Version Notification for draft-reddy-mif-dhcpv6-precedence-ops-02.txt

Arifumi Matsumoto <arifumi@nttv6.net> Thu, 25 October 2012 10:26 UTC

Return-Path: <n@arifumi.net>
X-Original-To: mif@ietfa.amsl.com
Delivered-To: mif@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8C13C21F8962 for <mif@ietfa.amsl.com>; Thu, 25 Oct 2012 03:26:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.977
X-Spam-Level:
X-Spam-Status: No, score=-102.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id c1odR++C4g-F for <mif@ietfa.amsl.com>; Thu, 25 Oct 2012 03:26:55 -0700 (PDT)
Received: from mail-la0-f44.google.com (mail-la0-f44.google.com [209.85.215.44]) by ietfa.amsl.com (Postfix) with ESMTP id A3DB221F893B for <mif@ietf.org>; Thu, 25 Oct 2012 03:26:54 -0700 (PDT)
Received: by mail-la0-f44.google.com with SMTP id b11so1414019lam.31 for <mif@ietf.org>; Thu, 25 Oct 2012 03:26:53 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:sender:x-originating-ip:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :x-gm-message-state; bh=B5OSYeqgXshAlVsI1xC402YB14nArGxVrCEOU8MRrls=; b=pSJW1tCBjOH3CZCw6tSn6Jdw6yLDTd28PRavbknhZFwNglggvEMkV5ZFeoe0F2ZT3Z edGP42urA8ntprbYu1TFhLr8bQRjbnFpTL4zT2PyKPedxhIgcClezjhlkYd2T2MHky39 JJZ0Ceg6E7Hx2Af/GlVq4RWH2efuoRDYXW3JRXSqBWSJBRnr222DVfK6ZZMYa4qXXlV/ 0mckPnXkAo9y8nLfMp/3Rpa23CCsRINEjHVwkY1yca+M1UGkj0TTxL6d+nP9XyMDFi/F TDlR64A19qWCI4QZ79psM3HkpWMsto4sYru7/e3NWewF96AlbhT64LRgh+32yaa0SKck YOJQ==
MIME-Version: 1.0
Received: by 10.152.109.145 with SMTP id hs17mr17377151lab.5.1351160813545; Thu, 25 Oct 2012 03:26:53 -0700 (PDT)
Sender: n@arifumi.net
Received: by 10.114.64.16 with HTTP; Thu, 25 Oct 2012 03:26:53 -0700 (PDT)
X-Originating-IP: [2001:df0:45:20::61]
In-Reply-To: <CAKD1Yr1Y_u9dZQuD2jDHJyGpoO7ue9gy3XbthbN+e0LMQtDgCg@mail.gmail.com>
References: <913383AAA69FF945B8F946018B75898A1480EDFA@xmb-rcd-x10.cisco.com> <CAKD1Yr1Y_u9dZQuD2jDHJyGpoO7ue9gy3XbthbN+e0LMQtDgCg@mail.gmail.com>
Date: Thu, 25 Oct 2012 19:26:53 +0900
X-Google-Sender-Auth: GESW8FQzy_xTpa-b-cqWL-dFAsc
Message-ID: <CABTuw1C+iV3a36q916+g3O7ttw0mDNL42gcprpOqvesHQuy9cw@mail.gmail.com>
From: Arifumi Matsumoto <arifumi@nttv6.net>
To: Lorenzo Colitti <lorenzo@google.com>
Content-Type: text/plain; charset="ISO-8859-1"
X-Gm-Message-State: ALoCoQmwOh9gp/DlNunwyNAKLSKRJT2hzJjC6MyWWp6p5gRYp725xjhURgmKUkoOt1rFKprz67J6
Cc: "mif@ietf.org" <mif@ietf.org>, "Tirumaleswar Reddy (tireddy)" <tireddy@cisco.com>
Subject: Re: [mif] FW: New Version Notification for draft-reddy-mif-dhcpv6-precedence-ops-02.txt
X-BeenThere: mif@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Multiple Interface Discussion List <mif.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mif>, <mailto:mif-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mif>
List-Post: <mailto:mif@ietf.org>
List-Help: <mailto:mif-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mif>, <mailto:mif-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Oct 2012 10:26:55 -0000

Hi,

2012/10/24 Lorenzo Colitti <lorenzo@google.com>:

> As regards the address selection option specifically:
>
> 1. The option itself is still work in progress in 6man. So the modifications
> should happen in 6man, not here. Otherwise we will have two working groups
> working on the same option which is likely to have bad results.
> 3. I don't understand the use case (Section 3.1). If the DHCPv6 relay is in
> the mobile access gateway, then it's in the mobile operator's network. If
> it's in the mobile operator's network, then how can it "influence the DHCPv6
> Server in the home network"? In general, the DHCPv6 server in the home
> network has no way of talking to the mobile operator's network.

It looks to me this is not the modifications to the address selection option
happening in 6man, but it is another proposal for tweaking DHCPv6 messages
from clients at DHCP relay agent.

So, in other words, this option just depends on the address selection option.
If it is true, a work that depends on another work can be done separately in
a separate wg.

I do not know whether mif is the right place for this proposal, but generally
speaking it is the right place where the scope and motivation matche best.

Thanks.

v2.23.0 | Report a Bug | By Email