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

Abdussalam Baryun <abdussalambaryun@gmail.com> Fri, 19 September 2014 12:57 UTC

Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5886E1A010E for <manet@ietfa.amsl.com>; Fri, 19 Sep 2014 05:57:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id z9u3_Nc07Pum for <manet@ietfa.amsl.com>; Fri, 19 Sep 2014 05:57:15 -0700 (PDT)
Received: from mail-yh0-x235.google.com (mail-yh0-x235.google.com [IPv6:2607:f8b0:4002:c01::235]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 395491A0127 for <manet@ietf.org>; Fri, 19 Sep 2014 05:57:15 -0700 (PDT)
Received: by mail-yh0-f53.google.com with SMTP id f73so523359yha.26 for <manet@ietf.org>; Fri, 19 Sep 2014 05:57:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=dXVsQ8XBtHufI6hIS1FFngTIB13QvwhDIZAykZX6afU=; b=FgJFKgk+88pJpfuDYp5TinSlgrn7rM7PsxlgH8IEKNpTSx8qfC8FYviaSJSALwJkUs xk7RbGvczY+7UH/7Qr71CbkX1EviCBIKm8qIvIk57TdFh/ECwWPx5PguWzlOfrdgabZp 35/RzGLIiKNE0Vlg26BXW40E+0H8c5fMdMcDk5yYXGpCzFVoJ8nvjwa/ECb1xZLg2FcH 9xCLCKWPo1r5JfSzBClwB4gobU/rocqgEpPbIgNrHxhbwRmMzP6fyaZLvzP2U2qEe0hw ALbJw0zvMKwmBLhIlQ+c33WV0tNlj1T8B1H4bnI4f/IJ5xGuH/oSRYsHWbX4EYFfn9+C DTIg==
MIME-Version: 1.0
X-Received: by 10.236.90.84 with SMTP id d60mr206503yhf.182.1411131434400; Fri, 19 Sep 2014 05:57:14 -0700 (PDT)
Received: by 10.170.86.196 with HTTP; Fri, 19 Sep 2014 05:57:14 -0700 (PDT)
In-Reply-To: <CAGnRvup=5NRJOZ6pKQn0_p+4mT7LUF3zBe6oJtHPFGGyH3AsQw@mail.gmail.com>
References: <CADnDZ8-Wv7oNr3KYfFEW-4zsij9WPUd9dE4m-uv5ZXUNh5Gz6A@mail.gmail.com> <CAGnRvup=5NRJOZ6pKQn0_p+4mT7LUF3zBe6oJtHPFGGyH3AsQw@mail.gmail.com>
Date: Fri, 19 Sep 2014 14:57:14 +0200
Message-ID: <CADnDZ8_WKV6V-1rcgDjWw=U_+5LksfTk8pSvOnOZbGJ4qN17pw@mail.gmail.com>
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: Henning Rogge <hrogge@gmail.com>
Content-Type: multipart/alternative; boundary="20cf301af78de0ff7a05036aa3ca"
Archived-At: http://mailarchive.ietf.org/arch/msg/manet/RSDEw2DNwVkCBQtR7pPMR7d8BIQ
Cc: "manet@ietf.org" <manet@ietf.org>, "draft-ietf-manet-olsrv2-multitopology@tools.ietf.org" <draft-ietf-manet-olsrv2-multitopology@tools.ietf.org>
Subject: Re: [manet] AB#2 (olsrv2-multitopology): Adding section for packets
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Mobile Ad-hoc Networks <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Sep 2014 12:57:17 -0000

Hi Henning,

On Thursday, September 18, 2014, Henning Rogge wrote:

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


I think it should do, to ensure (with its conditions) that any packet
have combine messages of only same topology. RFC7181 section 13.2 does not
ensure that because it is not MT protocol. So it will be good to refer to
that in one section in this draft of MT.


> 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?


IMO Conditions for MT are related to: metrics, route maintenance, and
packets. The draft tries to use assumptions but that can not be enough for
me without having analysis presented in IETF. IMHO, the dynamic topologies
can not have its control-messages mixed in one same packet. The draft
restricts that each topology has one-metric-type, but does not restrict
its control-packets, that is why we need a section about packets to
fix that. I will review the related drafts again to write down the full
conditions for this draft.

Regards,

AB