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

Stefano Faccin <sfaccin@rim.com> Fri, 12 August 2011 18:56 UTC

Return-Path: <sfaccin@rim.com>
X-Original-To: netext@ietfa.amsl.com
Delivered-To: netext@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0E2AD11E8095 for <netext@ietfa.amsl.com>; Fri, 12 Aug 2011 11:56:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 Q4pYZ3mw1f-f for <netext@ietfa.amsl.com>; Fri, 12 Aug 2011 11:56:26 -0700 (PDT)
Received: from mhs060cnc.rim.net (mhs060cnc.rim.net [208.65.73.34]) by ietfa.amsl.com (Postfix) with ESMTP id 2AA7F11E8090 for <netext@ietf.org>; Fri, 12 Aug 2011 11:56:24 -0700 (PDT)
X-AuditID: 0a41282f-b7cd4ae0000005d0-48-4e45776e5972
Received: from XHT104CNC.rim.net (xht104cnc.rim.net [10.65.22.52]) (using TLS with cipher AES128-SHA (AES128-SHA/128 bits)) (Client did not present a certificate) by mhs060cnc.rim.net (SBG) with SMTP id 4A.AD.01488.E67754E4; Fri, 12 Aug 2011 18:56:46 +0000 (GMT)
Received: from XCT103ADS.rim.net (10.67.111.44) by XHT104CNC.rim.net (10.65.22.52) with Microsoft SMTP Server (TLS) id 8.3.159.2; Fri, 12 Aug 2011 14:57:01 -0400
Received: from XMB101ADS.rim.net ([fe80::cce5:67de:a150:3c3b]) by XCT103ADS.rim.net ([fe80::c8f6:ae2e:c42b:3614%21]) with mapi id 14.01.0289.001; Fri, 12 Aug 2011 13:57:00 -0500
From: Stefano Faccin <sfaccin@rim.com>
To: "Basavaraj.Patil@nokia.com" <Basavaraj.Patil@nokia.com>
Thread-Topic: [netext] Consensus call: Adopt I-D draft-bernardos-netext-pmipv6-flowmob-03 as Netext WG doc?
Thread-Index: AQHMV6MuHZ6NbgcL2k6ZQy/+0fAoQZUZYTUAgAAD04D//68fgIAAdZtw//+PPYCAAHYUQIAAAKIQgAADQPA=
Date: Fri, 12 Aug 2011 18:56:59 +0000
Message-ID: <00151E171043D44DBF23C55EEAB45ED0018647@XMB101ADS.rim.net>
References: <00151E171043D44DBF23C55EEAB45ED0018607@XMB101ADS.rim.net> <CA6ADBE0.1D166%basavaraj.patil@nokia.com> <00151E171043D44DBF23C55EEAB45ED0018627@XMB101ADS.rim.net> <21E7D9BD69CC7241AAE00F4EA183B71908DD42@008-AM1MPN1-024.mgdnok.nokia.com>
In-Reply-To: <21E7D9BD69CC7241AAE00F4EA183B71908DD42@008-AM1MPN1-024.mgdnok.nokia.com>
Accept-Language: en-CA, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.70.110.253]
Content-Type: text/plain; charset="utf-8"
content-transfer-encoding: base64
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrAKsWRmVeSWpSXmKPExsXC5ShmoptX7upnsL1HyKJlfTebxbWfT9kd mDyWLPnJ5HH31iWmAKaoBkabxLy8/JLEklSFlNTiZFsln9T0xByFgKLMssTkSgWXzOLknMTM 3NQiJYXMFFslEyWFgpzE5NTc1LwSW6XEgoLUvBQlOy4FDGADVJaZp5Cal5yfkpmXbqvkGeyv a2FhaqlrqGSniwQS/nFnfLj0i7VgU2rFtK2TmBoYnyR1MXJySAiYSFyc/4oZwhaTuHBvPVsX IxeHkEAPk8Sri1tYIJyljBJP726CcrYyShxdNo8dpIVNQE1iyfO1QO0cHCIC1hLz+sCmMguo S9yaf5YFxBYWyJGYtu4zK4gtIpArMf/dIzYIO0nibscNsM0sAqoSB373g43hFXCTOHxGDWLV H0aJAw0bGEFqOAXCJDrnzwVbyyggK7H77HUmiF3iEreezGeC+EBAYsme81DfiEq8fPyPFcJW lFjU+Z0RZD6zgKbE+l36EK2KElO6H4KN5BUQlDg58wnYyUICMhITHy9mmcAoMQvJhlkI3bOQ dM9C0r2AkWUVo2BuRrGBmUFyXrJeUWauXl5qySZGcFLR0N/B2LdX6xCjAAejEg/vi0RXPyHW xLLiytxDjBIczEoivF2vXfyEeFMSK6tSi/Lji0pzUosPMVoAw2cisxR3cj4w4eWVxBsbGKBw lMR5g6UN/IQE0oHpKzs1tSC1CKaViYNTqoGxRmnLX85V69Plt3Rc/ndfRNG+roBtmdrPw0cW xty5p8X1jnfZxyNn5Rncsr683JrNON3HuYb7eNQfsW9BKa8DL7Hkp8dx77gl6cFXwzS1I21r tvF8A/bd4m9n6EiWaL/dznEhvVRmeVZdmObKwjc6fXotzy0FxWTi5tiu7Lle4WNvt4JhloIS S3FGoqEWc1FxIgBBXbMEQwMAAA==
Cc: "netext@ietf.org" <netext@ietf.org>
Subject: Re: [netext] Consensus call: Adopt I-D draft-bernardos-netext-pmipv6-flowmob-03 as Netext WG doc?
X-BeenThere: netext@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Mailing list for discusion of extensions to network mobility protocol, i.e PMIP6. " <netext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netext>, <mailto:netext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/netext>
List-Post: <mailto:netext@ietf.org>
List-Help: <mailto:netext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netext>, <mailto:netext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Aug 2011 18:56:28 -0000

