Re: [netext] Flow Mobility Draft

[Behcet Sarikaya <[e-mail]>]

Sri,

On Wed, Jul 23, 2014 at 12:03 PM, Sri Gundavelli (sgundave)
<[e-mail]> wrote:
> Behcet,
>
> Ok. Fair enough. I introduced a change related to UPN/FMI/FMA in the
> current version of the document. The proposal based on offline discussions
> was posted on June/19/2014 and subsequently when no objections were cited,
> the editor of the document drafted the text and inserted the same into the
> document.

The story does not stop there, there are other thing on UPN/UPA (by
the way it is UPN/UPA not UPN/FMI/FMA).


> Bottom line, if you have a issue with the current version, please post
> your issue. State the problem, suggest the text. Do not send your version
> of the document to the Editor to be included. I will not agree with you or
> any one else editing the document and inserting text for an issue that has
> no WG consensus. The point is on the consensus on on the issue and let the
> Editor do the drafting. But, if the issue is with the Editor's text, post
> it to the group and challenge it/suggest changes, don't just edit WG
> document.
>
> Please play by the rules.
>

I already did. You can check in the archive. I asked many questions
and received no replies.

I read Rev. 10 sentence by sentence. I don't think anybody else did
this in the WG.
I can claim that I know flow mobility and I can show my credentials.

My assessment was that the only way to incorporate my comments is to
edit Rev. 10 completely and that's what I did.

Regards,

Behcet
>
>
> Sri
>
>
>
>
> On 7/23/14 9:44 AM, "Behcet Sarikaya" <[e-mail]> wrote:
>
>>Hi Sri,
>>
>>On Tue, Jul 8, 2014 at 5:46 PM, Sri Gundavelli (sgundave)
>><[e-mail]> wrote:
>>> Behcet,
>>>
>>> Please post your proposed changes to the ML.
>>
>>I expected that the chairs would post Rev. 11 on the list, it seems
>>they did not.
>>I am going to post it hopefully before the meeting.
>>
>>
>>
>>> There is an editor for the
>>> document, so its more appropriate you let the WG decide as what goes
>>>into
>>> the document. Document editor just follows the WG consensus. You know
>>>this
>>> all very well ..
>>
>>You mean when you say something it is consensus when I say something it
>>is not?
>>
>>The editor is supposed to handle all comments. I don't remember the
>>editors asking the WG for every comment made, is there consensus on
>>this comment? I did not know that IETF worked like that.
>>
>>Regards,
>>
>>Behcet
>>
>>>
>>>
>>> Regards
>>> Sri
>>>
>>>
>>>
>>> On 7/8/14 9:46 AM, "Behcet Sarikaya" <[e-mail]> wrote:
>>>
>>>>Hi all,
>>>>
>>>>I have been commenting on draft-ietf-netext-pmipv6-flowmob for years.
>>>>At some point the chairs set up the issue tracker and asked us to use
>>>>it. I did put many comments on the issue tracker.
>>>>
>>>>In the meantime I have been involved in HA based flow binding entitled
>>>>Flow Bindings Initiated by Home Agents for Mobile IPv6
>>>>work was published as RFC 7109.
>>>>
>>>>I have noticed that the editor has consistently ignored all these
>>>>efforts.
>>>>
>>>>Now that we came to a point of final decision, I decided to put all my
>>>>comments in writing. I made an xml file from Rev. 10
>>>>(BTW we had asked the editor to submit xml file for the draft but he
>>>>did not listen as usual) and produced a complete revision which I
>>>>called Rev. 11 and sent it in an email to the chairs.
>>>>
>>>>Here are the main points in this draft:
>>>>This version is 5+ pages shorter than Rev. 10.
>>>>This version removes the use cases section and replaces it with an
>>>>overview of flow mobility actions describing the flow mobility
>>>>protocol explicitly.
>>>>This version removes FMI/FMA section.
>>>>This version adds Local Mobility Anchor Considerations, Mobile Access
>>>>Gateway considerations
>>>>and much needed IPv4 flow mobility support sections.
>>>>This section uses UPN/UPA messages to carry Flow Identification
>>>>Mobility option and Flow Binding Action Sub-Option
>>>>   and Target Care-of Address Sub-Option defined in RFC7109.
>>>>
>>>>I propose this version to be used for further work and let Carlos
>>>>further maintain the document in just a few steps that are left.
>>>>
>>>>Regards,
>>>>
>>>>Behcet
>>>>
>>>>_______________________________________________
>>>>netext mailing list
>>>>[e-mail]
>>>>https://www.ietf.org/mailman/listinfo/netext
>>>
>