Re: [MEXT] automotive reqs WG item

"Charles E. Perkins" <charles.perkins@earthlink.net> Mon, 07 November 2011 20:43 UTC

Return-Path: <charles.perkins@earthlink.net>
X-Original-To: mext@ietfa.amsl.com
Delivered-To: mext@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4515411E80D2 for <mext@ietfa.amsl.com>; Mon, 7 Nov 2011 12:43:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.336
X-Spam-Level:
X-Spam-Status: No, score=-2.336 tagged_above=-999 required=5 tests=[AWL=0.036, BAYES_00=-2.599, SARE_SUB_OBFU_Q1=0.227]
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 4kQky7Sbtvpg for <mext@ietfa.amsl.com>; Mon, 7 Nov 2011 12:43:02 -0800 (PST)
Received: from elasmtp-dupuy.atl.sa.earthlink.net (elasmtp-dupuy.atl.sa.earthlink.net [209.86.89.62]) by ietfa.amsl.com (Postfix) with ESMTP id 62E0711E80A6 for <mext@ietf.org>; Mon, 7 Nov 2011 12:43:02 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=Vj401QqF2ARIWrRevBfyNoe0vApLCE2/jyj6mWibpjvjsR2WnLAqei3P0fJwApKu; h=Received:Message-ID:Date:From:Organization:User-Agent:MIME-Version:To:CC:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP;
Received: from [138.111.58.2] (helo=[172.17.96.136]) by elasmtp-dupuy.atl.sa.earthlink.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from <charles.perkins@earthlink.net>) id 1RNW1z-0005Nx-Dw; Mon, 07 Nov 2011 15:42:59 -0500
Message-ID: <4EB842CE.5090202@earthlink.net>
Date: Mon, 07 Nov 2011 12:42:54 -0800
From: "Charles E. Perkins" <charles.perkins@earthlink.net>
Organization: Wichorus Inc.
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1
MIME-Version: 1.0
To: Basavaraj.Patil@nokia.com
References: <CADD9616.15355%basavaraj.patil@nokia.com>
In-Reply-To: <CADD9616.15355%basavaraj.patil@nokia.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 8bit
X-ELNK-Trace: 137d7d78656ed6919973fd6a8f21c4f2d780f4a490ca6956d5d4673fe7faad8604b48cbb0eb47f4864f28d83afca0ab2350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 138.111.58.2
Cc: mext@ietf.org
Subject: Re: [MEXT] automotive reqs WG item
X-BeenThere: mext@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Mobile IPv6 EXTensions WG <mext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mext>, <mailto:mext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mext>
List-Post: <mailto:mext@ietf.org>
List-Help: <mailto:mext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mext>, <mailto:mext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 07 Nov 2011 20:43:03 -0000

Hello Raj,

Not disagreeing that a BOF would be useful, but
I'm wondering whether the requirements as laid out
in the expired Internet Draft would fit in a single
working group.  The distinction between IP-based
and C2C-CC-based applications would probably need
a very contentious BOF, just on that single issue.
There have been so many failed proposals to replace
TCP, that it's hard to avoid skepticism for this one.

Anyway, I'd have more confidence that a BOF which was
restricted to just the mobility part of the problem
might get some useful results.

Regards,
Charlie P.




