Re: [netext] Consensus call: Adopt I-D draft-bernardos-netext-pmipv6-flowmob-03 as Netext WG doc?

Raj,
May I ask a question regarding the process? You claim the issues are not show stoppers. Let's assume we proceed and handle them in the data tracker to dissatisfaction of the people raising them. What then? How would you achieve progress then?

Stefano Faccin

Standards Manager
Research In Motion Corporation 
5000 Riverside Drive 
Building 6, Brazos East, Ste. 100
Irving, Texas 75039 USA 
Note: located in PST

Office: (972) 910 3451  
Internal: 820.63451
Mobile : (510) 230 8422
www.rim.com; www.blackberry.com 

 Consider the environment before printing.

-----Original Message-----
From: Basavaraj.Patil@nokia.com [mailto:Basavaraj.Patil@nokia.com] 
Sent: Friday, August 12, 2011 11:20 AM
To: Stefano Faccin
Cc: netext@ietf.org
Subject: Re: [netext] Consensus call: Adopt I-D draft-bernardos-netext-pmipv6-flowmob-03 as Netext WG doc?

Hi Stefano,

As I replied to Julien, I realize that we have discussed several aspects
of the I-D multiple times. But I do not believe there are issues which
could be termed as "fundamental" to the protocol.
Hence my suggestion would be for folks to raise these issues through the
tracker in a formal manner to ensure that they are resolved to the
satisfaction of all. Please take the time to frame your concerns and
issues on the ML and through the issue tracker.

-Raj

On 8/12/11 1:09 PM, "ext Stefano Faccin" <sfaccin@rim.com> wrote:

>Hello Raj,
>I cannot help but support Julien's view. He is correct that some points
>were raised not once, not twice, but several times, and have still not
>been addressed. 
>
>My answer to your question is
>
>> Q: Should we adopt as Netext WG I-D the document:
>> draft-bernardos-netext-pmipv6-flowmob-03 which will be used as the
>> starting point in specifying the flow mobility feature for Proxy
>> Mobile IPv6?
>>
>Yes  [    ]
>No    [ X ]
>
>Cheers,
>Stefano Faccin
>
>Standards Manager
>Research In Motion Corporation
>5000 Riverside Drive
>Building 6, Brazos East, Ste. 100
>Irving, Texas 75039 USA
>Note: located in PST
>
>Office: (972) 910 3451
>Internal: 820.63451
>Mobile : (510) 230 8422
>www.rim.com; www.blackberry.com
>
>
>
> Consider the environment before printing.
>
>
>
>On Wed, Aug 10, 2011 at 2:19 PM,  <Basavaraj.Patil@nokia.com> wrote:
>> Hello,
>>
>> At IETF81 the chairs made a proposal to adopt as WG I-D: Proxy Mobile
>>IPv6
>> Extensions to Support Flow Mobility
>> <draft-bernardos-netext-pmipv6-flowmob-03> As the starting point for
>> the specification defining flow mobility for Proxy Mobile IPv6.
>> We gauged support for and against adopting this I-D at the IETF81 WG
>> meeting with the following result:
>>
>> In favor: 18
>> Opposed: None
>>
>> As per process we are following up on the mailing list with the same
>> question. Please respond by Aug 18th, 2011 to the question below:
>>
>> Q: Should we adopt as Netext WG I-D the document:
>> draft-bernardos-netext-pmipv6-flowmob-03 which will be used as the
>> starting point in specifying the flow mobility feature for Proxy
>> Mobile IPv6?
>>
>> Yes   [ ]
>> No    [ ]
>>
>>
>> -Chairs
>>
>> IETF81 WG minutes are posted at:
>> http://www.ietf.org/proceedings/81/minutes/netext.txt
>>
>> _______________________________________________
>> netext mailing list
>> netext@ietf.org
>> https://www.ietf.org/mailman/listinfo/netext
>>
>_______________________________________________
>netext mailing list
>netext@ietf.org
>https://www.ietf.org/mailman/listinfo/netext
>
>---------------------------------------------------------------------
>This transmission (including any attachments) may contain confidential
>information, privileged material (including material protected by the
>solicitor-client or other applicable privileges), or constitute
>non-public information. Any use of this information by anyone other than
>the intended recipient is prohibited. If you have received this
>transmission in error, please immediately reply to the sender and delete
>this information from your system. Use, dissemination, distribution, or
>reproduction of this transmission by unintended recipients is not
>authorized and may be unlawful.

---------------------------------------------------------------------
This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful.