Re: [DMM] Call for adoption confirmation: draft-seite-dmm-rg-multihoming-02

"Sri Gundavelli (sgundave)" <sgundave@cisco.com> Thu, 03 December 2015 19:45 UTC

Return-Path: <sgundave@cisco.com>
X-Original-To: dmm@ietfa.amsl.com
Delivered-To: dmm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 437291A1AA1 for <dmm@ietfa.amsl.com>; Thu, 3 Dec 2015 11:45:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -13.911
X-Spam-Level:
X-Spam-Status: No, score=-13.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, J_CHICKENPOX_65=0.6, 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 GkqL3vc7kZSB for <dmm@ietfa.amsl.com>; Thu, 3 Dec 2015 11:45:07 -0800 (PST)
Received: from alln-iport-7.cisco.com (alln-iport-7.cisco.com [173.37.142.94]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 399DC1A0354 for <dmm@ietf.org>; Thu, 3 Dec 2015 11:45:07 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=5188; q=dns/txt; s=iport; t=1449171907; x=1450381507; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=/YMbCu73lvP8XHhnLYuxEVJ8uEAFfEBUUVFMxqC10nc=; b=YCNHtZ/UogAMoxRroqxXXGH//7RDC87Yu+ujx39g2uaq8l+tf0Rqszw1 5APJDic1XntLyrSr5Hu7Kyj7jHAX44z3DD5VhDTGMBV5DB2zE250r4xpe 9DJ9mu+9gpg/XxrF2zFzZhIsfDIv+nFVolDlnZpR5SgeoDPx9HELxAD4n M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0D/AQBbm2BW/5hdJa1egzpTbga9PAENgW4XCoVtAoFOOBQBAQEBAQEBgQqENAEBAQMBAQEBGh00CwULAgEIGB4QIQYLJQIEAQ0FG4d/AwoIDb0cDYRFAQEBAQEBAQEBAQEBAQEBAQEBAQEBGIZUhH2CU4ZoBZZhAYUshhiBd4FbSYN6iXKFBINng3EBHwEBQoIRHYFWcoRogQcBAQE
X-IronPort-AV: E=Sophos;i="5.20,378,1444694400"; d="scan'208";a="214593828"
Received: from rcdn-core-1.cisco.com ([173.37.93.152]) by alln-iport-7.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 03 Dec 2015 19:45:06 +0000
Received: from XCH-ALN-007.cisco.com (xch-aln-007.cisco.com [173.36.7.17]) by rcdn-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id tB3Jj6lo031773 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 3 Dec 2015 19:45:06 GMT
Received: from xch-aln-007.cisco.com (173.36.7.17) by XCH-ALN-007.cisco.com (173.36.7.17) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Thu, 3 Dec 2015 13:45:05 -0600
Received: from xch-aln-007.cisco.com ([173.36.7.17]) by XCH-ALN-007.cisco.com ([173.36.7.17]) with mapi id 15.00.1104.000; Thu, 3 Dec 2015 13:45:05 -0600
From: "Sri Gundavelli (sgundave)" <sgundave@cisco.com>
To: Jouni Korhonen <jouni.nospam@gmail.com>, "sarikaya@ieee.org" <sarikaya@ieee.org>
Thread-Topic: [DMM] Call for adoption confirmation: draft-seite-dmm-rg-multihoming-02
Thread-Index: AQHRLTP5U3hBilgf70Wa8tixkDuZPp64ilyAgAF06YCAAA8wAP//e9EA
Date: Thu, 03 Dec 2015 19:45:05 +0000
Message-ID: <D285DA4C.1C6DA6%sgundave@cisco.com>
References: <tencent_3D1069622110DFAF00D8DB64@qq.com> <CAKcc6Ae9McC_rrfv2mbvY1DdxO-Vj0exjjD0YPoPfD_sRi0c3A@mail.gmail.com> <565E3E35.9020707@gmail.com> <CAC8QAcf4ocbmpW2uOu3grBgceX-qJyHdVj3Ws-Mp3SVcXu94fw@mail.gmail.com> <565F5493.6060402@gmail.com> <CAC8QAcfa7ZePyN1Yfw-wLC9BNk_2rjmuxSYU3kr83yBdLis-nw@mail.gmail.com> <56609A22.7020103@gmail.com>
In-Reply-To: <56609A22.7020103@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.5.7.151005
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.152.21.158]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <51D73C7FBB49FF40A0CAB4E9BEEC6C47@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/dmm/3bExbtxL5ad53r-7GUuGHsdG7ZY>
Cc: dmm <dmm@ietf.org>
Subject: Re: [DMM] Call for adoption confirmation: draft-seite-dmm-rg-multihoming-02
X-BeenThere: dmm@ietf.org
X-Mailman-Version: 2.1.15
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: Thu, 03 Dec 2015 19:45:09 -0000

> For me (as an individual contributor) the I-D gives a standard way to
>register multiple transport connections/tunnels between a MAG and a LMA,
potentially over different technologies (wired, wireless, ..) on the
transport network side without needing to rely on engineering solutions


Ack. MAG's ability to register multiple IP transport end points is a basic
protocol semantic which is always present in enterprise architectures.

Problem with this thread it confuses the hell out of every thing. You
cannot explain and you cannot have a meaningful conversation. Pierrick
gave up and now I give up. But, this is not new; WG after WG, same folks
and same pattern.



