Re: [manet] draft-ietf-manet-olsrv2-multitopology and draft-dearlove-manet-tlv-naming-00.txt

I would find it hard to describe this as fast. Fast would be good, but instead we have processes to follow. As it is, from this point (never mind the time lost so far, in part because the authors had to make time to write the draft) there will be (at best, and therefore I hope) a few weeks delay before we can make progress on MT-OLSRv2 (unless our AD regards WG acceptance as enough to move that on, rather than WGLC, another stage to go through after this).

The observation by the AD has been on file for a while, and discussion on the need for a draft has been held. In its current state as an author draft, this discussion about WG acceptance is exactly the discussion on the form of the draft.

And I'm sorry, you may not have agreed to move the MT draft fast. But the WG accepted a WGLC, at a rate I'd call moderate, not fast.

-- 
Christopher Dearlove
Senior Principal Engineer, Information Assurance Group
Communications, Networks and Image Analysis Capability
BAE Systems Advanced Technology Centre
West Hanningfield Road, Great Baddow, Chelmsford, CM2 8HN, UK
Tel: +44 1245 242194 |  Fax: +44 1245 242124
chris.dearlove@baesystems.com | http://www.baesystems.com

BAE Systems (Operations) Limited
Registered Office: Warwick House, PO Box 87, Farnborough Aerospace Centre, Farnborough, Hants, GU14 6YU, UK
Registered in England & Wales No: 1996687

-----Original Message-----
From: manet [mailto:manet-bounces@ietf.org] On Behalf Of Abdussalam Baryun
Sent: 21 November 2014 02:21
To: Thomas Heide Clausen
Cc: manet
Subject: Re: [manet] draft-ietf-manet-olsrv2-multitopology and draft-dearlove-manet-tlv-naming-00.txt

----------------------! WARNING ! ---------------------- This message originates from outside our organisation, either from an external partner or from the internet.
Consider carefully whether you should click on any links, open any attachments or reply.
Follow the 'Report Suspicious Emails' link on IT matters for instructions on reporting suspicious email messages.
--------------------------------------------------------

Hi All,

I don't know why we have to move things fast. Moving things fast adds possible errors, and may confuse the community. We need to consider that participants need to give a decision on when to move things fast and when not to move things fast. I don't agree to move this draft fast nor agreed to move the multitopology draft fast. We could have done fast process if the draft was discussed before published, so that the WG can decide if fast is required. Just my opinion how things go fast in organisation that involve all.

On 11/10/14, Thomas Heide Clausen <thomas@thomasclausen.org> wrote:
> Since, of course, all y’all are compulsively reading the ID-announce 
> mailing list ;) you’ll have seen 
> draft-dearlove-manet-tlv-naming-00.txt document appear just today.
>
> This is in response to the review from our AD on 
> draft-ietf-manet-olsrv2-multitopology
> (http://www.ietf.org/mail-archive/web/manet/current/msg16875.html
> <http://www.ietf.org/mail-archive/web/manet/current/msg16875.html>), 
> in which he indicates that we probably should re-think the way we name 
> TLV types.
>
> As our AD requested, the authors did re-think, discuss a bit also with 
> our AD and chairs, and came to a conclusion ... and that conclusion is 
> in this I-D.

I request that our discussions related to adopted work and future discussions to be done on the list or within minutes. I think the WG should be able to be included in discussion between AD and authors, why WG was excluded?

Best Regards,

AB

_______________________________________________
manet mailing list
manet@ietf.org
https://www.ietf.org/mailman/listinfo/manet
********************************************************************
This email and any attachments are confidential to the intended
recipient and may also be privileged. If you are not the intended
recipient please delete it from your system and notify the sender.
You should not copy it or use it for any purpose nor disclose or
distribute its contents to any other person.
********************************************************************