Re: [manet] FW: I-D Action: draft-ietf-ospf-manet-single-hop-mdr-02.txt

"Dearlove, Christopher (UK)" <Chris.Dearlove@baesystems.com> Tue, 07 May 2013 17:21 UTC

From: "Dearlove, Christopher (UK)" <Chris.Dearlove@baesystems.com>
To: Abdussalam Baryun <abdussalambaryun@gmail.com>, manet <manet@ietf.org>
Thread-Topic: [manet] FW: I-D Action: draft-ietf-ospf-manet-single-hop-mdr-02.txt
Thread-Index: AQHOSwZdCyizLUxTNE+cIX4dQ0rfCJj5eAsAgABs0wCAABMhUA==
Date: Tue, 07 May 2013 17:20:52 +0000
Message-ID: <B31EEDDDB8ED7E4A93FDF12A4EECD30D25068C34@GLKXM0002V.GREENLNK.net>
References: <20130505151526.3223.18240.idtracker@ietfa.amsl.com> <001301ce49d9$eef2e630$ccd8b290$@olddog.co.uk> <CADnDZ89-i2gK6fDZNYi_t1QCxm03XuxdFRLtkYP_YQrMZw=omw@mail.gmail.com> <5188DA58.2080704@fkie.fraunhofer.de> <CADnDZ885m=u7ng-PGfb-0D182f2A3r_w+75JJROeHAdA0o7Qjw@mail.gmail.com>
In-Reply-To: <CADnDZ885m=u7ng-PGfb-0D182f2A3r_w+75JJROeHAdA0o7Qjw@mail.gmail.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
Content-Type: multipart/alternative; boundary="_000_B31EEDDDB8ED7E4A93FDF12A4EECD30D25068C34GLKXM0002VGREEN_"
MIME-Version: 1.0
Cc: "draft-ietf-ospf-manet-single-hop-mdr@tools.ietf.org" <draft-ietf-ospf-manet-single-hop-mdr@tools.ietf.org>
Subject: Re: [manet] FW: I-D Action: draft-ietf-ospf-manet-single-hop-mdr-02.txt
Precedence: list

This is an extension to OSPF. It is not a protocol to run on the manet UDP port/IP protocol as specified by RFC 5498. As such it isn't constrained to use RFC 5444.

--
Christopher Dearlove
Senior Principal Engineer, Communications 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<mailto: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

From: manet-bounces@ietf.org [mailto:manet-bounces@ietf.org] On Behalf Of Abdussalam Baryun
Sent: 07 May 2013 18:11
To: manet
Cc: draft-ietf-ospf-manet-single-hop-mdr@tools.ietf.org
Subject: Re: [manet] FW: I-D Action: draft-ietf-ospf-manet-single-hop-mdr-02.txt


*** WARNING ***
This message originates from outside our organisation, either from an external partner or the internet.
Keep this in mind if you answer this message.
Please see this process<http://intranet.ent.baesystems.com/howwework/security/spotlights/Documents/Dealing%20With%20Suspicious%20Emails.pdf> on how to deal with suspicious emails.
On Tue, May 7, 2013 at 11:41 AM, Henning Rogge <henning.rogge@fkie.fraunhofer.de<mailto:henning.rogge@fkie.fraunhofer.de>> wrote:
On 05/07/2013 11:36 AM, Abdussalam Baryun wrote:
Hi Ogier,
I was interested to find the RFC5444 format (MANET messaging format)
in the I-D. The document is for the manet case so why does it not use
RFC5444 in its work? Do you think using RFC5444 is not a good idea in
this I-D, please explain?


Read the title of the document again... you will notice the "OSPF".

the OSPF Manet-Extension has been developed in the OSPF working group using the OSPF message format.


I understand that you prefer using OSPF fomat for the I-D, which I was thinking of RFC5444. I read I-D and the extension is for manet not others. IMO it is ok all WGs may work together for the best of IETF protocols or formats. IMO that a routing protocol X  that wants to be extended for MANET cases SHOULD include additional messaging type considering rfc5444 format, but if that protocol has a reason why not to use RFC5444 then it will be understood,

AB


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

Re: [manet] FW: I-D Action: draft-ietf-ospf-manet… Abdussalam Baryun
[manet] FW: I-D Action: draft-ietf-ospf-manet-sin… Adrian Farrel
Re: [manet] FW: I-D Action: draft-ietf-ospf-manet… Henning Rogge
Re: [manet] FW: I-D Action: draft-ietf-ospf-manet… Ulrich Herberg
Re: [manet] FW: I-D Action: draft-ietf-ospf-manet… Abdussalam Baryun
Re: [manet] FW: I-D Action: draft-ietf-ospf-manet… Dearlove, Christopher (UK)
Re: [manet] I-D Action: draft-ietf-ospf-manet-sin… Stan Ratliff (sratliff)
Re: [manet] FW: I-D Action: draft-ietf-ospf-manet… Joe Macker
Re: [manet] FW: I-D Action: draft-ietf-ospf-manet… Abdussalam Baryun
Re: [manet] FW: I-D Action: draft-ietf-ospf-manet… Abdussalam Baryun
Re: [manet] FW: I-D Action: draft-ietf-ospf-manet… Dearlove, Christopher (UK)
Re: [manet] FW: I-D Action: draft-ietf-ospf-manet… Abdussalam Baryun
Re: [manet] FW: I-D Action: draft-ietf-ospf-manet… Abdussalam Baryun