Raj,
At this point I have no trust whatsoever that the issues that were raised will be considered at all. They have not been so far, so I expect the same will happen again. Even if in the tracker mechanism, I'd like to know what "to everybody satisfaction" means. It will once again be totally subjective, which then defies the whole process. I think too many people had to spend way too much time on this just to end up exactly where we were with no answers whatsoever (perhaps because there are none, if one existed I guess there would have been time to show it?). Again, I maintain a [NO]. Too bad we need to handle the discussion this way. 
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.


-----Original Message-----
From: Basavaraj.Patil@nokia.com [mailto:Basavaraj.Patil@nokia.com] 
Sent: Friday, August 12, 2011 11:45 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,

I realize that we have had discussions on these issues multiple times. But as you can see I cannot point to some text or emails on the list and say conclusively whether they have been resolved to everyones satisfaction or not. We will no doubt have the same discussion again. But I am hoping that with the use of the tracker and clearly capturing the issue and the proposed resolutions, we can at least make better decisions and eventually progress.

Please do write-up the issues and bring them to the list and/or issue tracker.

Thx.
-Raj

-----Original Message-----
From: ext Stefano Faccin [mailto:sfaccin@rim.com] 
Sent: Friday, August 12, 2011 1:41 PM
To: Patil Basavaraj (Nokia-CIC/Dallas)
Cc: netext@ietf.org
Subject: RE: [netext] Consensus call: Adopt I-D draft-bernardos-netext-pmipv6-flowmob-03 as Netext WG doc?

Raj,
Thanks for the clarification. Personally, I believe we are just postponing the discussion. If solutions had indeed been proposed, one would have had a chance to keep an open mind in considering it. For this reason, I have no choice but maintaining my indication as a "NO".
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.


-----Original Message-----
From: Basavaraj.Patil@nokia.com [mailto:Basavaraj.Patil@nokia.com] 
Sent: Friday, August 12, 2011 11:37 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,

The chairs will monitor the discussion closely and any proposed solutions
to the issues that are raised. Unless we(chairs), the people raising the
issue, as well as the WG members, are not satisfied with the resolution we
will not progress the document.
The point about the process here is that at the moment we are spinning
wheels without making any forward progress. With a more formal approach to
the discussion and use of the tools, we hope to avoid discussions that are
in an unending loop. I do hope that folks who raise issues are also
willing to listen to solutions with an open mind.

-Raj

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

>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.


---------------------------------------------------------------------
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.