On 11/7/2011 12:06 PM, Basavaraj.Patil@nokia.com wrote:
>
>
> On 11/7/11 9:52 AM, "ext karagian@cs.utwente.nl"<karagian@cs.utwente.nl>
> wrote:
>
>> Hi all,
>>
>> I agree with Alex and Thierry on this issue!
>> Where is the best place at the IETF to discuss and work out automotive
>> requirements?
>
> Maybe it would be worthwhile to organize a BoF and consider the potential
> for a separate WG since the automotive requirements are not just mobility
> related.
>
> -Raj
>
>>
>> Best regards,
>> Georgios
>>
>>> -----Original Message-----
>>> From: mext-bounces@ietf.org [mailto:mext-bounces@ietf.org] On Behalf Of
>>> Thierry Ernst
>>> Sent: maandag 7 november 2011 14:17
>>> To: mext@ietf.org
>>> Subject: Re: [MEXT] automotive reqs WG item
>>>
>>>
>>> Thanks Alex for raising this.
>>>
>>> My view on this is that the automotive industry has some needs that are
>>> partly related to NEMO RO, but not only related to NEMO.
>>>
>>> So, I would like to seek advice from our AD about where would be the
>>> best
>>> place at the IETF to discuss automotive requirements related to IPv6 ?
>>>
>>> Regarding the dratf itself, it is our intention to update it.
>>>
>>> Regards,
>>> Thierry
>>>
>>>
>>>
>>>
>>>
>>>
>>> On 07/11/11 14:06, Alexandru Petrescu wrote:
>>>> Hello Jari, WG members,
>>>>
>>>>
>>>> Le 28/10/2011 14:08, Jari Arkko a écrit :
>>>>> All,
>>>>>
>>>>> We are making some changes to the working group. While we have
>>>>> successfully published a large number of specifications in recent
>>>>> years, recently it has been difficult to make progress in the group.
>>>>> The chairs and ADs have looked at the situation and we believe we
>>>>> need a new focus and a bit of new organization as well. We are
>>>>> terminating the working group and moving the one remaining active
>>>>> work item to a new working group, the "DMM" working group. Here's
>>>>> what is going to happen:
>>>>>
>>>>> o Jouni Korhonen and Julien Laganier will become the chairs of the
>>>>> group.
>>>>>
>>>>> o The group will meet in Taipei (there is a MEXT slot in the agenda).
>>>>>
>>>>> o The charter of the group will be changed to focus only on the
>>>>> distributed mobility effort. We should discuss the details of this
>>>>> charter change both on the list and in the meeting. The meeting
>>>>> agenda should reserve some time both for technical discussions as
>>>>> well as the charter discussion.
>>>>>
>>>>> o Once the discussion on the list and in the meeting has finished, we
>>>>> will rename the group to "DMM" and put the new charter in effect.
>>>>>
>>>>> o If there are any other specifications that people would like to
>>>>> publish beyond the distributed mobility work, we can offer to AD
>>>>> sponsor them to RFCs outside the new working group.
>>>>
>>>> I wonder what is the plan about
>>>> draft-ietf-mext-nemo-ro-automotive-req-02? "Automotive Industry
>>>> Requirements for NEMO Route Optimization"
>>>> http://tools.ietf.org/html/draft-ietf-mext-nemo-ro-automotive-req-02
>>>>
>>>> I can see a number of options to move it forward, like for example:
>>>> - change in authorship, title.
>>>> - continue as part of new Charter (fulfill earlier objectives) or
>>>>    sponsor separately per your offer.
>>>> - change in focus.
>>>>
>>>> What do you think?
>>>>
>>>> Alex
>>>>
>>>>> If there is some significant new activity, we can create new working
>>>>> groups for that.
>>>>
>>>>
>>>>>
>>>>> Comments and feedback and/or alternate suggestions on this plan are
>>>>> welcome.
>>>>>
>>>>> We would like to thank Marcelo for your many years of service in
>>>>> MEXT. We could not have completed all the work we did without your
>>>>> energy and push for high quality results. We would also like to thank
>>>>> Jouni for taking on this new challenge, and Julien for continuing the
>>>>> work in this space.
>>>>>
>>>>> Jari and Ralph
>>>>>
>>>>> _______________________________________________ MEXT
>>> mailing list
>>>>> MEXT@ietf.org https://www.ietf.org/mailman/listinfo/mext
>>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> MEXT mailing list
>>>> MEXT@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/mext
>>
>> _______________________________________________
>> MEXT mailing list
>> MEXT@ietf.org
>> https://www.ietf.org/mailman/listinfo/mext
>
> _______________________________________________
> MEXT mailing list
> MEXT@ietf.org
> https://www.ietf.org/mailman/listinfo/mext
>