Hi Brian,

You deleted maybe by mistake the first three paragraphs of my previous mail.

Let me add to those one more point:

Previously mobility groups in IETF produced single protocols like
Mobile IP or Proxy Mobile IP.
These protocols have seen some operator adoption, of course not much but some.
This time we will be asking the operators to adopt exposing mobility
state protocol, enhanced mobility anchoring protocol and forwarding
path and signaling protocol (maybe forwarding path protocol and
signaling protocol)l.
And maybe deployment models protocol which was in the charter but
somehow got dropped.
How is that going to happen?

Anyway these are my concerns, I could not attend Interim call #2, I
believe many people could not including Jouni.
People should speak up, otherwise it appears like it is only my issue.

Regards,

Behcet

On Fri, Sep 26, 2014 at 11:22 AM, Brian Haberman
<[email protected]> wrote:
>
>
> On 9/26/14 11:14 AM, Behcet Sarikaya wrote:
>
>>
>> My question is we do that three four solution drafts and some of them
>> implemented.
>> What do we do with them?
>
> My expectation, as AD, is that the WG will assess the drafts presented
> by these teams for adoption.  People's opinion of those drafts should
> not be influenced by the fact they were written by a team.
>
>>
>> My advice to those colleagues wishing to lead the design teams is to
>> please come up with your own solution and get into the race with
>> others.
>
> Race?
>
>> How come they can get the hat of DT lead and produce something and get
>> priority over others who worked so hard?
>
> First of all, the chairs are well within their right to appoint DT
> leads.  They could have appointed all the other slots on the DT as well,
> but chose to ask for volunteers.
>
> I do not see anything in Jouni's note that indicates that a team's
> output gets any preferential treatment.  The rules of the IETF prevent that.
>
> To re-enforce Jouni's last sentence...
>
>>> These documents will be equivalent to any individual produced I-D, though.
>
> Regards,
> Brian
>
>
>
> _______________________________________________
> dmm mailing list
> [email protected]
> https://www.ietf.org/mailman/listinfo/dmm
>

_______________________________________________
dmm mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/dmm

Reply via email to