Re: [manet] AB#2 (olsrv2-multitopology): Adding section for packets

OK, I will agree I/we might have worded that slightly differently today. Rather than saying messages may be combined in packets, I would say messages (of different originators etc.)  can be sent to the multiplexer together for recommended inclusion in the same packet. But essentially this is a null comment, it says "The 5444 multiplexer may do what it is allowed to do."

-- 
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: Christopher Dearlove [mailto:christopher.dearlove@gmail.com] 
Sent: 18 September 2014 17:59
To: Henning Rogge
Cc: Abdussalam Baryun; manet@ietf.org; draft-ietf-manet-olsrv2-multitopology@tools.ietf.org
Subject: Re: [manet] AB#2 (olsrv2-multitopology): Adding section for packets

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

As Henning says, the original comment is wrong. It even uses the phrase RFC 7181 packets. There are no such things. (There are RFC 5444 packets, which may have some or all messages used by OLSRv2, or may not.)

--
Christopher Dearlove
christopher.dearlove@gmail.com (iPhone)
chris@mnemosyne.demon.co.uk (home)

> On 18 Sep 2014, at 17:24, Henning Rogge <hrogge@gmail.com> wrote:
> 
> On Thu, Sep 18, 2014 at 3:36 PM, Abdussalam Baryun 
> <abdussalambaryun@gmail.com> wrote:
>> 
>> The draft depends on RFC7181, however, the draft does not 
>> define/restrict
>> RFC7181 packets clearly. In RFC7181 section 13.2, it specifies what 
>> are the protocol packets. The protocol packets are having freedom to 
>> include all
>> RFC5444 messages even for other protocols. In 7181 it mentions in 
>> section
>> 13.2:
>> 
>> {{{
>> 
>> Messages with different originating routers MAY be combined for 
>> transmission within the same packet.  Messages from other protocols 
>> defined using [RFC5444], including but not limited to NHDP [RFC6130], 
>> MAY be combined for transmission within the same packet.
>> 
>> }}}
>> 
>> AB> For this protocol MT OLSRv2, it is reasonable to follow the 
>> AB> edition way
>> of RFC7181 and to having a subsection of packet and to describing the 
>> conditions for MT protocol in one clear section as did 7181 for 
>> non-MT protocol. So I suggest to add one section/subsection of 
>> packets for MT
>> OLSRv2 and that describes restrictions/conditions of multitopology 
>> messages to be combined among topologies.
> 
> I don't think the MT-OLSRv2 draft restricts the mechanism described in 
> section 13.2 of RFC 7181 in any way. It only defines extensions of the 
> existing TC messages. It does not even change any part of the flooding 
> process, including the flooding MPR set.
> 
> Could you maybe specify where you see the need of additional 
> restrictions/conditions and what kind of messages you want to combine 
> among different topologies?
> 
> Henning Rogge
> 
> _______________________________________________
> 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.
********************************************************************