Re: [OPSAWG] Comments on draft-opsawg-ersue-coman-probstate-reqs

Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de> Thu, 16 January 2014 15:29 UTC

Return-Path: <j.schoenwaelder@jacobs-university.de>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1E1DA1AE394 for <opsawg@ietfa.amsl.com>; Thu, 16 Jan 2014 07:29:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.788
X-Spam-Level:
X-Spam-Status: No, score=-2.788 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.538] 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 LaUhJhyJ-2-Y for <opsawg@ietfa.amsl.com>; Thu, 16 Jan 2014 07:29:29 -0800 (PST)
Received: from hermes.jacobs-university.de (hermes.jacobs-university.de [212.201.44.23]) by ietfa.amsl.com (Postfix) with ESMTP id 3FCA11AE393 for <opsawg@ietf.org>; Thu, 16 Jan 2014 07:29:29 -0800 (PST)
Received: from localhost (demetrius1.jacobs-university.de [212.201.44.46]) by hermes.jacobs-university.de (Postfix) with ESMTP id BFD2220066; Thu, 16 Jan 2014 16:29:16 +0100 (CET)
X-Virus-Scanned: amavisd-new at jacobs-university.de
Received: from hermes.jacobs-university.de ([212.201.44.23]) by localhost (demetrius1.jacobs-university.de [212.201.44.32]) (amavisd-new, port 10024) with ESMTP id cynmNqt9PMNT; Thu, 16 Jan 2014 16:29:16 +0100 (CET)
Received: from elstar.local (elstar.jacobs.jacobs-university.de [10.50.231.133]) by hermes.jacobs-university.de (Postfix) with ESMTP id E5B452004D; Thu, 16 Jan 2014 16:29:15 +0100 (CET)
Received: by elstar.local (Postfix, from userid 501) id C7F722AA8145; Thu, 16 Jan 2014 16:29:13 +0100 (CET)
Date: Thu, 16 Jan 2014 16:29:13 +0100
From: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
To: James Nguyen <james.huy.nguyen@gmail.com>
Message-ID: <20140116152913.GA2658@elstar.local>
Mail-Followup-To: James Nguyen <james.huy.nguyen@gmail.com>, "Ersue, Mehmet (NSN - DE/Munich)" <mehmet.ersue@nsn.com>, "opsawg@ietf.org" <opsawg@ietf.org>
References: <CANF0JMCZzziqvjvTJ0WaJ8Wo3kSNHDhhurmcYmX4FpcqWfq2+g@mail.gmail.com> <E4DE949E6CE3E34993A2FF8AE79131F8249B2D@DEMUMBX005.nsn-intra.net> <CANF4ybvR47wHioN61meNiR6b-DgXue0EnDy2gmHSQ=P4sSgkhA@mail.gmail.com> <20140116073734.GA1160@elstar.local> <CANF4ybsjOSmTbd2PEoAXoKK=VD7DeQjCps1ZRujnb48pasC1-w@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <CANF4ybsjOSmTbd2PEoAXoKK=VD7DeQjCps1ZRujnb48pasC1-w@mail.gmail.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Cc: "opsawg@ietf.org" <opsawg@ietf.org>
Subject: Re: [OPSAWG] Comments on draft-opsawg-ersue-coman-probstate-reqs
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Jan 2014 15:29:31 -0000

On Thu, Jan 16, 2014 at 09:38:30AM -0500, James Nguyen wrote:
> >
> >> (2) Section 3.3 Configuration Management
> >>
> >>     Session-oriented configuration protocol may be expensive for managing
> >> a large number of similar devices.  In a case when common redundant
> >> configurations is issued, reliable multicast with negative acknowledgement
> >> (e.g. Negative ACKnowledgement (NACK)-Oriented Reliable Multicast (NORM))
> >> would work best.  I suggest to add a reliable transport requirement in this
> >> section.  Moreover, a common data model would be needed.
> >>
> >>     Stateless configuration update solution would also work well for
> >> constrained networks.
> >
> > My assumption is that reliable multicast protocols are not simple and
> > bring their own can of worms. Can you point to prototype systems that
> > do successfully use reliable multicast to configure constrained
> > devices?
> 
> I certainly can list a couple of scenarios:
> 
> I assume that military radios could be categorized as constrained
> devices as they're often on the move and operated in unreliable
> networks with lossy links and/or highly disrupted environment.
> Military radios or military devices seem to fit the definitions that
> are listed in Section 1.6.
> 
> (1) In military theater or emergency disaster incident, a group of
> soldiers or a group of search-and-rescuers need to switch frequency of
> their radios to join other group's communication network.
> 
> (2) In battlefield, soldiers' need to be zero-outed (of
> configurations) to prevent these radios/comms devices to fall in
> enemies' hands.

Luckily, I am not familiar with any of this. But my concern remains
and in such scenarios, I would have serious trouble to define what
'reliable' means given that the group membership is open ended.

> > Can you also elaborate what "stateless configuration update solution"
> > means to you?
> 
> I meant stateless configuration management.
> 

And that means what to you? What is 'stateless'?

/js

-- 
Juergen Schoenwaelder           Jacobs University Bremen gGmbH
Phone: +49 421 200 3587         Campus Ring 1, 28759 Bremen, Germany
Fax:   +49 421 200 3103         <http://www.jacobs-university.de/>