Sri











On 12/3/15 11:38 AM, "dmm on behalf of Jouni Korhonen"
<dmm-bounces@ietf.org on behalf of jouni.nospam@gmail.com> wrote:

>Behcet,
>
>12/3/2015, 10:43 AM, Behcet Sarikaya kirjoitti:
>> Hi Jouni,
>>
>> On Wed, Dec 2, 2015 at 2:29 PM, Jouni Korhonen <jouni.nospam@gmail.com>
>>wrote:
>>> Behcet,
>>>
>>> 12/2/2015, 11:02 AM, Behcet Sarikaya kirjoitti:
>>>>
>>>> Hi Jouni,
>>>>
>>>>
>>>> On Tue, Dec 1, 2015 at 6:41 PM, Jouni Korhonen
>>>><jouni.nospam@gmail.com>
>>>> wrote:
>>>>>
>>>>> As an individual contributor I support the adoption of this I-D.
>>>>>MCoA is
>>>>> a
>>>>> feature that we still lack..
>>>>>
>>>>
>>>> Are you sure?
>>>>
>>>> MCoA is solved in Netext Flow Mobility draft,
>>>>
>>>> draft-ietf-netext-pmipv6-flowmob-14
>>>>
>>>> is the latest draft.
>>>
>>>
>>> Sorry for my improper wording regarding which part of the MCoA I
>>>meant. I
>>> don't see how draft-ietf-netext-pmipv6-flowmob-14 would handle the
>>>case of
>>> registration when the Proxy-CoAs are from the same MAG.
>>
>> I wonder why would that be needed?
>> MN doesn't need it.
>> So this draft seems to be addressing a non-problem.
>
>I'll let the WG to determine whether the feature is needed or not.
>
>For me (as an individual contributor) the I-D gives a standard way to
>register multiple transport connections/tunnels between a MAG and a LMA,
>potentially over different technologies (wired, wireless, ..) on the
>transport network side without needing to rely on engineering solutions
>to achieve the same (yes - I could do a somewhat similar solution e.g.
>using MPLS but that would then be loaded with all kinds of assumptions
>that may or may not work in multi vendor and cross operator environment).
>
>- JOuni
>
>>
>> Regards,
>>
>> Behcet
>>> The netext draft
>>> specifically states Proxy-CoAs are from different MAGs.
>>>
>>> But it was a good thing you brought this up. The two I-Ds need to be in
>>> sync.
>>>
>>>>
>>>> BTW there was an issue in WG adoption call in IETF 93 in Yokohama. The
>>>
>>>
>>> IETF 94 I presume.. AFAIR we did not ask for adoption in IETF 93.
>>>
>>>> chair asked only those who accept. The chair unfortunately did not ask
>>>> those who oppose.
>>>>
>>>> As you know, if the chair wishes to ask a single question then the
>>>> right one is any opposes.
>>>
>>>
>>> Obviously you are right here but I cannot really comment on this what
>>> happened in Yokohama since I was not on site or not even participating
>>> remotely.
>>>
>>> Anyway, all adoption calls are confirmed on the mailing list and the
>>>"sense
>>> of the room" during the meeting merely serves as informative quidance
>>>for
>>> chairs.
>>>
>>> - Jouni
>>>
>>>
>>>>
>>>> Regards,
>>>>
>>>> Behcet
>>>>>
>>>>> The document itself still needs quite a bit of work. For example, I
>>>>> wonder
>>>>> if the caption for Figure 2 is correct. Also, Section 4.1. option
>>>>>fiels
>>>>> descriptions are somewhat broken it seems. And so on multiple small
>>>>>nits
>>>>> like unexpanded acronyms etc. However, these are mainly editorials. I
>>>>> have
>>>>> no problem with the technical solution.
>>>>>
>>>>> - Jouni
>>>>>
>>>>>
>>>>>
>>>>> 11/25/2015, 8:22 AM, Dapeng Liu kirjoitti:
>>>>>>
>>>>>>
>>>>>> Hello all,
>>>>>>
>>>>>> In IETF94, we initiated the call for adoption for the draft:
>>>>>> draft-seite-dmm-rg-multihoming-02
>>>>>> <http://tools.ietf.org/html/draft-seite-dmm-rg-multihoming-02>:
>>>>>> http://tools.ietf.org/html/draft-seite-dmm-rg-multihoming-02
>>>>>> Seems have got sufficient support during the meeting. We'd like to
>>>>>> confirm the call for adoption in the mailing list for 2 weeks.
>>>>>> Please send your opinion and comments to the list before December 9.
>>>>>>
>>>>>>
>>>>>> Thanks,
>>>>>> ------
>>>>>> Best Regards,
>>>>>> Dapeng&Jouni
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>>
>>>>>> ------
>>>>>> Best Regards,
>>>>>> Dapeng Liu
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> dmm mailing list
>>>>>> dmm@ietf.org
>>>>>> https://www.ietf.org/mailman/listinfo/dmm
>>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> dmm mailing list
>>>>> dmm@ietf.org
>>>>> https://www.ietf.org/mailman/listinfo/dmm
>
>_______________________________________________
>dmm mailing list
>dmm@ietf.org
>https://www.ietf.org/mailman/listinfo/dmm