
From nobody Tue Dec  1 11:21:27 2015
Return-Path: <Ietf@thomasclausen.org>
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 0BD031A1A36 for <manet@ietfa.amsl.com>; Tue,  1 Dec 2015 11:21:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.103
X-Spam-Level: 
X-Spam-Status: No, score=-0.103 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, J_CHICKENPOX_57=0.6, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-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 fHZmx9K7lhaf for <manet@ietfa.amsl.com>; Tue,  1 Dec 2015 11:21:22 -0800 (PST)
Received: from maila2.tigertech.net (maila2.tigertech.net [208.80.4.152]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 150091A038C for <manet@ietf.org>; Tue,  1 Dec 2015 11:21:22 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by maila2.tigertech.net (Postfix) with ESMTP id 05170252050 for <manet@ietf.org>; Tue,  1 Dec 2015 11:21:22 -0800 (PST)
X-Virus-Scanned: Debian amavisd-new at maila2.tigertech.net
Received: from [192.168.147.111] (mtg91-1-82-227-24-173.fbx.proxad.net [82.227.24.173]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by maila2.tigertech.net (Postfix) with ESMTPSA id 0947C240857 for <manet@ietf.org>; Tue,  1 Dec 2015 11:21:20 -0800 (PST)
From: ietf@thomasclausen.org
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Message-Id: <F474BF24-D920-4A54-8F43-AB4B9FE939A8@thomasclausen.org>
Date: Tue, 1 Dec 2015 20:21:19 +0100
To: manet <manet@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 9.1 \(3096.5\))
X-Mailer: Apple Mail (2.3096.5)
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/K0ZUBVZOMHheKqHcfjgSBgNgFhI>
Subject: [manet] Stuff from review of aodv-11 page 1-22 that are still not folded into -12
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: <https://mailarchive.ietf.org/arch/browse/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: Tue, 01 Dec 2015 19:21:26 -0000

All,

I am working through the revised I-D to see what comments that I made =
previously have been addressed, and which still do apply.=20

As I sent my original review piecemeal, I=E2=80=99ll send my refresher =
in matching pieces (in part, in recognition that it is hard to get time =
to sit down and review the whole document in one go, and I do want to =
reply to the authors as quickly as possible)

In doing so, I am noticing additional things (notably, but not =
exclusively, to section 7 and beyond, which I didn=E2=80=99t get through =
reviewing last time around) which needs attention. I=E2=80=99ll gather =
that in separate emails a bit later, once I=E2=80=99ve worked through =
the complete, updated spec.

So onwards...=20

Abstract:
	I made the following comment, which still applies:

		=E2=80=9CThis is a little over-stating the =
applicability: these statements may=20
		 be true in some scenarios (for example, when there are =
few=20
		 concurrent traffic flows, and therefore few routes to =
repair, and=20
		 therefore few flooding operations to contend for =
channel access).
		 As a general statement, this last sentence is =
incorrect=E2=80=9D=E2=80=9D

Overview (and elsewhere):

	I made a comment previously that =E2=80=9CRouter client=E2=80=9D =
is a poorly chosen
	term, and have proposed alternatives. I=E2=80=99ve seen some =
attempts on the list
	at rather than change the term, explain it =E2=80=94 some of =
which is in this document.
	The =E2=80=9COverview=E2=80=9D still talks about =E2=80=9Ca =
router=E2=80=A6one of its clients=E2=80=9D - which is no less
	confusing than last time Iw went through it.

	I reiterate, why not use =E2=80=9CLocal Attached Network Set=E2=80=
=9D, which is the term used
	by other documents from this WG?=20

Overview:
	The term =E2=80=9Cconfirming adjacency=E2=80=9D is gone, and is =
now replaced by
	=E2=80=9Cconfirming bidirectionality=E2=80=9D - which, alas, =
still sounds like there is some active
	monitoring (HELLO message exchange) going on. Unless that is the =
case,
	then please be more specific here.=20

	I note that the term adjacency is used through and through the =
document, btw.

	I suggested in my last review:

		The overview must also include a paragraph on the =
intersections=20
		between this protocol and the forwarding plane =E2=80=94 =
this, as it is=20
		different (and more invasive) from that which is =
typically seen in=20
		routing protocols.

		Specifically, as a reactive protocol, it is required (at =
least) that the=20
		forwarding plane is modified :

		1) A =E2=80=9Cmiss=E2=80=9D when looking up a next hop =
for a data packet to be=20
		   forwarded, is signalled to the AODVv2 process so as =
to permit=20
		  that route discovery be launched;

		2) A =E2=80=9Cmiss=E2=80=9D when attempting to deliver a =
data packet to a next hop,=20
		   which was recorded in the routing table, is signalled =
to the AODVv2=20
		   process so as to permit that a route repair be =
initiated and/or a Route=20
		   Error be generated.

		3) A =E2=80=9Chit=E2=80=9D when looking up a next hop =
for a data packet to be forwarded=20
		    to a destination is signalled to the AODVv2 process =
so as to permit=20
		    maintenance of =E2=80=9Cactive route=E2=80=9D Route =
State, timers and such.

		Note that these things are necessary to call out in the =
=E2=80=9Coverview=E2=80=9D and in=20
		the =E2=80=9Capplicability statement=E2=80=9D, both: it =
is not that they are negatives per se,=20
		but that they are important factors governing the =
applicability of this protocol:=20
		will a given platform permit such access to the =
forwarding plane, for example?=20
		Important to understand if for that platform this =
protocol is apple

=09
	I see that this was not addressed in the overview, nor in the =
applicability other than
	by a forward reference to section 6.4. While it is positive that =
there is a section 6.4,
	this does not exonerate the overview and the applicability =
statement for being
	honest about the requirements (notably to the platform/os) that =
this protocol has=20
	for being applicable=20

	I suggested in my last review:
	=09
		=E2=80=9CIt is important to do more than this: 7182 does =
only provide =E2=80=9Ccontainers=E2=80=9D=20
		 for ICVs and timestamps, and does not specify how to =
use them to obtain=20
		 specific security properties. RFC7182 may be a tool =
that can be used, but=20
		 *how* that tool is used is what determines the security =
properties.

		Therefore, saying that =E2=80=9Csecurity is dealt with =
by using RFC7182=E2=80=9D is either an
		incomplete statement, or is indicative of insufficient =
security considerations.=E2=80=9D
=09
	The actual sentence in the I-D has been changed, now it =
explicitly names the
	two TLVs from 7182 that it uses. That is, alas, still not =
sufficient.

	Making the aside that was discussed recently on the list, that =
(i) control messages=20
	are not forwarded, and that (ii) they are modified in transit, =
the security/trust model
	is somewhat different from that of 7181 and consequently for =
what 7182 was initially
	written for. I think that  calling out the trust model, and how =
7182 actually is used here,
	might be what is called for.

	Continuing with the aside, this *especially* as the =
applicability statement says:

		"Providing security for a reactive routing protocol can =
be difficult=E2=80=9D


Terminology:

	My last review suggested:
		=E2=80=9CThis has been brought up on the list several =
times in the past, without having=20
		 been addressed.

		There are =E2=80=9Chosts=E2=80=9D and there are =
=E2=80=9Crouters=E2=80=9D =E2=80=94 whose roles are well defined.=20
		=E2=80=9CNode=E2=80=9D not so much =E2=80=94 which is =
clear from looking at the definition here: =E2=80=9Ceither=20
		AODVv2 routers or router clients=E2=80=9D (with =
=E2=80=9Crouter clients=E2=80=9D being defined as =E2=80=9Can=20
		AODVv2 router is also its own router client=E2=80=9D).

		This is very much related to the use of =E2=80=9CRouter =
Client=E2=80=9D, and both that term,=20
		and =E2=80=9Cnode=E2=80=9D indicative that some clarity =
is needed here.

		All a router cares about is =E2=80=9Can address=E2=80=9D. =
If that address is of a network, or=20
		a router, or an interface (and, if said interface is =
installed in a router or a host)=20
		doesn=E2=80=99t matter.

		So, =E2=80=9Can address=E2=80=9D is something that the =
routing protocol should care about
		finding paths to. Which means that each address that =
should be made=20
		reachable by the routing protocol should be advertised =
by (at least) one router=20
		in the network.

		One way of doing that would be to simply talk about =
=E2=80=9CAttached Networks=E2=80=9D as=20
		is done in RFC7181, wherein an address included in the =
=E2=80=9CAttached Network Set=E2=80=9D=20
		is advertised by an OLSRv2 router....in this case, the =
equivalent would be =E2=80=9Cfor each=20
		address in the Attached Network Set of an AODVv2 router =
the router MUST=20
		respond authoritatively to a RREQ, and MUST maintain the =
corresponding sequence number=E2=80=9D.

		The text, as it currently is, is really hard to read, =
and a re-edit along these lines would go a long way.=E2=80=9D

	I note that the terms =E2=80=9CNode=E2=80=9D and =E2=80=9CRouter =
Client=E2=80=9D are still used, in their original form,=20
	and that other than some slight wordsmithing this comment has =
not been addressed in the document.

	I reiterate that the need to use router, host, node, and router =
client in and by itself should
	be an indicator that tightening up of terminology is required.


	I made the following comment to Routable Unicast IP Address:

		=E2=80=9CAre there any technical reason why not simply =
*any* address could be=20
		 considered by the routing protocol?

		 My understanding, but correct me if I am wrong, is that =
all that is required is=20
		 that all interfaces in a given AODVv2 routing domain =
has an unique address.

		 That some of these addresses (by an IP addressing =
architecture document)=20
		 has special semantics associated (such as are link =
locals, or are for private=20
		 use, or are for example use only, or are for multicast) =
is out of scope here?

	I see nothing has changed on the above, so let me be more =
explicit: the routing protocol itself=20
	(probably) should not care about what kind of addresses are =
filled into it. Is an 192.16./16 address
	appropriate? Not across the internet, but it may be in =
somebody=E2=80=99s private deployments. Should
	the routing protocol be =E2=80=9Caddress police=E2=80=9D and is =
implementation of a =E2=80=9CI refuse to route these addresses=E2=80=A6=E2=
=80=9D
	a requirement for claiming conformance? Suggest simply stating =
what the requirements are under
	which the routing protocol will work =E2=80=94 and leave =
=E2=80=9Caddress assignment politics=E2=80=9D aside.

	I also continued:

		 Now, with that being said also, the WG wanted that =
RFC7181 supports not=20
		 just multiple interfaces, but also the same address =
used on multiple interfaces=20
		 of the same router. There were good reasons for that, =
and while it was not trivial=20
		 to implement, it turned out to be the right thing to =
support. If there are technical=20
		 reasons why this is not supported in AODVv2 (for =
example, if this cannot be=20
		 made work because of <reason>) then that should be =
called out in the=20
		 applicability statement also?

		Conversely, if it is possible in AODVv2, then I do not =
believe that it is clearly=20
		specified how (at least, in the =E2=80=9Cnaive=E2=80=9D =
on paper examples I drew up, something=20
		ended up not working). So either the protocol as-is does =
not support it (but=20
		could be made to?) or it is supported (but just need to =
be spelled out), or is=20
		not possible (and need to be disclaimed in the =
applicability statement).

		Stan Ratliff was a driving force in holding the WG=E2=80=99=
s collective feet to the fire=20
		in getting this support included in RFC7181, and would =
likely be the right=20
		person to consult on this matter?

	I actually have not seen changes, or comments, on this. In =
OLSRv2, the WG was making it
	a strong requirement that it should be possible to use the same =
IP address on different
	interfaces of a router. It was somewhat tedious to design =
around, but it was worked out, and
	the conditions under which that was possible were defined and =
documented.

	I would like to see the same done for this protocol.

	I also note that this is not unrelated to RFC6621-discussions. =
For example, when selecting
	S-MPRs on a multi-interface and multi-address-per-interface =
router, care must be taken
	least things won=E2=80=99t work. So, if (and this links back to =
previous mails) RFC6621 is a
	requirement or desire for this protocol, then there are some =
considerations required here.

	I see that the definition of =E2=80=9CRouter Client=E2=80=9D has =
changed to be=20

		=E2=80=9CAn address or address range=E2=80=A6the AODVv2 =
router=E2=80=99s interface addresses=20
		 are also configured as router clients=E2=80=9D

	Better than before, but still missing the target. The term =
=E2=80=9CRouter Client=E2=80=9D is, as I indicated
	numerous times before, odd.

	But the second part of the sentence, does that mean (what it =
says) that the interfaces=20
	must be configured specially, so as to be able to be =E2=80=9Crout=
er clients=E2=80=9D? That can=E2=80=99t be true.

	What you likely mean is:

		=E2=80=9CAn AODVv2 router is configured so as to =
consider its own interfaces as part of
		 the locally attached network set=E2=80=9D ?=20

	You configure the router, right? No special =E2=80=9Cinterface =
configuration properties=E2=80=9D are required
	for an interface to be announcable by  an AODVv2 router?
	(And, getting rid of node would actually make the definition =
shorter and nicer)

	Now, snipping out from the applicability statement:

		"Multi-homing of an IP address is not supported by =
AODVv2, and therefore a
		  Router Client, i.e. an IP Address,  =E2=80=A6 "
=09
	=E2=80=A6evidence to there being some redundant terminology here =
to weed away.

	The below is a little bit of a meta-comment, I am not quite sure =
what I think here.
	The definitions for Target Node and such were confusing before. =
They still are, somewhat.=20

	I think that it may be because the definitions now used are =
simply copy-pasted out from the=20
	tables in the previous version, for example:

		An AODVv2 Data Element containing the destination =
address of the
		IP packet triggering route discovery.

	OK, I can trace back and see that a Data Element is something =
that exists inside a=20
	protocol message. To me, however, that=E2=80=99s not really =
general terminology as such, but
	part of the specification of a packet format - or rather, it is =
the notation that you use=20
	when describing an algorithm. By the way, why are some notations =
in CamelCase=20
	whereas others have a space in them, e.g. =E2=80=9CTarget =
Node=E2=80=9D and =E2=80=9CTargMetric=E2=80=9D, both of which
	are Data Elements? Would be good with a consistent approach =
here.

	I *think* that it would be better to take all those =E2=80=9CData =
Element=E2=80=9D bits and move to a separate
	section (or subsection) to the terminology, and then keep all =
the =E2=80=9Cother stuff=E2=80=9D (Neighbor, =E2=80=A6)
	in its own section.

	I=E2=80=99m a great fan of calling this section =E2=80=9CTerminolo=
gy and Notation=E2=80=9D and then having two
	subsections, one which is =E2=80=9CTerminology=E2=80=9D and one =
which is =E2=80=9CNotation=E2=80=9D, with the=20
	TargMetric and Target Node being firmly in the latter.

	I made a comment:
		"Second, should =E2=80=9Cvalid route=E2=80=9D not be =
qualified by =E2=80=9Cto a specific address=E2=80=9D?=E2=80=9D

	Which was not addressed.

	I also made a comment on "Unreachable Address=E2=80=9D - I am =
glad I did, because I apparently
	had a different understanding than what was intended. I now see =
that an Unreachable Address
	by definition is an address listed in a RERR message, and not =
the same as an address to
	which no route has yet  been discovered? If yes, then please use =
a different term, such as
	=E2=80=9CFormerlyReachableAddress=E2=80=9D or something of the =
sort?

Applicability statement

	First, I would like to recognize the efforts made to improve =
this since last review. Thanks

	Second, the document states:

		"AODVv2 supports routers with multiple interfaces, as =
long as each
		   interface configured for AODVv2 has a unicast IP =
address.  A router
		   may use the same IP address on multiple interfaces.  =
Address
		   assignment procedures are out of scope for AODVv2.=E2=80=
=9D

	Is that true? Granted, I have not worked this through in detail, =
but I can present a counter-example:
	the use of RFC6621 means that there certainly are some =
constraints that must be respected least
	various flooding optimizations may not work.

	Secondly, if the multiple-interfaces-with-same-address are on =
the same L2, and this is what I
	have not worked through, are there any situations that will not =
work?

	The immediately previous version of this specification read:

		"AODVv2 supports routers with multiple interfaces, as =
long as each
		   interface configured for AODVv2 has its own unicast =
routable IP address"

	So what changed that means that each interface no longer needs =
its *own* unicast address?

	I pointed out to the Applicability Statement:

		I think that appendix B needs to be removed. =
Essentially, it makes claims that it is=20
		possible to do multi-homing =E2=80=94 but neither =
specifies how it is done, nor gives=20
		pointers to documents that justify the claim.

		AODVv2 does not support multi-homing =E2=80=94 that=E2=80=99=
s clear, and it is fine that it is=20
		called out here. Thank you for that.

		Now, with that being said, I am torn between being =
satisfied that it is called out on=20
		one hand, and wanting to have =E2=80=9Cmulti homing=E2=80=9D=
 on the other hand. RFC7181 supports=20
		multi-homing, FWIW.

		I believe that this also would merit some explicit =
discussion by the WG, in order to=20
		understand if this design decision is acceptable?

	I see that Appendix B still is in the document, and I do not =
recall having seen this discussed
	on the mailing list. Simply removing the reference from the =
Applicability Statement to Appendix B
	does not address the issue that I raised in my previous review.

To 4.1, I made the following comment:

	"Is this a should, or a SHOULD? If the latter, should it be a =
MUST?

	  In general, there are a lot of such =E2=80=9Cmaybe normative =
language=E2=80=9D through the=20
	 document, and I would much like to see an editorial pass =E2=80=94=
 essentially all=20
	 may/should/ must and friends carefully evaluated as if they =
should become=20
	 2119-terms, and ... more importantly (it has been called out =
before, fwiw)=20
	 quite a bit of should/SHOULD which ought to be transformed into =
MUST.

	Generally, aiming for a very a low number of SHOULD is a good =
design metric for a document=E2=80=9D

Aside from the general comment on 2119-language, why is this a SHOULD?

To 4.2, I made the following comment:

	As indicated earlier, I believe that the term =E2=80=9CRouter =
Client=E2=80=9D is ill chosen.=20
	I believe that it is more appropriately an =E2=80=9CAttached =
Network Set=E2=80=9D since =E2=80=94=20
	as indicated previously =E2=80=94 the term =E2=80=9CRouter =
Client=E2=80=9D is ambiguous. I am pleased=20
	to see, though, that this =E2=80=9CRouter Client List=E2=80=9D =
in reality is an =E2=80=9CAttached Network Set=E2=80=9D=20
	and so that change should be (relatively) easy.

The above comment still is applicable to this revision,

To 4.2, I made the following comment:

	Also, I recommend to not say =E2=80=9Csubnet=E2=80=9D =E2=80=94 =
how about rephrasing to =E2=80=9CIf a prefix=20
	is included in the attached network set of an AODVv2 router, =
then that AODVv2=20
	router MUST provide connectivity for, i.e. answer to RREQs and =
maintain=20
	sequence numbers for, all addresses from within that prefix.=E2=80=
=9D

I note that while the term has been removed from section 4, there=E2=80=99=
re 4 lingering instances of this term in the document, that could easily =
be removed.

I Also made a comment about Appendix B in my previous review, which is =
referenced here. That comment still applies.

To Section 4.3, I noticed:

	Does section 6.2 describe how to monitor an established =
adjacency=20
	only, or how to discover neighbouring AODVv2 routers? Looking in =
6.2, I see

		=E2=80=9CNot every pair of neighboring routers will =
necessarily form an adjacency,=E2=80=9D =E2=80=94=20
		 so it likely isn=E2=80=99t 6.2 that tells me how to =
maintain this table?

	In short, =E2=80=9CA neighbour table MUST be maintained=E2=80=9D =
=E2=80=94 where can I find information on how to do this?

	Section 6.2 states:

		=E2=80=9CThe default approach for monitoring =
bidirectional connectivity to the next hop toward=20
		 OrigAddr is to request acknowledgement of Route Reply =
messages.=E2=80=9D

		That certainly will tell me if a link over which an RREP =
is sent is bi-directional,=20
		but will not maintain a =E2=80=9Cneighbor table=E2=80=9D.

	So how is this done? Or, is the =E2=80=9CNeighbor Table=E2=80=9D =
not supposed to contain the=20
	complete set of neighbours? What information =E2=80=9C...MUST be =
maintained=E2=80=9D then, in this table?

	This is very unclear, I would not know how to implement a =
mechanism that populates this=20
	=E2=80=9CNeighbor Table=E2=80=9D with the needed information =
here.

I see no (relevant) changes to 6.2 nor to 4.3 so I assume that this =
comment has not been addressed

I am throwing this in here, as I am sure that I commented on that in the =
previous review, but I do not see that addressed: is Appendix C =
normative, or not? It represents =E2=80=9C a second specification of the =
protocol, in a different language=E2=80=9D from the main part of the =
specification. I have not walked through and made 200% sure that both =
are perfectly aligned and that there are no ambiguities, but having two =
different specifications of a protocol is a recipe for disaster.  Please =
either make 2000% sure that they are specifying the same thing without =
ambiguities, or remove one.

To section 4.4, I wrote:

	"would like to nit-pick that: the router can maintain this =
sequence number in whatever=20
	 format it pleases =E2=80=94 but, when it includes it in control =
messages, it must be=20
	 representable in a specified format, respecting certain =
rules.=E2=80=9D

I see that there were no changes following this comment.

To section 4.4 I asked for clarification as to if sequence numbers were =
per interface or per router, as the specification was unclear on that. =
The words has changed, but it still is unclear: how many sequence =
numbers does a router maintain? One? One per interface?

In my previous review, I expressed that it would be preferential to use =
=E2=80=9Ca notation of Sets=E2=80=9D rather than tables. I see that this =
has not changed.

I made a comment on node and address, let me pick this up again. The =
following:

	RteMsg.OrigAddr
	      An IP address of the node which requires the route, i.e., =
the
	      source address of the IP packet triggering the route =
request.

would be more compact and clear if getting rid of the term =E2=80=9Cnode=E2=
=80=9D and said:

RteMsg.OrigAddr
	The source address of the IP packet triggering the route =
request.


To section 4.6, and I (and others) have commented on this before:

   All AODVv2 routers MUST maintain a route table.  The route table
   entry is a conceptual data structure.  Implementations MAY use any
   internal representation but MUST contain the following information:

In order to avoid confusion, rename this to =E2=80=9CRouting Information =
Base=E2=80=9D or =E2=80=9CRouting Set=E2=80=9D =E2=80=94 a Routing Table =
is an operating system construct, whereon operations directly influence =
packet forwarding. What you are defining here is a RIB/an RS.

The confusion that I pointed out in my previous review on =E2=80=9CIP =
address=E2=80=9D and =E2=80=9CAddress=E2=80=9D being used a bit =
haphazardly persists, fwiw. It makes me think, can a router send an RREQ =
for a prefix?

I also called this out in my previous review as incorrect, and despite =
wordsmithing it still is:

	Route.NextHop
	      The source IP address of the message advertising the route =
to
	      Route.Address, i.e. an IP address of the AODVv2 router =
used for
	      the next hop on the path toward Route.Address.

If that =E2=80=9Cmessage=E2=80=9D is an RFC5444 entity, then it does to =
have a =E2=80=9Csource IP Address=E2=80=9D =E2=80=94 the encapsulating =
IP datagram containing the packet containing the message does. And the =
message MAY have an Originator Address


As I indicated, I am walking through my previous review and retaining =
those comments that I still think need attention =E2=80=94 and this is =
=E2=80=9Ccrossing off from part 1 of my previous review=E2=80=9D only. =
More to follow.

Thomas


From nobody Tue Dec  1 15:35:55 2015
Return-Path: <lberger@labn.net>
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 C799B1B2A65 for <manet@ietfa.amsl.com>; Tue,  1 Dec 2015 15:35:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.667
X-Spam-Level: 
X-Spam-Status: No, score=-1.667 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, IP_NOT_FRIENDLY=0.334, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no
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 Epi5G0vznPDd for <manet@ietfa.amsl.com>; Tue,  1 Dec 2015 15:35:51 -0800 (PST)
Received: from gproxy1-pub.mail.unifiedlayer.com (gproxy1-pub.mail.unifiedlayer.com [69.89.25.95]) by ietfa.amsl.com (Postfix) with SMTP id 772FD1B2A48 for <manet@ietf.org>; Tue,  1 Dec 2015 15:35:50 -0800 (PST)
Received: (qmail 27004 invoked by uid 0); 1 Dec 2015 23:35:49 -0000
Received: from unknown (HELO cmgw4) (10.0.90.85) by gproxy1.mail.unifiedlayer.com with SMTP; 1 Dec 2015 23:35:48 -0000
Received: from box313.bluehost.com ([69.89.31.113]) by cmgw4 with  id oPbd1r00T2SSUrH01PbgaS; Tue, 01 Dec 2015 16:35:48 -0700
X-Authority-Analysis: v=2.1 cv=IekUBwaa c=1 sm=1 tr=0 a=h1BC+oY+fLhyFmnTBx92Jg==:117 a=wU2YTnxGAAAA:8 a=cNaOj0WVAAAA:8 a=IkcTkHD0fZMA:10 a=-NfooI8aBGcA:10 a=uEJ9t1CZtbIA:10 a=wUQvQvOEmiQA:10 a=48vgC7mUAAAA:8 a=dOxtcvXA-qQqrKvyiFcA:9 a=aDGvxUjJiPbXNnWT:21 a=yPzEQNwvPWVHcBNb:21 a=QEXdDO2ut3YA:10
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=labn.net; s=default;  h=Content-Transfer-Encoding:Content-Type:In-Reply-To:MIME-Version:Date:Message-ID:From:To:References:Subject; bh=uhB5wZaJSvJz7eLQ3M9WCrKA/ZFpeRo/URUHIPwWlYQ=;  b=FNEMaW03uaWl6B6XbLqCfFdJcpjqKfBCnFsYLehkzUF+UHQtFIqbCnghPabx7JfipVekghn5bN4t0kKmcbyJhLHjSSF7wLHIDkuO42RyWjD07rqkEI4zv5OwCAhOQ6wA;
Received: from box313.bluehost.com ([69.89.31.113]:35154 helo=[127.0.0.1]) by box313.bluehost.com with esmtpa (Exim 4.84) (envelope-from <lberger@labn.net>) id 1a3uSP-0000gl-5A; Tue, 01 Dec 2015 16:35:37 -0700
References: <5575E8A7.6030508@labn.net>
To: manet@ietf.org, draft-ietf-manet-dlep@ietf.org
From: Lou Berger <lberger@labn.net>
X-Enigmail-Draft-Status: N1110
Message-ID: <565E2EC4.50504@labn.net>
Date: Tue, 1 Dec 2015 18:35:32 -0500
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.4.0
MIME-Version: 1.0
In-Reply-To: <5575E8A7.6030508@labn.net>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
X-Identified-User: {1038:box313.bluehost.com:labnmobi:labn.net} {sentby:smtp auth 69.89.31.113 authed with lberger@labn.net}
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/8Op8icXj6ETViIxVz1T7LsAqQPE>
Subject: [manet] DLEP-17 and RtgDir review of draft-ietf-manet-dlep-14
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: <https://mailarchive.ietf.org/arch/browse/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: Tue, 01 Dec 2015 23:35:53 -0000

Hello,

I have finally had a chance to review this draft and agree that DLEP-17
is a big step forward, but I still have some comments. Before starting
any new discussions I wanted to revisit my original review, to confirm
my view of status.  Please let me know if you disagree.


On 6/8/2015 3:10 PM, Lou Berger wrote:
> ...
>
> Major Issues:
>
>     - The length field of the generic data item (i.e., TLV) is only 8
>       bits.  While 255 bytes (assuming that this is the unit of measure,
>       which BTW isn't specified) is big enough today, allowing for
>       larger will greatly simplify things when 255 isn't enough. --
>       We've run into this in RSVP and it's a real pain.
Fixed.

>     - Version number is currently defined as a data item.  This means a
>       signal (i.e., message) needs to be potentially fully parsed to
>       discover what version is being used.  This precludes basic format
>       changes to the protocol.  Perhaps the Discovery and Init Signals
>       should be special cased to include version in their formats.  (And
>       shorten version to 8 bits from 32, as mentioned below).
Fixed.

>     - The document references, but does not define, 'in-session' and
>       'discovery' states.  These either need to be formally defined or
>       removed.  BTW we had exactly the same issue with LMP (RFC4204) and
>       ended up adding section 11 (FSMs) at a pretty late stage of the
>       process.

Definitely improved.  I still think there would be value in providing
the state diagram.  This would help clarify permitted/missing
transitions and events.  (For example TCP closes are not called out.)

>     - TCP session management is not defined, nor is the relationship
>       with TCP and DLEP sessions fully defined.  For example:
>
>       o Closing the TCP session is only mentioned in one place and in a
>         way that is inconsistent with the expected protocol behavior
>         (close TCP before ACK is received).
>
>       o What happens when a DLEP session is terminated, can the TCP
>         session be reused or must it be closed too?

Think this is mostly okay, i.e., Major item is close, but there are
still some minor issues, e.g., specifying behavior of an unexpected TCP
close.

>
>     - There is no transaction model defined.  For example, it's
>       completely unclear if only one unacknowledged Signal allowed at a
>       time, or perhaps just one per signal type is allowed, or perhaps
>       there are no restrictions.  This needs to be explicit.  

This is improved, but is still a bit unclear.  As I read section 4.1,
parallel 'destination-specific' transactions are now allowed. Also in
parallel with this,  a single 'Session Request' transaction is
permitted.  Looking at table 1, I think it's clear which are session
messages (1-8) and which are destination messages (9-13), but it is
unclear which category Link Characteristics fall into.  More
significantly, it's unclear how new messages should be handled.

One related point, but is really just a comment on the new error
handling text in section 4.1.  The last paragraphs state that response
failures will be detected by heartbeat failures.  This works for
complete failures, but won't detect the case of failed 'destination'
transaction.

>
>     - What is the purpose of retries and timeouts over TCP?  Retries
>       aren't needed over TCPs and it's unclear whey they are being used.
Fixed.

>     - The higher level implications of ACKs, over TCP, isn't really
>       clear.  It seems ACKs are defined for multiple purposes: reliable
>       transport, transaction acknowledgment and transaction results. Of
>       course the first isn't needed, and implications of the others
>       should be clear.  For example, in section 7.10, why would there be
>       a retry when receiving a Destination Up ACK signal indicating an
>       error?

Fixed, although the text still refers to responses as acknowledging
their corresponding messages which is a bit misleading.  Better to just
say that a response is triggered by the corresponding message.

>     - There is no discussion on scaling considerations. Are there really
>       none?  For example, how often might be appropriate to issue/limit
>       Peer Updates based to changes in link quality, or how to handle
>       the case where a large number (all or most) of destinations go
>       down.

Improved. There is now an informative section (7) which has some some
conformance statements, but no defined mechanisms.  I'd prefer to see
some mechanisms, but also understand that this may be FFS.

>     - There are 13 places where the protocol allows implementation to
>       define their own 'heuristics'.  Some of these seem unnecessary due
>       to the TCP point raised above, but any that remain in the protocol
>       should be fully specified to ensure predictable/consistent
>       behavior from implementations.

Much improved. It's down to 4 (one of which, in section 5.1) partially
conflicts with other text. Again, I think these should be fully specified.

>
>     - Data Items are defined for "Extensions" and "Experimental
>       Definition" (Sections 8.7 and 8.8).  Both seem to support for
>       optional mechanisms, but the former uses assigned numeric values,
>       why the latter uses UTF-8 strings.
>       o What, if any, is the intended distinction/relationship between
>         these?
>       o How does an "Experimental Definition" become standardized?

Again, much improved.  I'll start a separate thread related to the new
mechanism.

>     - Sections 8.19 and 8.20 define "Resources" related Data Items.  The
>       definition related to these basically says a resources is "An
>       8-bit integer percentage, 0-100, representing the amount of
>       resources allocated to receiving|transmitting data.".  If I were
>       implementing this protocol, I'd have no idea how to produce,
>       update or use this information.  I think there is some missing
>       informative and normative (RFC 2119) text related to these
>       formats.

Unless I missed it, no change.

The basic point is that the document should state what are interoperable
implementations supposed to do with this parameter.

>
>     - Sections 8.21 and 8.22 (Relative Link Quality) have a similar
>       problem of being under described, in particular it's unclear if
>       there's a meaningful, non-proprietary definition for link quality
>       that an implementation is to act on or if the passed value is just
>       passed for as monitoring information.  Either way, this needs to
>       be clarified.
Unless I missed it, no change.

The basic point is that the document should state what are interoperable
implementations supposed to do with this parameter.

>
>     - Section 9 defines a "credit-windowing scheme analogous to the one
>       documented in [RFC5578]". It describes how credits are exchanged,
>       but it provides zero definition on the implications or use of
>       credits relative to the data plane.   

moved to it's own document.

>     - Multiple ways to implement the same function are allowed, e.g.,
>       optional presence of Status, Interval and TCP port.  Generally
>       allowing such complicates testing and leads to interoperability
>       issues.  The document should pick one way and require it.

This issue is still there WRT Status and specifying TCP ports.  I
recommend always requiring the presence of TCP port filed and status
data items in places where they are optional today.

>     - The document doesn't state if there are any ordering requirements
>       on data items. It should be explicit on this, e.g., there are no
>       ordering requirements on the placement of Data Items within
>       Signals.
Fixed.

>     - The required and optional data items that are permitted on a
>       signal isn't always clear.  For example are 0/1/N copies of a
>       particular Data Item required/allowed.  Using something like ABNF
>       would really help formalize and clarify this.

Improved, but errors remain.  For example the Section 8.2 states 'one or
more DLEP data items' , when zero or more is correct.

>     - The document doesn't clearly delineate from informative/narrative
>       text, normative / required processing procedures, and message
>       formats. This by itself is not necessarily a major issue, it just
>       makes it harder to (write,) review and implement the protocol.
>       What is a major issue is that this approach allows for duplicate
>       (and sometimes contradictory) normative procedures and for
>       omissions in procedures (particularly related to exception/error
>       processing).  Specific examples are included above and below.  It
>       would be best to ensure that each required processing behavior is
>       defined just once and in a consistent way.

There is * a lot* of duplicative text in this document. While
consistency is improved, the redundant and scattered definition of
processing makes it very hard to tell if there are omissions or
contradictions.  I strongly recommend that the document remove any
redundant conformance statements.  That is, for any particular
processing or formatting requirement there is only one place that states
the requirement with RFC2119 MUST/SHOULD/MAY language.  Just one example
to illustrate (using idnits line numbering)

392	   DLEP modem implementations MUST announce all metric items that will
393	   be reported during the session, and provide default values for those
394	   metrics, in the Session Initialization Response message
395	   (Section 9.4). 


413	   As mentioned above, DLEP modem implementations MUST announce all
414	   supported metric items during the Session Initialization state.


640	   As mentioned before, the Session Initialization Response message MUST
641	   contain metric data items for all metrics that will be used during
642	   the session. 


1055	   All supported metric data items MUST be included in the Session
1056	   Initialization Response message,

1092	   The Session Initialization Response message MUST contain one of each
1093	   of the following data items, if the data item will be used during the
1094	   lifetime of the session:


Again, this more than just a style point.  It's really hard to tell if
all cases are covered from a review (and implementation) perspective
with the current redundant and distributed approach to processing
conformance.

>     - The security consideration section is inadequate.  This section
>       should address the security of the DLEP protocol, not user
>       traffic.  It should include an analysis of risks/threats/possible
>       exploits and how these are mitigated by the protocol.  rfc6952,
>       and the protocols it references can serve as examples.

I think the DLEP-17 related thread on this pretty much covers my open
concerns.  One point is that authentication of privacy of the discovery
signals/messages also is a concern and should be addressed.  I like the
proposed 802.1AE solution, but have no feel for if the security
directorate/AD will find this acceptable.

> Minor Issues:
>
>     - The data and signal type fields are both 8 bits.  This seems
>       pretty small, particularly the data type field.  Given this is a
>       control protocol, I think a larger (at least data type) field
>       would provide better "future proofing".
fixed.

>     - 2^32 versions are currently allowed (section 8.1).  This seems a
>       bit excessive.  I'd opt for max of 8 bits here myself.
fixed.

>     - It's probably too late, but it probably would be cleaner to have a
>       generic ack signal rather than a per signal type ack. I mention
>       this here as this may come up again when clarifying the
>       transaction model (as mentioned above.)
discussed/updated by doc/closed.

>     - Section 2: Assumptions
>       This section includes informative and normative text so is more
>       than just Assumptions.  Personally, I'd remove all normative text
>       from the section.

Almost fully addressed.  I thing the IPv6 recommendation is a bit
misplaced, and as discussed elsewhere, problematic.

>     - There are no specific rules related to UDP header formation.
This definition is mostly in section 5, but also partially (repeated) in
Section 9.  Pick one, please.

Also v6 is recommended in one place in the document and required in 5.1. 

It's unclear why section 5.1 constrains the source port values.

>     - Sections 8.10->8.17.  Isn't add/drop indicator needed for subnets
>       in destination update signals?
Closed.

>
>     - The IANA Considerations sections must follow​ RFC2360.
Getting closer, but still needs work to fully align with RFC5226. 
Notably absent are Well-Known IANA Policy Definitions and registry
namespaces.

>     - New registries must include initial values, which are defined in
>       the document.  (The document currently has many TBDs that should
>       be replaced.)
Fixed, although message values are defined both in table 1 and in the
body of section 9.
>     - New registries need an allocation policy, e.g.:
>     The registry should be established with registration policies of
>     "Standards Action" (for Standards Track documents) and
>     “Specification Required" (for other documents). The designated
>     expert is any current <fill-in> WG chair.
Still open.

> Nits:
>
>     - The document introduces the terms "signals" and "data items" for
>       what is commonly called "messages" and "TLVs" (or objects) in
>       other protocols.  It's probably too late to change this, but I
>       think the introduction of unique terminology is counter
>       productive.
discussed/updated/closed.

>     - Use of RFC 2119 conformance language is a bit rough, and there are
>       words in all caps that are not defined in RFC2119. Take a look at
>       http://trac.tools.ietf.org/wg/teas/trac/wiki/PSGuideline for some
>       suggestions.
Still an open issue.  Basically 2119 language should be used to cover
required processing that impacts externally visible behavior.  (It can't
apply to people or informative text.  Also each behavior should be
formally specified only once.  Certainly narrative/informative text
related to the processing can occur in multiple places as makes sense to
describe the solution.

>     - Internal socket operation is mentioned a couple of times.  It
>       really shouldn't be, the spec should define behavior on the wire.
mentioned now only once (line 569) -
>     - The Length fields are missing unit of measure (presumably octets)
fixed.

>     - The Mnemonics are used basically once and don't really add value,
>       suggest dropping them.
closed.
>     - How/when is the "Unknown Signal" Status Code sent?
>
>     - Section 8.7: Extension List should be shown as a variable length
>       field.

fixed.
>     - Section 8.8: Experiment List should be shown as a variable length
>       field.
dropped.

> That's it -- for now -- hopefully I didn't miss anything.  Look forward
> to hearing response to the above (and how I got things hopelessly wrong ;-)

Again good progress.  I do have a few more high level issues that I'll
raise in separate threads.

Lou
> Lou
>
>



From nobody Tue Dec  1 17:30:07 2015
Return-Path: <ratliffstan@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 6EF0D1B3068; Tue,  1 Dec 2015 17:30:06 -0800 (PST)
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 MOYSrAkXH6XJ; Tue,  1 Dec 2015 17:30:03 -0800 (PST)
Received: from mail-lf0-x22a.google.com (mail-lf0-x22a.google.com [IPv6:2a00:1450:4010:c07::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 79F7F1B3065; Tue,  1 Dec 2015 17:30:03 -0800 (PST)
Received: by lfdl133 with SMTP id l133so31838612lfd.2; Tue, 01 Dec 2015 17:30:01 -0800 (PST)
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=Qok3epUyoIp8O5dXbMJdU0WhdQT+8Cg61B0Armv1wJ4=; b=gXH01Vn4RIeaQp2RIqeA+E3pZ81aVuLRG5qJnX9gP0G9k2OwPC3gNhNLA9faXwKwza Zlg+F7ZqyjRMA/03CHaEIKxEUrBuDf7S4VLD0tvfoJHlH8X2Fww3gXGE7i8jcpnZdfB1 /1qO3JWc3mjClRyLQYaa5yt59Egp6KTmjasDkBJvFcU3PHszGvja/xhlQju9tniicEVA uqfKqDYI+x5EUxWGhZGEPhiNDBmAScbnQ/lsnC0lR7upLcmbiqlL3h+jPBDCYXAJ0jXH meZLVlIRzRrLDI5drDPMenzzQPb+Wme2HHMPsDr50sElq7YrrO7485DdoGXf9O2kFIqI Wz4Q==
MIME-Version: 1.0
X-Received: by 10.25.83.146 with SMTP id h140mr432597lfb.52.1449019801671; Tue, 01 Dec 2015 17:30:01 -0800 (PST)
Received: by 10.25.209.71 with HTTP; Tue, 1 Dec 2015 17:30:01 -0800 (PST)
In-Reply-To: <565E2EC4.50504@labn.net>
References: <5575E8A7.6030508@labn.net> <565E2EC4.50504@labn.net>
Date: Tue, 1 Dec 2015 20:30:01 -0500
Message-ID: <CALtoyo=2YrNT9CJCoqJ_x1+Cbyu8stfNuwjQXJFvjWfE9h+2Mw@mail.gmail.com>
From: Stan Ratliff <ratliffstan@gmail.com>
To: Lou Berger <lberger@labn.net>
Content-Type: multipart/alternative; boundary=001a11419fc08d21820525e0365f
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/OfQ3cf69gmQWjazOOsC_pgWoxys>
Cc: MANET IETF <manet@ietf.org>, draft-ietf-manet-dlep@ietf.org
Subject: Re: [manet] DLEP-17 and RtgDir review of draft-ietf-manet-dlep-14
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: <https://mailarchive.ietf.org/arch/browse/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: Wed, 02 Dec 2015 01:30:06 -0000

--001a11419fc08d21820525e0365f
Content-Type: text/plain; charset=UTF-8

Lou,

Thanks for the review. I wanted to respond to a couple of your points while
they're fresh on my mind:

On Tue, Dec 1, 2015 at 6:35 PM, Lou Berger <lberger@labn.net> wrote:

[snip]


> >     - Sections 8.19 and 8.20 define "Resources" related Data Items.  The
> >       definition related to these basically says a resources is "An
> >       8-bit integer percentage, 0-100, representing the amount of
> >       resources allocated to receiving|transmitting data.".  If I were
> >       implementing this protocol, I'd have no idea how to produce,
> >       update or use this information.  I think there is some missing
> >       informative and normative (RFC 2119) text related to these
> >       formats.
>
> Unless I missed it, no change.
>
> The basic point is that the document should state what are interoperable
> implementations supposed to do with this parameter.
>
> >
> >     - Sections 8.21 and 8.22 (Relative Link Quality) have a similar
> >       problem of being under described, in particular it's unclear if
> >       there's a meaningful, non-proprietary definition for link quality
> >       that an implementation is to act on or if the passed value is just
> >       passed for as monitoring information.  Either way, this needs to
> >       be clarified.
> Unless I missed it, no change.
>
> The basic point is that the document should state what are interoperable
> implementations supposed to do with this parameter.
>
> [snip]

The document doesn't mention what an interoperable implementation is
supposed to do with *any* data item. AFAIK, no data item has a "and here's
what you do with it" clause (and if there is one there, please let me know
and I'll delete it). ;-)

What you actually do with the data items is out of scope for this document
- by necessity. If we attempted to document what could (or should) be done
with these data items, the spec is 'deat meat' - we'll be at this for the
next 40 years, since the data (for instance, data rate) *could* be used in
more than one place - the complexity explodes exponentially, the arguing
goes on and on without end. The short answer is - when received, the data
can be a part of your implementation's information base.

Oh, and as to the 2 above data items - they are implemented with
proprietary algorithms. If words to that effect will clear the issue up,
let me know and I'll attempt to add that.

Regards,
Stan

--001a11419fc08d21820525e0365f
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Lou, <br><br></div>Thanks for the review. I wanted to=
 respond to a couple of your points while they&#39;re fresh on my mind: <br=
><div><div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Tue=
, Dec 1, 2015 at 6:35 PM, Lou Berger <span dir=3D"ltr">&lt;<a href=3D"mailt=
o:lberger@labn.net" target=3D"_blank">lberger@labn.net</a>&gt;</span> wrote=
:<br><div><br></div><div>[snip]<br>=C2=A0<br></div><blockquote class=3D"gma=
il_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-lef=
t:1ex">
&gt;=C2=A0 =C2=A0 =C2=A0- Sections 8.19 and 8.20 define &quot;Resources&quo=
t; related Data Items.=C2=A0 The<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0definition related to these basically says a=
 resources is &quot;An<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A08-bit integer percentage, 0-100, representin=
g the amount of<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0resources allocated to receiving|transmittin=
g data.&quot;.=C2=A0 If I were<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0implementing this protocol, I&#39;d have no =
idea how to produce,<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0update or use this information.=C2=A0 I thin=
k there is some missing<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0informative and normative (RFC 2119) text re=
lated to these<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0formats.<br>
<br>
Unless I missed it, no change.<br>
<br>
The basic point is that the document should state what are interoperable<br=
>
implementations supposed to do with this parameter.<br>
<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0- Sections 8.21 and 8.22 (Relative Link Quality) ha=
ve a similar<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0problem of being under described, in particu=
lar it&#39;s unclear if<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0there&#39;s a meaningful, non-proprietary de=
finition for link quality<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0that an implementation is to act on or if th=
e passed value is just<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0passed for as monitoring information.=C2=A0 =
Either way, this needs to<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0be clarified.<br>
Unless I missed it, no change.<br>
<br>
The basic point is that the document should state what are interoperable<br=
>
implementations supposed to do with this parameter.<br>
<br></blockquote></div>[snip]<br><br></div><div class=3D"gmail_extra">The d=
ocument doesn&#39;t mention what an interoperable implementation is suppose=
d to do with *any* data item. AFAIK, no data item has a &quot;and here&#39;=
s what you do with it&quot; clause (and if there is one there, please let m=
e know and I&#39;ll delete it). ;-)<br><br>What you actually do with the da=
ta items is out of scope for this document - by necessity. If we attempted =
to document what could (or should) be done with these data items, the spec =
is &#39;deat meat&#39; - we&#39;ll be at this for the next 40 years, since =
the data (for instance, data rate) *could* be used in more than one place -=
 the complexity explodes exponentially, the arguing goes on and on without =
end. The short answer is - when received, the data can be a part of your im=
plementation&#39;s information base. <br><br></div><div class=3D"gmail_extr=
a">Oh, and as to the 2 above data items - they are implemented with proprie=
tary algorithms. If words to that effect will clear the issue up, let me kn=
ow and I&#39;ll attempt to add that. <br><br></div><div class=3D"gmail_extr=
a">Regards,<br></div><div class=3D"gmail_extra">Stan<br><br></div></div></d=
iv></div>

--001a11419fc08d21820525e0365f--


From nobody Tue Dec  1 17:51:27 2015
Return-Path: <lberger@labn.net>
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 D097B1B30B4 for <manet@ietfa.amsl.com>; Tue,  1 Dec 2015 17:51:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.667
X-Spam-Level: 
X-Spam-Status: No, score=-1.667 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, IP_NOT_FRIENDLY=0.334, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no
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 0mIyiYsKV1bR for <manet@ietfa.amsl.com>; Tue,  1 Dec 2015 17:51:24 -0800 (PST)
Received: from gproxy5-pub.mail.unifiedlayer.com (gproxy5-pub.mail.unifiedlayer.com [67.222.38.55]) by ietfa.amsl.com (Postfix) with SMTP id 3B0621B30AF for <manet@ietf.org>; Tue,  1 Dec 2015 17:51:19 -0800 (PST)
Received: (qmail 2118 invoked by uid 0); 2 Dec 2015 01:51:17 -0000
Received: from unknown (HELO cmgw2) (10.0.90.83) by gproxy5.mail.unifiedlayer.com with SMTP; 2 Dec 2015 01:51:17 -0000
Received: from box313.bluehost.com ([69.89.31.113]) by cmgw2 with  id oRrC1r0062SSUrH01RrFjo; Tue, 01 Dec 2015 18:51:15 -0700
X-Authority-Analysis: v=2.1 cv=dqRIVTQ4 c=1 sm=1 tr=0 a=h1BC+oY+fLhyFmnTBx92Jg==:117 a=wU2YTnxGAAAA:8 a=cNaOj0WVAAAA:8 a=IkcTkHD0fZMA:10 a=-NfooI8aBGcA:10 a=uEJ9t1CZtbIA:10 a=wUQvQvOEmiQA:10 a=YtC-WPwpy5_K-0Ty4NoA:9 a=QEXdDO2ut3YA:10
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=labn.net; s=default;  h=Content-Transfer-Encoding:Content-Type:In-Reply-To:MIME-Version:Date:Message-ID:From:Cc:References:To:Subject; bh=nTL/asNdrPP2fYiCxxkOfHnXxWqVoLLq54rkunuccQo=;  b=LNEZJoFKYgQL8C5TNXTtr7f2gvlCXZsK7J3O9O/DiUz3Gc0og2IwnN+RTm+jj6VJFGiWzQzKR1VYqPvMYH/5eZy6+NE2k1zpnGd5HHuLk09wIM8+sSyyeDIeYEyz+JjT;
Received: from box313.bluehost.com ([69.89.31.113]:33497 helo=[127.0.0.1]) by box313.bluehost.com with esmtpa (Exim 4.84) (envelope-from <lberger@labn.net>) id 1a3wZd-000652-Ld; Tue, 01 Dec 2015 18:51:13 -0700
To: Stan Ratliff <ratliffstan@gmail.com>
References: <5575E8A7.6030508@labn.net> <565E2EC4.50504@labn.net> <CALtoyo=2YrNT9CJCoqJ_x1+Cbyu8stfNuwjQXJFvjWfE9h+2Mw@mail.gmail.com>
From: Lou Berger <lberger@labn.net>
X-Enigmail-Draft-Status: N1110
Message-ID: <565E4E8D.8080704@labn.net>
Date: Tue, 1 Dec 2015 20:51:09 -0500
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.4.0
MIME-Version: 1.0
In-Reply-To: <CALtoyo=2YrNT9CJCoqJ_x1+Cbyu8stfNuwjQXJFvjWfE9h+2Mw@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-Identified-User: {1038:box313.bluehost.com:labnmobi:labn.net} {sentby:smtp auth 69.89.31.113 authed with lberger@labn.net}
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/pGF6e39vW103XsNauSrELji5efA>
Cc: MANET IETF <manet@ietf.org>, draft-ietf-manet-dlep@ietf.org
Subject: Re: [manet] DLEP-17 and RtgDir review of draft-ietf-manet-dlep-14
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: <https://mailarchive.ietf.org/arch/browse/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: Wed, 02 Dec 2015 01:51:26 -0000

Stan,

On 12/1/2015 8:30 PM, Stan Ratliff wrote:
> Lou,
>
> Thanks for the review. I wanted to respond to a couple of your points
> while they're fresh on my mind:
>
> On Tue, Dec 1, 2015 at 6:35 PM, Lou Berger <lberger@labn.net
> <mailto:lberger@labn.net>> wrote:
>
> [snip]
>  
>
>     >     - Sections 8.19 and 8.20 define "Resources" related Data
>     Items.  The
>     >       definition related to these basically says a resources is "An
>     >       8-bit integer percentage, 0-100, representing the amount of
>     >       resources allocated to receiving|transmitting data.".  If
>     I were
>     >       implementing this protocol, I'd have no idea how to produce,
>     >       update or use this information.  I think there is some missing
>     >       informative and normative (RFC 2119) text related to these
>     >       formats.
>
>     Unless I missed it, no change.
>
>     The basic point is that the document should state what are
>     interoperable
>     implementations supposed to do with this parameter.
>
>     >
>     >     - Sections 8.21 and 8.22 (Relative Link Quality) have a similar
>     >       problem of being under described, in particular it's
>     unclear if
>     >       there's a meaningful, non-proprietary definition for link
>     quality
>     >       that an implementation is to act on or if the passed value
>     is just
>     >       passed for as monitoring information.  Either way, this
>     needs to
>     >       be clarified.
>     Unless I missed it, no change.
>
>     The basic point is that the document should state what are
>     interoperable
>     implementations supposed to do with this parameter.
>
> [snip]
>
> The document doesn't mention what an interoperable implementation is
> supposed to do with *any* data item. AFAIK, no data item has a "and
> here's what you do with it" clause (and if there is one there, please
> let me know and I'll delete it). ;-)

I think the spec is pretty clear what data items 1-16 mean and are to be
used and to be meaningful in an interoperable scenario.

>
> What you actually do with the data items is out of scope for this
> document - by necessity. If we attempted to document what could (or
> should) be done with these data items, the spec is 'deat meat' - we'll
> be at this for the next 40 years, since the data (for instance, data
> rate) *could* be used in more than one place - the complexity explodes
> exponentially, the arguing goes on and on without end. The short
> answer is - when received, the data can be a part of your
> implementation's information base.
>

for link quality, I think simply saying that the metric can be used (for
example) by a router when selecting between alternate available paths. 
In which case I'd ask why is this limited to 100 rather than the full
range of the field.

for resources, I actually have no guess as to what it means or what you
expect a router to do with this. Without additional information and
assuming your next statement is correct, it's for strictly proprietary
(and non-interoperable) applications, I'd say drop it from the spec.

Lou

> Oh, and as to the 2 above data items - they are implemented with
> proprietary algorithms. If words to that effect will clear the issue
> up, let me know and I'll attempt to add that.
>
> Regards,
> Stan
>



From nobody Tue Dec  1 19:36:46 2015
Return-Path: <ratliffstan@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 853A31B3240; Tue,  1 Dec 2015 19:36:45 -0800 (PST)
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 bVWUMFgqD6Ux; Tue,  1 Dec 2015 19:36:43 -0800 (PST)
Received: from mail-lf0-x22a.google.com (mail-lf0-x22a.google.com [IPv6:2a00:1450:4010:c07::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E2D541B323E; Tue,  1 Dec 2015 19:36:42 -0800 (PST)
Received: by lfaz4 with SMTP id z4so34606082lfa.0; Tue, 01 Dec 2015 19:36:41 -0800 (PST)
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=4vaAUJ9GJm7W+upqPvFSIKVbdcWGZVwSEZjTXA2nH84=; b=riFeyzNsBYdJU1JiQHtrobzfd5ikBBWjFqWMh5wShN87PCT651LeB6e75MI8VvfQ1c FAupniRifcHEYEVaXFxJAInDM+N50Qgn1c/yvtogQvxk/u49RagbM7NV5k4J98ysG2wQ tzTnn+Wt7V+XOjkRk4OwFNL9n7u+IOoCwxpaVX8oXokw0TzRtLaZc1XyUvRX+Hgam/2g GrVNV23ubZnysdAD6cnE6l9edW4zmSURzETi5tpA2WD3VpaC2ffFedylutj4vLXcB97a k8t/JiItBXltGs0WVeP0YO0H+ghaCHmlliifDUQX7uOZl7NUOhG8EKT3ulPB3PrEPEvN fVgw==
MIME-Version: 1.0
X-Received: by 10.25.83.146 with SMTP id h140mr695389lfb.52.1449027401113; Tue, 01 Dec 2015 19:36:41 -0800 (PST)
Received: by 10.25.209.71 with HTTP; Tue, 1 Dec 2015 19:36:41 -0800 (PST)
In-Reply-To: <565E4E8D.8080704@labn.net>
References: <5575E8A7.6030508@labn.net> <565E2EC4.50504@labn.net> <CALtoyo=2YrNT9CJCoqJ_x1+Cbyu8stfNuwjQXJFvjWfE9h+2Mw@mail.gmail.com> <565E4E8D.8080704@labn.net>
Date: Tue, 1 Dec 2015 22:36:41 -0500
Message-ID: <CALtoyokCuQOWAX8QYPK79_W+75cQhuFKvBGqwCf6NSpvD1-r2A@mail.gmail.com>
From: Stan Ratliff <ratliffstan@gmail.com>
To: Lou Berger <lberger@labn.net>
Content-Type: multipart/alternative; boundary=001a11419fc08369910525e1fbac
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/EXOlRXc16sCmHSPHAX8e5rI8Ywg>
Cc: MANET IETF <manet@ietf.org>, draft-ietf-manet-dlep@ietf.org
Subject: Re: [manet] DLEP-17 and RtgDir review of draft-ietf-manet-dlep-14
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: <https://mailarchive.ietf.org/arch/browse/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: Wed, 02 Dec 2015 03:36:45 -0000

--001a11419fc08369910525e1fbac
Content-Type: text/plain; charset=UTF-8

On Tue, Dec 1, 2015 at 8:51 PM, Lou Berger <lberger@labn.net> wrote:

> Stan,
>
> On 12/1/2015 8:30 PM, Stan Ratliff wrote:
> > Lou,
> >
> > Thanks for the review. I wanted to respond to a couple of your points
> > while they're fresh on my mind:
> >
> > On Tue, Dec 1, 2015 at 6:35 PM, Lou Berger <lberger@labn.net
> > <mailto:lberger@labn.net>> wrote:
> >
> > [snip]
> >
> >
> >     >     - Sections 8.19 and 8.20 define "Resources" related Data
> >     Items.  The
> >     >       definition related to these basically says a resources is "An
> >     >       8-bit integer percentage, 0-100, representing the amount of
> >     >       resources allocated to receiving|transmitting data.".  If
> >     I were
> >     >       implementing this protocol, I'd have no idea how to produce,
> >     >       update or use this information.  I think there is some
> missing
> >     >       informative and normative (RFC 2119) text related to these
> >     >       formats.
> >
> >     Unless I missed it, no change.
> >
> >     The basic point is that the document should state what are
> >     interoperable
> >     implementations supposed to do with this parameter.
> >
> >     >
> >     >     - Sections 8.21 and 8.22 (Relative Link Quality) have a similar
> >     >       problem of being under described, in particular it's
> >     unclear if
> >     >       there's a meaningful, non-proprietary definition for link
> >     quality
> >     >       that an implementation is to act on or if the passed value
> >     is just
> >     >       passed for as monitoring information.  Either way, this
> >     needs to
> >     >       be clarified.
> >     Unless I missed it, no change.
> >
> >     The basic point is that the document should state what are
> >     interoperable
> >     implementations supposed to do with this parameter.
> >
> > [snip]
> >
> > The document doesn't mention what an interoperable implementation is
> > supposed to do with *any* data item. AFAIK, no data item has a "and
> > here's what you do with it" clause (and if there is one there, please
> > let me know and I'll delete it). ;-)
>
> I think the spec is pretty clear what data items 1-16 mean and are to be
> used and to be meaningful in an interoperable scenario.
>
> >
> > What you actually do with the data items is out of scope for this
> > document - by necessity. If we attempted to document what could (or
> > should) be done with these data items, the spec is 'deat meat' - we'll
> > be at this for the next 40 years, since the data (for instance, data
> > rate) *could* be used in more than one place - the complexity explodes
> > exponentially, the arguing goes on and on without end. The short
> > answer is - when received, the data can be a part of your
> > implementation's information base.
> >
>
> for link quality, I think simply saying that the metric can be used (for
> example) by a router when selecting between alternate available paths.
>

That's true for any metric, including "Resources". I respectfully disagree
that we should step into the "... , and here's what you would do with
it..." morass. You said in your response "I think the spec is pretty clear
what data items 1-16 mean and are to be used", but I note again, the spec
doesn't specifically say how (or even whether) they are supposed to be
used. I do not believe we should make an exception for the above two.

Regards,
Stan




> In which case I'd ask why is this limited to 100 rather than the full
> range of the field.
>
> for resources, I actually have no guess as to what it means or what you
> expect a router to do with this. Without additional information and
> assuming your next statement is correct, it's for strictly proprietary
> (and non-interoperable) applications, I'd say drop it from the spec.
>
> Lou
>
> > Oh, and as to the 2 above data items - they are implemented with
> > proprietary algorithms. If words to that effect will clear the issue
> > up, let me know and I'll attempt to add that.
> >
> > Regards,
> > Stan
> >
>
>
>

--001a11419fc08369910525e1fbac
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><div class=3D"gmail_quo=
te">On Tue, Dec 1, 2015 at 8:51 PM, Lou Berger <span dir=3D"ltr">&lt;<a hre=
f=3D"mailto:lberger@labn.net" target=3D"_blank">lberger@labn.net</a>&gt;</s=
pan> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0p=
x 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Stan,<br>
<br>
On 12/1/2015 8:30 PM, Stan Ratliff wrote:<br>
&gt; Lou,<br>
&gt;<br>
&gt; Thanks for the review. I wanted to respond to a couple of your points<=
br>
&gt; while they&#39;re fresh on my mind:<br>
&gt;<br>
&gt; On Tue, Dec 1, 2015 at 6:35 PM, Lou Berger &lt;<a href=3D"mailto:lberg=
er@labn.net">lberger@labn.net</a><br>
&gt; &lt;mailto:<a href=3D"mailto:lberger@labn.net">lberger@labn.net</a>&gt=
;&gt; wrote:<br>
&gt;<br>
&gt; [snip]<br>
&gt;<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0- Sections 8.19 and 8.20 de=
fine &quot;Resources&quot; related Data<br>
&gt;=C2=A0 =C2=A0 =C2=A0Items.=C2=A0 The<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0definition related t=
o these basically says a resources is &quot;An<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A08-bit integer percen=
tage, 0-100, representing the amount of<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0resources allocated =
to receiving|transmitting data.&quot;.=C2=A0 If<br>
&gt;=C2=A0 =C2=A0 =C2=A0I were<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0implementing this pr=
otocol, I&#39;d have no idea how to produce,<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0update or use this i=
nformation.=C2=A0 I think there is some missing<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0informative and norm=
ative (RFC 2119) text related to these<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0formats.<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0Unless I missed it, no change.<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0The basic point is that the document should state w=
hat are<br>
&gt;=C2=A0 =C2=A0 =C2=A0interoperable<br>
&gt;=C2=A0 =C2=A0 =C2=A0implementations supposed to do with this parameter.=
<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0- Sections 8.21 and 8.22 (R=
elative Link Quality) have a similar<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0problem of being und=
er described, in particular it&#39;s<br>
&gt;=C2=A0 =C2=A0 =C2=A0unclear if<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0there&#39;s a meanin=
gful, non-proprietary definition for link<br>
&gt;=C2=A0 =C2=A0 =C2=A0quality<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0that an implementati=
on is to act on or if the passed value<br>
&gt;=C2=A0 =C2=A0 =C2=A0is just<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0passed for as monito=
ring information.=C2=A0 Either way, this<br>
&gt;=C2=A0 =C2=A0 =C2=A0needs to<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0be clarified.<br>
&gt;=C2=A0 =C2=A0 =C2=A0Unless I missed it, no change.<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0The basic point is that the document should state w=
hat are<br>
&gt;=C2=A0 =C2=A0 =C2=A0interoperable<br>
&gt;=C2=A0 =C2=A0 =C2=A0implementations supposed to do with this parameter.=
<br>
&gt;<br>
&gt; [snip]<br>
&gt;<br>
&gt; The document doesn&#39;t mention what an interoperable implementation =
is<br>
&gt; supposed to do with *any* data item. AFAIK, no data item has a &quot;a=
nd<br>
&gt; here&#39;s what you do with it&quot; clause (and if there is one there=
, please<br>
&gt; let me know and I&#39;ll delete it). ;-)<br>
<br>
I think the spec is pretty clear what data items 1-16 mean and are to be<br=
>
used and to be meaningful in an interoperable scenario.<br>
<br>
&gt;<br>
&gt; What you actually do with the data items is out of scope for this<br>
&gt; document - by necessity. If we attempted to document what could (or<br=
>
&gt; should) be done with these data items, the spec is &#39;deat meat&#39;=
 - we&#39;ll<br>
&gt; be at this for the next 40 years, since the data (for instance, data<b=
r>
&gt; rate) *could* be used in more than one place - the complexity explodes=
<br>
&gt; exponentially, the arguing goes on and on without end. The short<br>
&gt; answer is - when received, the data can be a part of your<br>
&gt; implementation&#39;s information base.<br>
&gt;<br>
<br>
for link quality, I think simply saying that the metric can be used (for<br=
>
example) by a router when selecting between alternate available paths.<br><=
/blockquote><div><br></div><div>That&#39;s true for any metric, including &=
quot;Resources&quot;. I respectfully disagree that we should step into the =
&quot;... , and here&#39;s what you would do with it...&quot; morass. You s=
aid in your response &quot;I think the spec is pretty clear what data items=
 1-16 mean and are to be used&quot;, but I note again, the spec doesn&#39;t=
 specifically say how (or even whether) they are supposed to be used. I do =
not believe we should make an exception for the above two. <br><br></div><d=
iv>Regards,<br></div><div>Stan<br><br><br> </div><div>=C2=A0</div><blockquo=
te class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px =
solid rgb(204,204,204);padding-left:1ex">
In which case I&#39;d ask why is this limited to 100 rather than the full<b=
r>
range of the field.<br>
<br>
for resources, I actually have no guess as to what it means or what you<br>
expect a router to do with this. Without additional information and<br>
assuming your next statement is correct, it&#39;s for strictly proprietary<=
br>
(and non-interoperable) applications, I&#39;d say drop it from the spec.<br=
>
<br>
Lou<br>
<br>
&gt; Oh, and as to the 2 above data items - they are implemented with<br>
&gt; proprietary algorithms. If words to that effect will clear the issue<b=
r>
&gt; up, let me know and I&#39;ll attempt to add that.<br>
&gt;<br>
&gt; Regards,<br>
&gt; Stan<br>
&gt;<br>
<br>
<br>
</blockquote></div><br></div></div>

--001a11419fc08369910525e1fbac--


From nobody Wed Dec  2 02:42:58 2015
Return-Path: <chris.dearlove@baesystems.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 DA6921A8763 for <manet@ietfa.amsl.com>; Wed,  2 Dec 2015 02:42:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.909
X-Spam-Level: 
X-Spam-Status: No, score=-1.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, T_RP_MATCHES_RCVD=-0.01] 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 3ID5-mPnjWH9 for <manet@ietfa.amsl.com>; Wed,  2 Dec 2015 02:42:52 -0800 (PST)
Received: from ukmta4.baesystems.com (ukmta4.baesystems.com [20.133.40.56]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A6F9E1A8760 for <manet@ietf.org>; Wed,  2 Dec 2015 02:42:51 -0800 (PST)
X-IronPort-AV: E=Sophos; i="5.20,372,1444690800"; d="scan'208,217"; a="18748859"
Received: from unknown (HELO baemasodc005.greenlnk.net) ([10.108.52.29]) by ukmta4.baesystems.com with ESMTP; 02 Dec 2015 10:42:48 +0000
X-IronPort-AV: E=Sophos;i="5.20,372,1444690800";  d="scan'208,217";a="125804711"
Received: from glkxh0004v.greenlnk.net ([10.109.2.35]) by baemasodc005.greenlnk.net with ESMTP; 02 Dec 2015 10:42:49 +0000
Received: from GLKXM0002V.GREENLNK.net ([169.254.5.2]) by GLKXH0004V.GREENLNK.net ([10.109.2.35]) with mapi id 14.03.0248.002; Wed, 2 Dec 2015 10:42:49 +0000
From: "Dearlove, Christopher (UK)" <chris.dearlove@baesystems.com>
To: "manet@ietf.org" <manet@ietf.org>
Thread-Topic: DLEP-17 review, part 1
Thread-Index: AdEs6MT5z4eIceQwQq+TqWGCuJRrnw==
Date: Wed, 2 Dec 2015 10:42:48 +0000
Message-ID: <B31EEDDDB8ED7E4A93FDF12A4EECD30D7D76BD5F@GLKXM0002V.GREENLNK.net>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.109.62.6]
Content-Type: multipart/alternative; boundary="_000_B31EEDDDB8ED7E4A93FDF12A4EECD30D7D76BD5FGLKXM0002VGREEN_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/YV3eWX402G-B2l-a2iniUljAZtg>
Subject: [manet] DLEP-17 review, part 1
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: <https://mailarchive.ietf.org/arch/browse/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: Wed, 02 Dec 2015 10:42:57 -0000

--_000_B31EEDDDB8ED7E4A93FDF12A4EECD30D7D76BD5FGLKXM0002VGREEN_
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable

I'm calling this part 1, as I hope to get time to review the rest. But as I=
'm not sure when, I'll give you what I've got up to and including Section 4=
. Of course I might want to revisit after reading rest of draft.

Section 1. I think 802.11 should at the least be qualified with IEEE on fir=
st use. On balance I think not referencing it is OK, but I did think about =
that.

Section 1, paragraph 2. The issue with an event driven paradigm is message =
loss. Here of course you plan no message loss by having a reliable modem-ro=
uter link. But that (a) isn't indicated here, and (b) this appears to be di=
scussing what happens within the network, where message loss is a real issu=
e. So I think this wording could be improved.

Section 1, reference to DAMA. This I think needs a reference at least. It s=
ort of jars a bit, but may be important (not clear).

Section 1, top of page 6, I think it would be appropriate to indicate that =
DLEP is designed to handle ranges of values that cover all realistic cases.=
 (At least somewhere in the introductory part, not necessarily here.)

I found Figure 2 and text around it confusing. I think what we have is two =
modems of type A - just saying modem A usually means the modem named A, and=
 two of them? But insert type (assuming that's what's meant) in appropriate=
 places and it gets clearer.

Section 1.1, first paragraph. I think data item is usually Data Item. (I ha=
ven't gone through and checked consistency in general - not even where I'm =
up to - this just stood out.)

Section 1.1, second paragraph, "based on a heartbeat". Strictly it doesn't =
time out based on a heartbeat, it times out unless maintained by a message,=
 possibly a heartbeat, i.e. may time out based on absence of a heartbeat (o=
r other message).

Section 1.1. paragraph 3 "a specific, addressable location (e.g. an address=
)". What other possibilities are there other than an address? This also equ=
ates an addressable location and an address, which is confusing. Probably j=
ust delete the parenthesis.

Section 1.1 says a destination may be physical or logical. I think this sho=
uld start a paragraph, or here be a paragraph on its own. Then the next par=
agraph says what a physical destination is, good. But the next paragraph st=
arts with multicast, and only some way into the paragraph do we discover we=
're now talking about logical destinations. That should be how the paragrap=
h starts.

Section 1.1 says that algorithms used in multicast are up to the implementa=
tion. But I think (and maybe this is done later when specific metrics are i=
ntroduced) the implementer needs to know what a metric is meant to mean, in=
 particular in the multicast case. For example is latency related to worst =
case or average group member?

Section 1.1 final paragraph, "(e.g. multicast)". Are there any other logica=
l examples?

Section 2, security is said to be handled by transport. I know there's been=
 some discussion of this, but for these comments I'll take the draft as wri=
tten. The example is TLS, which is applicable to TCP. But some DLEP message=
s are UDP, what's the security mechanism there? (I've yet to understand how=
 critical the UDP messages are.)

Section 3, first paragraph should "with" be "by", before "a 'best effort'"?

Section 3, penultimate paragraph, from the outside the need to tear down a =
session and re-establish it in order to add new information seems wasteful.=
 Though a simpler protocol of course. Is this expected to be rare?

Section 4. A key issue throughout this, but not clearly indicated up front,=
 is that DLEP is designed for a reliable link between modem and router. (I'=
m not yet sure how reliable the UDP messages need to be.)

Section 4, paragraph 1. This discusses DLEP states in terms that cover both=
 modem and radio. In practice each must run its own state machine. With rel=
iable messages with short responses, those states should be corresponding, =
except short transients. But it's also said later that there can be signifi=
cant delays (but do those apply to state-changing messages?) At the least I=
 think this should be indicated.

Section 4, paragraph 2, "as well as" should this be e.g. "instead of"?

Section 4, paragraph 3. Why should the EUI format match that between the mo=
dem and the radio. Why should DLEP - which should be running over a layer 4=
 connection between the two - know, even less care, what layer 2 addressing=
 is being used on that modem-router link?

Section 4 paragraphs 4 and 6, I think could be clearer that the pair of mes=
sages is one each.

Section 4, paragraph 5 (this may be answered later). Can  the receiver of a=
 Destination Up message (modem or router?) become re-interested after becom=
ing uninterested?

Section 4.1. I spot a military influence in "one (1)". But here I don't thi=
nk needed.

Section 4.1 raised questions in my mind about timeouts and lack thereof - e=
specially as there's an earlier reference (about heartbeats) to timeouts. T=
his is just to say note that the reader may have questions here. Is it wort=
h avoiding them?



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

--_000_B31EEDDDB8ED7E4A93FDF12A4EECD30D7D76BD5FGLKXM0002VGREEN_
Content-Type: text/html; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii">
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-GB" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">I&#8217;m calling this part 1, as I hope to get time=
 to review the rest. But as I&#8217;m not sure when, I&#8217;ll give you wh=
at I&#8217;ve got up to and including Section 4. Of course I might want to =
revisit after reading rest of draft.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Section 1. I think 802.11 should at the least be qua=
lified with IEEE on first use. On balance I think not referencing it is OK,=
 but I did think about that.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Section 1, paragraph 2. The issue with an event driv=
en paradigm is message loss. Here of course you plan no message loss by hav=
ing a reliable modem-router link. But that (a) isn&#8217;t indicated here, =
and (b) this appears to be discussing what
 happens within the network, where message loss is a real issue. So I think=
 this wording could be improved.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Section 1, reference to DAMA. This I think needs a r=
eference at least. It sort of jars a bit, but may be important (not clear).=
<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Section 1, top of page 6, I think it would be approp=
riate to indicate that DLEP is designed to handle ranges of values that cov=
er all realistic cases. (At least somewhere in the introductory part, not n=
ecessarily here.)<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">I found Figure 2 and text around it confusing. I thi=
nk what we have is two modems of type A &#8211; just saying modem A usually=
 means the modem named A, and two of them? But insert type (assuming that&#=
8217;s what&#8217;s meant) in appropriate places and
 it gets clearer.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Section 1.1, first paragraph. I think data item is u=
sually Data Item. (I haven&#8217;t gone through and checked consistency in =
general &#8211; not even where I&#8217;m up to &#8211; this just stood out.=
)<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Section 1.1, second paragraph, &#8220;based on a hea=
rtbeat&#8221;. Strictly it doesn&#8217;t time out based on a heartbeat, it =
times out unless maintained by a message, possibly a heartbeat, i.e. may ti=
me out based on absence of a heartbeat (or other message).<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Section 1.1. paragraph 3 &#8220;a specific, addressa=
ble location (e.g. an address)&#8221;. What other possibilities are there o=
ther than an address? This also equates an addressable location and an addr=
ess, which is confusing. Probably just delete
 the parenthesis.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Section 1.1 says a destination may be physical or lo=
gical. I think this should start a paragraph, or here be a paragraph on its=
 own. Then the next paragraph says what a physical destination is, good. Bu=
t the next paragraph starts with multicast,
 and only some way into the paragraph do we discover we&#8217;re now talkin=
g about logical destinations. That should be how the paragraph starts.<o:p>=
</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Section 1.1 says that algorithms used in multicast a=
re up to the implementation. But I think (and maybe this is done later when=
 specific metrics are introduced) the implementer needs to know what a metr=
ic is meant to mean, in particular
 in the multicast case. For example is latency related to worst case or ave=
rage group member?<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Section 1.1 final paragraph, &#8220;(e.g. multicast)=
&#8221;. Are there any other logical examples?<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Section 2, security is said to be handled by transpo=
rt. I know there&#8217;s been some discussion of this, but for these commen=
ts I&#8217;ll take the draft as written. The example is TLS, which is appli=
cable to TCP. But some DLEP messages are UDP,
 what&#8217;s the security mechanism there? (I&#8217;ve yet to understand h=
ow critical the UDP messages are.)<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Section 3, first paragraph should &#8220;with&#8221;=
 be &#8221;by&#8221;, before &#8220;a &#8216;best effort&#8217;&#8221;?<o:p=
></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Section 3, penultimate paragraph, from the outside t=
he need to tear down a session and re-establish it in order to add new info=
rmation seems wasteful. Though a simpler protocol of course. Is this expect=
ed to be rare?<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Section 4. A key issue throughout this, but not clea=
rly indicated up front, is that DLEP is designed for a reliable link betwee=
n modem and router. (I&#8217;m not yet sure how reliable the UDP messages n=
eed to be.)<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Section 4, paragraph 1. This discusses DLEP states i=
n terms that cover both modem and radio. In practice each must run its own =
state machine. With reliable messages with short responses, those states sh=
ould be corresponding, except short
 transients. But it&#8217;s also said later that there can be significant d=
elays (but do those apply to state-changing messages?) At the least I think=
 this should be indicated.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Section 4, paragraph 2, &#8220;as well as&#8221; sho=
uld this be e.g. &#8220;instead of&#8221;?<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Section 4, paragraph 3. Why should the EUI format ma=
tch that between the modem and the radio. Why should DLEP &#8211; which sho=
uld be running over a layer 4 connection between the two - know, even less =
care, what layer 2 addressing is being used
 on that modem-router link?<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Section 4 paragraphs 4 and 6, I think could be clear=
er that the pair of messages is one each.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Section 4, paragraph 5 (this may be answered later).=
 Can&nbsp; the receiver of a Destination Up message (modem or router?) beco=
me re-interested after becoming uninterested?<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Section 4.1. I spot a military influence in &#8220;o=
ne (1)&#8221;. But here I don&#8217;t think needed.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Section 4.1 raised questions in my mind about timeou=
ts and lack thereof &#8211; especially as there&#8217;s an earlier referenc=
e (about heartbeats) to timeouts. This is just to say note that the reader =
may have questions here. Is it worth avoiding
 them?<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<p>********************************************************************<br>
This email and any attachments are confidential to the intended<br>
recipient and may also be privileged. If you are not the intended<br>
recipient please delete it from your system and notify the sender.<br>
You should not copy it or use it for any purpose nor disclose or<br>
distribute its contents to any other person.<br>
********************************************************************</p></b=
ody>
</html>

--_000_B31EEDDDB8ED7E4A93FDF12A4EECD30D7D76BD5FGLKXM0002VGREEN_--


From nobody Wed Dec  2 06:13:24 2015
Return-Path: <sratliff@idirect.net>
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 6841C1A9064 for <manet@ietfa.amsl.com>; Wed,  2 Dec 2015 06:13:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 Wtf8JxmlXAvG for <manet@ietfa.amsl.com>; Wed,  2 Dec 2015 06:13:16 -0800 (PST)
Received: from smtp2.idirect.net (smtp2.idirect.net [198.180.159.66]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E9ABB1A9040 for <manet@ietf.org>; Wed,  2 Dec 2015 06:13:15 -0800 (PST)
IronPort-PHdr: 9a23:gp92WxRUWoBi9XnPD04Qqw9JH9psv+yvbD5Q0YIujvd0So/mwa65YBaN2/xhgRfzUJnB7Loc0qyN4/6mATZLv8/JmUtBWaIPfidNsd8RkQ0kDZzNImzAB9muURYHGt9fXkRu5XCxPBsdMs//Y1rPvi/6tmZKSV3BPAZ4bt74BpTVx5zukbvipduLOU4W3XKUWvBbElaflU3prM4YgI9veO4a6yDihT92QdlQ3n5iPlmJnhzxtY+a9Z9n9DlM6bp6r5YTGY2zRakzTKRZATI6KCh1oZSz7ViQBTeIszEwX2wMlh1WDkyNxxHgX4zttTP6u/A1mBS5fIe+Gbs0QzW5qatmQQXsjzkKHzQw/XrGkdB9ibkdqxWk8Vg3iYvdZoyJHPtzYq2beskVDyIVW89XWjBpA46gYc0IFeVXbshCqIyo7WEHsR+/CwfoTNjzwzlMi268lfkhye09FQDI0iQhE9MUvX/I6tP4KPFBAqiO0KDUwGCbPLtt0jDn5d2NK0h5rA==
X-IronPort-AV: E=Sophos;i="5.20,373,1444708800"; d="scan'208,217";a="285493"
X-IPAS-Result: A2DLAQCH+15W/8r6+gpdGQEBAQEPAQEBAYI+gR9vBrtqghoBDYFuhg4CgX4UAQEBAQEBAQGBCYItggcBAQEBAw4fOCQCAQgRBAEBKAcyFAkIAQEEARIIx3MBAQEBAQEBAwEBAQEBAQEBARqGVoR7hCoRAVWEKAWScoNqAYgdhRaBYoRDklqDch8BAYJTHYFWcoQuOoEHAQEB
From: "Ratliff, Stanley" <sratliff@idirect.net>
To: "Dearlove, Christopher (UK)" <chris.dearlove@baesystems.com>, "manet@ietf.org" <manet@ietf.org>
Thread-Topic: DLEP-17 review, part 1
Thread-Index: AdEs6MT5z4eIceQwQq+TqWGCuJRrnwAIpSfQ
Date: Wed, 2 Dec 2015 14:13:11 +0000
Message-ID: <9bce68171af242f2abcfa3af482365c7@VAUSDITCHM2.idirect.net>
References: <B31EEDDDB8ED7E4A93FDF12A4EECD30D7D76BD5F@GLKXM0002V.GREENLNK.net>
In-Reply-To: <B31EEDDDB8ED7E4A93FDF12A4EECD30D7D76BD5F@GLKXM0002V.GREENLNK.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.250.250.20]
Content-Type: multipart/alternative; boundary="_000_9bce68171af242f2abcfa3af482365c7VAUSDITCHM2idirectnet_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/c3jM41ghdy74qbVDALgR9YvTRKE>
Subject: Re: [manet] DLEP-17 review, part 1
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: <https://mailarchive.ietf.org/arch/browse/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: Wed, 02 Dec 2015 14:13:22 -0000

--_000_9bce68171af242f2abcfa3af482365c7VAUSDITCHM2idirectnet_
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable

Chris,

Thanks for the review input.

Regards,
Stan


From: manet [mailto:manet-bounces@ietf.org] On Behalf Of Dearlove, Christop=
her (UK)
Sent: Wednesday, December 02, 2015 5:43 AM
To: manet@ietf.org
Subject: [manet] DLEP-17 review, part 1

I'm calling this part 1, as I hope to get time to review the rest. But as I=
'm not sure when, I'll give you what I've got up to and including Section 4=
. Of course I might want to revisit after reading rest of draft.

Section 1. I think 802.11 should at the least be qualified with IEEE on fir=
st use. On balance I think not referencing it is OK, but I did think about =
that.

Section 1, paragraph 2. The issue with an event driven paradigm is message =
loss. Here of course you plan no message loss by having a reliable modem-ro=
uter link. But that (a) isn't indicated here, and (b) this appears to be di=
scussing what happens within the network, where message loss is a real issu=
e. So I think this wording could be improved.

Section 1, reference to DAMA. This I think needs a reference at least. It s=
ort of jars a bit, but may be important (not clear).

Section 1, top of page 6, I think it would be appropriate to indicate that =
DLEP is designed to handle ranges of values that cover all realistic cases.=
 (At least somewhere in the introductory part, not necessarily here.)

I found Figure 2 and text around it confusing. I think what we have is two =
modems of type A - just saying modem A usually means the modem named A, and=
 two of them? But insert type (assuming that's what's meant) in appropriate=
 places and it gets clearer.

Section 1.1, first paragraph. I think data item is usually Data Item. (I ha=
ven't gone through and checked consistency in general - not even where I'm =
up to - this just stood out.)

Section 1.1, second paragraph, "based on a heartbeat". Strictly it doesn't =
time out based on a heartbeat, it times out unless maintained by a message,=
 possibly a heartbeat, i.e. may time out based on absence of a heartbeat (o=
r other message).

Section 1.1. paragraph 3 "a specific, addressable location (e.g. an address=
)". What other possibilities are there other than an address? This also equ=
ates an addressable location and an address, which is confusing. Probably j=
ust delete the parenthesis.

Section 1.1 says a destination may be physical or logical. I think this sho=
uld start a paragraph, or here be a paragraph on its own. Then the next par=
agraph says what a physical destination is, good. But the next paragraph st=
arts with multicast, and only some way into the paragraph do we discover we=
're now talking about logical destinations. That should be how the paragrap=
h starts.

Section 1.1 says that algorithms used in multicast are up to the implementa=
tion. But I think (and maybe this is done later when specific metrics are i=
ntroduced) the implementer needs to know what a metric is meant to mean, in=
 particular in the multicast case. For example is latency related to worst =
case or average group member?

Section 1.1 final paragraph, "(e.g. multicast)". Are there any other logica=
l examples?

Section 2, security is said to be handled by transport. I know there's been=
 some discussion of this, but for these comments I'll take the draft as wri=
tten. The example is TLS, which is applicable to TCP. But some DLEP message=
s are UDP, what's the security mechanism there? (I've yet to understand how=
 critical the UDP messages are.)

Section 3, first paragraph should "with" be "by", before "a 'best effort'"?

Section 3, penultimate paragraph, from the outside the need to tear down a =
session and re-establish it in order to add new information seems wasteful.=
 Though a simpler protocol of course. Is this expected to be rare?

Section 4. A key issue throughout this, but not clearly indicated up front,=
 is that DLEP is designed for a reliable link between modem and router. (I'=
m not yet sure how reliable the UDP messages need to be.)

Section 4, paragraph 1. This discusses DLEP states in terms that cover both=
 modem and radio. In practice each must run its own state machine. With rel=
iable messages with short responses, those states should be corresponding, =
except short transients. But it's also said later that there can be signifi=
cant delays (but do those apply to state-changing messages?) At the least I=
 think this should be indicated.

Section 4, paragraph 2, "as well as" should this be e.g. "instead of"?

Section 4, paragraph 3. Why should the EUI format match that between the mo=
dem and the radio. Why should DLEP - which should be running over a layer 4=
 connection between the two - know, even less care, what layer 2 addressing=
 is being used on that modem-router link?

Section 4 paragraphs 4 and 6, I think could be clearer that the pair of mes=
sages is one each.

Section 4, paragraph 5 (this may be answered later). Can  the receiver of a=
 Destination Up message (modem or router?) become re-interested after becom=
ing uninterested?

Section 4.1. I spot a military influence in "one (1)". But here I don't thi=
nk needed.

Section 4.1 raised questions in my mind about timeouts and lack thereof - e=
specially as there's an earlier reference (about heartbeats) to timeouts. T=
his is just to say note that the reader may have questions here. Is it wort=
h avoiding them?




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

_____________________________________________________
This electronic message and any files transmitted with it contains
information from iDirect, which may be privileged, proprietary
and/or confidential. It is intended solely for the use of the individual
or entity to whom they are addressed. If you are not the original
recipient or the person responsible for delivering the email to the
intended recipient, be advised that you have received this email
in error, and that any use, dissemination, forwarding, printing, or
copying of this email is strictly prohibited. If you received this email
in error, please delete it and immediately notify the sender.
_____________________________________________________

--_000_9bce68171af242f2abcfa3af482365c7VAUSDITCHM2idirectnet_
Content-Type: text/html; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii">
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p
	{mso-style-priority:99;
	mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:12.0pt;
	font-family:"Times New Roman",serif;}
span.EmailStyle17
	{mso-style-type:personal;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
span.EmailStyle19
	{mso-style-type:personal-reply;
	font-family:"Calibri",sans-serif;
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Chris, <o:p></o:p></sp=
an></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Thanks for the review =
input. <o:p>
</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Regards,<o:p></o:p></s=
pan></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Stan<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b>From:</b> manet [mailto:manet-bounces@ietf.org] <=
b>On Behalf Of
</b>Dearlove, Christopher (UK)<br>
<b>Sent:</b> Wednesday, December 02, 2015 5:43 AM<br>
<b>To:</b> manet@ietf.org<br>
<b>Subject:</b> [manet] DLEP-17 review, part 1<o:p></o:p></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB">I&#8217;m calling this part 1, =
as I hope to get time to review the rest. But as I&#8217;m not sure when, I=
&#8217;ll give you what I&#8217;ve got up to and including Section 4. Of co=
urse I might want to revisit after reading rest of draft.<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB">Section 1. I think 802.11 shoul=
d at the least be qualified with IEEE on first use. On balance I think not =
referencing it is OK, but I did think about that.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB">Section 1, paragraph 2. The iss=
ue with an event driven paradigm is message loss. Here of course you plan n=
o message loss by having a reliable modem-router link. But that (a) isn&#82=
17;t indicated here, and (b) this appears
 to be discussing what happens within the network, where message loss is a =
real issue. So I think this wording could be improved.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB">Section 1, reference to DAMA. T=
his I think needs a reference at least. It sort of jars a bit, but may be i=
mportant (not clear).<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB">Section 1, top of page 6, I thi=
nk it would be appropriate to indicate that DLEP is designed to handle rang=
es of values that cover all realistic cases. (At least somewhere in the int=
roductory part, not necessarily here.)<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB">I found Figure 2 and text aroun=
d it confusing. I think what we have is two modems of type A &#8211; just s=
aying modem A usually means the modem named A, and two of them? But insert =
type (assuming that&#8217;s what&#8217;s meant) in appropriate
 places and it gets clearer.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB">Section 1.1, first paragraph. I=
 think data item is usually Data Item. (I haven&#8217;t gone through and ch=
ecked consistency in general &#8211; not even where I&#8217;m up to &#8211;=
 this just stood out.)<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB">Section 1.1, second paragraph, =
&#8220;based on a heartbeat&#8221;. Strictly it doesn&#8217;t time out base=
d on a heartbeat, it times out unless maintained by a message, possibly a h=
eartbeat, i.e. may time out based on absence of a heartbeat
 (or other message).<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB">Section 1.1. paragraph 3 &#8220=
;a specific, addressable location (e.g. an address)&#8221;. What other poss=
ibilities are there other than an address? This also equates an addressable=
 location and an address, which is confusing. Probably
 just delete the parenthesis.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB">Section 1.1 says a destination =
may be physical or logical. I think this should start a paragraph, or here =
be a paragraph on its own. Then the next paragraph says what a physical des=
tination is, good. But the next paragraph
 starts with multicast, and only some way into the paragraph do we discover=
 we&#8217;re now talking about logical destinations. That should be how the=
 paragraph starts.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB">Section 1.1 says that algorithm=
s used in multicast are up to the implementation. But I think (and maybe th=
is is done later when specific metrics are introduced) the implementer need=
s to know what a metric is meant to
 mean, in particular in the multicast case. For example is latency related =
to worst case or average group member?<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB">Section 1.1 final paragraph, &#=
8220;(e.g. multicast)&#8221;. Are there any other logical examples?<o:p></o=
:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB">Section 2, security is said to =
be handled by transport. I know there&#8217;s been some discussion of this,=
 but for these comments I&#8217;ll take the draft as written. The example i=
s TLS, which is applicable to TCP. But some DLEP
 messages are UDP, what&#8217;s the security mechanism there? (I&#8217;ve y=
et to understand how critical the UDP messages are.)<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB">Section 3, first paragraph shou=
ld &#8220;with&#8221; be &#8221;by&#8221;, before &#8220;a &#8216;best effo=
rt&#8217;&#8221;?<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB">Section 3, penultimate paragrap=
h, from the outside the need to tear down a session and re-establish it in =
order to add new information seems wasteful. Though a simpler protocol of c=
ourse. Is this expected to be rare?<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB">Section 4. A key issue througho=
ut this, but not clearly indicated up front, is that DLEP is designed for a=
 reliable link between modem and router. (I&#8217;m not yet sure how reliab=
le the UDP messages need to be.)<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB">Section 4, paragraph 1. This di=
scusses DLEP states in terms that cover both modem and radio. In practice e=
ach must run its own state machine. With reliable messages with short respo=
nses, those states should be corresponding,
 except short transients. But it&#8217;s also said later that there can be =
significant delays (but do those apply to state-changing messages?) At the =
least I think this should be indicated.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB">Section 4, paragraph 2, &#8220;=
as well as&#8221; should this be e.g. &#8220;instead of&#8221;?<o:p></o:p><=
/span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB">Section 4, paragraph 3. Why sho=
uld the EUI format match that between the modem and the radio. Why should D=
LEP &#8211; which should be running over a layer 4 connection between the t=
wo - know, even less care, what layer 2 addressing
 is being used on that modem-router link?<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB">Section 4 paragraphs 4 and 6, I=
 think could be clearer that the pair of messages is one each.<o:p></o:p></=
span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB">Section 4, paragraph 5 (this ma=
y be answered later). Can&nbsp; the receiver of a Destination Up message (m=
odem or router?) become re-interested after becoming uninterested?<o:p></o:=
p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB">Section 4.1. I spot a military =
influence in &#8220;one (1)&#8221;. But here I don&#8217;t think needed.<o:=
p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB">Section 4.1 raised questions in=
 my mind about timeouts and lack thereof &#8211; especially as there&#8217;=
s an earlier reference (about heartbeats) to timeouts. This is just to say =
note that the reader may have questions here. Is
 it worth avoiding them?<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB"><o:p>&nbsp;</o:p></span></p>
<p><span lang=3D"EN-GB">***************************************************=
*****************<br>
This email and any attachments are confidential to the intended<br>
recipient and may also be privileged. If you are not the intended<br>
recipient please delete it from your system and notify the sender.<br>
You should not copy it or use it for any purpose nor disclose or<br>
distribute its contents to any other person.<br>
********************************************************************<o:p></=
o:p></span></p>
</div>
</div>
<br><span style=3D"font-size: 8pt; font-family: Arial, sans-serif; color: #=
003366;">_____________________________________________________<br>This elec=
tronic message and any files transmitted with it contains<br>information fr=
om iDirect, which may be privileged, proprietary<br>and/or confidential. It=
 is intended solely for the use of the individual<br>or entity to whom they=
 are addressed. If you are not the original<br>recipient or the person resp=
onsible for delivering the email to the<br>intended recipient, be advised t=
hat you have received this email<br>in error, and that any use, disseminati=
on, forwarding, printing, or<br>copying of this email is strictly prohibite=
d. If you received this email<br>in error, please delete it and immediately=
 notify the sender.<br>____________________________________________________=
_</span></body>
</html>

--_000_9bce68171af242f2abcfa3af482365c7VAUSDITCHM2idirectnet_--


From nobody Wed Dec  2 06:25:10 2015
Return-Path: <vmercieca0@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 7673C1A90B1 for <manet@ietfa.amsl.com>; Wed,  2 Dec 2015 06:25:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.149
X-Spam-Level: 
X-Spam-Status: No, score=-1.149 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, J_CHICKENPOX_57=0.6, SPF_PASS=-0.001] autolearn=no
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 iWQR6t52gVNw for <manet@ietfa.amsl.com>; Wed,  2 Dec 2015 06:24:52 -0800 (PST)
Received: from mail-lf0-x243.google.com (mail-lf0-x243.google.com [IPv6:2a00:1450:4010:c07::243]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5B1961A9080 for <manet@ietf.org>; Wed,  2 Dec 2015 06:24:51 -0800 (PST)
Received: by lfr20 with SMTP id 20so5102614lfr.0 for <manet@ietf.org>; Wed, 02 Dec 2015 06:24:49 -0800 (PST)
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=D8oqKTxj2N9Bw2knwN4m0+fqS7azJclA/9OPtbcHHAI=; b=GjD54+TrWxuFkVANBCxQzh+pI0Go3fyNCrlT8mg7LbDag1FrBqOdLhV+P2A8L+cpBr MlWm1SnAgIbrjzi9VpydFIsNBRPrKA4xM7jHZuBJHbFE8321fQf3BtesZokshNT9sFky JpWcLvhwMSTpFGbtD8sEMPLM7AlYBz3QXCVGE56d6amsZSDYt8gKaX13KsnOw4qJNoZf UauNfan/zsm2uH8O5ENZAPmcYKSVwFjURXT+SSB6CYpUiHCmepUVKjbkyimoi6cViX3y I322kmXsdz0IVcAuSwn7FQ6BjfMS22StWLfFuOy/yPTz004P3QO5Qv8RvNpJNC96C1wM BK6A==
MIME-Version: 1.0
X-Received: by 10.25.168.6 with SMTP id r6mr3283799lfe.94.1449066289407; Wed, 02 Dec 2015 06:24:49 -0800 (PST)
Received: by 10.112.16.2 with HTTP; Wed, 2 Dec 2015 06:24:49 -0800 (PST)
In-Reply-To: <F474BF24-D920-4A54-8F43-AB4B9FE939A8@thomasclausen.org>
References: <F474BF24-D920-4A54-8F43-AB4B9FE939A8@thomasclausen.org>
Date: Wed, 2 Dec 2015 14:24:49 +0000
Message-ID: <CAAePS4Dmv=j_ASKhsX+kenP-xaDUWUEFuzYGduxu+FR_C2R-MA@mail.gmail.com>
From: Victoria Mercieca <vmercieca0@gmail.com>
To: ietf@thomasclausen.org
Content-Type: multipart/alternative; boundary=001a11407d406fae2d0525eb090d
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/hlwbvEE0sypCWpRVPQYuNl-4jLo>
Cc: manet <manet@ietf.org>
Subject: Re: [manet] Stuff from review of aodv-11 page 1-22 that are still not folded into -12
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: <https://mailarchive.ietf.org/arch/browse/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: Wed, 02 Dec 2015 14:25:00 -0000

--001a11407d406fae2d0525eb090d
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hello Thomas,

Thank you again for your time spent reviewing AODVv2. I apologise that we
did not give a "point by point" response to your comments on draft 11 - I
felt that since most of the comments were around a few major topics, it
made sense to address the topic across the whole draft, rather than respond
to every single comment in order. I did also try to start a discussion on
the MANET list based on your comments from draft 11, but did not see any
responses.

Thank you again, we will discuss and intend to respond soon.

Kind regards,
Victoria.



On Tue, Dec 1, 2015 at 7:21 PM, <ietf@thomasclausen.org> wrote:

> All,
>
> I am working through the revised I-D to see what comments that I made
> previously have been addressed, and which still do apply.
>
> As I sent my original review piecemeal, I=E2=80=99ll send my refresher in=
 matching
> pieces (in part, in recognition that it is hard to get time to sit down a=
nd
> review the whole document in one go, and I do want to reply to the author=
s
> as quickly as possible)
>
> In doing so, I am noticing additional things (notably, but not
> exclusively, to section 7 and beyond, which I didn=E2=80=99t get through =
reviewing
> last time around) which needs attention. I=E2=80=99ll gather that in sepa=
rate
> emails a bit later, once I=E2=80=99ve worked through the complete, update=
d spec.
>
> So onwards...
>
> Abstract:
>         I made the following comment, which still applies:
>
>                 =E2=80=9CThis is a little over-stating the applicability:=
 these
> statements may
>                  be true in some scenarios (for example, when there are f=
ew
>                  concurrent traffic flows, and therefore few routes to
> repair, and
>                  therefore few flooding operations to contend for channel
> access).
>                  As a general statement, this last sentence is incorrect=
=E2=80=9D=E2=80=9D
>
> Overview (and elsewhere):
>
>         I made a comment previously that =E2=80=9CRouter client=E2=80=9D =
is a poorly chosen
>         term, and have proposed alternatives. I=E2=80=99ve seen some atte=
mpts on
> the list
>         at rather than change the term, explain it =E2=80=94 some of whic=
h is in
> this document.
>         The =E2=80=9COverview=E2=80=9D still talks about =E2=80=9Ca route=
r=E2=80=A6one of its clients=E2=80=9D -
> which is no less
>         confusing than last time Iw went through it.
>
>         I reiterate, why not use =E2=80=9CLocal Attached Network Set=E2=
=80=9D, which is
> the term used
>         by other documents from this WG?
>
> Overview:
>         The term =E2=80=9Cconfirming adjacency=E2=80=9D is gone, and is n=
ow replaced by
>         =E2=80=9Cconfirming bidirectionality=E2=80=9D - which, alas, stil=
l sounds like
> there is some active
>         monitoring (HELLO message exchange) going on. Unless that is the
> case,
>         then please be more specific here.
>
>         I note that the term adjacency is used through and through the
> document, btw.
>
>         I suggested in my last review:
>
>                 The overview must also include a paragraph on the
> intersections
>                 between this protocol and the forwarding plane =E2=80=94 =
this, as
> it is
>                 different (and more invasive) from that which is typicall=
y
> seen in
>                 routing protocols.
>
>                 Specifically, as a reactive protocol, it is required (at
> least) that the
>                 forwarding plane is modified :
>
>                 1) A =E2=80=9Cmiss=E2=80=9D when looking up a next hop fo=
r a data packet
> to be
>                    forwarded, is signalled to the AODVv2 process so as to
> permit
>                   that route discovery be launched;
>
>                 2) A =E2=80=9Cmiss=E2=80=9D when attempting to deliver a =
data packet to a
> next hop,
>                    which was recorded in the routing table, is signalled
> to the AODVv2
>                    process so as to permit that a route repair be
> initiated and/or a Route
>                    Error be generated.
>
>                 3) A =E2=80=9Chit=E2=80=9D when looking up a next hop for=
 a data packet to
> be forwarded
>                     to a destination is signalled to the AODVv2 process s=
o
> as to permit
>                     maintenance of =E2=80=9Cactive route=E2=80=9D Route S=
tate, timers and
> such.
>
>                 Note that these things are necessary to call out in the
> =E2=80=9Coverview=E2=80=9D and in
>                 the =E2=80=9Capplicability statement=E2=80=9D, both: it i=
s not that they
> are negatives per se,
>                 but that they are important factors governing the
> applicability of this protocol:
>                 will a given platform permit such access to the forwardin=
g
> plane, for example?
>                 Important to understand if for that platform this protoco=
l
> is apple
>
>
>         I see that this was not addressed in the overview, nor in the
> applicability other than
>         by a forward reference to section 6.4. While it is positive that
> there is a section 6.4,
>         this does not exonerate the overview and the applicability
> statement for being
>         honest about the requirements (notably to the platform/os) that
> this protocol has
>         for being applicable
>
>         I suggested in my last review:
>
>                 =E2=80=9CIt is important to do more than this: 7182 does =
only
> provide =E2=80=9Ccontainers=E2=80=9D
>                  for ICVs and timestamps, and does not specify how to use
> them to obtain
>                  specific security properties. RFC7182 may be a tool that
> can be used, but
>                  *how* that tool is used is what determines the security
> properties.
>
>                 Therefore, saying that =E2=80=9Csecurity is dealt with by=
 using
> RFC7182=E2=80=9D is either an
>                 incomplete statement, or is indicative of insufficient
> security considerations.=E2=80=9D
>
>         The actual sentence in the I-D has been changed, now it explicitl=
y
> names the
>         two TLVs from 7182 that it uses. That is, alas, still not
> sufficient.
>
>         Making the aside that was discussed recently on the list, that (i=
)
> control messages
>         are not forwarded, and that (ii) they are modified in transit, th=
e
> security/trust model
>         is somewhat different from that of 7181 and consequently for what
> 7182 was initially
>         written for. I think that  calling out the trust model, and how
> 7182 actually is used here,
>         might be what is called for.
>
>         Continuing with the aside, this *especially* as the applicability
> statement says:
>
>                 "Providing security for a reactive routing protocol can b=
e
> difficult=E2=80=9D
>
>
> Terminology:
>
>         My last review suggested:
>                 =E2=80=9CThis has been brought up on the list several tim=
es in the
> past, without having
>                  been addressed.
>
>                 There are =E2=80=9Chosts=E2=80=9D and there are =E2=80=9C=
routers=E2=80=9D =E2=80=94 whose roles
> are well defined.
>                 =E2=80=9CNode=E2=80=9D not so much =E2=80=94 which is cle=
ar from looking at the
> definition here: =E2=80=9Ceither
>                 AODVv2 routers or router clients=E2=80=9D (with =E2=80=9C=
router clients=E2=80=9D
> being defined as =E2=80=9Can
>                 AODVv2 router is also its own router client=E2=80=9D).
>
>                 This is very much related to the use of =E2=80=9CRouter C=
lient=E2=80=9D,
> and both that term,
>                 and =E2=80=9Cnode=E2=80=9D indicative that some clarity i=
s needed here.
>
>                 All a router cares about is =E2=80=9Can address=E2=80=9D.=
 If that address
> is of a network, or
>                 a router, or an interface (and, if said interface is
> installed in a router or a host)
>                 doesn=E2=80=99t matter.
>
>                 So, =E2=80=9Can address=E2=80=9D is something that the ro=
uting protocol
> should care about
>                 finding paths to. Which means that each address that
> should be made
>                 reachable by the routing protocol should be advertised by
> (at least) one router
>                 in the network.
>
>                 One way of doing that would be to simply talk about
> =E2=80=9CAttached Networks=E2=80=9D as
>                 is done in RFC7181, wherein an address included in the
> =E2=80=9CAttached Network Set=E2=80=9D
>                 is advertised by an OLSRv2 router....in this case, the
> equivalent would be =E2=80=9Cfor each
>                 address in the Attached Network Set of an AODVv2 router
> the router MUST
>                 respond authoritatively to a RREQ, and MUST maintain the
> corresponding sequence number=E2=80=9D.
>
>                 The text, as it currently is, is really hard to read, and
> a re-edit along these lines would go a long way.=E2=80=9D
>
>         I note that the terms =E2=80=9CNode=E2=80=9D and =E2=80=9CRouter =
Client=E2=80=9D are still used,
> in their original form,
>         and that other than some slight wordsmithing this comment has not
> been addressed in the document.
>
>         I reiterate that the need to use router, host, node, and router
> client in and by itself should
>         be an indicator that tightening up of terminology is required.
>
>
>         I made the following comment to Routable Unicast IP Address:
>
>                 =E2=80=9CAre there any technical reason why not simply *a=
ny*
> address could be
>                  considered by the routing protocol?
>
>                  My understanding, but correct me if I am wrong, is that
> all that is required is
>                  that all interfaces in a given AODVv2 routing domain has
> an unique address.
>
>                  That some of these addresses (by an IP addressing
> architecture document)
>                  has special semantics associated (such as are link
> locals, or are for private
>                  use, or are for example use only, or are for multicast)
> is out of scope here?
>
>         I see nothing has changed on the above, so let me be more
> explicit: the routing protocol itself
>         (probably) should not care about what kind of addresses are fille=
d
> into it. Is an 192.16./16 address
>         appropriate? Not across the internet, but it may be in somebody=
=E2=80=99s
> private deployments. Should
>         the routing protocol be =E2=80=9Caddress police=E2=80=9D and is i=
mplementation of
> a =E2=80=9CI refuse to route these addresses=E2=80=A6=E2=80=9D
>         a requirement for claiming conformance? Suggest simply stating
> what the requirements are under
>         which the routing protocol will work =E2=80=94 and leave =E2=80=
=9Caddress
> assignment politics=E2=80=9D aside.
>
>         I also continued:
>
>                  Now, with that being said also, the WG wanted that
> RFC7181 supports not
>                  just multiple interfaces, but also the same address used
> on multiple interfaces
>                  of the same router. There were good reasons for that, an=
d
> while it was not trivial
>                  to implement, it turned out to be the right thing to
> support. If there are technical
>                  reasons why this is not supported in AODVv2 (for example=
,
> if this cannot be
>                  made work because of <reason>) then that should be calle=
d
> out in the
>                  applicability statement also?
>
>                 Conversely, if it is possible in AODVv2, then I do not
> believe that it is clearly
>                 specified how (at least, in the =E2=80=9Cnaive=E2=80=9D o=
n paper examples
> I drew up, something
>                 ended up not working). So either the protocol as-is does
> not support it (but
>                 could be made to?) or it is supported (but just need to b=
e
> spelled out), or is
>                 not possible (and need to be disclaimed in the
> applicability statement).
>
>                 Stan Ratliff was a driving force in holding the WG=E2=80=
=99s
> collective feet to the fire
>                 in getting this support included in RFC7181, and would
> likely be the right
>                 person to consult on this matter?
>
>         I actually have not seen changes, or comments, on this. In OLSRv2=
,
> the WG was making it
>         a strong requirement that it should be possible to use the same I=
P
> address on different
>         interfaces of a router. It was somewhat tedious to design around,
> but it was worked out, and
>         the conditions under which that was possible were defined and
> documented.
>
>         I would like to see the same done for this protocol.
>
>         I also note that this is not unrelated to RFC6621-discussions. Fo=
r
> example, when selecting
>         S-MPRs on a multi-interface and multi-address-per-interface
> router, care must be taken
>         least things won=E2=80=99t work. So, if (and this links back to p=
revious
> mails) RFC6621 is a
>         requirement or desire for this protocol, then there are some
> considerations required here.
>
>         I see that the definition of =E2=80=9CRouter Client=E2=80=9D has =
changed to be
>
>                 =E2=80=9CAn address or address range=E2=80=A6the AODVv2 r=
outer=E2=80=99s interface
> addresses
>                  are also configured as router clients=E2=80=9D
>
>         Better than before, but still missing the target. The term =E2=80=
=9CRouter
> Client=E2=80=9D is, as I indicated
>         numerous times before, odd.
>
>         But the second part of the sentence, does that mean (what it says=
)
> that the interfaces
>         must be configured specially, so as to be able to be =E2=80=9Crou=
ter
> clients=E2=80=9D? That can=E2=80=99t be true.
>
>         What you likely mean is:
>
>                 =E2=80=9CAn AODVv2 router is configured so as to consider=
 its own
> interfaces as part of
>                  the locally attached network set=E2=80=9D ?
>
>         You configure the router, right? No special =E2=80=9Cinterface
> configuration properties=E2=80=9D are required
>         for an interface to be announcable by  an AODVv2 router?
>         (And, getting rid of node would actually make the definition
> shorter and nicer)
>
>         Now, snipping out from the applicability statement:
>
>                 "Multi-homing of an IP address is not supported by AODVv2=
,
> and therefore a
>                   Router Client, i.e. an IP Address,  =E2=80=A6 "
>
>         =E2=80=A6evidence to there being some redundant terminology here =
to weed
> away.
>
>         The below is a little bit of a meta-comment, I am not quite sure
> what I think here.
>         The definitions for Target Node and such were confusing before.
> They still are, somewhat.
>
>         I think that it may be because the definitions now used are simpl=
y
> copy-pasted out from the
>         tables in the previous version, for example:
>
>                 An AODVv2 Data Element containing the destination address
> of the
>                 IP packet triggering route discovery.
>
>         OK, I can trace back and see that a Data Element is something tha=
t
> exists inside a
>         protocol message. To me, however, that=E2=80=99s not really gener=
al
> terminology as such, but
>         part of the specification of a packet format - or rather, it is
> the notation that you use
>         when describing an algorithm. By the way, why are some notations
> in CamelCase
>         whereas others have a space in them, e.g. =E2=80=9CTarget Node=E2=
=80=9D and
> =E2=80=9CTargMetric=E2=80=9D, both of which
>         are Data Elements? Would be good with a consistent approach here.
>
>         I *think* that it would be better to take all those =E2=80=9CData=
 Element=E2=80=9D
> bits and move to a separate
>         section (or subsection) to the terminology, and then keep all the
> =E2=80=9Cother stuff=E2=80=9D (Neighbor, =E2=80=A6)
>         in its own section.
>
>         I=E2=80=99m a great fan of calling this section =E2=80=9CTerminol=
ogy and Notation=E2=80=9D
> and then having two
>         subsections, one which is =E2=80=9CTerminology=E2=80=9D and one w=
hich is
> =E2=80=9CNotation=E2=80=9D, with the
>         TargMetric and Target Node being firmly in the latter.
>
>         I made a comment:
>                 "Second, should =E2=80=9Cvalid route=E2=80=9D not be qual=
ified by =E2=80=9Cto a
> specific address=E2=80=9D?=E2=80=9D
>
>         Which was not addressed.
>
>         I also made a comment on "Unreachable Address=E2=80=9D - I am gla=
d I did,
> because I apparently
>         had a different understanding than what was intended. I now see
> that an Unreachable Address
>         by definition is an address listed in a RERR message, and not the
> same as an address to
>         which no route has yet  been discovered? If yes, then please use =
a
> different term, such as
>         =E2=80=9CFormerlyReachableAddress=E2=80=9D or something of the so=
rt?
>
> Applicability statement
>
>         First, I would like to recognize the efforts made to improve this
> since last review. Thanks
>
>         Second, the document states:
>
>                 "AODVv2 supports routers with multiple interfaces, as lon=
g
> as each
>                    interface configured for AODVv2 has a unicast IP
> address.  A router
>                    may use the same IP address on multiple interfaces.
> Address
>                    assignment procedures are out of scope for AODVv2.=E2=
=80=9D
>
>         Is that true? Granted, I have not worked this through in detail,
> but I can present a counter-example:
>         the use of RFC6621 means that there certainly are some constraint=
s
> that must be respected least
>         various flooding optimizations may not work.
>
>         Secondly, if the multiple-interfaces-with-same-address are on the
> same L2, and this is what I
>         have not worked through, are there any situations that will not
> work?
>
>         The immediately previous version of this specification read:
>
>                 "AODVv2 supports routers with multiple interfaces, as lon=
g
> as each
>                    interface configured for AODVv2 has its own unicast
> routable IP address"
>
>         So what changed that means that each interface no longer needs it=
s
> *own* unicast address?
>
>         I pointed out to the Applicability Statement:
>
>                 I think that appendix B needs to be removed. Essentially,
> it makes claims that it is
>                 possible to do multi-homing =E2=80=94 but neither specifi=
es how it
> is done, nor gives
>                 pointers to documents that justify the claim.
>
>                 AODVv2 does not support multi-homing =E2=80=94 that=E2=80=
=99s clear, and
> it is fine that it is
>                 called out here. Thank you for that.
>
>                 Now, with that being said, I am torn between being
> satisfied that it is called out on
>                 one hand, and wanting to have =E2=80=9Cmulti homing=E2=80=
=9D on the other
> hand. RFC7181 supports
>                 multi-homing, FWIW.
>
>                 I believe that this also would merit some explicit
> discussion by the WG, in order to
>                 understand if this design decision is acceptable?
>
>         I see that Appendix B still is in the document, and I do not
> recall having seen this discussed
>         on the mailing list. Simply removing the reference from the
> Applicability Statement to Appendix B
>         does not address the issue that I raised in my previous review.
>
> To 4.1, I made the following comment:
>
>         "Is this a should, or a SHOULD? If the latter, should it be a MUS=
T?
>
>           In general, there are a lot of such =E2=80=9Cmaybe normative la=
nguage=E2=80=9D
> through the
>          document, and I would much like to see an editorial pass =E2=80=
=94
> essentially all
>          may/should/ must and friends carefully evaluated as if they
> should become
>          2119-terms, and ... more importantly (it has been called out
> before, fwiw)
>          quite a bit of should/SHOULD which ought to be transformed into
> MUST.
>
>         Generally, aiming for a very a low number of SHOULD is a good
> design metric for a document=E2=80=9D
>
> Aside from the general comment on 2119-language, why is this a SHOULD?
>
> To 4.2, I made the following comment:
>
>         As indicated earlier, I believe that the term =E2=80=9CRouter Cli=
ent=E2=80=9D is
> ill chosen.
>         I believe that it is more appropriately an =E2=80=9CAttached Netw=
ork Set=E2=80=9D
> since =E2=80=94
>         as indicated previously =E2=80=94 the term =E2=80=9CRouter Client=
=E2=80=9D is ambiguous. I
> am pleased
>         to see, though, that this =E2=80=9CRouter Client List=E2=80=9D in=
 reality is an
> =E2=80=9CAttached Network Set=E2=80=9D
>         and so that change should be (relatively) easy.
>
> The above comment still is applicable to this revision,
>
> To 4.2, I made the following comment:
>
>         Also, I recommend to not say =E2=80=9Csubnet=E2=80=9D =E2=80=94 h=
ow about rephrasing to
> =E2=80=9CIf a prefix
>         is included in the attached network set of an AODVv2 router, then
> that AODVv2
>         router MUST provide connectivity for, i.e. answer to RREQs and
> maintain
>         sequence numbers for, all addresses from within that prefix.=E2=
=80=9D
>
> I note that while the term has been removed from section 4, there=E2=80=
=99re 4
> lingering instances of this term in the document, that could easily be
> removed.
>
> I Also made a comment about Appendix B in my previous review, which is
> referenced here. That comment still applies.
>
> To Section 4.3, I noticed:
>
>         Does section 6.2 describe how to monitor an established adjacency
>         only, or how to discover neighbouring AODVv2 routers? Looking in
> 6.2, I see
>
>                 =E2=80=9CNot every pair of neighboring routers will neces=
sarily
> form an adjacency,=E2=80=9D =E2=80=94
>                  so it likely isn=E2=80=99t 6.2 that tells me how to main=
tain this
> table?
>
>         In short, =E2=80=9CA neighbour table MUST be maintained=E2=80=9D =
=E2=80=94 where can I
> find information on how to do this?
>
>         Section 6.2 states:
>
>                 =E2=80=9CThe default approach for monitoring bidirectiona=
l
> connectivity to the next hop toward
>                  OrigAddr is to request acknowledgement of Route Reply
> messages.=E2=80=9D
>
>                 That certainly will tell me if a link over which an RREP
> is sent is bi-directional,
>                 but will not maintain a =E2=80=9Cneighbor table=E2=80=9D.
>
>         So how is this done? Or, is the =E2=80=9CNeighbor Table=E2=80=9D =
not supposed to
> contain the
>         complete set of neighbours? What information =E2=80=9C...MUST be
> maintained=E2=80=9D then, in this table?
>
>         This is very unclear, I would not know how to implement a
> mechanism that populates this
>         =E2=80=9CNeighbor Table=E2=80=9D with the needed information here=
.
>
> I see no (relevant) changes to 6.2 nor to 4.3 so I assume that this
> comment has not been addressed
>
> I am throwing this in here, as I am sure that I commented on that in the
> previous review, but I do not see that addressed: is Appendix C normative=
,
> or not? It represents =E2=80=9C a second specification of the protocol, i=
n a
> different language=E2=80=9D from the main part of the specification. I ha=
ve not
> walked through and made 200% sure that both are perfectly aligned and tha=
t
> there are no ambiguities, but having two different specifications of a
> protocol is a recipe for disaster.  Please either make 2000% sure that th=
ey
> are specifying the same thing without ambiguities, or remove one.
>
> To section 4.4, I wrote:
>
>         "would like to nit-pick that: the router can maintain this
> sequence number in whatever
>          format it pleases =E2=80=94 but, when it includes it in control =
messages,
> it must be
>          representable in a specified format, respecting certain rules.=
=E2=80=9D
>
> I see that there were no changes following this comment.
>
> To section 4.4 I asked for clarification as to if sequence numbers were
> per interface or per router, as the specification was unclear on that. Th=
e
> words has changed, but it still is unclear: how many sequence numbers doe=
s
> a router maintain? One? One per interface?
>
> In my previous review, I expressed that it would be preferential to use =
=E2=80=9Ca
> notation of Sets=E2=80=9D rather than tables. I see that this has not cha=
nged.
>
> I made a comment on node and address, let me pick this up again. The
> following:
>
>         RteMsg.OrigAddr
>               An IP address of the node which requires the route, i.e., t=
he
>               source address of the IP packet triggering the route reques=
t.
>
> would be more compact and clear if getting rid of the term =E2=80=9Cnode=
=E2=80=9D and said:
>
> RteMsg.OrigAddr
>         The source address of the IP packet triggering the route request.
>
>
> To section 4.6, and I (and others) have commented on this before:
>
>    All AODVv2 routers MUST maintain a route table.  The route table
>    entry is a conceptual data structure.  Implementations MAY use any
>    internal representation but MUST contain the following information:
>
> In order to avoid confusion, rename this to =E2=80=9CRouting Information =
Base=E2=80=9D or
> =E2=80=9CRouting Set=E2=80=9D =E2=80=94 a Routing Table is an operating s=
ystem construct, whereon
> operations directly influence packet forwarding. What you are defining he=
re
> is a RIB/an RS.
>
> The confusion that I pointed out in my previous review on =E2=80=9CIP add=
ress=E2=80=9D and
> =E2=80=9CAddress=E2=80=9D being used a bit haphazardly persists, fwiw. It=
 makes me think,
> can a router send an RREQ for a prefix?
>
> I also called this out in my previous review as incorrect, and despite
> wordsmithing it still is:
>
>         Route.NextHop
>               The source IP address of the message advertising the route =
to
>               Route.Address, i.e. an IP address of the AODVv2 router used
> for
>               the next hop on the path toward Route.Address.
>
> If that =E2=80=9Cmessage=E2=80=9D is an RFC5444 entity, then it does to h=
ave a =E2=80=9Csource IP
> Address=E2=80=9D =E2=80=94 the encapsulating IP datagram containing the p=
acket containing
> the message does. And the message MAY have an Originator Address
>
>
> As I indicated, I am walking through my previous review and retaining
> those comments that I still think need attention =E2=80=94 and this is =
=E2=80=9Ccrossing
> off from part 1 of my previous review=E2=80=9D only. More to follow.
>
> Thomas
>
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www.ietf.org/mailman/listinfo/manet
>

--001a11407d406fae2d0525eb090d
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div><div><div><div>Hello Thomas,<br><br></div>Thank you a=
gain for your time spent reviewing AODVv2. I apologise that we did not give=
 a &quot;point by point&quot; response to your comments on draft 11 - I fel=
t that since most of the comments were around a few major topics, it made s=
ense to address the topic across the whole draft, rather than respond to ev=
ery single comment in order. I did also try to start a discussion on the MA=
NET list based on your comments from draft 11, but did not see any response=
s. <br><br></div>Thank you again, we will discuss and intend to respond soo=
n.<br><br></div>Kind regards,<br></div>Victoria.<br><div><div><br><br></div=
></div></div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On T=
ue, Dec 1, 2015 at 7:21 PM,  <span dir=3D"ltr">&lt;<a href=3D"mailto:ietf@t=
homasclausen.org" target=3D"_blank">ietf@thomasclausen.org</a>&gt;</span> w=
rote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;borde=
r-left:1px #ccc solid;padding-left:1ex">All,<br>
<br>
I am working through the revised I-D to see what comments that I made previ=
ously have been addressed, and which still do apply.<br>
<br>
As I sent my original review piecemeal, I=E2=80=99ll send my refresher in m=
atching pieces (in part, in recognition that it is hard to get time to sit =
down and review the whole document in one go, and I do want to reply to the=
 authors as quickly as possible)<br>
<br>
In doing so, I am noticing additional things (notably, but not exclusively,=
 to section 7 and beyond, which I didn=E2=80=99t get through reviewing last=
 time around) which needs attention. I=E2=80=99ll gather that in separate e=
mails a bit later, once I=E2=80=99ve worked through the complete, updated s=
pec.<br>
<br>
So onwards...<br>
<br>
Abstract:<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 I made the following comment, which still appli=
es:<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =E2=80=9CThis is a =
little over-stating the applicability: these statements may<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0be true in so=
me scenarios (for example, when there are few<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0concurrent tr=
affic flows, and therefore few routes to repair, and<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0therefore few=
 flooding operations to contend for channel access).<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0As a general =
statement, this last sentence is incorrect=E2=80=9D=E2=80=9D<br>
<br>
Overview (and elsewhere):<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 I made a comment previously that =E2=80=9CRoute=
r client=E2=80=9D is a poorly chosen<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 term, and have proposed alternatives. I=E2=80=
=99ve seen some attempts on the list<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 at rather than change the term, explain it =E2=
=80=94 some of which is in this document.<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 The =E2=80=9COverview=E2=80=9D still talks abou=
t =E2=80=9Ca router=E2=80=A6one of its clients=E2=80=9D - which is no less<=
br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 confusing than last time Iw went through it.<br=
>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 I reiterate, why not use =E2=80=9CLocal Attache=
d Network Set=E2=80=9D, which is the term used<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 by other documents from this WG?<br>
<br>
Overview:<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 The term =E2=80=9Cconfirming adjacency=E2=80=9D=
 is gone, and is now replaced by<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =E2=80=9Cconfirming bidirectionality=E2=80=9D -=
 which, alas, still sounds like there is some active<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 monitoring (HELLO message exchange) going on. U=
nless that is the case,<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 then please be more specific here.<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 I note that the term adjacency is used through =
and through the document, btw.<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 I suggested in my last review:<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 The overview must a=
lso include a paragraph on the intersections<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 between this protoc=
ol and the forwarding plane =E2=80=94 this, as it is<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 different (and more=
 invasive) from that which is typically seen in<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 routing protocols.<=
br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Specifically, as a =
reactive protocol, it is required (at least) that the<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 forwarding plane is=
 modified :<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 1) A =E2=80=9Cmiss=
=E2=80=9D when looking up a next hop for a data packet to be<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0forwar=
ded, is signalled to the AODVv2 process so as to permit<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 that route d=
iscovery be launched;<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 2) A =E2=80=9Cmiss=
=E2=80=9D when attempting to deliver a data packet to a next hop,<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0which =
was recorded in the routing table, is signalled to the AODVv2<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0proces=
s so as to permit that a route repair be initiated and/or a Route<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Error =
be generated.<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 3) A =E2=80=9Chit=
=E2=80=9D when looking up a next hop for a data packet to be forwarded<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 to a =
destination is signalled to the AODVv2 process so as to permit<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 maint=
enance of =E2=80=9Cactive route=E2=80=9D Route State, timers and such.<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Note that these thi=
ngs are necessary to call out in the =E2=80=9Coverview=E2=80=9D and in<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 the =E2=80=9Capplic=
ability statement=E2=80=9D, both: it is not that they are negatives per se,=
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 but that they are i=
mportant factors governing the applicability of this protocol:<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 will a given platfo=
rm permit such access to the forwarding plane, for example?<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Important to unders=
tand if for that platform this protocol is apple<br>
<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 I see that this was not addressed in the overvi=
ew, nor in the applicability other than<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 by a forward reference to section 6.4. While it=
 is positive that there is a section 6.4,<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 this does not exonerate the overview and the ap=
plicability statement for being<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 honest about the requirements (notably to the p=
latform/os) that this protocol has<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 for being applicable<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 I suggested in my last review:<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =E2=80=9CIt is impo=
rtant to do more than this: 7182 does only provide =E2=80=9Ccontainers=E2=
=80=9D<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0for ICVs and =
timestamps, and does not specify how to use them to obtain<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0specific secu=
rity properties. RFC7182 may be a tool that can be used, but<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0*how* that to=
ol is used is what determines the security properties.<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Therefore, saying t=
hat =E2=80=9Csecurity is dealt with by using RFC7182=E2=80=9D is either an<=
br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 incomplete statemen=
t, or is indicative of insufficient security considerations.=E2=80=9D<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 The actual sentence in the I-D has been changed=
, now it explicitly names the<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 two TLVs from 7182 that it uses. That is, alas,=
 still not sufficient.<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Making the aside that was discussed recently on=
 the list, that (i) control messages<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 are not forwarded, and that (ii) they are modif=
ied in transit, the security/trust model<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 is somewhat different from that of 7181 and con=
sequently for what 7182 was initially<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 written for. I think that=C2=A0 calling out the=
 trust model, and how 7182 actually is used here,<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 might be what is called for.<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Continuing with the aside, this *especially* as=
 the applicability statement says:<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 &quot;Providing sec=
urity for a reactive routing protocol can be difficult=E2=80=9D<br>
<br>
<br>
Terminology:<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 My last review suggested:<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =E2=80=9CThis has b=
een brought up on the list several times in the past, without having<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0been addresse=
d.<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 There are =E2=80=9C=
hosts=E2=80=9D and there are =E2=80=9Crouters=E2=80=9D =E2=80=94 whose role=
s are well defined.<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =E2=80=9CNode=E2=80=
=9D not so much =E2=80=94 which is clear from looking at the definition her=
e: =E2=80=9Ceither<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 AODVv2 routers or r=
outer clients=E2=80=9D (with =E2=80=9Crouter clients=E2=80=9D being defined=
 as =E2=80=9Can<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 AODVv2 router is al=
so its own router client=E2=80=9D).<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 This is very much r=
elated to the use of =E2=80=9CRouter Client=E2=80=9D, and both that term,<b=
r>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 and =E2=80=9Cnode=
=E2=80=9D indicative that some clarity is needed here.<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 All a router cares =
about is =E2=80=9Can address=E2=80=9D. If that address is of a network, or<=
br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 a router, or an int=
erface (and, if said interface is installed in a router or a host)<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 doesn=E2=80=99t mat=
ter.<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 So, =E2=80=9Can add=
ress=E2=80=9D is something that the routing protocol should care about<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 finding paths to. W=
hich means that each address that should be made<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 reachable by the ro=
uting protocol should be advertised by (at least) one router<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 in the network.<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 One way of doing th=
at would be to simply talk about =E2=80=9CAttached Networks=E2=80=9D as<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 is done in RFC7181,=
 wherein an address included in the =E2=80=9CAttached Network Set=E2=80=9D<=
br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 is advertised by an=
 OLSRv2 router....in this case, the equivalent would be =E2=80=9Cfor each<b=
r>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 address in the Atta=
ched Network Set of an AODVv2 router the router MUST<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 respond authoritati=
vely to a RREQ, and MUST maintain the corresponding sequence number=E2=80=
=9D.<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 The text, as it cur=
rently is, is really hard to read, and a re-edit along these lines would go=
 a long way.=E2=80=9D<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 I note that the terms =E2=80=9CNode=E2=80=9D an=
d =E2=80=9CRouter Client=E2=80=9D are still used, in their original form,<b=
r>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 and that other than some slight wordsmithing th=
is comment has not been addressed in the document.<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 I reiterate that the need to use router, host, =
node, and router client in and by itself should<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 be an indicator that tightening up of terminolo=
gy is required.<br>
<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 I made the following comment to Routable Unicas=
t IP Address:<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =E2=80=9CAre there =
any technical reason why not simply *any* address could be<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0considered by=
 the routing protocol?<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0My understand=
ing, but correct me if I am wrong, is that all that is required is<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0that all inte=
rfaces in a given AODVv2 routing domain has an unique address.<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0That some of =
these addresses (by an IP addressing architecture document)<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0has special s=
emantics associated (such as are link locals, or are for private<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0use, or are f=
or example use only, or are for multicast) is out of scope here?<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 I see nothing has changed on the above, so let =
me be more explicit: the routing protocol itself<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 (probably) should not care about what kind of a=
ddresses are filled into it. Is an 192.16./16 address<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 appropriate? Not across the internet, but it ma=
y be in somebody=E2=80=99s private deployments. Should<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 the routing protocol be =E2=80=9Caddress police=
=E2=80=9D and is implementation of a =E2=80=9CI refuse to route these addre=
sses=E2=80=A6=E2=80=9D<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 a requirement for claiming conformance? Suggest=
 simply stating what the requirements are under<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 which the routing protocol will work =E2=80=94 =
and leave =E2=80=9Caddress assignment politics=E2=80=9D aside.<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 I also continued:<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Now, with tha=
t being said also, the WG wanted that RFC7181 supports not<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0just multiple=
 interfaces, but also the same address used on multiple interfaces<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0of the same r=
outer. There were good reasons for that, and while it was not trivial<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0to implement,=
 it turned out to be the right thing to support. If there are technical<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0reasons why t=
his is not supported in AODVv2 (for example, if this cannot be<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0made work bec=
ause of &lt;reason&gt;) then that should be called out in the<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0applicability=
 statement also?<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Conversely, if it i=
s possible in AODVv2, then I do not believe that it is clearly<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 specified how (at l=
east, in the =E2=80=9Cnaive=E2=80=9D on paper examples I drew up, something=
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 ended up not workin=
g). So either the protocol as-is does not support it (but<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 could be made to?) =
or it is supported (but just need to be spelled out), or is<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 not possible (and n=
eed to be disclaimed in the applicability statement).<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Stan Ratliff was a =
driving force in holding the WG=E2=80=99s collective feet to the fire<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 in getting this sup=
port included in RFC7181, and would likely be the right<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 person to consult o=
n this matter?<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 I actually have not seen changes, or comments, =
on this. In OLSRv2, the WG was making it<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 a strong requirement that it should be possible=
 to use the same IP address on different<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 interfaces of a router. It was somewhat tedious=
 to design around, but it was worked out, and<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 the conditions under which that was possible we=
re defined and documented.<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 I would like to see the same done for this prot=
ocol.<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 I also note that this is not unrelated to RFC66=
21-discussions. For example, when selecting<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 S-MPRs on a multi-interface and multi-address-p=
er-interface router, care must be taken<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 least things won=E2=80=99t work. So, if (and th=
is links back to previous mails) RFC6621 is a<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 requirement or desire for this protocol, then t=
here are some considerations required here.<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 I see that the definition of =E2=80=9CRouter Cl=
ient=E2=80=9D has changed to be<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =E2=80=9CAn address=
 or address range=E2=80=A6the AODVv2 router=E2=80=99s interface addresses<b=
r>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0are also conf=
igured as router clients=E2=80=9D<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Better than before, but still missing the targe=
t. The term =E2=80=9CRouter Client=E2=80=9D is, as I indicated<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 numerous times before, odd.<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 But the second part of the sentence, does that =
mean (what it says) that the interfaces<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 must be configured specially, so as to be able =
to be =E2=80=9Crouter clients=E2=80=9D? That can=E2=80=99t be true.<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 What you likely mean is:<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =E2=80=9CAn AODVv2 =
router is configured so as to consider its own interfaces as part of<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0the locally a=
ttached network set=E2=80=9D ?<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 You configure the router, right? No special =E2=
=80=9Cinterface configuration properties=E2=80=9D are required<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 for an interface to be announcable by=C2=A0 an =
AODVv2 router?<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 (And, getting rid of node would actually make t=
he definition shorter and nicer)<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Now, snipping out from the applicability statem=
ent:<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 &quot;Multi-homing =
of an IP address is not supported by AODVv2, and therefore a<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Router Clien=
t, i.e. an IP Address,=C2=A0 =E2=80=A6 &quot;<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =E2=80=A6evidence to there being some redundant=
 terminology here to weed away.<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 The below is a little bit of a meta-comment, I =
am not quite sure what I think here.<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 The definitions for Target Node and such were c=
onfusing before. They still are, somewhat.<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 I think that it may be because the definitions =
now used are simply copy-pasted out from the<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 tables in the previous version, for example:<br=
>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 An AODVv2 Data Elem=
ent containing the destination address of the<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 IP packet triggerin=
g route discovery.<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 OK, I can trace back and see that a Data Elemen=
t is something that exists inside a<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 protocol message. To me, however, that=E2=80=99=
s not really general terminology as such, but<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 part of the specification of a packet format - =
or rather, it is the notation that you use<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 when describing an algorithm. By the way, why a=
re some notations in CamelCase<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 whereas others have a space in them, e.g. =E2=
=80=9CTarget Node=E2=80=9D and =E2=80=9CTargMetric=E2=80=9D, both of which<=
br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 are Data Elements? Would be good with a consist=
ent approach here.<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 I *think* that it would be better to take all t=
hose =E2=80=9CData Element=E2=80=9D bits and move to a separate<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 section (or subsection) to the terminology, and=
 then keep all the =E2=80=9Cother stuff=E2=80=9D (Neighbor, =E2=80=A6)<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 in its own section.<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 I=E2=80=99m a great fan of calling this section=
 =E2=80=9CTerminology and Notation=E2=80=9D and then having two<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 subsections, one which is =E2=80=9CTerminology=
=E2=80=9D and one which is =E2=80=9CNotation=E2=80=9D, with the<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 TargMetric and Target Node being firmly in the =
latter.<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 I made a comment:<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 &quot;Second, shoul=
d =E2=80=9Cvalid route=E2=80=9D not be qualified by =E2=80=9Cto a specific =
address=E2=80=9D?=E2=80=9D<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Which was not addressed.<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 I also made a comment on &quot;Unreachable Addr=
ess=E2=80=9D - I am glad I did, because I apparently<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 had a different understanding than what was int=
ended. I now see that an Unreachable Address<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 by definition is an address listed in a RERR me=
ssage, and not the same as an address to<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 which no route has yet=C2=A0 been discovered? I=
f yes, then please use a different term, such as<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =E2=80=9CFormerlyReachableAddress=E2=80=9D or s=
omething of the sort?<br>
<br>
Applicability statement<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 First, I would like to recognize the efforts ma=
de to improve this since last review. Thanks<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Second, the document states:<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 &quot;AODVv2 suppor=
ts routers with multiple interfaces, as long as each<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0interf=
ace configured for AODVv2 has a unicast IP address.=C2=A0 A router<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0may us=
e the same IP address on multiple interfaces.=C2=A0 Address<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0assign=
ment procedures are out of scope for AODVv2.=E2=80=9D<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Is that true? Granted, I have not worked this t=
hrough in detail, but I can present a counter-example:<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 the use of RFC6621 means that there certainly a=
re some constraints that must be respected least<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 various flooding optimizations may not work.<br=
>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Secondly, if the multiple-interfaces-with-same-=
address are on the same L2, and this is what I<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 have not worked through, are there any situatio=
ns that will not work?<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 The immediately previous version of this specif=
ication read:<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 &quot;AODVv2 suppor=
ts routers with multiple interfaces, as long as each<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0interf=
ace configured for AODVv2 has its own unicast routable IP address&quot;<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 So what changed that means that each interface =
no longer needs its *own* unicast address?<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 I pointed out to the Applicability Statement:<b=
r>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 I think that append=
ix B needs to be removed. Essentially, it makes claims that it is<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 possible to do mult=
i-homing =E2=80=94 but neither specifies how it is done, nor gives<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 pointers to documen=
ts that justify the claim.<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 AODVv2 does not sup=
port multi-homing =E2=80=94 that=E2=80=99s clear, and it is fine that it is=
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 called out here. Th=
ank you for that.<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Now, with that bein=
g said, I am torn between being satisfied that it is called out on<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 one hand, and wanti=
ng to have =E2=80=9Cmulti homing=E2=80=9D on the other hand. RFC7181 suppor=
ts<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 multi-homing, FWIW.=
<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 I believe that this=
 also would merit some explicit discussion by the WG, in order to<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 understand if this =
design decision is acceptable?<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 I see that Appendix B still is in the document,=
 and I do not recall having seen this discussed<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 on the mailing list. Simply removing the refere=
nce from the Applicability Statement to Appendix B<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 does not address the issue that I raised in my =
previous review.<br>
<br>
To 4.1, I made the following comment:<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 &quot;Is this a should, or a SHOULD? If the lat=
ter, should it be a MUST?<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 In general, there are a lot of such =E2=
=80=9Cmaybe normative language=E2=80=9D through the<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0document, and I would much like to see an=
 editorial pass =E2=80=94 essentially all<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0may/should/ must and friends carefully ev=
aluated as if they should become<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A02119-terms, and ... more importantly (it =
has been called out before, fwiw)<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0quite a bit of should/SHOULD which ought =
to be transformed into MUST.<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Generally, aiming for a very a low number of SH=
OULD is a good design metric for a document=E2=80=9D<br>
<br>
Aside from the general comment on 2119-language, why is this a SHOULD?<br>
<br>
To 4.2, I made the following comment:<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 As indicated earlier, I believe that the term =
=E2=80=9CRouter Client=E2=80=9D is ill chosen.<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 I believe that it is more appropriately an =E2=
=80=9CAttached Network Set=E2=80=9D since =E2=80=94<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 as indicated previously =E2=80=94 the term =E2=
=80=9CRouter Client=E2=80=9D is ambiguous. I am pleased<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 to see, though, that this =E2=80=9CRouter Clien=
t List=E2=80=9D in reality is an =E2=80=9CAttached Network Set=E2=80=9D<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 and so that change should be (relatively) easy.=
<br>
<br>
The above comment still is applicable to this revision,<br>
<br>
To 4.2, I made the following comment:<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Also, I recommend to not say =E2=80=9Csubnet=E2=
=80=9D =E2=80=94 how about rephrasing to =E2=80=9CIf a prefix<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 is included in the attached network set of an A=
ODVv2 router, then that AODVv2<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 router MUST provide connectivity for, i.e. answ=
er to RREQs and maintain<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 sequence numbers for, all addresses from within=
 that prefix.=E2=80=9D<br>
<br>
I note that while the term has been removed from section 4, there=E2=80=99r=
e 4 lingering instances of this term in the document, that could easily be =
removed.<br>
<br>
I Also made a comment about Appendix B in my previous review, which is refe=
renced here. That comment still applies.<br>
<br>
To Section 4.3, I noticed:<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Does section 6.2 describe how to monitor an est=
ablished adjacency<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 only, or how to discover neighbouring AODVv2 ro=
uters? Looking in 6.2, I see<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =E2=80=9CNot every =
pair of neighboring routers will necessarily form an adjacency,=E2=80=9D =
=E2=80=94<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0so it likely =
isn=E2=80=99t 6.2 that tells me how to maintain this table?<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 In short, =E2=80=9CA neighbour table MUST be ma=
intained=E2=80=9D =E2=80=94 where can I find information on how to do this?=
<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Section 6.2 states:<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =E2=80=9CThe defaul=
t approach for monitoring bidirectional connectivity to the next hop toward=
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0OrigAddr is t=
o request acknowledgement of Route Reply messages.=E2=80=9D<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 That certainly will=
 tell me if a link over which an RREP is sent is bi-directional,<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 but will not mainta=
in a =E2=80=9Cneighbor table=E2=80=9D.<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 So how is this done? Or, is the =E2=80=9CNeighb=
or Table=E2=80=9D not supposed to contain the<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 complete set of neighbours? What information =
=E2=80=9C...MUST be maintained=E2=80=9D then, in this table?<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 This is very unclear, I would not know how to i=
mplement a mechanism that populates this<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =E2=80=9CNeighbor Table=E2=80=9D with the neede=
d information here.<br>
<br>
I see no (relevant) changes to 6.2 nor to 4.3 so I assume that this comment=
 has not been addressed<br>
<br>
I am throwing this in here, as I am sure that I commented on that in the pr=
evious review, but I do not see that addressed: is Appendix C normative, or=
 not? It represents =E2=80=9C a second specification of the protocol, in a =
different language=E2=80=9D from the main part of the specification. I have=
 not walked through and made 200% sure that both are perfectly aligned and =
that there are no ambiguities, but having two different specifications of a=
 protocol is a recipe for disaster.=C2=A0 Please either make 2000% sure tha=
t they are specifying the same thing without ambiguities, or remove one.<br=
>
<br>
To section 4.4, I wrote:<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 &quot;would like to nit-pick that: the router c=
an maintain this sequence number in whatever<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0format it pleases =E2=80=94 but, when it =
includes it in control messages, it must be<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0representable in a specified format, resp=
ecting certain rules.=E2=80=9D<br>
<br>
I see that there were no changes following this comment.<br>
<br>
To section 4.4 I asked for clarification as to if sequence numbers were per=
 interface or per router, as the specification was unclear on that. The wor=
ds has changed, but it still is unclear: how many sequence numbers does a r=
outer maintain? One? One per interface?<br>
<br>
In my previous review, I expressed that it would be preferential to use =E2=
=80=9Ca notation of Sets=E2=80=9D rather than tables. I see that this has n=
ot changed.<br>
<br>
I made a comment on node and address, let me pick this up again. The follow=
ing:<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 RteMsg.OrigAddr<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 An IP address of the node =
which requires the route, i.e., the<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 source address of the IP p=
acket triggering the route request.<br>
<br>
would be more compact and clear if getting rid of the term =E2=80=9Cnode=E2=
=80=9D and said:<br>
<br>
RteMsg.OrigAddr<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 The source address of the IP packet triggering =
the route request.<br>
<br>
<br>
To section 4.6, and I (and others) have commented on this before:<br>
<br>
=C2=A0 =C2=A0All AODVv2 routers MUST maintain a route table.=C2=A0 The rout=
e table<br>
=C2=A0 =C2=A0entry is a conceptual data structure.=C2=A0 Implementations MA=
Y use any<br>
=C2=A0 =C2=A0internal representation but MUST contain the following informa=
tion:<br>
<br>
In order to avoid confusion, rename this to =E2=80=9CRouting Information Ba=
se=E2=80=9D or =E2=80=9CRouting Set=E2=80=9D =E2=80=94 a Routing Table is a=
n operating system construct, whereon operations directly influence packet =
forwarding. What you are defining here is a RIB/an RS.<br>
<br>
The confusion that I pointed out in my previous review on =E2=80=9CIP addre=
ss=E2=80=9D and =E2=80=9CAddress=E2=80=9D being used a bit haphazardly pers=
ists, fwiw. It makes me think, can a router send an RREQ for a prefix?<br>
<br>
I also called this out in my previous review as incorrect, and despite word=
smithing it still is:<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Route.NextHop<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 The source IP address of t=
he message advertising the route to<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Route.Address, i.e. an IP =
address of the AODVv2 router used for<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 the next hop on the path t=
oward Route.Address.<br>
<br>
If that =E2=80=9Cmessage=E2=80=9D is an RFC5444 entity, then it does to hav=
e a =E2=80=9Csource IP Address=E2=80=9D =E2=80=94 the encapsulating IP data=
gram containing the packet containing the message does. And the message MAY=
 have an Originator Address<br>
<br>
<br>
As I indicated, I am walking through my previous review and retaining those=
 comments that I still think need attention =E2=80=94 and this is =E2=80=9C=
crossing off from part 1 of my previous review=E2=80=9D only. More to follo=
w.<br>
<br>
Thomas<br>
<br>
_______________________________________________<br>
manet mailing list<br>
<a href=3D"mailto:manet@ietf.org">manet@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/manet" rel=3D"noreferrer" =
target=3D"_blank">https://www.ietf.org/mailman/listinfo/manet</a><br>
</blockquote></div><br></div>

--001a11407d406fae2d0525eb090d--


From nobody Wed Dec  2 07:45:46 2015
Return-Path: <chris.dearlove@baesystems.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 D95EE1A6FFA for <manet@ietfa.amsl.com>; Wed,  2 Dec 2015 07:45:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.102
X-Spam-Level: 
X-Spam-Status: No, score=-4.102 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RDNS_NONE=0.793] 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 ITQgJBZOmqMQ for <manet@ietfa.amsl.com>; Wed,  2 Dec 2015 07:45:42 -0800 (PST)
Received: from ukmta2.baesystems.com (unknown [20.133.0.56]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C1E771A899A for <manet@ietf.org>; Wed,  2 Dec 2015 07:45:41 -0800 (PST)
X-IronPort-AV: E=Sophos; i="5.20,373,1444690800"; d="scan'208,217"; a="21479678"
Received: from unknown (HELO baemasmds017.greenlnk.net) ([10.15.207.104]) by ukmta2.baesystems.com with ESMTP; 02 Dec 2015 15:45:40 +0000
X-IronPort-AV: E=Sophos;i="5.20,373,1444690800";  d="scan'208,217";a="122591402"
Received: from glkxh0004v.greenlnk.net ([10.109.2.35]) by baemasmds017.greenlnk.net with ESMTP; 02 Dec 2015 15:45:39 +0000
Received: from GLKXM0002V.GREENLNK.net ([169.254.5.2]) by GLKXH0004V.GREENLNK.net ([10.109.2.35]) with mapi id 14.03.0248.002; Wed, 2 Dec 2015 15:45:39 +0000
From: "Dearlove, Christopher (UK)" <chris.dearlove@baesystems.com>
To: "manet@ietf.org" <manet@ietf.org>
Thread-Topic: DLEP-17 review, part 2
Thread-Index: AdEtF8LPEqE82C/QRHiZoEIShHRovg==
Date: Wed, 2 Dec 2015 15:45:39 +0000
Message-ID: <B31EEDDDB8ED7E4A93FDF12A4EECD30D7D76BF02@GLKXM0002V.GREENLNK.net>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.109.62.6]
Content-Type: multipart/alternative; boundary="_000_B31EEDDDB8ED7E4A93FDF12A4EECD30D7D76BF02GLKXM0002VGREEN_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/fOAP1xaMoBiBiHaYt4K-qJX_PmA>
Subject: [manet] DLEP-17 review, part 2
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: <https://mailarchive.ietf.org/arch/browse/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: Wed, 02 Dec 2015 15:45:46 -0000

--_000_B31EEDDDB8ED7E4A93FDF12A4EECD30D7D76BF02GLKXM0002VGREEN_
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable

Just section 5 this time.

First paragraph. Peer is a new term, and not explained. Here it means modem=
 or router. But later when implementation is being used for modem or router=
 (and I don't like that usage, for me implementation is about a specific re=
alisation of the protocol) peer is being used for the other device (modem/r=
outer when this device - the implementation - is router/modem). I think som=
e work on this terminology is needed.

Section 5 before section 5.1 (what I often find convenient to call section =
5.0) last paragraph, these are, I think, TCP ports. (I don't think used for=
 UDP, but should be indicated.) It's not clear why we might want multiple p=
orts.

Section 5.0, final paragraph, the address/port combination should be (say t=
hat it is) one the modem can be reached and received on.

Section 5.1. Why unused port? Why not the DLEP port? At least as an option.=
 And RFC 6335 calls these (49152+) "Dynamic Ports, also known as the Privat=
e or Ephemeral Ports" not unused ports.

I know there's discussion over IPv6 and IPv4 and broadcast addresses, so I'=
ll not comment further. Except to say as written I think it says not only t=
hat IPv6 must be implemented, but that you must send IPv6 in all cases.

Section 5.1 second paragraph. This waiting and resending is not the transac=
tion model described in Section 4.1. I'm guessing that's because the latter=
 is only intended in the TCP states. But this should be clearer.

Apart from previous comment on "three (3)" style, I think that it would be =
better if named parameters were used, with later recommended values. And if=
 there are several values, useful to know if in a fixed (or recommended) re=
lationship. (Yes, there are some relationships given that way e.g. two time=
s heartbeat.) But this is a style question, not a "right or wrong" thing.

Not sure why jitter is recommended.

Section 5.1 first full paragraph on page 13. Why might more than one addres=
s/port combination be used. (I'm actually not quite sure why more than one =
might be offered, but perhaps it's that the unused port might not be unused=
 in some cases.)

Same paragraph, should origin address be source address?

Section 5.1, penultimate paragraph. It's not clear why these signals might =
still want to be sent, what the purpose or value is.

Section 5.1 final paragraph. Is this then saying must start the router in S=
ession Initialisation State?

Section 5.2, second paragraph. Parsing is here introduced, but not discusse=
d for previous signals. That I think is one of those things that makes you =
stop and wonder why. Is it clearer to have a blanket comment about parsing =
somewhere, and elsewhere just stick to received?

Section 5.3, second paragraph. Not particularly keen on lists that are i.e.=
 (RFC Editor will demand a following comma btw) and finished etc., but it's=
 not actually wrong.

Section 5.3 (or 5.3.0 to be clear) final paragraph. And the peer? (As termi=
nology used here, but see earlier comment.)

Section 5.3.1 first two paragraphs have a MAY a MUST and a SHOULD. I can on=
ly make these even consistent by assuming that the latter two are MUST/SHOU=
LD in the case where the MAY is so, otherwise not. This could be clearer. (=
Also worth considering if it's a good mix.)

Section 5.4 Odd mixture of heartbeat time lengths and seconds.

Section 5.4 pre-penultimate paragraph, Destination Down messages MUST NOT b=
e sent. Why that specific case (only)?


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

--_000_B31EEDDDB8ED7E4A93FDF12A4EECD30D7D76BF02GLKXM0002VGREEN_
Content-Type: text/html; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii">
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-GB" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">Just section 5 this time.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">First paragraph. Peer is a new term, and not explain=
ed. Here it means modem or router. But later when implementation is being u=
sed for modem or router (and I don&#8217;t like that usage, for me implemen=
tation is about a specific realisation of
 the protocol) peer is being used for the other device (modem/router when t=
his device &#8211; the implementation &#8211; is router/modem). I think som=
e work on this terminology is needed.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Section 5 before section 5.1 (what I often find conv=
enient to call section 5.0) last paragraph, these are, I think, TCP ports. =
(I don&#8217;t think used for UDP, but should be indicated.) It&#8217;s not=
 clear why we might want multiple ports.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Section 5.0, final paragraph, the address/port combi=
nation should be (say that it is) one the modem can be reached and received=
 on.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Section 5.1. Why unused port? Why not the DLEP port?=
 At least as an option. And RFC 6335 calls these (49152&#43;) &#8220;Dynami=
c Ports, also known as the Private or Ephemeral Ports&#8221; not unused por=
ts.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">I know there&#8217;s discussion over IPv6 and IPv4 a=
nd broadcast addresses, so I&#8217;ll not comment further. Except to say as=
 written I think it says not only that IPv6 must be implemented, but that y=
ou must send IPv6 in all cases.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Section 5.1 second paragraph. This waiting and resen=
ding is not the transaction model described in Section 4.1. I&#8217;m guess=
ing that&#8217;s because the latter is only intended in the TCP states. But=
 this should be clearer.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Apart from previous comment on &#8220;three (3)&#822=
1; style, I think that it would be better if named parameters were used, wi=
th later recommended values. And if there are several values, useful to kno=
w if in a fixed (or recommended) relationship.
 (Yes, there are some relationships given that way e.g. two times heartbeat=
.) But this is a style question, not a &#8220;right or wrong&#8221; thing.<=
o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Not sure why jitter is recommended.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Section 5.1 first full paragraph on page 13. Why mig=
ht more than one address/port combination be used. (I&#8217;m actually not =
quite sure why more than one might be offered, but perhaps it&#8217;s that =
the unused port might not be unused in some cases.)<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Same paragraph, should origin address be source addr=
ess?<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Section 5.1, penultimate paragraph. It&#8217;s not c=
lear why these signals might still want to be sent, what the purpose or val=
ue is.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Section 5.1 final paragraph. Is this then saying mus=
t start the router in Session Initialisation State?<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Section 5.2, second paragraph. Parsing is here intro=
duced, but not discussed for previous signals. That I think is one of those=
 things that makes you stop and wonder why. Is it clearer to have a blanket=
 comment about parsing somewhere,
 and elsewhere just stick to received?<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Section 5.3, second paragraph. Not particularly keen=
 on lists that are i.e. (RFC Editor will demand a following comma btw) and =
finished etc., but it&#8217;s not actually wrong.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Section 5.3 (or 5.3.0 to be clear) final paragraph. =
And the peer? (As terminology used here, but see earlier comment.)<o:p></o:=
p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Section 5.3.1 first two paragraphs have a MAY a MUST=
 and a SHOULD. I can only make these even consistent by assuming that the l=
atter two are MUST/SHOULD in the case where the MAY is so, otherwise not. T=
his could be clearer. (Also worth
 considering if it&#8217;s a good mix.)<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Section 5.4 Odd mixture of heartbeat time lengths an=
d seconds.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Section 5.4 pre-penultimate paragraph, Destination D=
own messages MUST NOT be sent. Why that specific case (only)?<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<p>********************************************************************<br>
This email and any attachments are confidential to the intended<br>
recipient and may also be privileged. If you are not the intended<br>
recipient please delete it from your system and notify the sender.<br>
You should not copy it or use it for any purpose nor disclose or<br>
distribute its contents to any other person.<br>
********************************************************************</p></b=
ody>
</html>

--_000_B31EEDDDB8ED7E4A93FDF12A4EECD30D7D76BF02GLKXM0002VGREEN_--


From nobody Wed Dec  2 08:06:04 2015
Return-Path: <chris.dearlove@baesystems.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 DF90F1AD182 for <manet@ietfa.amsl.com>; Wed,  2 Dec 2015 08:06:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.309
X-Spam-Level: 
X-Spam-Status: No, score=-1.309 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, J_CHICKENPOX_57=0.6, T_RP_MATCHES_RCVD=-0.01] autolearn=no
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 N9BydHz0R1Rp for <manet@ietfa.amsl.com>; Wed,  2 Dec 2015 08:05:56 -0800 (PST)
Received: from ukmta4.baesystems.com (ukmta4.baesystems.com [20.133.40.56]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 575851ACF02 for <manet@ietf.org>; Wed,  2 Dec 2015 08:05:41 -0800 (PST)
X-IronPort-AV: E=Sophos; i="5.20,373,1444690800"; d="scan'208,217"; a="18825363"
Received: from unknown (HELO baemasodc005.greenlnk.net) ([10.108.52.29]) by ukmta4.baesystems.com with ESMTP; 02 Dec 2015 16:05:36 +0000
X-IronPort-AV: E=Sophos;i="5.20,373,1444690800";  d="scan'208,217";a="125879757"
Received: from glkxh0001v.greenlnk.net ([10.109.2.32]) by baemasodc005.greenlnk.net with ESMTP; 02 Dec 2015 16:05:27 +0000
Received: from GLKXM0002V.GREENLNK.net ([169.254.5.2]) by GLKXH0001V.GREENLNK.net ([10.109.2.32]) with mapi id 14.03.0248.002; Wed, 2 Dec 2015 15:56:49 +0000
From: "Dearlove, Christopher (UK)" <chris.dearlove@baesystems.com>
To: Victoria Mercieca <vmercieca0@gmail.com>, "ietf@thomasclausen.org" <ietf@thomasclausen.org>
Thread-Topic: [manet] Stuff from review of aodv-11 page 1-22 that are still not folded into -12
Thread-Index: AQHRLG2A8UiZ6Ehm0kWlE5acD7I27J63wYuAgAAXQKA=
Date: Wed, 2 Dec 2015 15:56:47 +0000
Message-ID: <B31EEDDDB8ED7E4A93FDF12A4EECD30D7D76BF1C@GLKXM0002V.GREENLNK.net>
References: <F474BF24-D920-4A54-8F43-AB4B9FE939A8@thomasclausen.org> <CAAePS4Dmv=j_ASKhsX+kenP-xaDUWUEFuzYGduxu+FR_C2R-MA@mail.gmail.com>
In-Reply-To: <CAAePS4Dmv=j_ASKhsX+kenP-xaDUWUEFuzYGduxu+FR_C2R-MA@mail.gmail.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.109.62.6]
Content-Type: multipart/alternative; boundary="_000_B31EEDDDB8ED7E4A93FDF12A4EECD30D7D76BF1CGLKXM0002VGREEN_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/TC_WKyAYdwAIAOwHOfhj8eyDXCA>
Cc: manet <manet@ietf.org>
Subject: Re: [manet] Stuff from review of aodv-11 page 1-22 that are still not folded into -12
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: <https://mailarchive.ietf.org/arch/browse/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: Wed, 02 Dec 2015 16:06:04 -0000

--_000_B31EEDDDB8ED7E4A93FDF12A4EECD30D7D76BF1CGLKXM0002VGREEN_
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64

SSBtYWRlIGFuIG9ic2VydmF0aW9uICh0aGF0IFJGQyA2NjIxIGlzIGNvbXBsZXRlbHkgaW5hcHBs
aWNhYmxlKSBvbiAtMTIsIGJ1dCBiYXNlZCBpbiBwYXJ0IG9uIHRoYXQsIEnigJltIHdhaXRpbmcg
dG8gcmV2aWV3IHRoZSBuZXh0IGRyYWZ0LCByYXRoZXIgdGhhbiB0aGlzIG9uZS4gKFRpbWUgSSBj
YW4gbWFrZSBJ4oCZbSBsb29raW5nIGF0IERMRVAsIHdoaWNoIGFwcGVhcnMgY2xvc2VyIHRvIGZp
bmFsLCB0aG91Z2ggdGhlcmXigJlzIGEgY291cGxlIG9mIG9wZW4gcXVlc3Rpb25zIG9uIElQdjYg
YW5kIFRMUy4pDQoNCk9ic2VydmluZyB0aGlzIGRpc2N1c3Npb24gKG9mIEFPRFZ2MikgdGhlcmUg
c2VlbXMgdG8gYmUgYSBzaWduaWZpY2FudCBpc3N1ZSBvbiBob3AgYnkgaG9wIHZlcnN1cyBlbmQg
dG8gZW5kIGJpZGlyZWN0aW9uYWxpdHkuIEFzIEnigJl2ZSBjb21tZW50ZWQgYmVmb3JlLCBJ4oCZ
dmUgZm91bmQgZW5vdWdoIGluIHRoZSDigJxvdXRzaWRl4oCdIHBhcnRzIG9mIHRoZSBzcGVjaWZp
Y2F0aW9uLCB0aGF0IEkgaGF2ZW7igJl0IGdvdCBzdHVjayBpbnRvIHRoZSBhY3R1YWwgY29yZSBw
cm90b2NvbCwgc28gSSBkb27igJl0IHlldCBoYXZlIGEgdmlldyBvbiB0aGlzLiAoSSBoYXZlIGEg
dmlldyB0aGF0IGJpZGlyZWN0aW9uYWxpdHkgbmVlZHMgZW5zdXJpbmcgd29ya3MsIGFuZCB0byBi
ZSBpbnRlcm9wZXJhYmxlLCBidXQgdGhhdOKAmXMgYXMgZmFyIGFzIEnigJl2ZSBnb3QuKSBCdXQg
aXTigJlzIGEgYml0IGNvbmNlcm5pbmcgdGhhdCB0aGlzIHN0aWxsIGlzbuKAmXQgY2xlYXIg4oCT
IGFuZCBJ4oCZdmUgc2VlbiBubyByZXBvcnRzIG9mIGFuIGltcGxlbWVudGF0aW9uIG9mIGVpdGhl
ci4gSXMgdGhlcmUgb25lPw0KDQoNCkZyb206IG1hbmV0IFttYWlsdG86bWFuZXQtYm91bmNlc0Bp
ZXRmLm9yZ10gT24gQmVoYWxmIE9mIFZpY3RvcmlhIE1lcmNpZWNhDQpTZW50OiAwMiBEZWNlbWJl
ciAyMDE1IDE0OjI1DQpUbzogaWV0ZkB0aG9tYXNjbGF1c2VuLm9yZw0KQ2M6IG1hbmV0DQpTdWJq
ZWN0OiBSZTogW21hbmV0XSBTdHVmZiBmcm9tIHJldmlldyBvZiBhb2R2LTExIHBhZ2UgMS0yMiB0
aGF0IGFyZSBzdGlsbCBub3QgZm9sZGVkIGludG8gLTEyDQoNCg0KKioqIFdBUk5JTkcgKioqDQpU
aGlzIG1lc3NhZ2Ugb3JpZ2luYXRlcyBmcm9tIG91dHNpZGUgb3VyIG9yZ2FuaXNhdGlvbiwgZWl0
aGVyIGZyb20gYW4gZXh0ZXJuYWwgcGFydG5lciBvciB0aGUgaW50ZXJuZXQuDQpDb25zaWRlciBj
YXJlZnVsbHkgd2hldGhlciB5b3Ugc2hvdWxkIGNsaWNrIG9uIGFueSBsaW5rcywgb3BlbiBhbnkg
YXR0YWNobWVudHMgb3IgcmVwbHkuDQpGb3IgaW5mb3JtYXRpb24gcmVnYXJkaW5nIFJlZCBGbGFn
cyB0aGF0IHlvdSBjYW4gbG9vayBvdXQgZm9yIGluIGVtYWlscyB5b3UgcmVjZWl2ZSwgY2xpY2sg
aGVyZTxodHRwOi8vaW50cmFuZXQuZW50LmJhZXN5c3RlbXMuY29tL2hvd3dld29yay9zZWN1cml0
eS9zcG90bGlnaHRzL0RvY3VtZW50cy9SZWQlMjBGbGFncy5wZGY+Lg0KSWYgeW91IGZlZWwgdGhl
IGVtYWlsIGlzIHN1c3BpY2lvdXMsIHBsZWFzZSBmb2xsb3cgdGhpcyBwcm9jZXNzPGh0dHA6Ly9p
bnRyYW5ldC5lbnQuYmFlc3lzdGVtcy5jb20vaG93d2V3b3JrL3NlY3VyaXR5L3Nwb3RsaWdodHMv
RG9jdW1lbnRzL0RlYWxpbmclMjBXaXRoJTIwU3VzcGljaW91cyUyMEVtYWlscy5wZGY+Lg0KKioq
IFdBUk5JTkcgKioqDQpFWFRFUk5BTCBFTUFJTCAtLSBUaGlzIG1lc3NhZ2Ugb3JpZ2luYXRlcyBm
cm9tIG91dHNpZGUgb3VyIG9yZ2FuaXphdGlvbi4NCg0KSGVsbG8gVGhvbWFzLA0KVGhhbmsgeW91
IGFnYWluIGZvciB5b3VyIHRpbWUgc3BlbnQgcmV2aWV3aW5nIEFPRFZ2Mi4gSSBhcG9sb2dpc2Ug
dGhhdCB3ZSBkaWQgbm90IGdpdmUgYSAicG9pbnQgYnkgcG9pbnQiIHJlc3BvbnNlIHRvIHlvdXIg
Y29tbWVudHMgb24gZHJhZnQgMTEgLSBJIGZlbHQgdGhhdCBzaW5jZSBtb3N0IG9mIHRoZSBjb21t
ZW50cyB3ZXJlIGFyb3VuZCBhIGZldyBtYWpvciB0b3BpY3MsIGl0IG1hZGUgc2Vuc2UgdG8gYWRk
cmVzcyB0aGUgdG9waWMgYWNyb3NzIHRoZSB3aG9sZSBkcmFmdCwgcmF0aGVyIHRoYW4gcmVzcG9u
ZCB0byBldmVyeSBzaW5nbGUgY29tbWVudCBpbiBvcmRlci4gSSBkaWQgYWxzbyB0cnkgdG8gc3Rh
cnQgYSBkaXNjdXNzaW9uIG9uIHRoZSBNQU5FVCBsaXN0IGJhc2VkIG9uIHlvdXIgY29tbWVudHMg
ZnJvbSBkcmFmdCAxMSwgYnV0IGRpZCBub3Qgc2VlIGFueSByZXNwb25zZXMuDQpUaGFuayB5b3Ug
YWdhaW4sIHdlIHdpbGwgZGlzY3VzcyBhbmQgaW50ZW5kIHRvIHJlc3BvbmQgc29vbi4NCktpbmQg
cmVnYXJkcywNClZpY3RvcmlhLg0KDQoNCk9uIFR1ZSwgRGVjIDEsIDIwMTUgYXQgNzoyMSBQTSwg
PGlldGZAdGhvbWFzY2xhdXNlbi5vcmc8bWFpbHRvOmlldGZAdGhvbWFzY2xhdXNlbi5vcmc+PiB3
cm90ZToNCkFsbCwNCg0KSSBhbSB3b3JraW5nIHRocm91Z2ggdGhlIHJldmlzZWQgSS1EIHRvIHNl
ZSB3aGF0IGNvbW1lbnRzIHRoYXQgSSBtYWRlIHByZXZpb3VzbHkgaGF2ZSBiZWVuIGFkZHJlc3Nl
ZCwgYW5kIHdoaWNoIHN0aWxsIGRvIGFwcGx5Lg0KDQpBcyBJIHNlbnQgbXkgb3JpZ2luYWwgcmV2
aWV3IHBpZWNlbWVhbCwgSeKAmWxsIHNlbmQgbXkgcmVmcmVzaGVyIGluIG1hdGNoaW5nIHBpZWNl
cyAoaW4gcGFydCwgaW4gcmVjb2duaXRpb24gdGhhdCBpdCBpcyBoYXJkIHRvIGdldCB0aW1lIHRv
IHNpdCBkb3duIGFuZCByZXZpZXcgdGhlIHdob2xlIGRvY3VtZW50IGluIG9uZSBnbywgYW5kIEkg
ZG8gd2FudCB0byByZXBseSB0byB0aGUgYXV0aG9ycyBhcyBxdWlja2x5IGFzIHBvc3NpYmxlKQ0K
DQpJbiBkb2luZyBzbywgSSBhbSBub3RpY2luZyBhZGRpdGlvbmFsIHRoaW5ncyAobm90YWJseSwg
YnV0IG5vdCBleGNsdXNpdmVseSwgdG8gc2VjdGlvbiA3IGFuZCBiZXlvbmQsIHdoaWNoIEkgZGlk
buKAmXQgZ2V0IHRocm91Z2ggcmV2aWV3aW5nIGxhc3QgdGltZSBhcm91bmQpIHdoaWNoIG5lZWRz
IGF0dGVudGlvbi4gSeKAmWxsIGdhdGhlciB0aGF0IGluIHNlcGFyYXRlIGVtYWlscyBhIGJpdCBs
YXRlciwgb25jZSBJ4oCZdmUgd29ya2VkIHRocm91Z2ggdGhlIGNvbXBsZXRlLCB1cGRhdGVkIHNw
ZWMuDQoNClNvIG9ud2FyZHMuLi4NCg0KQWJzdHJhY3Q6DQogICAgICAgIEkgbWFkZSB0aGUgZm9s
bG93aW5nIGNvbW1lbnQsIHdoaWNoIHN0aWxsIGFwcGxpZXM6DQoNCiAgICAgICAgICAgICAgICDi
gJxUaGlzIGlzIGEgbGl0dGxlIG92ZXItc3RhdGluZyB0aGUgYXBwbGljYWJpbGl0eTogdGhlc2Ug
c3RhdGVtZW50cyBtYXkNCiAgICAgICAgICAgICAgICAgYmUgdHJ1ZSBpbiBzb21lIHNjZW5hcmlv
cyAoZm9yIGV4YW1wbGUsIHdoZW4gdGhlcmUgYXJlIGZldw0KICAgICAgICAgICAgICAgICBjb25j
dXJyZW50IHRyYWZmaWMgZmxvd3MsIGFuZCB0aGVyZWZvcmUgZmV3IHJvdXRlcyB0byByZXBhaXIs
IGFuZA0KICAgICAgICAgICAgICAgICB0aGVyZWZvcmUgZmV3IGZsb29kaW5nIG9wZXJhdGlvbnMg
dG8gY29udGVuZCBmb3IgY2hhbm5lbCBhY2Nlc3MpLg0KICAgICAgICAgICAgICAgICBBcyBhIGdl
bmVyYWwgc3RhdGVtZW50LCB0aGlzIGxhc3Qgc2VudGVuY2UgaXMgaW5jb3JyZWN04oCd4oCdDQoN
Ck92ZXJ2aWV3IChhbmQgZWxzZXdoZXJlKToNCg0KICAgICAgICBJIG1hZGUgYSBjb21tZW50IHBy
ZXZpb3VzbHkgdGhhdCDigJxSb3V0ZXIgY2xpZW504oCdIGlzIGEgcG9vcmx5IGNob3Nlbg0KICAg
ICAgICB0ZXJtLCBhbmQgaGF2ZSBwcm9wb3NlZCBhbHRlcm5hdGl2ZXMuIEnigJl2ZSBzZWVuIHNv
bWUgYXR0ZW1wdHMgb24gdGhlIGxpc3QNCiAgICAgICAgYXQgcmF0aGVyIHRoYW4gY2hhbmdlIHRo
ZSB0ZXJtLCBleHBsYWluIGl0IOKAlCBzb21lIG9mIHdoaWNoIGlzIGluIHRoaXMgZG9jdW1lbnQu
DQogICAgICAgIFRoZSDigJxPdmVydmlld+KAnSBzdGlsbCB0YWxrcyBhYm91dCDigJxhIHJvdXRl
cuKApm9uZSBvZiBpdHMgY2xpZW50c+KAnSAtIHdoaWNoIGlzIG5vIGxlc3MNCiAgICAgICAgY29u
ZnVzaW5nIHRoYW4gbGFzdCB0aW1lIEl3IHdlbnQgdGhyb3VnaCBpdC4NCg0KICAgICAgICBJIHJl
aXRlcmF0ZSwgd2h5IG5vdCB1c2Ug4oCcTG9jYWwgQXR0YWNoZWQgTmV0d29yayBTZXTigJ0sIHdo
aWNoIGlzIHRoZSB0ZXJtIHVzZWQNCiAgICAgICAgYnkgb3RoZXIgZG9jdW1lbnRzIGZyb20gdGhp
cyBXRz8NCg0KT3ZlcnZpZXc6DQogICAgICAgIFRoZSB0ZXJtIOKAnGNvbmZpcm1pbmcgYWRqYWNl
bmN54oCdIGlzIGdvbmUsIGFuZCBpcyBub3cgcmVwbGFjZWQgYnkNCiAgICAgICAg4oCcY29uZmly
bWluZyBiaWRpcmVjdGlvbmFsaXR54oCdIC0gd2hpY2gsIGFsYXMsIHN0aWxsIHNvdW5kcyBsaWtl
IHRoZXJlIGlzIHNvbWUgYWN0aXZlDQogICAgICAgIG1vbml0b3JpbmcgKEhFTExPIG1lc3NhZ2Ug
ZXhjaGFuZ2UpIGdvaW5nIG9uLiBVbmxlc3MgdGhhdCBpcyB0aGUgY2FzZSwNCiAgICAgICAgdGhl
biBwbGVhc2UgYmUgbW9yZSBzcGVjaWZpYyBoZXJlLg0KDQogICAgICAgIEkgbm90ZSB0aGF0IHRo
ZSB0ZXJtIGFkamFjZW5jeSBpcyB1c2VkIHRocm91Z2ggYW5kIHRocm91Z2ggdGhlIGRvY3VtZW50
LCBidHcuDQoNCiAgICAgICAgSSBzdWdnZXN0ZWQgaW4gbXkgbGFzdCByZXZpZXc6DQoNCiAgICAg
ICAgICAgICAgICBUaGUgb3ZlcnZpZXcgbXVzdCBhbHNvIGluY2x1ZGUgYSBwYXJhZ3JhcGggb24g
dGhlIGludGVyc2VjdGlvbnMNCiAgICAgICAgICAgICAgICBiZXR3ZWVuIHRoaXMgcHJvdG9jb2wg
YW5kIHRoZSBmb3J3YXJkaW5nIHBsYW5lIOKAlCB0aGlzLCBhcyBpdCBpcw0KICAgICAgICAgICAg
ICAgIGRpZmZlcmVudCAoYW5kIG1vcmUgaW52YXNpdmUpIGZyb20gdGhhdCB3aGljaCBpcyB0eXBp
Y2FsbHkgc2VlbiBpbg0KICAgICAgICAgICAgICAgIHJvdXRpbmcgcHJvdG9jb2xzLg0KDQogICAg
ICAgICAgICAgICAgU3BlY2lmaWNhbGx5LCBhcyBhIHJlYWN0aXZlIHByb3RvY29sLCBpdCBpcyBy
ZXF1aXJlZCAoYXQgbGVhc3QpIHRoYXQgdGhlDQogICAgICAgICAgICAgICAgZm9yd2FyZGluZyBw
bGFuZSBpcyBtb2RpZmllZCA6DQoNCiAgICAgICAgICAgICAgICAxKSBBIOKAnG1pc3PigJ0gd2hl
biBsb29raW5nIHVwIGEgbmV4dCBob3AgZm9yIGEgZGF0YSBwYWNrZXQgdG8gYmUNCiAgICAgICAg
ICAgICAgICAgICBmb3J3YXJkZWQsIGlzIHNpZ25hbGxlZCB0byB0aGUgQU9EVnYyIHByb2Nlc3Mg
c28gYXMgdG8gcGVybWl0DQogICAgICAgICAgICAgICAgICB0aGF0IHJvdXRlIGRpc2NvdmVyeSBi
ZSBsYXVuY2hlZDsNCg0KICAgICAgICAgICAgICAgIDIpIEEg4oCcbWlzc+KAnSB3aGVuIGF0dGVt
cHRpbmcgdG8gZGVsaXZlciBhIGRhdGEgcGFja2V0IHRvIGEgbmV4dCBob3AsDQogICAgICAgICAg
ICAgICAgICAgd2hpY2ggd2FzIHJlY29yZGVkIGluIHRoZSByb3V0aW5nIHRhYmxlLCBpcyBzaWdu
YWxsZWQgdG8gdGhlIEFPRFZ2Mg0KICAgICAgICAgICAgICAgICAgIHByb2Nlc3Mgc28gYXMgdG8g
cGVybWl0IHRoYXQgYSByb3V0ZSByZXBhaXIgYmUgaW5pdGlhdGVkIGFuZC9vciBhIFJvdXRlDQog
ICAgICAgICAgICAgICAgICAgRXJyb3IgYmUgZ2VuZXJhdGVkLg0KDQogICAgICAgICAgICAgICAg
MykgQSDigJxoaXTigJ0gd2hlbiBsb29raW5nIHVwIGEgbmV4dCBob3AgZm9yIGEgZGF0YSBwYWNr
ZXQgdG8gYmUgZm9yd2FyZGVkDQogICAgICAgICAgICAgICAgICAgIHRvIGEgZGVzdGluYXRpb24g
aXMgc2lnbmFsbGVkIHRvIHRoZSBBT0RWdjIgcHJvY2VzcyBzbyBhcyB0byBwZXJtaXQNCiAgICAg
ICAgICAgICAgICAgICAgbWFpbnRlbmFuY2Ugb2Yg4oCcYWN0aXZlIHJvdXRl4oCdIFJvdXRlIFN0
YXRlLCB0aW1lcnMgYW5kIHN1Y2guDQoNCiAgICAgICAgICAgICAgICBOb3RlIHRoYXQgdGhlc2Ug
dGhpbmdzIGFyZSBuZWNlc3NhcnkgdG8gY2FsbCBvdXQgaW4gdGhlIOKAnG92ZXJ2aWV34oCdIGFu
ZCBpbg0KICAgICAgICAgICAgICAgIHRoZSDigJxhcHBsaWNhYmlsaXR5IHN0YXRlbWVudOKAnSwg
Ym90aDogaXQgaXMgbm90IHRoYXQgdGhleSBhcmUgbmVnYXRpdmVzIHBlciBzZSwNCiAgICAgICAg
ICAgICAgICBidXQgdGhhdCB0aGV5IGFyZSBpbXBvcnRhbnQgZmFjdG9ycyBnb3Zlcm5pbmcgdGhl
IGFwcGxpY2FiaWxpdHkgb2YgdGhpcyBwcm90b2NvbDoNCiAgICAgICAgICAgICAgICB3aWxsIGEg
Z2l2ZW4gcGxhdGZvcm0gcGVybWl0IHN1Y2ggYWNjZXNzIHRvIHRoZSBmb3J3YXJkaW5nIHBsYW5l
LCBmb3IgZXhhbXBsZT8NCiAgICAgICAgICAgICAgICBJbXBvcnRhbnQgdG8gdW5kZXJzdGFuZCBp
ZiBmb3IgdGhhdCBwbGF0Zm9ybSB0aGlzIHByb3RvY29sIGlzIGFwcGxlDQoNCg0KICAgICAgICBJ
IHNlZSB0aGF0IHRoaXMgd2FzIG5vdCBhZGRyZXNzZWQgaW4gdGhlIG92ZXJ2aWV3LCBub3IgaW4g
dGhlIGFwcGxpY2FiaWxpdHkgb3RoZXIgdGhhbg0KICAgICAgICBieSBhIGZvcndhcmQgcmVmZXJl
bmNlIHRvIHNlY3Rpb24gNi40LiBXaGlsZSBpdCBpcyBwb3NpdGl2ZSB0aGF0IHRoZXJlIGlzIGEg
c2VjdGlvbiA2LjQsDQogICAgICAgIHRoaXMgZG9lcyBub3QgZXhvbmVyYXRlIHRoZSBvdmVydmll
dyBhbmQgdGhlIGFwcGxpY2FiaWxpdHkgc3RhdGVtZW50IGZvciBiZWluZw0KICAgICAgICBob25l
c3QgYWJvdXQgdGhlIHJlcXVpcmVtZW50cyAobm90YWJseSB0byB0aGUgcGxhdGZvcm0vb3MpIHRo
YXQgdGhpcyBwcm90b2NvbCBoYXMNCiAgICAgICAgZm9yIGJlaW5nIGFwcGxpY2FibGUNCg0KICAg
ICAgICBJIHN1Z2dlc3RlZCBpbiBteSBsYXN0IHJldmlldzoNCg0KICAgICAgICAgICAgICAgIOKA
nEl0IGlzIGltcG9ydGFudCB0byBkbyBtb3JlIHRoYW4gdGhpczogNzE4MiBkb2VzIG9ubHkgcHJv
dmlkZSDigJxjb250YWluZXJz4oCdDQogICAgICAgICAgICAgICAgIGZvciBJQ1ZzIGFuZCB0aW1l
c3RhbXBzLCBhbmQgZG9lcyBub3Qgc3BlY2lmeSBob3cgdG8gdXNlIHRoZW0gdG8gb2J0YWluDQog
ICAgICAgICAgICAgICAgIHNwZWNpZmljIHNlY3VyaXR5IHByb3BlcnRpZXMuIFJGQzcxODIgbWF5
IGJlIGEgdG9vbCB0aGF0IGNhbiBiZSB1c2VkLCBidXQNCiAgICAgICAgICAgICAgICAgKmhvdyog
dGhhdCB0b29sIGlzIHVzZWQgaXMgd2hhdCBkZXRlcm1pbmVzIHRoZSBzZWN1cml0eSBwcm9wZXJ0
aWVzLg0KDQogICAgICAgICAgICAgICAgVGhlcmVmb3JlLCBzYXlpbmcgdGhhdCDigJxzZWN1cml0
eSBpcyBkZWFsdCB3aXRoIGJ5IHVzaW5nIFJGQzcxODLigJ0gaXMgZWl0aGVyIGFuDQogICAgICAg
ICAgICAgICAgaW5jb21wbGV0ZSBzdGF0ZW1lbnQsIG9yIGlzIGluZGljYXRpdmUgb2YgaW5zdWZm
aWNpZW50IHNlY3VyaXR5IGNvbnNpZGVyYXRpb25zLuKAnQ0KDQogICAgICAgIFRoZSBhY3R1YWwg
c2VudGVuY2UgaW4gdGhlIEktRCBoYXMgYmVlbiBjaGFuZ2VkLCBub3cgaXQgZXhwbGljaXRseSBu
YW1lcyB0aGUNCiAgICAgICAgdHdvIFRMVnMgZnJvbSA3MTgyIHRoYXQgaXQgdXNlcy4gVGhhdCBp
cywgYWxhcywgc3RpbGwgbm90IHN1ZmZpY2llbnQuDQoNCiAgICAgICAgTWFraW5nIHRoZSBhc2lk
ZSB0aGF0IHdhcyBkaXNjdXNzZWQgcmVjZW50bHkgb24gdGhlIGxpc3QsIHRoYXQgKGkpIGNvbnRy
b2wgbWVzc2FnZXMNCiAgICAgICAgYXJlIG5vdCBmb3J3YXJkZWQsIGFuZCB0aGF0IChpaSkgdGhl
eSBhcmUgbW9kaWZpZWQgaW4gdHJhbnNpdCwgdGhlIHNlY3VyaXR5L3RydXN0IG1vZGVsDQogICAg
ICAgIGlzIHNvbWV3aGF0IGRpZmZlcmVudCBmcm9tIHRoYXQgb2YgNzE4MSBhbmQgY29uc2VxdWVu
dGx5IGZvciB3aGF0IDcxODIgd2FzIGluaXRpYWxseQ0KICAgICAgICB3cml0dGVuIGZvci4gSSB0
aGluayB0aGF0ICBjYWxsaW5nIG91dCB0aGUgdHJ1c3QgbW9kZWwsIGFuZCBob3cgNzE4MiBhY3R1
YWxseSBpcyB1c2VkIGhlcmUsDQogICAgICAgIG1pZ2h0IGJlIHdoYXQgaXMgY2FsbGVkIGZvci4N
Cg0KICAgICAgICBDb250aW51aW5nIHdpdGggdGhlIGFzaWRlLCB0aGlzICplc3BlY2lhbGx5KiBh
cyB0aGUgYXBwbGljYWJpbGl0eSBzdGF0ZW1lbnQgc2F5czoNCg0KICAgICAgICAgICAgICAgICJQ
cm92aWRpbmcgc2VjdXJpdHkgZm9yIGEgcmVhY3RpdmUgcm91dGluZyBwcm90b2NvbCBjYW4gYmUg
ZGlmZmljdWx04oCdDQoNCg0KVGVybWlub2xvZ3k6DQoNCiAgICAgICAgTXkgbGFzdCByZXZpZXcg
c3VnZ2VzdGVkOg0KICAgICAgICAgICAgICAgIOKAnFRoaXMgaGFzIGJlZW4gYnJvdWdodCB1cCBv
biB0aGUgbGlzdCBzZXZlcmFsIHRpbWVzIGluIHRoZSBwYXN0LCB3aXRob3V0IGhhdmluZw0KICAg
ICAgICAgICAgICAgICBiZWVuIGFkZHJlc3NlZC4NCg0KICAgICAgICAgICAgICAgIFRoZXJlIGFy
ZSDigJxob3N0c+KAnSBhbmQgdGhlcmUgYXJlIOKAnHJvdXRlcnPigJ0g4oCUIHdob3NlIHJvbGVz
IGFyZSB3ZWxsIGRlZmluZWQuDQogICAgICAgICAgICAgICAg4oCcTm9kZeKAnSBub3Qgc28gbXVj
aCDigJQgd2hpY2ggaXMgY2xlYXIgZnJvbSBsb29raW5nIGF0IHRoZSBkZWZpbml0aW9uIGhlcmU6
IOKAnGVpdGhlcg0KICAgICAgICAgICAgICAgIEFPRFZ2MiByb3V0ZXJzIG9yIHJvdXRlciBjbGll
bnRz4oCdICh3aXRoIOKAnHJvdXRlciBjbGllbnRz4oCdIGJlaW5nIGRlZmluZWQgYXMg4oCcYW4N
CiAgICAgICAgICAgICAgICBBT0RWdjIgcm91dGVyIGlzIGFsc28gaXRzIG93biByb3V0ZXIgY2xp
ZW504oCdKS4NCg0KICAgICAgICAgICAgICAgIFRoaXMgaXMgdmVyeSBtdWNoIHJlbGF0ZWQgdG8g
dGhlIHVzZSBvZiDigJxSb3V0ZXIgQ2xpZW504oCdLCBhbmQgYm90aCB0aGF0IHRlcm0sDQogICAg
ICAgICAgICAgICAgYW5kIOKAnG5vZGXigJ0gaW5kaWNhdGl2ZSB0aGF0IHNvbWUgY2xhcml0eSBp
cyBuZWVkZWQgaGVyZS4NCg0KICAgICAgICAgICAgICAgIEFsbCBhIHJvdXRlciBjYXJlcyBhYm91
dCBpcyDigJxhbiBhZGRyZXNz4oCdLiBJZiB0aGF0IGFkZHJlc3MgaXMgb2YgYSBuZXR3b3JrLCBv
cg0KICAgICAgICAgICAgICAgIGEgcm91dGVyLCBvciBhbiBpbnRlcmZhY2UgKGFuZCwgaWYgc2Fp
ZCBpbnRlcmZhY2UgaXMgaW5zdGFsbGVkIGluIGEgcm91dGVyIG9yIGEgaG9zdCkNCiAgICAgICAg
ICAgICAgICBkb2VzbuKAmXQgbWF0dGVyLg0KDQogICAgICAgICAgICAgICAgU28sIOKAnGFuIGFk
ZHJlc3PigJ0gaXMgc29tZXRoaW5nIHRoYXQgdGhlIHJvdXRpbmcgcHJvdG9jb2wgc2hvdWxkIGNh
cmUgYWJvdXQNCiAgICAgICAgICAgICAgICBmaW5kaW5nIHBhdGhzIHRvLiBXaGljaCBtZWFucyB0
aGF0IGVhY2ggYWRkcmVzcyB0aGF0IHNob3VsZCBiZSBtYWRlDQogICAgICAgICAgICAgICAgcmVh
Y2hhYmxlIGJ5IHRoZSByb3V0aW5nIHByb3RvY29sIHNob3VsZCBiZSBhZHZlcnRpc2VkIGJ5IChh
dCBsZWFzdCkgb25lIHJvdXRlcg0KICAgICAgICAgICAgICAgIGluIHRoZSBuZXR3b3JrLg0KDQog
ICAgICAgICAgICAgICAgT25lIHdheSBvZiBkb2luZyB0aGF0IHdvdWxkIGJlIHRvIHNpbXBseSB0
YWxrIGFib3V0IOKAnEF0dGFjaGVkIE5ldHdvcmtz4oCdIGFzDQogICAgICAgICAgICAgICAgaXMg
ZG9uZSBpbiBSRkM3MTgxLCB3aGVyZWluIGFuIGFkZHJlc3MgaW5jbHVkZWQgaW4gdGhlIOKAnEF0
dGFjaGVkIE5ldHdvcmsgU2V04oCdDQogICAgICAgICAgICAgICAgaXMgYWR2ZXJ0aXNlZCBieSBh
biBPTFNSdjIgcm91dGVyLi4uLmluIHRoaXMgY2FzZSwgdGhlIGVxdWl2YWxlbnQgd291bGQgYmUg
4oCcZm9yIGVhY2gNCiAgICAgICAgICAgICAgICBhZGRyZXNzIGluIHRoZSBBdHRhY2hlZCBOZXR3
b3JrIFNldCBvZiBhbiBBT0RWdjIgcm91dGVyIHRoZSByb3V0ZXIgTVVTVA0KICAgICAgICAgICAg
ICAgIHJlc3BvbmQgYXV0aG9yaXRhdGl2ZWx5IHRvIGEgUlJFUSwgYW5kIE1VU1QgbWFpbnRhaW4g
dGhlIGNvcnJlc3BvbmRpbmcgc2VxdWVuY2UgbnVtYmVy4oCdLg0KDQogICAgICAgICAgICAgICAg
VGhlIHRleHQsIGFzIGl0IGN1cnJlbnRseSBpcywgaXMgcmVhbGx5IGhhcmQgdG8gcmVhZCwgYW5k
IGEgcmUtZWRpdCBhbG9uZyB0aGVzZSBsaW5lcyB3b3VsZCBnbyBhIGxvbmcgd2F5LuKAnQ0KDQog
ICAgICAgIEkgbm90ZSB0aGF0IHRoZSB0ZXJtcyDigJxOb2Rl4oCdIGFuZCDigJxSb3V0ZXIgQ2xp
ZW504oCdIGFyZSBzdGlsbCB1c2VkLCBpbiB0aGVpciBvcmlnaW5hbCBmb3JtLA0KICAgICAgICBh
bmQgdGhhdCBvdGhlciB0aGFuIHNvbWUgc2xpZ2h0IHdvcmRzbWl0aGluZyB0aGlzIGNvbW1lbnQg
aGFzIG5vdCBiZWVuIGFkZHJlc3NlZCBpbiB0aGUgZG9jdW1lbnQuDQoNCiAgICAgICAgSSByZWl0
ZXJhdGUgdGhhdCB0aGUgbmVlZCB0byB1c2Ugcm91dGVyLCBob3N0LCBub2RlLCBhbmQgcm91dGVy
IGNsaWVudCBpbiBhbmQgYnkgaXRzZWxmIHNob3VsZA0KICAgICAgICBiZSBhbiBpbmRpY2F0b3Ig
dGhhdCB0aWdodGVuaW5nIHVwIG9mIHRlcm1pbm9sb2d5IGlzIHJlcXVpcmVkLg0KDQoNCiAgICAg
ICAgSSBtYWRlIHRoZSBmb2xsb3dpbmcgY29tbWVudCB0byBSb3V0YWJsZSBVbmljYXN0IElQIEFk
ZHJlc3M6DQoNCiAgICAgICAgICAgICAgICDigJxBcmUgdGhlcmUgYW55IHRlY2huaWNhbCByZWFz
b24gd2h5IG5vdCBzaW1wbHkgKmFueSogYWRkcmVzcyBjb3VsZCBiZQ0KICAgICAgICAgICAgICAg
ICBjb25zaWRlcmVkIGJ5IHRoZSByb3V0aW5nIHByb3RvY29sPw0KDQogICAgICAgICAgICAgICAg
IE15IHVuZGVyc3RhbmRpbmcsIGJ1dCBjb3JyZWN0IG1lIGlmIEkgYW0gd3JvbmcsIGlzIHRoYXQg
YWxsIHRoYXQgaXMgcmVxdWlyZWQgaXMNCiAgICAgICAgICAgICAgICAgdGhhdCBhbGwgaW50ZXJm
YWNlcyBpbiBhIGdpdmVuIEFPRFZ2MiByb3V0aW5nIGRvbWFpbiBoYXMgYW4gdW5pcXVlIGFkZHJl
c3MuDQoNCiAgICAgICAgICAgICAgICAgVGhhdCBzb21lIG9mIHRoZXNlIGFkZHJlc3NlcyAoYnkg
YW4gSVAgYWRkcmVzc2luZyBhcmNoaXRlY3R1cmUgZG9jdW1lbnQpDQogICAgICAgICAgICAgICAg
IGhhcyBzcGVjaWFsIHNlbWFudGljcyBhc3NvY2lhdGVkIChzdWNoIGFzIGFyZSBsaW5rIGxvY2Fs
cywgb3IgYXJlIGZvciBwcml2YXRlDQogICAgICAgICAgICAgICAgIHVzZSwgb3IgYXJlIGZvciBl
eGFtcGxlIHVzZSBvbmx5LCBvciBhcmUgZm9yIG11bHRpY2FzdCkgaXMgb3V0IG9mIHNjb3BlIGhl
cmU/DQoNCiAgICAgICAgSSBzZWUgbm90aGluZyBoYXMgY2hhbmdlZCBvbiB0aGUgYWJvdmUsIHNv
IGxldCBtZSBiZSBtb3JlIGV4cGxpY2l0OiB0aGUgcm91dGluZyBwcm90b2NvbCBpdHNlbGYNCiAg
ICAgICAgKHByb2JhYmx5KSBzaG91bGQgbm90IGNhcmUgYWJvdXQgd2hhdCBraW5kIG9mIGFkZHJl
c3NlcyBhcmUgZmlsbGVkIGludG8gaXQuIElzIGFuIDE5Mi4xNi4vMTYgYWRkcmVzcw0KICAgICAg
ICBhcHByb3ByaWF0ZT8gTm90IGFjcm9zcyB0aGUgaW50ZXJuZXQsIGJ1dCBpdCBtYXkgYmUgaW4g
c29tZWJvZHnigJlzIHByaXZhdGUgZGVwbG95bWVudHMuIFNob3VsZA0KICAgICAgICB0aGUgcm91
dGluZyBwcm90b2NvbCBiZSDigJxhZGRyZXNzIHBvbGljZeKAnSBhbmQgaXMgaW1wbGVtZW50YXRp
b24gb2YgYSDigJxJIHJlZnVzZSB0byByb3V0ZSB0aGVzZSBhZGRyZXNzZXPigKbigJ0NCiAgICAg
ICAgYSByZXF1aXJlbWVudCBmb3IgY2xhaW1pbmcgY29uZm9ybWFuY2U/IFN1Z2dlc3Qgc2ltcGx5
IHN0YXRpbmcgd2hhdCB0aGUgcmVxdWlyZW1lbnRzIGFyZSB1bmRlcg0KICAgICAgICB3aGljaCB0
aGUgcm91dGluZyBwcm90b2NvbCB3aWxsIHdvcmsg4oCUIGFuZCBsZWF2ZSDigJxhZGRyZXNzIGFz
c2lnbm1lbnQgcG9saXRpY3PigJ0gYXNpZGUuDQoNCiAgICAgICAgSSBhbHNvIGNvbnRpbnVlZDoN
Cg0KICAgICAgICAgICAgICAgICBOb3csIHdpdGggdGhhdCBiZWluZyBzYWlkIGFsc28sIHRoZSBX
RyB3YW50ZWQgdGhhdCBSRkM3MTgxIHN1cHBvcnRzIG5vdA0KICAgICAgICAgICAgICAgICBqdXN0
IG11bHRpcGxlIGludGVyZmFjZXMsIGJ1dCBhbHNvIHRoZSBzYW1lIGFkZHJlc3MgdXNlZCBvbiBt
dWx0aXBsZSBpbnRlcmZhY2VzDQogICAgICAgICAgICAgICAgIG9mIHRoZSBzYW1lIHJvdXRlci4g
VGhlcmUgd2VyZSBnb29kIHJlYXNvbnMgZm9yIHRoYXQsIGFuZCB3aGlsZSBpdCB3YXMgbm90IHRy
aXZpYWwNCiAgICAgICAgICAgICAgICAgdG8gaW1wbGVtZW50LCBpdCB0dXJuZWQgb3V0IHRvIGJl
IHRoZSByaWdodCB0aGluZyB0byBzdXBwb3J0LiBJZiB0aGVyZSBhcmUgdGVjaG5pY2FsDQogICAg
ICAgICAgICAgICAgIHJlYXNvbnMgd2h5IHRoaXMgaXMgbm90IHN1cHBvcnRlZCBpbiBBT0RWdjIg
KGZvciBleGFtcGxlLCBpZiB0aGlzIGNhbm5vdCBiZQ0KICAgICAgICAgICAgICAgICBtYWRlIHdv
cmsgYmVjYXVzZSBvZiA8cmVhc29uPikgdGhlbiB0aGF0IHNob3VsZCBiZSBjYWxsZWQgb3V0IGlu
IHRoZQ0KICAgICAgICAgICAgICAgICBhcHBsaWNhYmlsaXR5IHN0YXRlbWVudCBhbHNvPw0KDQog
ICAgICAgICAgICAgICAgQ29udmVyc2VseSwgaWYgaXQgaXMgcG9zc2libGUgaW4gQU9EVnYyLCB0
aGVuIEkgZG8gbm90IGJlbGlldmUgdGhhdCBpdCBpcyBjbGVhcmx5DQogICAgICAgICAgICAgICAg
c3BlY2lmaWVkIGhvdyAoYXQgbGVhc3QsIGluIHRoZSDigJxuYWl2ZeKAnSBvbiBwYXBlciBleGFt
cGxlcyBJIGRyZXcgdXAsIHNvbWV0aGluZw0KICAgICAgICAgICAgICAgIGVuZGVkIHVwIG5vdCB3
b3JraW5nKS4gU28gZWl0aGVyIHRoZSBwcm90b2NvbCBhcy1pcyBkb2VzIG5vdCBzdXBwb3J0IGl0
IChidXQNCiAgICAgICAgICAgICAgICBjb3VsZCBiZSBtYWRlIHRvPykgb3IgaXQgaXMgc3VwcG9y
dGVkIChidXQganVzdCBuZWVkIHRvIGJlIHNwZWxsZWQgb3V0KSwgb3IgaXMNCiAgICAgICAgICAg
ICAgICBub3QgcG9zc2libGUgKGFuZCBuZWVkIHRvIGJlIGRpc2NsYWltZWQgaW4gdGhlIGFwcGxp
Y2FiaWxpdHkgc3RhdGVtZW50KS4NCg0KICAgICAgICAgICAgICAgIFN0YW4gUmF0bGlmZiB3YXMg
YSBkcml2aW5nIGZvcmNlIGluIGhvbGRpbmcgdGhlIFdH4oCZcyBjb2xsZWN0aXZlIGZlZXQgdG8g
dGhlIGZpcmUNCiAgICAgICAgICAgICAgICBpbiBnZXR0aW5nIHRoaXMgc3VwcG9ydCBpbmNsdWRl
ZCBpbiBSRkM3MTgxLCBhbmQgd291bGQgbGlrZWx5IGJlIHRoZSByaWdodA0KICAgICAgICAgICAg
ICAgIHBlcnNvbiB0byBjb25zdWx0IG9uIHRoaXMgbWF0dGVyPw0KDQogICAgICAgIEkgYWN0dWFs
bHkgaGF2ZSBub3Qgc2VlbiBjaGFuZ2VzLCBvciBjb21tZW50cywgb24gdGhpcy4gSW4gT0xTUnYy
LCB0aGUgV0cgd2FzIG1ha2luZyBpdA0KICAgICAgICBhIHN0cm9uZyByZXF1aXJlbWVudCB0aGF0
IGl0IHNob3VsZCBiZSBwb3NzaWJsZSB0byB1c2UgdGhlIHNhbWUgSVAgYWRkcmVzcyBvbiBkaWZm
ZXJlbnQNCiAgICAgICAgaW50ZXJmYWNlcyBvZiBhIHJvdXRlci4gSXQgd2FzIHNvbWV3aGF0IHRl
ZGlvdXMgdG8gZGVzaWduIGFyb3VuZCwgYnV0IGl0IHdhcyB3b3JrZWQgb3V0LCBhbmQNCiAgICAg
ICAgdGhlIGNvbmRpdGlvbnMgdW5kZXIgd2hpY2ggdGhhdCB3YXMgcG9zc2libGUgd2VyZSBkZWZp
bmVkIGFuZCBkb2N1bWVudGVkLg0KDQogICAgICAgIEkgd291bGQgbGlrZSB0byBzZWUgdGhlIHNh
bWUgZG9uZSBmb3IgdGhpcyBwcm90b2NvbC4NCg0KICAgICAgICBJIGFsc28gbm90ZSB0aGF0IHRo
aXMgaXMgbm90IHVucmVsYXRlZCB0byBSRkM2NjIxLWRpc2N1c3Npb25zLiBGb3IgZXhhbXBsZSwg
d2hlbiBzZWxlY3RpbmcNCiAgICAgICAgUy1NUFJzIG9uIGEgbXVsdGktaW50ZXJmYWNlIGFuZCBt
dWx0aS1hZGRyZXNzLXBlci1pbnRlcmZhY2Ugcm91dGVyLCBjYXJlIG11c3QgYmUgdGFrZW4NCiAg
ICAgICAgbGVhc3QgdGhpbmdzIHdvbuKAmXQgd29yay4gU28sIGlmIChhbmQgdGhpcyBsaW5rcyBi
YWNrIHRvIHByZXZpb3VzIG1haWxzKSBSRkM2NjIxIGlzIGENCiAgICAgICAgcmVxdWlyZW1lbnQg
b3IgZGVzaXJlIGZvciB0aGlzIHByb3RvY29sLCB0aGVuIHRoZXJlIGFyZSBzb21lIGNvbnNpZGVy
YXRpb25zIHJlcXVpcmVkIGhlcmUuDQoNCiAgICAgICAgSSBzZWUgdGhhdCB0aGUgZGVmaW5pdGlv
biBvZiDigJxSb3V0ZXIgQ2xpZW504oCdIGhhcyBjaGFuZ2VkIHRvIGJlDQoNCiAgICAgICAgICAg
ICAgICDigJxBbiBhZGRyZXNzIG9yIGFkZHJlc3MgcmFuZ2XigKZ0aGUgQU9EVnYyIHJvdXRlcuKA
mXMgaW50ZXJmYWNlIGFkZHJlc3Nlcw0KICAgICAgICAgICAgICAgICBhcmUgYWxzbyBjb25maWd1
cmVkIGFzIHJvdXRlciBjbGllbnRz4oCdDQoNCiAgICAgICAgQmV0dGVyIHRoYW4gYmVmb3JlLCBi
dXQgc3RpbGwgbWlzc2luZyB0aGUgdGFyZ2V0LiBUaGUgdGVybSDigJxSb3V0ZXIgQ2xpZW504oCd
IGlzLCBhcyBJIGluZGljYXRlZA0KICAgICAgICBudW1lcm91cyB0aW1lcyBiZWZvcmUsIG9kZC4N
Cg0KICAgICAgICBCdXQgdGhlIHNlY29uZCBwYXJ0IG9mIHRoZSBzZW50ZW5jZSwgZG9lcyB0aGF0
IG1lYW4gKHdoYXQgaXQgc2F5cykgdGhhdCB0aGUgaW50ZXJmYWNlcw0KICAgICAgICBtdXN0IGJl
IGNvbmZpZ3VyZWQgc3BlY2lhbGx5LCBzbyBhcyB0byBiZSBhYmxlIHRvIGJlIOKAnHJvdXRlciBj
bGllbnRz4oCdPyBUaGF0IGNhbuKAmXQgYmUgdHJ1ZS4NCg0KICAgICAgICBXaGF0IHlvdSBsaWtl
bHkgbWVhbiBpczoNCg0KICAgICAgICAgICAgICAgIOKAnEFuIEFPRFZ2MiByb3V0ZXIgaXMgY29u
ZmlndXJlZCBzbyBhcyB0byBjb25zaWRlciBpdHMgb3duIGludGVyZmFjZXMgYXMgcGFydCBvZg0K
ICAgICAgICAgICAgICAgICB0aGUgbG9jYWxseSBhdHRhY2hlZCBuZXR3b3JrIHNldOKAnSA/DQoN
CiAgICAgICAgWW91IGNvbmZpZ3VyZSB0aGUgcm91dGVyLCByaWdodD8gTm8gc3BlY2lhbCDigJxp
bnRlcmZhY2UgY29uZmlndXJhdGlvbiBwcm9wZXJ0aWVz4oCdIGFyZSByZXF1aXJlZA0KICAgICAg
ICBmb3IgYW4gaW50ZXJmYWNlIHRvIGJlIGFubm91bmNhYmxlIGJ5ICBhbiBBT0RWdjIgcm91dGVy
Pw0KICAgICAgICAoQW5kLCBnZXR0aW5nIHJpZCBvZiBub2RlIHdvdWxkIGFjdHVhbGx5IG1ha2Ug
dGhlIGRlZmluaXRpb24gc2hvcnRlciBhbmQgbmljZXIpDQoNCiAgICAgICAgTm93LCBzbmlwcGlu
ZyBvdXQgZnJvbSB0aGUgYXBwbGljYWJpbGl0eSBzdGF0ZW1lbnQ6DQoNCiAgICAgICAgICAgICAg
ICAiTXVsdGktaG9taW5nIG9mIGFuIElQIGFkZHJlc3MgaXMgbm90IHN1cHBvcnRlZCBieSBBT0RW
djIsIGFuZCB0aGVyZWZvcmUgYQ0KICAgICAgICAgICAgICAgICAgUm91dGVyIENsaWVudCwgaS5l
LiBhbiBJUCBBZGRyZXNzLCAg4oCmICINCg0KICAgICAgICDigKZldmlkZW5jZSB0byB0aGVyZSBi
ZWluZyBzb21lIHJlZHVuZGFudCB0ZXJtaW5vbG9neSBoZXJlIHRvIHdlZWQgYXdheS4NCg0KICAg
ICAgICBUaGUgYmVsb3cgaXMgYSBsaXR0bGUgYml0IG9mIGEgbWV0YS1jb21tZW50LCBJIGFtIG5v
dCBxdWl0ZSBzdXJlIHdoYXQgSSB0aGluayBoZXJlLg0KICAgICAgICBUaGUgZGVmaW5pdGlvbnMg
Zm9yIFRhcmdldCBOb2RlIGFuZCBzdWNoIHdlcmUgY29uZnVzaW5nIGJlZm9yZS4gVGhleSBzdGls
bCBhcmUsIHNvbWV3aGF0Lg0KDQogICAgICAgIEkgdGhpbmsgdGhhdCBpdCBtYXkgYmUgYmVjYXVz
ZSB0aGUgZGVmaW5pdGlvbnMgbm93IHVzZWQgYXJlIHNpbXBseSBjb3B5LXBhc3RlZCBvdXQgZnJv
bSB0aGUNCiAgICAgICAgdGFibGVzIGluIHRoZSBwcmV2aW91cyB2ZXJzaW9uLCBmb3IgZXhhbXBs
ZToNCg0KICAgICAgICAgICAgICAgIEFuIEFPRFZ2MiBEYXRhIEVsZW1lbnQgY29udGFpbmluZyB0
aGUgZGVzdGluYXRpb24gYWRkcmVzcyBvZiB0aGUNCiAgICAgICAgICAgICAgICBJUCBwYWNrZXQg
dHJpZ2dlcmluZyByb3V0ZSBkaXNjb3ZlcnkuDQoNCiAgICAgICAgT0ssIEkgY2FuIHRyYWNlIGJh
Y2sgYW5kIHNlZSB0aGF0IGEgRGF0YSBFbGVtZW50IGlzIHNvbWV0aGluZyB0aGF0IGV4aXN0cyBp
bnNpZGUgYQ0KICAgICAgICBwcm90b2NvbCBtZXNzYWdlLiBUbyBtZSwgaG93ZXZlciwgdGhhdOKA
mXMgbm90IHJlYWxseSBnZW5lcmFsIHRlcm1pbm9sb2d5IGFzIHN1Y2gsIGJ1dA0KICAgICAgICBw
YXJ0IG9mIHRoZSBzcGVjaWZpY2F0aW9uIG9mIGEgcGFja2V0IGZvcm1hdCAtIG9yIHJhdGhlciwg
aXQgaXMgdGhlIG5vdGF0aW9uIHRoYXQgeW91IHVzZQ0KICAgICAgICB3aGVuIGRlc2NyaWJpbmcg
YW4gYWxnb3JpdGhtLiBCeSB0aGUgd2F5LCB3aHkgYXJlIHNvbWUgbm90YXRpb25zIGluIENhbWVs
Q2FzZQ0KICAgICAgICB3aGVyZWFzIG90aGVycyBoYXZlIGEgc3BhY2UgaW4gdGhlbSwgZS5nLiDi
gJxUYXJnZXQgTm9kZeKAnSBhbmQg4oCcVGFyZ01ldHJpY+KAnSwgYm90aCBvZiB3aGljaA0KICAg
ICAgICBhcmUgRGF0YSBFbGVtZW50cz8gV291bGQgYmUgZ29vZCB3aXRoIGEgY29uc2lzdGVudCBh
cHByb2FjaCBoZXJlLg0KDQogICAgICAgIEkgKnRoaW5rKiB0aGF0IGl0IHdvdWxkIGJlIGJldHRl
ciB0byB0YWtlIGFsbCB0aG9zZSDigJxEYXRhIEVsZW1lbnTigJ0gYml0cyBhbmQgbW92ZSB0byBh
IHNlcGFyYXRlDQogICAgICAgIHNlY3Rpb24gKG9yIHN1YnNlY3Rpb24pIHRvIHRoZSB0ZXJtaW5v
bG9neSwgYW5kIHRoZW4ga2VlcCBhbGwgdGhlIOKAnG90aGVyIHN0dWZm4oCdIChOZWlnaGJvciwg
4oCmKQ0KICAgICAgICBpbiBpdHMgb3duIHNlY3Rpb24uDQoNCiAgICAgICAgSeKAmW0gYSBncmVh
dCBmYW4gb2YgY2FsbGluZyB0aGlzIHNlY3Rpb24g4oCcVGVybWlub2xvZ3kgYW5kIE5vdGF0aW9u
4oCdIGFuZCB0aGVuIGhhdmluZyB0d28NCiAgICAgICAgc3Vic2VjdGlvbnMsIG9uZSB3aGljaCBp
cyDigJxUZXJtaW5vbG9neeKAnSBhbmQgb25lIHdoaWNoIGlzIOKAnE5vdGF0aW9u4oCdLCB3aXRo
IHRoZQ0KICAgICAgICBUYXJnTWV0cmljIGFuZCBUYXJnZXQgTm9kZSBiZWluZyBmaXJtbHkgaW4g
dGhlIGxhdHRlci4NCg0KICAgICAgICBJIG1hZGUgYSBjb21tZW50Og0KICAgICAgICAgICAgICAg
ICJTZWNvbmQsIHNob3VsZCDigJx2YWxpZCByb3V0ZeKAnSBub3QgYmUgcXVhbGlmaWVkIGJ5IOKA
nHRvIGEgc3BlY2lmaWMgYWRkcmVzc+KAnT/igJ0NCg0KICAgICAgICBXaGljaCB3YXMgbm90IGFk
ZHJlc3NlZC4NCg0KICAgICAgICBJIGFsc28gbWFkZSBhIGNvbW1lbnQgb24gIlVucmVhY2hhYmxl
IEFkZHJlc3PigJ0gLSBJIGFtIGdsYWQgSSBkaWQsIGJlY2F1c2UgSSBhcHBhcmVudGx5DQogICAg
ICAgIGhhZCBhIGRpZmZlcmVudCB1bmRlcnN0YW5kaW5nIHRoYW4gd2hhdCB3YXMgaW50ZW5kZWQu
IEkgbm93IHNlZSB0aGF0IGFuIFVucmVhY2hhYmxlIEFkZHJlc3MNCiAgICAgICAgYnkgZGVmaW5p
dGlvbiBpcyBhbiBhZGRyZXNzIGxpc3RlZCBpbiBhIFJFUlIgbWVzc2FnZSwgYW5kIG5vdCB0aGUg
c2FtZSBhcyBhbiBhZGRyZXNzIHRvDQogICAgICAgIHdoaWNoIG5vIHJvdXRlIGhhcyB5ZXQgIGJl
ZW4gZGlzY292ZXJlZD8gSWYgeWVzLCB0aGVuIHBsZWFzZSB1c2UgYSBkaWZmZXJlbnQgdGVybSwg
c3VjaCBhcw0KICAgICAgICDigJxGb3JtZXJseVJlYWNoYWJsZUFkZHJlc3PigJ0gb3Igc29tZXRo
aW5nIG9mIHRoZSBzb3J0Pw0KDQpBcHBsaWNhYmlsaXR5IHN0YXRlbWVudA0KDQogICAgICAgIEZp
cnN0LCBJIHdvdWxkIGxpa2UgdG8gcmVjb2duaXplIHRoZSBlZmZvcnRzIG1hZGUgdG8gaW1wcm92
ZSB0aGlzIHNpbmNlIGxhc3QgcmV2aWV3LiBUaGFua3MNCg0KICAgICAgICBTZWNvbmQsIHRoZSBk
b2N1bWVudCBzdGF0ZXM6DQoNCiAgICAgICAgICAgICAgICAiQU9EVnYyIHN1cHBvcnRzIHJvdXRl
cnMgd2l0aCBtdWx0aXBsZSBpbnRlcmZhY2VzLCBhcyBsb25nIGFzIGVhY2gNCiAgICAgICAgICAg
ICAgICAgICBpbnRlcmZhY2UgY29uZmlndXJlZCBmb3IgQU9EVnYyIGhhcyBhIHVuaWNhc3QgSVAg
YWRkcmVzcy4gIEEgcm91dGVyDQogICAgICAgICAgICAgICAgICAgbWF5IHVzZSB0aGUgc2FtZSBJ
UCBhZGRyZXNzIG9uIG11bHRpcGxlIGludGVyZmFjZXMuICBBZGRyZXNzDQogICAgICAgICAgICAg
ICAgICAgYXNzaWdubWVudCBwcm9jZWR1cmVzIGFyZSBvdXQgb2Ygc2NvcGUgZm9yIEFPRFZ2Mi7i
gJ0NCg0KICAgICAgICBJcyB0aGF0IHRydWU/IEdyYW50ZWQsIEkgaGF2ZSBub3Qgd29ya2VkIHRo
aXMgdGhyb3VnaCBpbiBkZXRhaWwsIGJ1dCBJIGNhbiBwcmVzZW50IGEgY291bnRlci1leGFtcGxl
Og0KICAgICAgICB0aGUgdXNlIG9mIFJGQzY2MjEgbWVhbnMgdGhhdCB0aGVyZSBjZXJ0YWlubHkg
YXJlIHNvbWUgY29uc3RyYWludHMgdGhhdCBtdXN0IGJlIHJlc3BlY3RlZCBsZWFzdA0KICAgICAg
ICB2YXJpb3VzIGZsb29kaW5nIG9wdGltaXphdGlvbnMgbWF5IG5vdCB3b3JrLg0KDQogICAgICAg
IFNlY29uZGx5LCBpZiB0aGUgbXVsdGlwbGUtaW50ZXJmYWNlcy13aXRoLXNhbWUtYWRkcmVzcyBh
cmUgb24gdGhlIHNhbWUgTDIsIGFuZCB0aGlzIGlzIHdoYXQgSQ0KICAgICAgICBoYXZlIG5vdCB3
b3JrZWQgdGhyb3VnaCwgYXJlIHRoZXJlIGFueSBzaXR1YXRpb25zIHRoYXQgd2lsbCBub3Qgd29y
az8NCg0KICAgICAgICBUaGUgaW1tZWRpYXRlbHkgcHJldmlvdXMgdmVyc2lvbiBvZiB0aGlzIHNw
ZWNpZmljYXRpb24gcmVhZDoNCg0KICAgICAgICAgICAgICAgICJBT0RWdjIgc3VwcG9ydHMgcm91
dGVycyB3aXRoIG11bHRpcGxlIGludGVyZmFjZXMsIGFzIGxvbmcgYXMgZWFjaA0KICAgICAgICAg
ICAgICAgICAgIGludGVyZmFjZSBjb25maWd1cmVkIGZvciBBT0RWdjIgaGFzIGl0cyBvd24gdW5p
Y2FzdCByb3V0YWJsZSBJUCBhZGRyZXNzIg0KDQogICAgICAgIFNvIHdoYXQgY2hhbmdlZCB0aGF0
IG1lYW5zIHRoYXQgZWFjaCBpbnRlcmZhY2Ugbm8gbG9uZ2VyIG5lZWRzIGl0cyAqb3duKiB1bmlj
YXN0IGFkZHJlc3M/DQoNCiAgICAgICAgSSBwb2ludGVkIG91dCB0byB0aGUgQXBwbGljYWJpbGl0
eSBTdGF0ZW1lbnQ6DQoNCiAgICAgICAgICAgICAgICBJIHRoaW5rIHRoYXQgYXBwZW5kaXggQiBu
ZWVkcyB0byBiZSByZW1vdmVkLiBFc3NlbnRpYWxseSwgaXQgbWFrZXMgY2xhaW1zIHRoYXQgaXQg
aXMNCiAgICAgICAgICAgICAgICBwb3NzaWJsZSB0byBkbyBtdWx0aS1ob21pbmcg4oCUIGJ1dCBu
ZWl0aGVyIHNwZWNpZmllcyBob3cgaXQgaXMgZG9uZSwgbm9yIGdpdmVzDQogICAgICAgICAgICAg
ICAgcG9pbnRlcnMgdG8gZG9jdW1lbnRzIHRoYXQganVzdGlmeSB0aGUgY2xhaW0uDQoNCiAgICAg
ICAgICAgICAgICBBT0RWdjIgZG9lcyBub3Qgc3VwcG9ydCBtdWx0aS1ob21pbmcg4oCUIHRoYXTi
gJlzIGNsZWFyLCBhbmQgaXQgaXMgZmluZSB0aGF0IGl0IGlzDQogICAgICAgICAgICAgICAgY2Fs
bGVkIG91dCBoZXJlLiBUaGFuayB5b3UgZm9yIHRoYXQuDQoNCiAgICAgICAgICAgICAgICBOb3cs
IHdpdGggdGhhdCBiZWluZyBzYWlkLCBJIGFtIHRvcm4gYmV0d2VlbiBiZWluZyBzYXRpc2ZpZWQg
dGhhdCBpdCBpcyBjYWxsZWQgb3V0IG9uDQogICAgICAgICAgICAgICAgb25lIGhhbmQsIGFuZCB3
YW50aW5nIHRvIGhhdmUg4oCcbXVsdGkgaG9taW5n4oCdIG9uIHRoZSBvdGhlciBoYW5kLiBSRkM3
MTgxIHN1cHBvcnRzDQogICAgICAgICAgICAgICAgbXVsdGktaG9taW5nLCBGV0lXLg0KDQogICAg
ICAgICAgICAgICAgSSBiZWxpZXZlIHRoYXQgdGhpcyBhbHNvIHdvdWxkIG1lcml0IHNvbWUgZXhw
bGljaXQgZGlzY3Vzc2lvbiBieSB0aGUgV0csIGluIG9yZGVyIHRvDQogICAgICAgICAgICAgICAg
dW5kZXJzdGFuZCBpZiB0aGlzIGRlc2lnbiBkZWNpc2lvbiBpcyBhY2NlcHRhYmxlPw0KDQogICAg
ICAgIEkgc2VlIHRoYXQgQXBwZW5kaXggQiBzdGlsbCBpcyBpbiB0aGUgZG9jdW1lbnQsIGFuZCBJ
IGRvIG5vdCByZWNhbGwgaGF2aW5nIHNlZW4gdGhpcyBkaXNjdXNzZWQNCiAgICAgICAgb24gdGhl
IG1haWxpbmcgbGlzdC4gU2ltcGx5IHJlbW92aW5nIHRoZSByZWZlcmVuY2UgZnJvbSB0aGUgQXBw
bGljYWJpbGl0eSBTdGF0ZW1lbnQgdG8gQXBwZW5kaXggQg0KICAgICAgICBkb2VzIG5vdCBhZGRy
ZXNzIHRoZSBpc3N1ZSB0aGF0IEkgcmFpc2VkIGluIG15IHByZXZpb3VzIHJldmlldy4NCg0KVG8g
NC4xLCBJIG1hZGUgdGhlIGZvbGxvd2luZyBjb21tZW50Og0KDQogICAgICAgICJJcyB0aGlzIGEg
c2hvdWxkLCBvciBhIFNIT1VMRD8gSWYgdGhlIGxhdHRlciwgc2hvdWxkIGl0IGJlIGEgTVVTVD8N
Cg0KICAgICAgICAgIEluIGdlbmVyYWwsIHRoZXJlIGFyZSBhIGxvdCBvZiBzdWNoIOKAnG1heWJl
IG5vcm1hdGl2ZSBsYW5ndWFnZeKAnSB0aHJvdWdoIHRoZQ0KICAgICAgICAgZG9jdW1lbnQsIGFu
ZCBJIHdvdWxkIG11Y2ggbGlrZSB0byBzZWUgYW4gZWRpdG9yaWFsIHBhc3Mg4oCUIGVzc2VudGlh
bGx5IGFsbA0KICAgICAgICAgbWF5L3Nob3VsZC8gbXVzdCBhbmQgZnJpZW5kcyBjYXJlZnVsbHkg
ZXZhbHVhdGVkIGFzIGlmIHRoZXkgc2hvdWxkIGJlY29tZQ0KICAgICAgICAgMjExOS10ZXJtcywg
YW5kIC4uLiBtb3JlIGltcG9ydGFudGx5IChpdCBoYXMgYmVlbiBjYWxsZWQgb3V0IGJlZm9yZSwg
ZndpdykNCiAgICAgICAgIHF1aXRlIGEgYml0IG9mIHNob3VsZC9TSE9VTEQgd2hpY2ggb3VnaHQg
dG8gYmUgdHJhbnNmb3JtZWQgaW50byBNVVNULg0KDQogICAgICAgIEdlbmVyYWxseSwgYWltaW5n
IGZvciBhIHZlcnkgYSBsb3cgbnVtYmVyIG9mIFNIT1VMRCBpcyBhIGdvb2QgZGVzaWduIG1ldHJp
YyBmb3IgYSBkb2N1bWVudOKAnQ0KDQpBc2lkZSBmcm9tIHRoZSBnZW5lcmFsIGNvbW1lbnQgb24g
MjExOS1sYW5ndWFnZSwgd2h5IGlzIHRoaXMgYSBTSE9VTEQ/DQoNClRvIDQuMiwgSSBtYWRlIHRo
ZSBmb2xsb3dpbmcgY29tbWVudDoNCg0KICAgICAgICBBcyBpbmRpY2F0ZWQgZWFybGllciwgSSBi
ZWxpZXZlIHRoYXQgdGhlIHRlcm0g4oCcUm91dGVyIENsaWVudOKAnSBpcyBpbGwgY2hvc2VuLg0K
ICAgICAgICBJIGJlbGlldmUgdGhhdCBpdCBpcyBtb3JlIGFwcHJvcHJpYXRlbHkgYW4g4oCcQXR0
YWNoZWQgTmV0d29yayBTZXTigJ0gc2luY2Ug4oCUDQogICAgICAgIGFzIGluZGljYXRlZCBwcmV2
aW91c2x5IOKAlCB0aGUgdGVybSDigJxSb3V0ZXIgQ2xpZW504oCdIGlzIGFtYmlndW91cy4gSSBh
bSBwbGVhc2VkDQogICAgICAgIHRvIHNlZSwgdGhvdWdoLCB0aGF0IHRoaXMg4oCcUm91dGVyIENs
aWVudCBMaXN04oCdIGluIHJlYWxpdHkgaXMgYW4g4oCcQXR0YWNoZWQgTmV0d29yayBTZXTigJ0N
CiAgICAgICAgYW5kIHNvIHRoYXQgY2hhbmdlIHNob3VsZCBiZSAocmVsYXRpdmVseSkgZWFzeS4N
Cg0KVGhlIGFib3ZlIGNvbW1lbnQgc3RpbGwgaXMgYXBwbGljYWJsZSB0byB0aGlzIHJldmlzaW9u
LA0KDQpUbyA0LjIsIEkgbWFkZSB0aGUgZm9sbG93aW5nIGNvbW1lbnQ6DQoNCiAgICAgICAgQWxz
bywgSSByZWNvbW1lbmQgdG8gbm90IHNheSDigJxzdWJuZXTigJ0g4oCUIGhvdyBhYm91dCByZXBo
cmFzaW5nIHRvIOKAnElmIGEgcHJlZml4DQogICAgICAgIGlzIGluY2x1ZGVkIGluIHRoZSBhdHRh
Y2hlZCBuZXR3b3JrIHNldCBvZiBhbiBBT0RWdjIgcm91dGVyLCB0aGVuIHRoYXQgQU9EVnYyDQog
ICAgICAgIHJvdXRlciBNVVNUIHByb3ZpZGUgY29ubmVjdGl2aXR5IGZvciwgaS5lLiBhbnN3ZXIg
dG8gUlJFUXMgYW5kIG1haW50YWluDQogICAgICAgIHNlcXVlbmNlIG51bWJlcnMgZm9yLCBhbGwg
YWRkcmVzc2VzIGZyb20gd2l0aGluIHRoYXQgcHJlZml4LuKAnQ0KDQpJIG5vdGUgdGhhdCB3aGls
ZSB0aGUgdGVybSBoYXMgYmVlbiByZW1vdmVkIGZyb20gc2VjdGlvbiA0LCB0aGVyZeKAmXJlIDQg
bGluZ2VyaW5nIGluc3RhbmNlcyBvZiB0aGlzIHRlcm0gaW4gdGhlIGRvY3VtZW50LCB0aGF0IGNv
dWxkIGVhc2lseSBiZSByZW1vdmVkLg0KDQpJIEFsc28gbWFkZSBhIGNvbW1lbnQgYWJvdXQgQXBw
ZW5kaXggQiBpbiBteSBwcmV2aW91cyByZXZpZXcsIHdoaWNoIGlzIHJlZmVyZW5jZWQgaGVyZS4g
VGhhdCBjb21tZW50IHN0aWxsIGFwcGxpZXMuDQoNClRvIFNlY3Rpb24gNC4zLCBJIG5vdGljZWQ6
DQoNCiAgICAgICAgRG9lcyBzZWN0aW9uIDYuMiBkZXNjcmliZSBob3cgdG8gbW9uaXRvciBhbiBl
c3RhYmxpc2hlZCBhZGphY2VuY3kNCiAgICAgICAgb25seSwgb3IgaG93IHRvIGRpc2NvdmVyIG5l
aWdoYm91cmluZyBBT0RWdjIgcm91dGVycz8gTG9va2luZyBpbiA2LjIsIEkgc2VlDQoNCiAgICAg
ICAgICAgICAgICDigJxOb3QgZXZlcnkgcGFpciBvZiBuZWlnaGJvcmluZyByb3V0ZXJzIHdpbGwg
bmVjZXNzYXJpbHkgZm9ybSBhbiBhZGphY2VuY3ks4oCdIOKAlA0KICAgICAgICAgICAgICAgICBz
byBpdCBsaWtlbHkgaXNu4oCZdCA2LjIgdGhhdCB0ZWxscyBtZSBob3cgdG8gbWFpbnRhaW4gdGhp
cyB0YWJsZT8NCg0KICAgICAgICBJbiBzaG9ydCwg4oCcQSBuZWlnaGJvdXIgdGFibGUgTVVTVCBi
ZSBtYWludGFpbmVk4oCdIOKAlCB3aGVyZSBjYW4gSSBmaW5kIGluZm9ybWF0aW9uIG9uIGhvdyB0
byBkbyB0aGlzPw0KDQogICAgICAgIFNlY3Rpb24gNi4yIHN0YXRlczoNCg0KICAgICAgICAgICAg
ICAgIOKAnFRoZSBkZWZhdWx0IGFwcHJvYWNoIGZvciBtb25pdG9yaW5nIGJpZGlyZWN0aW9uYWwg
Y29ubmVjdGl2aXR5IHRvIHRoZSBuZXh0IGhvcCB0b3dhcmQNCiAgICAgICAgICAgICAgICAgT3Jp
Z0FkZHIgaXMgdG8gcmVxdWVzdCBhY2tub3dsZWRnZW1lbnQgb2YgUm91dGUgUmVwbHkgbWVzc2Fn
ZXMu4oCdDQoNCiAgICAgICAgICAgICAgICBUaGF0IGNlcnRhaW5seSB3aWxsIHRlbGwgbWUgaWYg
YSBsaW5rIG92ZXIgd2hpY2ggYW4gUlJFUCBpcyBzZW50IGlzIGJpLWRpcmVjdGlvbmFsLA0KICAg
ICAgICAgICAgICAgIGJ1dCB3aWxsIG5vdCBtYWludGFpbiBhIOKAnG5laWdoYm9yIHRhYmxl4oCd
Lg0KDQogICAgICAgIFNvIGhvdyBpcyB0aGlzIGRvbmU/IE9yLCBpcyB0aGUg4oCcTmVpZ2hib3Ig
VGFibGXigJ0gbm90IHN1cHBvc2VkIHRvIGNvbnRhaW4gdGhlDQogICAgICAgIGNvbXBsZXRlIHNl
dCBvZiBuZWlnaGJvdXJzPyBXaGF0IGluZm9ybWF0aW9uIOKAnC4uLk1VU1QgYmUgbWFpbnRhaW5l
ZOKAnSB0aGVuLCBpbiB0aGlzIHRhYmxlPw0KDQogICAgICAgIFRoaXMgaXMgdmVyeSB1bmNsZWFy
LCBJIHdvdWxkIG5vdCBrbm93IGhvdyB0byBpbXBsZW1lbnQgYSBtZWNoYW5pc20gdGhhdCBwb3B1
bGF0ZXMgdGhpcw0KICAgICAgICDigJxOZWlnaGJvciBUYWJsZeKAnSB3aXRoIHRoZSBuZWVkZWQg
aW5mb3JtYXRpb24gaGVyZS4NCg0KSSBzZWUgbm8gKHJlbGV2YW50KSBjaGFuZ2VzIHRvIDYuMiBu
b3IgdG8gNC4zIHNvIEkgYXNzdW1lIHRoYXQgdGhpcyBjb21tZW50IGhhcyBub3QgYmVlbiBhZGRy
ZXNzZWQNCg0KSSBhbSB0aHJvd2luZyB0aGlzIGluIGhlcmUsIGFzIEkgYW0gc3VyZSB0aGF0IEkg
Y29tbWVudGVkIG9uIHRoYXQgaW4gdGhlIHByZXZpb3VzIHJldmlldywgYnV0IEkgZG8gbm90IHNl
ZSB0aGF0IGFkZHJlc3NlZDogaXMgQXBwZW5kaXggQyBub3JtYXRpdmUsIG9yIG5vdD8gSXQgcmVw
cmVzZW50cyDigJwgYSBzZWNvbmQgc3BlY2lmaWNhdGlvbiBvZiB0aGUgcHJvdG9jb2wsIGluIGEg
ZGlmZmVyZW50IGxhbmd1YWdl4oCdIGZyb20gdGhlIG1haW4gcGFydCBvZiB0aGUgc3BlY2lmaWNh
dGlvbi4gSSBoYXZlIG5vdCB3YWxrZWQgdGhyb3VnaCBhbmQgbWFkZSAyMDAlIHN1cmUgdGhhdCBi
b3RoIGFyZSBwZXJmZWN0bHkgYWxpZ25lZCBhbmQgdGhhdCB0aGVyZSBhcmUgbm8gYW1iaWd1aXRp
ZXMsIGJ1dCBoYXZpbmcgdHdvIGRpZmZlcmVudCBzcGVjaWZpY2F0aW9ucyBvZiBhIHByb3RvY29s
IGlzIGEgcmVjaXBlIGZvciBkaXNhc3Rlci4gIFBsZWFzZSBlaXRoZXIgbWFrZSAyMDAwJSBzdXJl
IHRoYXQgdGhleSBhcmUgc3BlY2lmeWluZyB0aGUgc2FtZSB0aGluZyB3aXRob3V0IGFtYmlndWl0
aWVzLCBvciByZW1vdmUgb25lLg0KDQpUbyBzZWN0aW9uIDQuNCwgSSB3cm90ZToNCg0KICAgICAg
ICAid291bGQgbGlrZSB0byBuaXQtcGljayB0aGF0OiB0aGUgcm91dGVyIGNhbiBtYWludGFpbiB0
aGlzIHNlcXVlbmNlIG51bWJlciBpbiB3aGF0ZXZlcg0KICAgICAgICAgZm9ybWF0IGl0IHBsZWFz
ZXMg4oCUIGJ1dCwgd2hlbiBpdCBpbmNsdWRlcyBpdCBpbiBjb250cm9sIG1lc3NhZ2VzLCBpdCBt
dXN0IGJlDQogICAgICAgICByZXByZXNlbnRhYmxlIGluIGEgc3BlY2lmaWVkIGZvcm1hdCwgcmVz
cGVjdGluZyBjZXJ0YWluIHJ1bGVzLuKAnQ0KDQpJIHNlZSB0aGF0IHRoZXJlIHdlcmUgbm8gY2hh
bmdlcyBmb2xsb3dpbmcgdGhpcyBjb21tZW50Lg0KDQpUbyBzZWN0aW9uIDQuNCBJIGFza2VkIGZv
ciBjbGFyaWZpY2F0aW9uIGFzIHRvIGlmIHNlcXVlbmNlIG51bWJlcnMgd2VyZSBwZXIgaW50ZXJm
YWNlIG9yIHBlciByb3V0ZXIsIGFzIHRoZSBzcGVjaWZpY2F0aW9uIHdhcyB1bmNsZWFyIG9uIHRo
YXQuIFRoZSB3b3JkcyBoYXMgY2hhbmdlZCwgYnV0IGl0IHN0aWxsIGlzIHVuY2xlYXI6IGhvdyBt
YW55IHNlcXVlbmNlIG51bWJlcnMgZG9lcyBhIHJvdXRlciBtYWludGFpbj8gT25lPyBPbmUgcGVy
IGludGVyZmFjZT8NCg0KSW4gbXkgcHJldmlvdXMgcmV2aWV3LCBJIGV4cHJlc3NlZCB0aGF0IGl0
IHdvdWxkIGJlIHByZWZlcmVudGlhbCB0byB1c2Ug4oCcYSBub3RhdGlvbiBvZiBTZXRz4oCdIHJh
dGhlciB0aGFuIHRhYmxlcy4gSSBzZWUgdGhhdCB0aGlzIGhhcyBub3QgY2hhbmdlZC4NCg0KSSBt
YWRlIGEgY29tbWVudCBvbiBub2RlIGFuZCBhZGRyZXNzLCBsZXQgbWUgcGljayB0aGlzIHVwIGFn
YWluLiBUaGUgZm9sbG93aW5nOg0KDQogICAgICAgIFJ0ZU1zZy5PcmlnQWRkcg0KICAgICAgICAg
ICAgICBBbiBJUCBhZGRyZXNzIG9mIHRoZSBub2RlIHdoaWNoIHJlcXVpcmVzIHRoZSByb3V0ZSwg
aS5lLiwgdGhlDQogICAgICAgICAgICAgIHNvdXJjZSBhZGRyZXNzIG9mIHRoZSBJUCBwYWNrZXQg
dHJpZ2dlcmluZyB0aGUgcm91dGUgcmVxdWVzdC4NCg0Kd291bGQgYmUgbW9yZSBjb21wYWN0IGFu
ZCBjbGVhciBpZiBnZXR0aW5nIHJpZCBvZiB0aGUgdGVybSDigJxub2Rl4oCdIGFuZCBzYWlkOg0K
DQpSdGVNc2cuT3JpZ0FkZHINCiAgICAgICAgVGhlIHNvdXJjZSBhZGRyZXNzIG9mIHRoZSBJUCBw
YWNrZXQgdHJpZ2dlcmluZyB0aGUgcm91dGUgcmVxdWVzdC4NCg0KDQpUbyBzZWN0aW9uIDQuNiwg
YW5kIEkgKGFuZCBvdGhlcnMpIGhhdmUgY29tbWVudGVkIG9uIHRoaXMgYmVmb3JlOg0KDQogICBB
bGwgQU9EVnYyIHJvdXRlcnMgTVVTVCBtYWludGFpbiBhIHJvdXRlIHRhYmxlLiAgVGhlIHJvdXRl
IHRhYmxlDQogICBlbnRyeSBpcyBhIGNvbmNlcHR1YWwgZGF0YSBzdHJ1Y3R1cmUuICBJbXBsZW1l
bnRhdGlvbnMgTUFZIHVzZSBhbnkNCiAgIGludGVybmFsIHJlcHJlc2VudGF0aW9uIGJ1dCBNVVNU
IGNvbnRhaW4gdGhlIGZvbGxvd2luZyBpbmZvcm1hdGlvbjoNCg0KSW4gb3JkZXIgdG8gYXZvaWQg
Y29uZnVzaW9uLCByZW5hbWUgdGhpcyB0byDigJxSb3V0aW5nIEluZm9ybWF0aW9uIEJhc2XigJ0g
b3Ig4oCcUm91dGluZyBTZXTigJ0g4oCUIGEgUm91dGluZyBUYWJsZSBpcyBhbiBvcGVyYXRpbmcg
c3lzdGVtIGNvbnN0cnVjdCwgd2hlcmVvbiBvcGVyYXRpb25zIGRpcmVjdGx5IGluZmx1ZW5jZSBw
YWNrZXQgZm9yd2FyZGluZy4gV2hhdCB5b3UgYXJlIGRlZmluaW5nIGhlcmUgaXMgYSBSSUIvYW4g
UlMuDQoNClRoZSBjb25mdXNpb24gdGhhdCBJIHBvaW50ZWQgb3V0IGluIG15IHByZXZpb3VzIHJl
dmlldyBvbiDigJxJUCBhZGRyZXNz4oCdIGFuZCDigJxBZGRyZXNz4oCdIGJlaW5nIHVzZWQgYSBi
aXQgaGFwaGF6YXJkbHkgcGVyc2lzdHMsIGZ3aXcuIEl0IG1ha2VzIG1lIHRoaW5rLCBjYW4gYSBy
b3V0ZXIgc2VuZCBhbiBSUkVRIGZvciBhIHByZWZpeD8NCg0KSSBhbHNvIGNhbGxlZCB0aGlzIG91
dCBpbiBteSBwcmV2aW91cyByZXZpZXcgYXMgaW5jb3JyZWN0LCBhbmQgZGVzcGl0ZSB3b3Jkc21p
dGhpbmcgaXQgc3RpbGwgaXM6DQoNCiAgICAgICAgUm91dGUuTmV4dEhvcA0KICAgICAgICAgICAg
ICBUaGUgc291cmNlIElQIGFkZHJlc3Mgb2YgdGhlIG1lc3NhZ2UgYWR2ZXJ0aXNpbmcgdGhlIHJv
dXRlIHRvDQogICAgICAgICAgICAgIFJvdXRlLkFkZHJlc3MsIGkuZS4gYW4gSVAgYWRkcmVzcyBv
ZiB0aGUgQU9EVnYyIHJvdXRlciB1c2VkIGZvcg0KICAgICAgICAgICAgICB0aGUgbmV4dCBob3Ag
b24gdGhlIHBhdGggdG93YXJkIFJvdXRlLkFkZHJlc3MuDQoNCklmIHRoYXQg4oCcbWVzc2FnZeKA
nSBpcyBhbiBSRkM1NDQ0IGVudGl0eSwgdGhlbiBpdCBkb2VzIHRvIGhhdmUgYSDigJxzb3VyY2Ug
SVAgQWRkcmVzc+KAnSDigJQgdGhlIGVuY2Fwc3VsYXRpbmcgSVAgZGF0YWdyYW0gY29udGFpbmlu
ZyB0aGUgcGFja2V0IGNvbnRhaW5pbmcgdGhlIG1lc3NhZ2UgZG9lcy4gQW5kIHRoZSBtZXNzYWdl
IE1BWSBoYXZlIGFuIE9yaWdpbmF0b3IgQWRkcmVzcw0KDQoNCkFzIEkgaW5kaWNhdGVkLCBJIGFt
IHdhbGtpbmcgdGhyb3VnaCBteSBwcmV2aW91cyByZXZpZXcgYW5kIHJldGFpbmluZyB0aG9zZSBj
b21tZW50cyB0aGF0IEkgc3RpbGwgdGhpbmsgbmVlZCBhdHRlbnRpb24g4oCUIGFuZCB0aGlzIGlz
IOKAnGNyb3NzaW5nIG9mZiBmcm9tIHBhcnQgMSBvZiBteSBwcmV2aW91cyByZXZpZXfigJ0gb25s
eS4gTW9yZSB0byBmb2xsb3cuDQoNClRob21hcw0KDQpfX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fXw0KbWFuZXQgbWFpbGluZyBsaXN0DQptYW5ldEBpZXRmLm9y
ZzxtYWlsdG86bWFuZXRAaWV0Zi5vcmc+DQpodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xp
c3RpbmZvL21hbmV0DQoNCioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioq
KioqKioqKioqKioqKioqKioqKioqKioqKioqClRoaXMgZW1haWwgYW5kIGFueSBhdHRhY2htZW50
cyBhcmUgY29uZmlkZW50aWFsIHRvIHRoZSBpbnRlbmRlZApyZWNpcGllbnQgYW5kIG1heSBhbHNv
IGJlIHByaXZpbGVnZWQuIElmIHlvdSBhcmUgbm90IHRoZSBpbnRlbmRlZApyZWNpcGllbnQgcGxl
YXNlIGRlbGV0ZSBpdCBmcm9tIHlvdXIgc3lzdGVtIGFuZCBub3RpZnkgdGhlIHNlbmRlci4KWW91
IHNob3VsZCBub3QgY29weSBpdCBvciB1c2UgaXQgZm9yIGFueSBwdXJwb3NlIG5vciBkaXNjbG9z
ZSBvcgpkaXN0cmlidXRlIGl0cyBjb250ZW50cyB0byBhbnkgb3RoZXIgcGVyc29uLgoqKioqKioq
KioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioq
KioqKgo=

--_000_B31EEDDDB8ED7E4A93FDF12A4EECD30D7D76BF1CGLKXM0002VGREEN_
Content-Type: text/html; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTQgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
Q2FsaWJyaTsNCglwYW5vc2UtMToyIDE1IDUgMiAyIDIgNCAzIDIgNDt9DQpAZm9udC1mYWNlDQoJ
e2ZvbnQtZmFtaWx5OlRhaG9tYTsNCglwYW5vc2UtMToyIDExIDYgNCAzIDUgNCA0IDIgNDt9DQov
KiBTdHlsZSBEZWZpbml0aW9ucyAqLw0KcC5Nc29Ob3JtYWwsIGxpLk1zb05vcm1hbCwgZGl2Lk1z
b05vcm1hbA0KCXttYXJnaW46MGNtOw0KCW1hcmdpbi1ib3R0b206LjAwMDFwdDsNCglmb250LXNp
emU6MTIuMHB0Ow0KCWZvbnQtZmFtaWx5OiJUaW1lcyBOZXcgUm9tYW4iLCJzZXJpZiI7fQ0KYTps
aW5rLCBzcGFuLk1zb0h5cGVybGluaw0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJY29sb3I6
Ymx1ZTsNCgl0ZXh0LWRlY29yYXRpb246dW5kZXJsaW5lO30NCmE6dmlzaXRlZCwgc3Bhbi5Nc29I
eXBlcmxpbmtGb2xsb3dlZA0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJY29sb3I6cHVycGxl
Ow0KCXRleHQtZGVjb3JhdGlvbjp1bmRlcmxpbmU7fQ0Kc3Bhbi5FbWFpbFN0eWxlMTkNCgl7bXNv
LXN0eWxlLXR5cGU6cGVyc29uYWwtcmVwbHk7DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLCJzYW5z
LXNlcmlmIjsNCgljb2xvcjojMUY0OTdEO30NCi5Nc29DaHBEZWZhdWx0DQoJe21zby1zdHlsZS10
eXBlOmV4cG9ydC1vbmx5Ow0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIiwic2Fucy1zZXJpZiI7DQoJ
bXNvLWZhcmVhc3QtbGFuZ3VhZ2U6RU4tVVM7fQ0KQHBhZ2UgV29yZFNlY3Rpb24xDQoJe3NpemU6
NjEyLjBwdCA3OTIuMHB0Ow0KCW1hcmdpbjo3Mi4wcHQgNzIuMHB0IDcyLjBwdCA3Mi4wcHQ7fQ0K
ZGl2LldvcmRTZWN0aW9uMQ0KCXtwYWdlOldvcmRTZWN0aW9uMTt9DQotLT48L3N0eWxlPjwhLS1b
aWYgZ3RlIG1zbyA5XT48eG1sPg0KPG86c2hhcGVkZWZhdWx0cyB2OmV4dD0iZWRpdCIgc3BpZG1h
eD0iMTAyNiIgLz4NCjwveG1sPjwhW2VuZGlmXS0tPjwhLS1baWYgZ3RlIG1zbyA5XT48eG1sPg0K
PG86c2hhcGVsYXlvdXQgdjpleHQ9ImVkaXQiPg0KPG86aWRtYXAgdjpleHQ9ImVkaXQiIGRhdGE9
IjEiIC8+DQo8L286c2hhcGVsYXlvdXQ+PC94bWw+PCFbZW5kaWZdLS0+DQo8L2hlYWQ+DQo8Ym9k
eSBsYW5nPSJFTi1HQiIgbGluaz0iYmx1ZSIgdmxpbms9InB1cnBsZSI+DQo8ZGl2IGNsYXNzPSJX
b3JkU2VjdGlvbjEiPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6
ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlm
JnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPkkgbWFkZSBhbiBvYnNlcnZhdGlvbiAodGhhdCBSRkMgNjYy
MSBpcyBjb21wbGV0ZWx5IGluYXBwbGljYWJsZSkgb24gLTEyLCBidXQgYmFzZWQgaW4gcGFydCBv
biB0aGF0LCBJ4oCZbSB3YWl0aW5nIHRvIHJldmlldyB0aGUgbmV4dCBkcmFmdCwgcmF0aGVyIHRo
YW4gdGhpcyBvbmUuDQogKFRpbWUgSSBjYW4gbWFrZSBJ4oCZbSBsb29raW5nIGF0IERMRVAsIHdo
aWNoIGFwcGVhcnMgY2xvc2VyIHRvIGZpbmFsLCB0aG91Z2ggdGhlcmXigJlzIGEgY291cGxlIG9m
IG9wZW4gcXVlc3Rpb25zIG9uIElQdjYgYW5kIFRMUy4pPG86cD48L286cD48L3NwYW4+PC9wPg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1m
YW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOiMx
RjQ5N0QiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
PjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkm
cXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xvcjojMUY0OTdEIj5PYnNlcnZpbmcgdGhp
cyBkaXNjdXNzaW9uIChvZiBBT0RWdjIpIHRoZXJlIHNlZW1zIHRvIGJlIGEgc2lnbmlmaWNhbnQg
aXNzdWUgb24gaG9wIGJ5IGhvcCB2ZXJzdXMgZW5kIHRvIGVuZCBiaWRpcmVjdGlvbmFsaXR5LiBB
cyBJ4oCZdmUgY29tbWVudGVkIGJlZm9yZSwgSeKAmXZlDQogZm91bmQgZW5vdWdoIGluIHRoZSDi
gJxvdXRzaWRl4oCdIHBhcnRzIG9mIHRoZSBzcGVjaWZpY2F0aW9uLCB0aGF0IEkgaGF2ZW7igJl0
IGdvdCBzdHVjayBpbnRvIHRoZSBhY3R1YWwgY29yZSBwcm90b2NvbCwgc28gSSBkb27igJl0IHll
dCBoYXZlIGEgdmlldyBvbiB0aGlzLiAoSSBoYXZlIGEgdmlldyB0aGF0IGJpZGlyZWN0aW9uYWxp
dHkgbmVlZHMgZW5zdXJpbmcgd29ya3MsIGFuZCB0byBiZSBpbnRlcm9wZXJhYmxlLCBidXQgdGhh
dOKAmXMgYXMgZmFyIGFzIEnigJl2ZQ0KIGdvdC4pIEJ1dCBpdOKAmXMgYSBiaXQgY29uY2Vybmlu
ZyB0aGF0IHRoaXMgc3RpbGwgaXNu4oCZdCBjbGVhciDigJMgYW5kIEnigJl2ZSBzZWVuIG5vIHJl
cG9ydHMgb2YgYW4gaW1wbGVtZW50YXRpb24gb2YgZWl0aGVyLiBJcyB0aGVyZSBvbmU/PG86cD48
L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQt
c2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNl
cmlmJnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFt
aWx5OiZxdW90O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xvcjojMUY0
OTdEIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48
Yj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6
JnF1b3Q7VGFob21hJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDsiPkZyb206PC9zcGFuPjwv
Yj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6
JnF1b3Q7VGFob21hJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDsiPiBtYW5ldCBbbWFpbHRv
Om1hbmV0LWJvdW5jZXNAaWV0Zi5vcmddDQo8Yj5PbiBCZWhhbGYgT2YgPC9iPlZpY3RvcmlhIE1l
cmNpZWNhPGJyPg0KPGI+U2VudDo8L2I+IDAyIERlY2VtYmVyIDIwMTUgMTQ6MjU8YnI+DQo8Yj5U
bzo8L2I+IGlldGZAdGhvbWFzY2xhdXNlbi5vcmc8YnI+DQo8Yj5DYzo8L2I+IG1hbmV0PGJyPg0K
PGI+U3ViamVjdDo8L2I+IFJlOiBbbWFuZXRdIFN0dWZmIGZyb20gcmV2aWV3IG9mIGFvZHYtMTEg
cGFnZSAxLTIyIHRoYXQgYXJlIHN0aWxsIG5vdCBmb2xkZWQgaW50byAtMTI8bzpwPjwvbzpwPjwv
c3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxk
aXYgc3R5bGU9ImJvcmRlcjpzb2xpZCBibGFjayAxLjBwdDtwYWRkaW5nOjIuMHB0IDIuMHB0IDIu
MHB0IDIuMHB0Ij4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIGFsaWduPSJjZW50ZXIiIHN0eWxlPSJ0
ZXh0LWFsaWduOmNlbnRlcjtiYWNrZ3JvdW5kOndoaXRlIj48c3BhbiBzdHlsZT0iZm9udC1mYW1p
bHk6JnF1b3Q7QXJpYWwmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xvcjpibGFjayI+
PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
IGFsaWduPSJjZW50ZXIiIHN0eWxlPSJ0ZXh0LWFsaWduOmNlbnRlcjtiYWNrZ3JvdW5kOndoaXRl
Ij48Yj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjE1LjBwdDtmb250LWZhbWlseTomcXVvdDtBcmlh
bCZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOiMzMzM5NzIiPioqKiBXQVJOSU5H
ICoqKjxvOnA+PC9vOnA+PC9zcGFuPjwvYj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIiBhbGlnbj0iY2VudGVyIiBzdHlsZT0ibWFyZ2luLWJvdHRvbToxMi4wcHQ7dGV4
dC1hbGlnbjpjZW50ZXI7YmFja2dyb3VuZDp3aGl0ZSI+DQo8ZW0+PHNwYW4gc3R5bGU9ImZvbnQt
c2l6ZToxMC41cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDssJnF1b3Q7c2Fucy1zZXJp
ZiZxdW90Oztjb2xvcjojMzMzOTcyIj5UaGlzIG1lc3NhZ2Ugb3JpZ2luYXRlcyBmcm9tIG91dHNp
ZGUgb3VyIG9yZ2FuaXNhdGlvbiwgZWl0aGVyIGZyb20gYW4gZXh0ZXJuYWwgcGFydG5lciBvciB0
aGUgaW50ZXJuZXQuPC9zcGFuPjwvZW0+PGk+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC41cHQ7
Zm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xv
cjojMzMzOTcyIj48YnI+DQo8ZW0+PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90O0FyaWFs
JnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDsiPkNvbnNpZGVyIGNhcmVmdWxseSB3aGV0aGVy
IHlvdSBzaG91bGQgY2xpY2sgb24gYW55IGxpbmtzLCBvcGVuIGFueSBhdHRhY2htZW50cyBvciBy
ZXBseS48L3NwYW4+PC9lbT48YnI+DQo8ZW0+PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90
O0FyaWFsJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDsiPkZvciBpbmZvcm1hdGlvbiByZWdh
cmRpbmcgPC9zcGFuPg0KPC9lbT48L3NwYW4+PC9pPjxzdHJvbmc+PGk+PHNwYW4gc3R5bGU9ImZv
bnQtc2l6ZToxMC41cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDssJnF1b3Q7c2Fucy1z
ZXJpZiZxdW90Oztjb2xvcjpyZWQiPlJlZCBGbGFnczwvc3Bhbj48L2k+PC9zdHJvbmc+PGVtPjxz
cGFuIHN0eWxlPSJmb250LXNpemU6MTAuNXB0O2ZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7
LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6IzMzMzk3MiI+IHRoYXQgeW91IGNhbiBsb29r
IG91dCBmb3IgaW4gZW1haWxzIHlvdSByZWNlaXZlLA0KIGNsaWNrIDxhIGhyZWY9Imh0dHA6Ly9p
bnRyYW5ldC5lbnQuYmFlc3lzdGVtcy5jb20vaG93d2V3b3JrL3NlY3VyaXR5L3Nwb3RsaWdodHMv
RG9jdW1lbnRzL1JlZCUyMEZsYWdzLnBkZiI+DQpoZXJlPC9hPi48L3NwYW4+PC9lbT48aT48c3Bh
biBzdHlsZT0iZm9udC1zaXplOjEwLjVwdDtmb250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90Oywm
cXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOiMzMzM5NzIiPjxicj4NCjxlbT48c3BhbiBzdHls
ZT0iZm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90OyI+
SWYgeW91IGZlZWwgdGhlIGVtYWlsIGlzIHN1c3BpY2lvdXMsIHBsZWFzZSBmb2xsb3cNCjxhIGhy
ZWY9Imh0dHA6Ly9pbnRyYW5ldC5lbnQuYmFlc3lzdGVtcy5jb20vaG93d2V3b3JrL3NlY3VyaXR5
L3Nwb3RsaWdodHMvRG9jdW1lbnRzL0RlYWxpbmclMjBXaXRoJTIwU3VzcGljaW91cyUyMEVtYWls
cy5wZGYiPg0KdGhpcyBwcm9jZXNzPC9hPi48L3NwYW4+PC9lbT48L3NwYW4+PC9pPjxzcGFuIHN0
eWxlPSJmb250LXNpemU6MTAuNXB0O2ZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LCZxdW90
O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6IzMzMzk3MiI+PG86cD48L286cD48L3NwYW4+PC9wPg0K
PC9kaXY+DQo8L2Rpdj4NCjxkaXY+DQo8ZGl2IHN0eWxlPSJib3JkZXI6c29saWQgd2luZG93dGV4
dCAxLjBwdDtwYWRkaW5nOjEuMHB0IDQuMHB0IDEuMHB0IDQuMHB0Ij4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiIGFsaWduPSJjZW50ZXIiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28t
bWFyZ2luLWJvdHRvbS1hbHQ6YXV0bzt0ZXh0LWFsaWduOmNlbnRlciI+DQo8c3BhbiBzdHlsZT0i
Zm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90OyI+Kjxz
dHJvbmc+PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LCZxdW90O3Nh
bnMtc2VyaWYmcXVvdDsiPioqDQo8L3NwYW4+PC9zdHJvbmc+PC9zcGFuPjxzdHJvbmc+PHNwYW4g
c3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDssJnF1
b3Q7c2Fucy1zZXJpZiZxdW90OyI+V0FSTklORw0KPC9zcGFuPjwvc3Ryb25nPjxzdHJvbmc+PHNw
YW4gc3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYm
cXVvdDsiPioqKjwvc3Bhbj48L3N0cm9uZz48c3BhbiBzdHlsZT0iZm9udC1zaXplOjguNXB0O2Zv
bnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDsiPjxicj4N
Cjwvc3Bhbj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtB
cmlhbCZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7Ij5FWFRFUk5BTCBFTUFJTCAtLSBUaGlz
IG1lc3NhZ2Ugb3JpZ2luYXRlcyBmcm9tIG91dHNpZGUgb3VyIG9yZ2FuaXphdGlvbjwvc3Bhbj48
c3BhbiBzdHlsZT0iZm9udC1zaXplOjguNXB0O2ZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7
LCZxdW90O3NhbnMtc2VyaWYmcXVvdDsiPi48L3NwYW4+PG86cD48L286cD48L3A+DQo8L2Rpdj4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2
Pg0KPGRpdj4NCjxkaXY+DQo8ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxl
PSJtYXJnaW4tYm90dG9tOjEyLjBwdCI+SGVsbG8gVGhvbWFzLDxvOnA+PC9vOnA+PC9wPg0KPC9k
aXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2luLWJvdHRvbToxMi4wcHQiPlRo
YW5rIHlvdSBhZ2FpbiBmb3IgeW91ciB0aW1lIHNwZW50IHJldmlld2luZyBBT0RWdjIuIEkgYXBv
bG9naXNlIHRoYXQgd2UgZGlkIG5vdCBnaXZlIGEgJnF1b3Q7cG9pbnQgYnkgcG9pbnQmcXVvdDsg
cmVzcG9uc2UgdG8geW91ciBjb21tZW50cyBvbiBkcmFmdCAxMSAtIEkgZmVsdCB0aGF0IHNpbmNl
IG1vc3Qgb2YgdGhlIGNvbW1lbnRzIHdlcmUgYXJvdW5kIGEgZmV3IG1ham9yDQogdG9waWNzLCBp
dCBtYWRlIHNlbnNlIHRvIGFkZHJlc3MgdGhlIHRvcGljIGFjcm9zcyB0aGUgd2hvbGUgZHJhZnQs
IHJhdGhlciB0aGFuIHJlc3BvbmQgdG8gZXZlcnkgc2luZ2xlIGNvbW1lbnQgaW4gb3JkZXIuIEkg
ZGlkIGFsc28gdHJ5IHRvIHN0YXJ0IGEgZGlzY3Vzc2lvbiBvbiB0aGUgTUFORVQgbGlzdCBiYXNl
ZCBvbiB5b3VyIGNvbW1lbnRzIGZyb20gZHJhZnQgMTEsIGJ1dCBkaWQgbm90IHNlZSBhbnkgcmVz
cG9uc2VzLg0KPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0
eWxlPSJtYXJnaW4tYm90dG9tOjEyLjBwdCI+VGhhbmsgeW91IGFnYWluLCB3ZSB3aWxsIGRpc2N1
c3MgYW5kIGludGVuZCB0byByZXNwb25kIHNvb24uPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiPktpbmQgcmVnYXJkcyw8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCI+VmljdG9yaWEuPG86cD48L286cD48L3A+DQo8ZGl2Pg0KPGRp
dj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJnaW4tYm90dG9tOjEyLjBwdCI+PG86
cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCI+T24gVHVlLCBEZWMgMSwgMjAxNSBhdCA3OjIxIFBNLCAmbHQ7PGEgaHJlZj0ibWFp
bHRvOmlldGZAdGhvbWFzY2xhdXNlbi5vcmciIHRhcmdldD0iX2JsYW5rIj5pZXRmQHRob21hc2Ns
YXVzZW4ub3JnPC9hPiZndDsgd3JvdGU6PG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9y
bWFsIj5BbGwsPGJyPg0KPGJyPg0KSSBhbSB3b3JraW5nIHRocm91Z2ggdGhlIHJldmlzZWQgSS1E
IHRvIHNlZSB3aGF0IGNvbW1lbnRzIHRoYXQgSSBtYWRlIHByZXZpb3VzbHkgaGF2ZSBiZWVuIGFk
ZHJlc3NlZCwgYW5kIHdoaWNoIHN0aWxsIGRvIGFwcGx5Ljxicj4NCjxicj4NCkFzIEkgc2VudCBt
eSBvcmlnaW5hbCByZXZpZXcgcGllY2VtZWFsLCBJ4oCZbGwgc2VuZCBteSByZWZyZXNoZXIgaW4g
bWF0Y2hpbmcgcGllY2VzIChpbiBwYXJ0LCBpbiByZWNvZ25pdGlvbiB0aGF0IGl0IGlzIGhhcmQg
dG8gZ2V0IHRpbWUgdG8gc2l0IGRvd24gYW5kIHJldmlldyB0aGUgd2hvbGUgZG9jdW1lbnQgaW4g
b25lIGdvLCBhbmQgSSBkbyB3YW50IHRvIHJlcGx5IHRvIHRoZSBhdXRob3JzIGFzIHF1aWNrbHkg
YXMgcG9zc2libGUpPGJyPg0KPGJyPg0KSW4gZG9pbmcgc28sIEkgYW0gbm90aWNpbmcgYWRkaXRp
b25hbCB0aGluZ3MgKG5vdGFibHksIGJ1dCBub3QgZXhjbHVzaXZlbHksIHRvIHNlY3Rpb24gNyBh
bmQgYmV5b25kLCB3aGljaCBJIGRpZG7igJl0IGdldCB0aHJvdWdoIHJldmlld2luZyBsYXN0IHRp
bWUgYXJvdW5kKSB3aGljaCBuZWVkcyBhdHRlbnRpb24uIEnigJlsbCBnYXRoZXIgdGhhdCBpbiBz
ZXBhcmF0ZSBlbWFpbHMgYSBiaXQgbGF0ZXIsIG9uY2UgSeKAmXZlIHdvcmtlZCB0aHJvdWdoIHRo
ZQ0KIGNvbXBsZXRlLCB1cGRhdGVkIHNwZWMuPGJyPg0KPGJyPg0KU28gb253YXJkcy4uLjxicj4N
Cjxicj4NCkFic3RyYWN0Ojxicj4NCiZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyBJIG1hZGUg
dGhlIGZvbGxvd2luZyBjb21tZW50LCB3aGljaCBzdGlsbCBhcHBsaWVzOjxicj4NCjxicj4NCiZu
YnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsg4oCc
VGhpcyBpcyBhIGxpdHRsZSBvdmVyLXN0YXRpbmcgdGhlIGFwcGxpY2FiaWxpdHk6IHRoZXNlIHN0
YXRlbWVudHMgbWF5PGJyPg0KJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJz
cDsgJm5ic3A7ICZuYnNwOyAmbmJzcDtiZSB0cnVlIGluIHNvbWUgc2NlbmFyaW9zIChmb3IgZXhh
bXBsZSwgd2hlbiB0aGVyZSBhcmUgZmV3PGJyPg0KJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7
ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDtjb25jdXJyZW50IHRyYWZmaWMgZmxv
d3MsIGFuZCB0aGVyZWZvcmUgZmV3IHJvdXRlcyB0byByZXBhaXIsIGFuZDxicj4NCiZuYnNwOyAm
bmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7dGhl
cmVmb3JlIGZldyBmbG9vZGluZyBvcGVyYXRpb25zIHRvIGNvbnRlbmQgZm9yIGNoYW5uZWwgYWNj
ZXNzKS48YnI+DQombmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJz
cDsgJm5ic3A7ICZuYnNwO0FzIGEgZ2VuZXJhbCBzdGF0ZW1lbnQsIHRoaXMgbGFzdCBzZW50ZW5j
ZSBpcyBpbmNvcnJlY3TigJ3igJ08YnI+DQo8YnI+DQpPdmVydmlldyAoYW5kIGVsc2V3aGVyZSk6
PGJyPg0KPGJyPg0KJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7IEkgbWFkZSBhIGNvbW1lbnQg
cHJldmlvdXNseSB0aGF0IOKAnFJvdXRlciBjbGllbnTigJ0gaXMgYSBwb29ybHkgY2hvc2VuPGJy
Pg0KJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7IHRlcm0sIGFuZCBoYXZlIHByb3Bvc2VkIGFs
dGVybmF0aXZlcy4gSeKAmXZlIHNlZW4gc29tZSBhdHRlbXB0cyBvbiB0aGUgbGlzdDxicj4NCiZu
YnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyBhdCByYXRoZXIgdGhhbiBjaGFuZ2UgdGhlIHRlcm0s
IGV4cGxhaW4gaXQg4oCUIHNvbWUgb2Ygd2hpY2ggaXMgaW4gdGhpcyBkb2N1bWVudC48YnI+DQom
bmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgVGhlIOKAnE92ZXJ2aWV34oCdIHN0aWxsIHRhbGtz
IGFib3V0IOKAnGEgcm91dGVy4oCmb25lIG9mIGl0cyBjbGllbnRz4oCdIC0gd2hpY2ggaXMgbm8g
bGVzczxicj4NCiZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyBjb25mdXNpbmcgdGhhbiBsYXN0
IHRpbWUgSXcgd2VudCB0aHJvdWdoIGl0Ljxicj4NCjxicj4NCiZuYnNwOyAmbmJzcDsgJm5ic3A7
ICZuYnNwOyBJIHJlaXRlcmF0ZSwgd2h5IG5vdCB1c2Ug4oCcTG9jYWwgQXR0YWNoZWQgTmV0d29y
ayBTZXTigJ0sIHdoaWNoIGlzIHRoZSB0ZXJtIHVzZWQ8YnI+DQombmJzcDsgJm5ic3A7ICZuYnNw
OyAmbmJzcDsgYnkgb3RoZXIgZG9jdW1lbnRzIGZyb20gdGhpcyBXRz88YnI+DQo8YnI+DQpPdmVy
dmlldzo8YnI+DQombmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgVGhlIHRlcm0g4oCcY29uZmly
bWluZyBhZGphY2VuY3nigJ0gaXMgZ29uZSwgYW5kIGlzIG5vdyByZXBsYWNlZCBieTxicj4NCiZu
YnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyDigJxjb25maXJtaW5nIGJpZGlyZWN0aW9uYWxpdHni
gJ0gLSB3aGljaCwgYWxhcywgc3RpbGwgc291bmRzIGxpa2UgdGhlcmUgaXMgc29tZSBhY3RpdmU8
YnI+DQombmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgbW9uaXRvcmluZyAoSEVMTE8gbWVzc2Fn
ZSBleGNoYW5nZSkgZ29pbmcgb24uIFVubGVzcyB0aGF0IGlzIHRoZSBjYXNlLDxicj4NCiZuYnNw
OyAmbmJzcDsgJm5ic3A7ICZuYnNwOyB0aGVuIHBsZWFzZSBiZSBtb3JlIHNwZWNpZmljIGhlcmUu
PGJyPg0KPGJyPg0KJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7IEkgbm90ZSB0aGF0IHRoZSB0
ZXJtIGFkamFjZW5jeSBpcyB1c2VkIHRocm91Z2ggYW5kIHRocm91Z2ggdGhlIGRvY3VtZW50LCBi
dHcuPGJyPg0KPGJyPg0KJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7IEkgc3VnZ2VzdGVkIGlu
IG15IGxhc3QgcmV2aWV3Ojxicj4NCjxicj4NCiZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAm
bmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgVGhlIG92ZXJ2aWV3IG11c3QgYWxzbyBpbmNsdWRl
IGEgcGFyYWdyYXBoIG9uIHRoZSBpbnRlcnNlY3Rpb25zPGJyPg0KJm5ic3A7ICZuYnNwOyAmbmJz
cDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyBiZXR3ZWVuIHRoaXMgcHJvdG9j
b2wgYW5kIHRoZSBmb3J3YXJkaW5nIHBsYW5lIOKAlCB0aGlzLCBhcyBpdCBpczxicj4NCiZuYnNw
OyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgZGlmZmVy
ZW50IChhbmQgbW9yZSBpbnZhc2l2ZSkgZnJvbSB0aGF0IHdoaWNoIGlzIHR5cGljYWxseSBzZWVu
IGluPGJyPg0KJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7
ICZuYnNwOyByb3V0aW5nIHByb3RvY29scy48YnI+DQo8YnI+DQombmJzcDsgJm5ic3A7ICZuYnNw
OyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7IFNwZWNpZmljYWxseSwgYXMgYSBy
ZWFjdGl2ZSBwcm90b2NvbCwgaXQgaXMgcmVxdWlyZWQgKGF0IGxlYXN0KSB0aGF0IHRoZTxicj4N
CiZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsg
Zm9yd2FyZGluZyBwbGFuZSBpcyBtb2RpZmllZCA6PGJyPg0KPGJyPg0KJm5ic3A7ICZuYnNwOyAm
bmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAxKSBBIOKAnG1pc3PigJ0g
d2hlbiBsb29raW5nIHVwIGEgbmV4dCBob3AgZm9yIGEgZGF0YSBwYWNrZXQgdG8gYmU8YnI+DQom
bmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZu
YnNwOyAmbmJzcDtmb3J3YXJkZWQsIGlzIHNpZ25hbGxlZCB0byB0aGUgQU9EVnYyIHByb2Nlc3Mg
c28gYXMgdG8gcGVybWl0PGJyPg0KJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAm
bmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgdGhhdCByb3V0ZSBkaXNjb3ZlcnkgYmUgbGF1bmNo
ZWQ7PGJyPg0KPGJyPg0KJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsg
Jm5ic3A7ICZuYnNwOyAyKSBBIOKAnG1pc3PigJ0gd2hlbiBhdHRlbXB0aW5nIHRvIGRlbGl2ZXIg
YSBkYXRhIHBhY2tldCB0byBhIG5leHQgaG9wLDxicj4NCiZuYnNwOyAmbmJzcDsgJm5ic3A7ICZu
YnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwO3doaWNoIHdhcyBy
ZWNvcmRlZCBpbiB0aGUgcm91dGluZyB0YWJsZSwgaXMgc2lnbmFsbGVkIHRvIHRoZSBBT0RWdjI8
YnI+DQombmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5i
c3A7ICZuYnNwOyAmbmJzcDtwcm9jZXNzIHNvIGFzIHRvIHBlcm1pdCB0aGF0IGEgcm91dGUgcmVw
YWlyIGJlIGluaXRpYXRlZCBhbmQvb3IgYSBSb3V0ZTxicj4NCiZuYnNwOyAmbmJzcDsgJm5ic3A7
ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwO0Vycm9yIGJl
IGdlbmVyYXRlZC48YnI+DQo8YnI+DQombmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7
ICZuYnNwOyAmbmJzcDsgJm5ic3A7IDMpIEEg4oCcaGl04oCdIHdoZW4gbG9va2luZyB1cCBhIG5l
eHQgaG9wIGZvciBhIGRhdGEgcGFja2V0IHRvIGJlIGZvcndhcmRlZDxicj4NCiZuYnNwOyAmbmJz
cDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNw
OyB0byBhIGRlc3RpbmF0aW9uIGlzIHNpZ25hbGxlZCB0byB0aGUgQU9EVnYyIHByb2Nlc3Mgc28g
YXMgdG8gcGVybWl0PGJyPg0KJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJz
cDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7IG1haW50ZW5hbmNlIG9mIOKAnGFjdGl2ZSBy
b3V0ZeKAnSBSb3V0ZSBTdGF0ZSwgdGltZXJzIGFuZCBzdWNoLjxicj4NCjxicj4NCiZuYnNwOyAm
bmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgTm90ZSB0aGF0
IHRoZXNlIHRoaW5ncyBhcmUgbmVjZXNzYXJ5IHRvIGNhbGwgb3V0IGluIHRoZSDigJxvdmVydmll
d+KAnSBhbmQgaW48YnI+DQombmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNw
OyAmbmJzcDsgJm5ic3A7IHRoZSDigJxhcHBsaWNhYmlsaXR5IHN0YXRlbWVudOKAnSwgYm90aDog
aXQgaXMgbm90IHRoYXQgdGhleSBhcmUgbmVnYXRpdmVzIHBlciBzZSw8YnI+DQombmJzcDsgJm5i
c3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7IGJ1dCB0aGF0IHRo
ZXkgYXJlIGltcG9ydGFudCBmYWN0b3JzIGdvdmVybmluZyB0aGUgYXBwbGljYWJpbGl0eSBvZiB0
aGlzIHByb3RvY29sOjxicj4NCiZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5i
c3A7ICZuYnNwOyAmbmJzcDsgd2lsbCBhIGdpdmVuIHBsYXRmb3JtIHBlcm1pdCBzdWNoIGFjY2Vz
cyB0byB0aGUgZm9yd2FyZGluZyBwbGFuZSwgZm9yIGV4YW1wbGU/PGJyPg0KJm5ic3A7ICZuYnNw
OyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyBJbXBvcnRhbnQgdG8g
dW5kZXJzdGFuZCBpZiBmb3IgdGhhdCBwbGF0Zm9ybSB0aGlzIHByb3RvY29sIGlzIGFwcGxlPGJy
Pg0KPGJyPg0KPGJyPg0KJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7IEkgc2VlIHRoYXQgdGhp
cyB3YXMgbm90IGFkZHJlc3NlZCBpbiB0aGUgb3ZlcnZpZXcsIG5vciBpbiB0aGUgYXBwbGljYWJp
bGl0eSBvdGhlciB0aGFuPGJyPg0KJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7IGJ5IGEgZm9y
d2FyZCByZWZlcmVuY2UgdG8gc2VjdGlvbiA2LjQuIFdoaWxlIGl0IGlzIHBvc2l0aXZlIHRoYXQg
dGhlcmUgaXMgYSBzZWN0aW9uIDYuNCw8YnI+DQombmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsg
dGhpcyBkb2VzIG5vdCBleG9uZXJhdGUgdGhlIG92ZXJ2aWV3IGFuZCB0aGUgYXBwbGljYWJpbGl0
eSBzdGF0ZW1lbnQgZm9yIGJlaW5nPGJyPg0KJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7IGhv
bmVzdCBhYm91dCB0aGUgcmVxdWlyZW1lbnRzIChub3RhYmx5IHRvIHRoZSBwbGF0Zm9ybS9vcykg
dGhhdCB0aGlzIHByb3RvY29sIGhhczxicj4NCiZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyBm
b3IgYmVpbmcgYXBwbGljYWJsZTxicj4NCjxicj4NCiZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNw
OyBJIHN1Z2dlc3RlZCBpbiBteSBsYXN0IHJldmlldzo8YnI+DQo8YnI+DQombmJzcDsgJm5ic3A7
ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7IOKAnEl0IGlzIGltcG9y
dGFudCB0byBkbyBtb3JlIHRoYW4gdGhpczogNzE4MiBkb2VzIG9ubHkgcHJvdmlkZSDigJxjb250
YWluZXJz4oCdPGJyPg0KJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsg
Jm5ic3A7ICZuYnNwOyAmbmJzcDtmb3IgSUNWcyBhbmQgdGltZXN0YW1wcywgYW5kIGRvZXMgbm90
IHNwZWNpZnkgaG93IHRvIHVzZSB0aGVtIHRvIG9idGFpbjxicj4NCiZuYnNwOyAmbmJzcDsgJm5i
c3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7c3BlY2lmaWMgc2Vj
dXJpdHkgcHJvcGVydGllcy4gUkZDNzE4MiBtYXkgYmUgYSB0b29sIHRoYXQgY2FuIGJlIHVzZWQs
IGJ1dDxicj4NCiZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNw
OyAmbmJzcDsgJm5ic3A7KmhvdyogdGhhdCB0b29sIGlzIHVzZWQgaXMgd2hhdCBkZXRlcm1pbmVz
IHRoZSBzZWN1cml0eSBwcm9wZXJ0aWVzLjxicj4NCjxicj4NCiZuYnNwOyAmbmJzcDsgJm5ic3A7
ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgVGhlcmVmb3JlLCBzYXlpbmcgdGhh
dCDigJxzZWN1cml0eSBpcyBkZWFsdCB3aXRoIGJ5IHVzaW5nIFJGQzcxODLigJ0gaXMgZWl0aGVy
IGFuPGJyPg0KJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7
ICZuYnNwOyBpbmNvbXBsZXRlIHN0YXRlbWVudCwgb3IgaXMgaW5kaWNhdGl2ZSBvZiBpbnN1ZmZp
Y2llbnQgc2VjdXJpdHkgY29uc2lkZXJhdGlvbnMu4oCdPGJyPg0KPGJyPg0KJm5ic3A7ICZuYnNw
OyAmbmJzcDsgJm5ic3A7IFRoZSBhY3R1YWwgc2VudGVuY2UgaW4gdGhlIEktRCBoYXMgYmVlbiBj
aGFuZ2VkLCBub3cgaXQgZXhwbGljaXRseSBuYW1lcyB0aGU8YnI+DQombmJzcDsgJm5ic3A7ICZu
YnNwOyAmbmJzcDsgdHdvIFRMVnMgZnJvbSA3MTgyIHRoYXQgaXQgdXNlcy4gVGhhdCBpcywgYWxh
cywgc3RpbGwgbm90IHN1ZmZpY2llbnQuPGJyPg0KPGJyPg0KJm5ic3A7ICZuYnNwOyAmbmJzcDsg
Jm5ic3A7IE1ha2luZyB0aGUgYXNpZGUgdGhhdCB3YXMgZGlzY3Vzc2VkIHJlY2VudGx5IG9uIHRo
ZSBsaXN0LCB0aGF0IChpKSBjb250cm9sIG1lc3NhZ2VzPGJyPg0KJm5ic3A7ICZuYnNwOyAmbmJz
cDsgJm5ic3A7IGFyZSBub3QgZm9yd2FyZGVkLCBhbmQgdGhhdCAoaWkpIHRoZXkgYXJlIG1vZGlm
aWVkIGluIHRyYW5zaXQsIHRoZSBzZWN1cml0eS90cnVzdCBtb2RlbDxicj4NCiZuYnNwOyAmbmJz
cDsgJm5ic3A7ICZuYnNwOyBpcyBzb21ld2hhdCBkaWZmZXJlbnQgZnJvbSB0aGF0IG9mIDcxODEg
YW5kIGNvbnNlcXVlbnRseSBmb3Igd2hhdCA3MTgyIHdhcyBpbml0aWFsbHk8YnI+DQombmJzcDsg
Jm5ic3A7ICZuYnNwOyAmbmJzcDsgd3JpdHRlbiBmb3IuIEkgdGhpbmsgdGhhdCZuYnNwOyBjYWxs
aW5nIG91dCB0aGUgdHJ1c3QgbW9kZWwsIGFuZCBob3cgNzE4MiBhY3R1YWxseSBpcyB1c2VkIGhl
cmUsPGJyPg0KJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7IG1pZ2h0IGJlIHdoYXQgaXMgY2Fs
bGVkIGZvci48YnI+DQo8YnI+DQombmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgQ29udGludWlu
ZyB3aXRoIHRoZSBhc2lkZSwgdGhpcyAqZXNwZWNpYWxseSogYXMgdGhlIGFwcGxpY2FiaWxpdHkg
c3RhdGVtZW50IHNheXM6PGJyPg0KPGJyPg0KJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZu
YnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmcXVvdDtQcm92aWRpbmcgc2VjdXJpdHkgZm9yIGEg
cmVhY3RpdmUgcm91dGluZyBwcm90b2NvbCBjYW4gYmUgZGlmZmljdWx04oCdPGJyPg0KPGJyPg0K
PGJyPg0KVGVybWlub2xvZ3k6PGJyPg0KPGJyPg0KJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7
IE15IGxhc3QgcmV2aWV3IHN1Z2dlc3RlZDo8YnI+DQombmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJz
cDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7IOKAnFRoaXMgaGFzIGJlZW4gYnJvdWdodCB1
cCBvbiB0aGUgbGlzdCBzZXZlcmFsIHRpbWVzIGluIHRoZSBwYXN0LCB3aXRob3V0IGhhdmluZzxi
cj4NCiZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJz
cDsgJm5ic3A7YmVlbiBhZGRyZXNzZWQuPGJyPg0KPGJyPg0KJm5ic3A7ICZuYnNwOyAmbmJzcDsg
Jm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyBUaGVyZSBhcmUg4oCcaG9zdHPigJ0g
YW5kIHRoZXJlIGFyZSDigJxyb3V0ZXJz4oCdIOKAlCB3aG9zZSByb2xlcyBhcmUgd2VsbCBkZWZp
bmVkLjxicj4NCiZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNw
OyAmbmJzcDsg4oCcTm9kZeKAnSBub3Qgc28gbXVjaCDigJQgd2hpY2ggaXMgY2xlYXIgZnJvbSBs
b29raW5nIGF0IHRoZSBkZWZpbml0aW9uIGhlcmU6IOKAnGVpdGhlcjxicj4NCiZuYnNwOyAmbmJz
cDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgQU9EVnYyIHJvdXRl
cnMgb3Igcm91dGVyIGNsaWVudHPigJ0gKHdpdGgg4oCccm91dGVyIGNsaWVudHPigJ0gYmVpbmcg
ZGVmaW5lZCBhcyDigJxhbjxicj4NCiZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsg
Jm5ic3A7ICZuYnNwOyAmbmJzcDsgQU9EVnYyIHJvdXRlciBpcyBhbHNvIGl0cyBvd24gcm91dGVy
IGNsaWVudOKAnSkuPGJyPg0KPGJyPg0KJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNw
OyAmbmJzcDsgJm5ic3A7ICZuYnNwOyBUaGlzIGlzIHZlcnkgbXVjaCByZWxhdGVkIHRvIHRoZSB1
c2Ugb2Yg4oCcUm91dGVyIENsaWVudOKAnSwgYW5kIGJvdGggdGhhdCB0ZXJtLDxicj4NCiZuYnNw
OyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgYW5kIOKA
nG5vZGXigJ0gaW5kaWNhdGl2ZSB0aGF0IHNvbWUgY2xhcml0eSBpcyBuZWVkZWQgaGVyZS48YnI+
DQo8YnI+DQombmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsg
Jm5ic3A7IEFsbCBhIHJvdXRlciBjYXJlcyBhYm91dCBpcyDigJxhbiBhZGRyZXNz4oCdLiBJZiB0
aGF0IGFkZHJlc3MgaXMgb2YgYSBuZXR3b3JrLCBvcjxicj4NCiZuYnNwOyAmbmJzcDsgJm5ic3A7
ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgYSByb3V0ZXIsIG9yIGFuIGludGVy
ZmFjZSAoYW5kLCBpZiBzYWlkIGludGVyZmFjZSBpcyBpbnN0YWxsZWQgaW4gYSByb3V0ZXIgb3Ig
YSBob3N0KTxicj4NCiZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZu
YnNwOyAmbmJzcDsgZG9lc27igJl0IG1hdHRlci48YnI+DQo8YnI+DQombmJzcDsgJm5ic3A7ICZu
YnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7IFNvLCDigJxhbiBhZGRyZXNz
4oCdIGlzIHNvbWV0aGluZyB0aGF0IHRoZSByb3V0aW5nIHByb3RvY29sIHNob3VsZCBjYXJlIGFi
b3V0PGJyPg0KJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7
ICZuYnNwOyBmaW5kaW5nIHBhdGhzIHRvLiBXaGljaCBtZWFucyB0aGF0IGVhY2ggYWRkcmVzcyB0
aGF0IHNob3VsZCBiZSBtYWRlPGJyPg0KJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNw
OyAmbmJzcDsgJm5ic3A7ICZuYnNwOyByZWFjaGFibGUgYnkgdGhlIHJvdXRpbmcgcHJvdG9jb2wg
c2hvdWxkIGJlIGFkdmVydGlzZWQgYnkgKGF0IGxlYXN0KSBvbmUgcm91dGVyPGJyPg0KJm5ic3A7
ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyBpbiB0aGUg
bmV0d29yay48YnI+DQo8YnI+DQombmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZu
YnNwOyAmbmJzcDsgJm5ic3A7IE9uZSB3YXkgb2YgZG9pbmcgdGhhdCB3b3VsZCBiZSB0byBzaW1w
bHkgdGFsayBhYm91dCDigJxBdHRhY2hlZCBOZXR3b3Jrc+KAnSBhczxicj4NCiZuYnNwOyAmbmJz
cDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgaXMgZG9uZSBpbiBS
RkM3MTgxLCB3aGVyZWluIGFuIGFkZHJlc3MgaW5jbHVkZWQgaW4gdGhlIOKAnEF0dGFjaGVkIE5l
dHdvcmsgU2V04oCdPGJyPg0KJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJz
cDsgJm5ic3A7ICZuYnNwOyBpcyBhZHZlcnRpc2VkIGJ5IGFuIE9MU1J2MiByb3V0ZXIuLi4uaW4g
dGhpcyBjYXNlLCB0aGUgZXF1aXZhbGVudCB3b3VsZCBiZSDigJxmb3IgZWFjaDxicj4NCiZuYnNw
OyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgYWRkcmVz
cyBpbiB0aGUgQXR0YWNoZWQgTmV0d29yayBTZXQgb2YgYW4gQU9EVnYyIHJvdXRlciB0aGUgcm91
dGVyIE1VU1Q8YnI+DQombmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAm
bmJzcDsgJm5ic3A7IHJlc3BvbmQgYXV0aG9yaXRhdGl2ZWx5IHRvIGEgUlJFUSwgYW5kIE1VU1Qg
bWFpbnRhaW4gdGhlIGNvcnJlc3BvbmRpbmcgc2VxdWVuY2UgbnVtYmVy4oCdLjxicj4NCjxicj4N
CiZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsg
VGhlIHRleHQsIGFzIGl0IGN1cnJlbnRseSBpcywgaXMgcmVhbGx5IGhhcmQgdG8gcmVhZCwgYW5k
IGEgcmUtZWRpdCBhbG9uZyB0aGVzZSBsaW5lcyB3b3VsZCBnbyBhIGxvbmcgd2F5LuKAnTxicj4N
Cjxicj4NCiZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyBJIG5vdGUgdGhhdCB0aGUgdGVybXMg
4oCcTm9kZeKAnSBhbmQg4oCcUm91dGVyIENsaWVudOKAnSBhcmUgc3RpbGwgdXNlZCwgaW4gdGhl
aXIgb3JpZ2luYWwgZm9ybSw8YnI+DQombmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgYW5kIHRo
YXQgb3RoZXIgdGhhbiBzb21lIHNsaWdodCB3b3Jkc21pdGhpbmcgdGhpcyBjb21tZW50IGhhcyBu
b3QgYmVlbiBhZGRyZXNzZWQgaW4gdGhlIGRvY3VtZW50Ljxicj4NCjxicj4NCiZuYnNwOyAmbmJz
cDsgJm5ic3A7ICZuYnNwOyBJIHJlaXRlcmF0ZSB0aGF0IHRoZSBuZWVkIHRvIHVzZSByb3V0ZXIs
IGhvc3QsIG5vZGUsIGFuZCByb3V0ZXIgY2xpZW50IGluIGFuZCBieSBpdHNlbGYgc2hvdWxkPGJy
Pg0KJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7IGJlIGFuIGluZGljYXRvciB0aGF0IHRpZ2h0
ZW5pbmcgdXAgb2YgdGVybWlub2xvZ3kgaXMgcmVxdWlyZWQuPGJyPg0KPGJyPg0KPGJyPg0KJm5i
c3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7IEkgbWFkZSB0aGUgZm9sbG93aW5nIGNvbW1lbnQgdG8g
Um91dGFibGUgVW5pY2FzdCBJUCBBZGRyZXNzOjxicj4NCjxicj4NCiZuYnNwOyAmbmJzcDsgJm5i
c3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsg4oCcQXJlIHRoZXJlIGFueSB0
ZWNobmljYWwgcmVhc29uIHdoeSBub3Qgc2ltcGx5ICphbnkqIGFkZHJlc3MgY291bGQgYmU8YnI+
DQombmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7
ICZuYnNwO2NvbnNpZGVyZWQgYnkgdGhlIHJvdXRpbmcgcHJvdG9jb2w/PGJyPg0KPGJyPg0KJm5i
c3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJz
cDtNeSB1bmRlcnN0YW5kaW5nLCBidXQgY29ycmVjdCBtZSBpZiBJIGFtIHdyb25nLCBpcyB0aGF0
IGFsbCB0aGF0IGlzIHJlcXVpcmVkIGlzPGJyPg0KJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7
ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDt0aGF0IGFsbCBpbnRlcmZhY2VzIGlu
IGEgZ2l2ZW4gQU9EVnYyIHJvdXRpbmcgZG9tYWluIGhhcyBhbiB1bmlxdWUgYWRkcmVzcy48YnI+
DQo8YnI+DQombmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsg
Jm5ic3A7ICZuYnNwO1RoYXQgc29tZSBvZiB0aGVzZSBhZGRyZXNzZXMgKGJ5IGFuIElQIGFkZHJl
c3NpbmcgYXJjaGl0ZWN0dXJlIGRvY3VtZW50KTxicj4NCiZuYnNwOyAmbmJzcDsgJm5ic3A7ICZu
YnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7aGFzIHNwZWNpYWwgc2VtYW50
aWNzIGFzc29jaWF0ZWQgKHN1Y2ggYXMgYXJlIGxpbmsgbG9jYWxzLCBvciBhcmUgZm9yIHByaXZh
dGU8YnI+DQombmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsg
Jm5ic3A7ICZuYnNwO3VzZSwgb3IgYXJlIGZvciBleGFtcGxlIHVzZSBvbmx5LCBvciBhcmUgZm9y
IG11bHRpY2FzdCkgaXMgb3V0IG9mIHNjb3BlIGhlcmU/PGJyPg0KPGJyPg0KJm5ic3A7ICZuYnNw
OyAmbmJzcDsgJm5ic3A7IEkgc2VlIG5vdGhpbmcgaGFzIGNoYW5nZWQgb24gdGhlIGFib3ZlLCBz
byBsZXQgbWUgYmUgbW9yZSBleHBsaWNpdDogdGhlIHJvdXRpbmcgcHJvdG9jb2wgaXRzZWxmPGJy
Pg0KJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7IChwcm9iYWJseSkgc2hvdWxkIG5vdCBjYXJl
IGFib3V0IHdoYXQga2luZCBvZiBhZGRyZXNzZXMgYXJlIGZpbGxlZCBpbnRvIGl0LiBJcyBhbiAx
OTIuMTYuLzE2IGFkZHJlc3M8YnI+DQombmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgYXBwcm9w
cmlhdGU/IE5vdCBhY3Jvc3MgdGhlIGludGVybmV0LCBidXQgaXQgbWF5IGJlIGluIHNvbWVib2R5
4oCZcyBwcml2YXRlIGRlcGxveW1lbnRzLiBTaG91bGQ8YnI+DQombmJzcDsgJm5ic3A7ICZuYnNw
OyAmbmJzcDsgdGhlIHJvdXRpbmcgcHJvdG9jb2wgYmUg4oCcYWRkcmVzcyBwb2xpY2XigJ0gYW5k
IGlzIGltcGxlbWVudGF0aW9uIG9mIGEg4oCcSSByZWZ1c2UgdG8gcm91dGUgdGhlc2UgYWRkcmVz
c2Vz4oCm4oCdPGJyPg0KJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7IGEgcmVxdWlyZW1lbnQg
Zm9yIGNsYWltaW5nIGNvbmZvcm1hbmNlPyBTdWdnZXN0IHNpbXBseSBzdGF0aW5nIHdoYXQgdGhl
IHJlcXVpcmVtZW50cyBhcmUgdW5kZXI8YnI+DQombmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsg
d2hpY2ggdGhlIHJvdXRpbmcgcHJvdG9jb2wgd2lsbCB3b3JrIOKAlCBhbmQgbGVhdmUg4oCcYWRk
cmVzcyBhc3NpZ25tZW50IHBvbGl0aWNz4oCdIGFzaWRlLjxicj4NCjxicj4NCiZuYnNwOyAmbmJz
cDsgJm5ic3A7ICZuYnNwOyBJIGFsc28gY29udGludWVkOjxicj4NCjxicj4NCiZuYnNwOyAmbmJz
cDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7Tm93LCB3
aXRoIHRoYXQgYmVpbmcgc2FpZCBhbHNvLCB0aGUgV0cgd2FudGVkIHRoYXQgUkZDNzE4MSBzdXBw
b3J0cyBub3Q8YnI+DQombmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAm
bmJzcDsgJm5ic3A7ICZuYnNwO2p1c3QgbXVsdGlwbGUgaW50ZXJmYWNlcywgYnV0IGFsc28gdGhl
IHNhbWUgYWRkcmVzcyB1c2VkIG9uIG11bHRpcGxlIGludGVyZmFjZXM8YnI+DQombmJzcDsgJm5i
c3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwO29mIHRo
ZSBzYW1lIHJvdXRlci4gVGhlcmUgd2VyZSBnb29kIHJlYXNvbnMgZm9yIHRoYXQsIGFuZCB3aGls
ZSBpdCB3YXMgbm90IHRyaXZpYWw8YnI+DQombmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5i
c3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwO3RvIGltcGxlbWVudCwgaXQgdHVybmVkIG91
dCB0byBiZSB0aGUgcmlnaHQgdGhpbmcgdG8gc3VwcG9ydC4gSWYgdGhlcmUgYXJlIHRlY2huaWNh
bDxicj4NCiZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAm
bmJzcDsgJm5ic3A7cmVhc29ucyB3aHkgdGhpcyBpcyBub3Qgc3VwcG9ydGVkIGluIEFPRFZ2MiAo
Zm9yIGV4YW1wbGUsIGlmIHRoaXMgY2Fubm90IGJlPGJyPg0KJm5ic3A7ICZuYnNwOyAmbmJzcDsg
Jm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDttYWRlIHdvcmsgYmVjYXVz
ZSBvZiAmbHQ7cmVhc29uJmd0OykgdGhlbiB0aGF0IHNob3VsZCBiZSBjYWxsZWQgb3V0IGluIHRo
ZTxicj4NCiZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAm
bmJzcDsgJm5ic3A7YXBwbGljYWJpbGl0eSBzdGF0ZW1lbnQgYWxzbz88YnI+DQo8YnI+DQombmJz
cDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7IENvbnZl
cnNlbHksIGlmIGl0IGlzIHBvc3NpYmxlIGluIEFPRFZ2MiwgdGhlbiBJIGRvIG5vdCBiZWxpZXZl
IHRoYXQgaXQgaXMgY2xlYXJseTxicj4NCiZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJz
cDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgc3BlY2lmaWVkIGhvdyAoYXQgbGVhc3QsIGluIHRoZSDi
gJxuYWl2ZeKAnSBvbiBwYXBlciBleGFtcGxlcyBJIGRyZXcgdXAsIHNvbWV0aGluZzxicj4NCiZu
YnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgZW5k
ZWQgdXAgbm90IHdvcmtpbmcpLiBTbyBlaXRoZXIgdGhlIHByb3RvY29sIGFzLWlzIGRvZXMgbm90
IHN1cHBvcnQgaXQgKGJ1dDxicj4NCiZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsg
Jm5ic3A7ICZuYnNwOyAmbmJzcDsgY291bGQgYmUgbWFkZSB0bz8pIG9yIGl0IGlzIHN1cHBvcnRl
ZCAoYnV0IGp1c3QgbmVlZCB0byBiZSBzcGVsbGVkIG91dCksIG9yIGlzPGJyPg0KJm5ic3A7ICZu
YnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyBub3QgcG9zc2li
bGUgKGFuZCBuZWVkIHRvIGJlIGRpc2NsYWltZWQgaW4gdGhlIGFwcGxpY2FiaWxpdHkgc3RhdGVt
ZW50KS48YnI+DQo8YnI+DQombmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNw
OyAmbmJzcDsgJm5ic3A7IFN0YW4gUmF0bGlmZiB3YXMgYSBkcml2aW5nIGZvcmNlIGluIGhvbGRp
bmcgdGhlIFdH4oCZcyBjb2xsZWN0aXZlIGZlZXQgdG8gdGhlIGZpcmU8YnI+DQombmJzcDsgJm5i
c3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7IGluIGdldHRpbmcg
dGhpcyBzdXBwb3J0IGluY2x1ZGVkIGluIFJGQzcxODEsIGFuZCB3b3VsZCBsaWtlbHkgYmUgdGhl
IHJpZ2h0PGJyPg0KJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5i
c3A7ICZuYnNwOyBwZXJzb24gdG8gY29uc3VsdCBvbiB0aGlzIG1hdHRlcj88YnI+DQo8YnI+DQom
bmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgSSBhY3R1YWxseSBoYXZlIG5vdCBzZWVuIGNoYW5n
ZXMsIG9yIGNvbW1lbnRzLCBvbiB0aGlzLiBJbiBPTFNSdjIsIHRoZSBXRyB3YXMgbWFraW5nIGl0
PGJyPg0KJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7IGEgc3Ryb25nIHJlcXVpcmVtZW50IHRo
YXQgaXQgc2hvdWxkIGJlIHBvc3NpYmxlIHRvIHVzZSB0aGUgc2FtZSBJUCBhZGRyZXNzIG9uIGRp
ZmZlcmVudDxicj4NCiZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyBpbnRlcmZhY2VzIG9mIGEg
cm91dGVyLiBJdCB3YXMgc29tZXdoYXQgdGVkaW91cyB0byBkZXNpZ24gYXJvdW5kLCBidXQgaXQg
d2FzIHdvcmtlZCBvdXQsIGFuZDxicj4NCiZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyB0aGUg
Y29uZGl0aW9ucyB1bmRlciB3aGljaCB0aGF0IHdhcyBwb3NzaWJsZSB3ZXJlIGRlZmluZWQgYW5k
IGRvY3VtZW50ZWQuPGJyPg0KPGJyPg0KJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7IEkgd291
bGQgbGlrZSB0byBzZWUgdGhlIHNhbWUgZG9uZSBmb3IgdGhpcyBwcm90b2NvbC48YnI+DQo8YnI+
DQombmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgSSBhbHNvIG5vdGUgdGhhdCB0aGlzIGlzIG5v
dCB1bnJlbGF0ZWQgdG8gUkZDNjYyMS1kaXNjdXNzaW9ucy4gRm9yIGV4YW1wbGUsIHdoZW4gc2Vs
ZWN0aW5nPGJyPg0KJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7IFMtTVBScyBvbiBhIG11bHRp
LWludGVyZmFjZSBhbmQgbXVsdGktYWRkcmVzcy1wZXItaW50ZXJmYWNlIHJvdXRlciwgY2FyZSBt
dXN0IGJlIHRha2VuPGJyPg0KJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7IGxlYXN0IHRoaW5n
cyB3b27igJl0IHdvcmsuIFNvLCBpZiAoYW5kIHRoaXMgbGlua3MgYmFjayB0byBwcmV2aW91cyBt
YWlscykgUkZDNjYyMSBpcyBhPGJyPg0KJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7IHJlcXVp
cmVtZW50IG9yIGRlc2lyZSBmb3IgdGhpcyBwcm90b2NvbCwgdGhlbiB0aGVyZSBhcmUgc29tZSBj
b25zaWRlcmF0aW9ucyByZXF1aXJlZCBoZXJlLjxicj4NCjxicj4NCiZuYnNwOyAmbmJzcDsgJm5i
c3A7ICZuYnNwOyBJIHNlZSB0aGF0IHRoZSBkZWZpbml0aW9uIG9mIOKAnFJvdXRlciBDbGllbnTi
gJ0gaGFzIGNoYW5nZWQgdG8gYmU8YnI+DQo8YnI+DQombmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJz
cDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7IOKAnEFuIGFkZHJlc3Mgb3IgYWRkcmVzcyBy
YW5nZeKApnRoZSBBT0RWdjIgcm91dGVy4oCZcyBpbnRlcmZhY2UgYWRkcmVzc2VzPGJyPg0KJm5i
c3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJz
cDthcmUgYWxzbyBjb25maWd1cmVkIGFzIHJvdXRlciBjbGllbnRz4oCdPGJyPg0KPGJyPg0KJm5i
c3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7IEJldHRlciB0aGFuIGJlZm9yZSwgYnV0IHN0aWxsIG1p
c3NpbmcgdGhlIHRhcmdldC4gVGhlIHRlcm0g4oCcUm91dGVyIENsaWVudOKAnSBpcywgYXMgSSBp
bmRpY2F0ZWQ8YnI+DQombmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgbnVtZXJvdXMgdGltZXMg
YmVmb3JlLCBvZGQuPGJyPg0KPGJyPg0KJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7IEJ1dCB0
aGUgc2Vjb25kIHBhcnQgb2YgdGhlIHNlbnRlbmNlLCBkb2VzIHRoYXQgbWVhbiAod2hhdCBpdCBz
YXlzKSB0aGF0IHRoZSBpbnRlcmZhY2VzPGJyPg0KJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7
IG11c3QgYmUgY29uZmlndXJlZCBzcGVjaWFsbHksIHNvIGFzIHRvIGJlIGFibGUgdG8gYmUg4oCc
cm91dGVyIGNsaWVudHPigJ0/IFRoYXQgY2Fu4oCZdCBiZSB0cnVlLjxicj4NCjxicj4NCiZuYnNw
OyAmbmJzcDsgJm5ic3A7ICZuYnNwOyBXaGF0IHlvdSBsaWtlbHkgbWVhbiBpczo8YnI+DQo8YnI+
DQombmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7
IOKAnEFuIEFPRFZ2MiByb3V0ZXIgaXMgY29uZmlndXJlZCBzbyBhcyB0byBjb25zaWRlciBpdHMg
b3duIGludGVyZmFjZXMgYXMgcGFydCBvZjxicj4NCiZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNw
OyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7dGhlIGxvY2FsbHkgYXR0YWNoZWQg
bmV0d29yayBzZXTigJ0gPzxicj4NCjxicj4NCiZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyBZ
b3UgY29uZmlndXJlIHRoZSByb3V0ZXIsIHJpZ2h0PyBObyBzcGVjaWFsIOKAnGludGVyZmFjZSBj
b25maWd1cmF0aW9uIHByb3BlcnRpZXPigJ0gYXJlIHJlcXVpcmVkPGJyPg0KJm5ic3A7ICZuYnNw
OyAmbmJzcDsgJm5ic3A7IGZvciBhbiBpbnRlcmZhY2UgdG8gYmUgYW5ub3VuY2FibGUgYnkmbmJz
cDsgYW4gQU9EVnYyIHJvdXRlcj88YnI+DQombmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgKEFu
ZCwgZ2V0dGluZyByaWQgb2Ygbm9kZSB3b3VsZCBhY3R1YWxseSBtYWtlIHRoZSBkZWZpbml0aW9u
IHNob3J0ZXIgYW5kIG5pY2VyKTxicj4NCjxicj4NCiZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNw
OyBOb3csIHNuaXBwaW5nIG91dCBmcm9tIHRoZSBhcHBsaWNhYmlsaXR5IHN0YXRlbWVudDo8YnI+
DQo8YnI+DQombmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsg
Jm5ic3A7ICZxdW90O011bHRpLWhvbWluZyBvZiBhbiBJUCBhZGRyZXNzIGlzIG5vdCBzdXBwb3J0
ZWQgYnkgQU9EVnYyLCBhbmQgdGhlcmVmb3JlIGE8YnI+DQombmJzcDsgJm5ic3A7ICZuYnNwOyAm
bmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyBSb3V0ZXIgQ2xpZW50LCBp
LmUuIGFuIElQIEFkZHJlc3MsJm5ic3A7IOKApiAmcXVvdDs8YnI+DQo8YnI+DQombmJzcDsgJm5i
c3A7ICZuYnNwOyAmbmJzcDsg4oCmZXZpZGVuY2UgdG8gdGhlcmUgYmVpbmcgc29tZSByZWR1bmRh
bnQgdGVybWlub2xvZ3kgaGVyZSB0byB3ZWVkIGF3YXkuPGJyPg0KPGJyPg0KJm5ic3A7ICZuYnNw
OyAmbmJzcDsgJm5ic3A7IFRoZSBiZWxvdyBpcyBhIGxpdHRsZSBiaXQgb2YgYSBtZXRhLWNvbW1l
bnQsIEkgYW0gbm90IHF1aXRlIHN1cmUgd2hhdCBJIHRoaW5rIGhlcmUuPGJyPg0KJm5ic3A7ICZu
YnNwOyAmbmJzcDsgJm5ic3A7IFRoZSBkZWZpbml0aW9ucyBmb3IgVGFyZ2V0IE5vZGUgYW5kIHN1
Y2ggd2VyZSBjb25mdXNpbmcgYmVmb3JlLiBUaGV5IHN0aWxsIGFyZSwgc29tZXdoYXQuPGJyPg0K
PGJyPg0KJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7IEkgdGhpbmsgdGhhdCBpdCBtYXkgYmUg
YmVjYXVzZSB0aGUgZGVmaW5pdGlvbnMgbm93IHVzZWQgYXJlIHNpbXBseSBjb3B5LXBhc3RlZCBv
dXQgZnJvbSB0aGU8YnI+DQombmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgdGFibGVzIGluIHRo
ZSBwcmV2aW91cyB2ZXJzaW9uLCBmb3IgZXhhbXBsZTo8YnI+DQo8YnI+DQombmJzcDsgJm5ic3A7
ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7IEFuIEFPRFZ2MiBEYXRh
IEVsZW1lbnQgY29udGFpbmluZyB0aGUgZGVzdGluYXRpb24gYWRkcmVzcyBvZiB0aGU8YnI+DQom
bmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7IElQ
IHBhY2tldCB0cmlnZ2VyaW5nIHJvdXRlIGRpc2NvdmVyeS48YnI+DQo8YnI+DQombmJzcDsgJm5i
c3A7ICZuYnNwOyAmbmJzcDsgT0ssIEkgY2FuIHRyYWNlIGJhY2sgYW5kIHNlZSB0aGF0IGEgRGF0
YSBFbGVtZW50IGlzIHNvbWV0aGluZyB0aGF0IGV4aXN0cyBpbnNpZGUgYTxicj4NCiZuYnNwOyAm
bmJzcDsgJm5ic3A7ICZuYnNwOyBwcm90b2NvbCBtZXNzYWdlLiBUbyBtZSwgaG93ZXZlciwgdGhh
dOKAmXMgbm90IHJlYWxseSBnZW5lcmFsIHRlcm1pbm9sb2d5IGFzIHN1Y2gsIGJ1dDxicj4NCiZu
YnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyBwYXJ0IG9mIHRoZSBzcGVjaWZpY2F0aW9uIG9mIGEg
cGFja2V0IGZvcm1hdCAtIG9yIHJhdGhlciwgaXQgaXMgdGhlIG5vdGF0aW9uIHRoYXQgeW91IHVz
ZTxicj4NCiZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyB3aGVuIGRlc2NyaWJpbmcgYW4gYWxn
b3JpdGhtLiBCeSB0aGUgd2F5LCB3aHkgYXJlIHNvbWUgbm90YXRpb25zIGluIENhbWVsQ2FzZTxi
cj4NCiZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyB3aGVyZWFzIG90aGVycyBoYXZlIGEgc3Bh
Y2UgaW4gdGhlbSwgZS5nLiDigJxUYXJnZXQgTm9kZeKAnSBhbmQg4oCcVGFyZ01ldHJpY+KAnSwg
Ym90aCBvZiB3aGljaDxicj4NCiZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyBhcmUgRGF0YSBF
bGVtZW50cz8gV291bGQgYmUgZ29vZCB3aXRoIGEgY29uc2lzdGVudCBhcHByb2FjaCBoZXJlLjxi
cj4NCjxicj4NCiZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyBJICp0aGluayogdGhhdCBpdCB3
b3VsZCBiZSBiZXR0ZXIgdG8gdGFrZSBhbGwgdGhvc2Ug4oCcRGF0YSBFbGVtZW504oCdIGJpdHMg
YW5kIG1vdmUgdG8gYSBzZXBhcmF0ZTxicj4NCiZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyBz
ZWN0aW9uIChvciBzdWJzZWN0aW9uKSB0byB0aGUgdGVybWlub2xvZ3ksIGFuZCB0aGVuIGtlZXAg
YWxsIHRoZSDigJxvdGhlciBzdHVmZuKAnSAoTmVpZ2hib3IsIOKApik8YnI+DQombmJzcDsgJm5i
c3A7ICZuYnNwOyAmbmJzcDsgaW4gaXRzIG93biBzZWN0aW9uLjxicj4NCjxicj4NCiZuYnNwOyAm
bmJzcDsgJm5ic3A7ICZuYnNwOyBJ4oCZbSBhIGdyZWF0IGZhbiBvZiBjYWxsaW5nIHRoaXMgc2Vj
dGlvbiDigJxUZXJtaW5vbG9neSBhbmQgTm90YXRpb27igJ0gYW5kIHRoZW4gaGF2aW5nIHR3bzxi
cj4NCiZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyBzdWJzZWN0aW9ucywgb25lIHdoaWNoIGlz
IOKAnFRlcm1pbm9sb2d54oCdIGFuZCBvbmUgd2hpY2ggaXMg4oCcTm90YXRpb27igJ0sIHdpdGgg
dGhlPGJyPg0KJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7IFRhcmdNZXRyaWMgYW5kIFRhcmdl
dCBOb2RlIGJlaW5nIGZpcm1seSBpbiB0aGUgbGF0dGVyLjxicj4NCjxicj4NCiZuYnNwOyAmbmJz
cDsgJm5ic3A7ICZuYnNwOyBJIG1hZGUgYSBjb21tZW50Ojxicj4NCiZuYnNwOyAmbmJzcDsgJm5i
c3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJnF1b3Q7U2Vjb25kLCBzaG91
bGQg4oCcdmFsaWQgcm91dGXigJ0gbm90IGJlIHF1YWxpZmllZCBieSDigJx0byBhIHNwZWNpZmlj
IGFkZHJlc3PigJ0/4oCdPGJyPg0KPGJyPg0KJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7IFdo
aWNoIHdhcyBub3QgYWRkcmVzc2VkLjxicj4NCjxicj4NCiZuYnNwOyAmbmJzcDsgJm5ic3A7ICZu
YnNwOyBJIGFsc28gbWFkZSBhIGNvbW1lbnQgb24gJnF1b3Q7VW5yZWFjaGFibGUgQWRkcmVzc+KA
nSAtIEkgYW0gZ2xhZCBJIGRpZCwgYmVjYXVzZSBJIGFwcGFyZW50bHk8YnI+DQombmJzcDsgJm5i
c3A7ICZuYnNwOyAmbmJzcDsgaGFkIGEgZGlmZmVyZW50IHVuZGVyc3RhbmRpbmcgdGhhbiB3aGF0
IHdhcyBpbnRlbmRlZC4gSSBub3cgc2VlIHRoYXQgYW4gVW5yZWFjaGFibGUgQWRkcmVzczxicj4N
CiZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyBieSBkZWZpbml0aW9uIGlzIGFuIGFkZHJlc3Mg
bGlzdGVkIGluIGEgUkVSUiBtZXNzYWdlLCBhbmQgbm90IHRoZSBzYW1lIGFzIGFuIGFkZHJlc3Mg
dG88YnI+DQombmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgd2hpY2ggbm8gcm91dGUgaGFzIHll
dCZuYnNwOyBiZWVuIGRpc2NvdmVyZWQ/IElmIHllcywgdGhlbiBwbGVhc2UgdXNlIGEgZGlmZmVy
ZW50IHRlcm0sIHN1Y2ggYXM8YnI+DQombmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsg4oCcRm9y
bWVybHlSZWFjaGFibGVBZGRyZXNz4oCdIG9yIHNvbWV0aGluZyBvZiB0aGUgc29ydD88YnI+DQo8
YnI+DQpBcHBsaWNhYmlsaXR5IHN0YXRlbWVudDxicj4NCjxicj4NCiZuYnNwOyAmbmJzcDsgJm5i
c3A7ICZuYnNwOyBGaXJzdCwgSSB3b3VsZCBsaWtlIHRvIHJlY29nbml6ZSB0aGUgZWZmb3J0cyBt
YWRlIHRvIGltcHJvdmUgdGhpcyBzaW5jZSBsYXN0IHJldmlldy4gVGhhbmtzPGJyPg0KPGJyPg0K
Jm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7IFNlY29uZCwgdGhlIGRvY3VtZW50IHN0YXRlczo8
YnI+DQo8YnI+DQombmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJz
cDsgJm5ic3A7ICZxdW90O0FPRFZ2MiBzdXBwb3J0cyByb3V0ZXJzIHdpdGggbXVsdGlwbGUgaW50
ZXJmYWNlcywgYXMgbG9uZyBhcyBlYWNoPGJyPg0KJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7
ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7aW50ZXJmYWNlIGNvbmZp
Z3VyZWQgZm9yIEFPRFZ2MiBoYXMgYSB1bmljYXN0IElQIGFkZHJlc3MuJm5ic3A7IEEgcm91dGVy
PGJyPg0KJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZu
YnNwOyAmbmJzcDsgJm5ic3A7bWF5IHVzZSB0aGUgc2FtZSBJUCBhZGRyZXNzIG9uIG11bHRpcGxl
IGludGVyZmFjZXMuJm5ic3A7IEFkZHJlc3M8YnI+DQombmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJz
cDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDthc3NpZ25tZW50IHBy
b2NlZHVyZXMgYXJlIG91dCBvZiBzY29wZSBmb3IgQU9EVnYyLuKAnTxicj4NCjxicj4NCiZuYnNw
OyAmbmJzcDsgJm5ic3A7ICZuYnNwOyBJcyB0aGF0IHRydWU/IEdyYW50ZWQsIEkgaGF2ZSBub3Qg
d29ya2VkIHRoaXMgdGhyb3VnaCBpbiBkZXRhaWwsIGJ1dCBJIGNhbiBwcmVzZW50IGEgY291bnRl
ci1leGFtcGxlOjxicj4NCiZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyB0aGUgdXNlIG9mIFJG
QzY2MjEgbWVhbnMgdGhhdCB0aGVyZSBjZXJ0YWlubHkgYXJlIHNvbWUgY29uc3RyYWludHMgdGhh
dCBtdXN0IGJlIHJlc3BlY3RlZCBsZWFzdDxicj4NCiZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNw
OyB2YXJpb3VzIGZsb29kaW5nIG9wdGltaXphdGlvbnMgbWF5IG5vdCB3b3JrLjxicj4NCjxicj4N
CiZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyBTZWNvbmRseSwgaWYgdGhlIG11bHRpcGxlLWlu
dGVyZmFjZXMtd2l0aC1zYW1lLWFkZHJlc3MgYXJlIG9uIHRoZSBzYW1lIEwyLCBhbmQgdGhpcyBp
cyB3aGF0IEk8YnI+DQombmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgaGF2ZSBub3Qgd29ya2Vk
IHRocm91Z2gsIGFyZSB0aGVyZSBhbnkgc2l0dWF0aW9ucyB0aGF0IHdpbGwgbm90IHdvcms/PGJy
Pg0KPGJyPg0KJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7IFRoZSBpbW1lZGlhdGVseSBwcmV2
aW91cyB2ZXJzaW9uIG9mIHRoaXMgc3BlY2lmaWNhdGlvbiByZWFkOjxicj4NCjxicj4NCiZuYnNw
OyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJnF1b3Q7
QU9EVnYyIHN1cHBvcnRzIHJvdXRlcnMgd2l0aCBtdWx0aXBsZSBpbnRlcmZhY2VzLCBhcyBsb25n
IGFzIGVhY2g8YnI+DQombmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAm
bmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDtpbnRlcmZhY2UgY29uZmlndXJlZCBmb3IgQU9EVnYy
IGhhcyBpdHMgb3duIHVuaWNhc3Qgcm91dGFibGUgSVAgYWRkcmVzcyZxdW90Ozxicj4NCjxicj4N
CiZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyBTbyB3aGF0IGNoYW5nZWQgdGhhdCBtZWFucyB0
aGF0IGVhY2ggaW50ZXJmYWNlIG5vIGxvbmdlciBuZWVkcyBpdHMgKm93biogdW5pY2FzdCBhZGRy
ZXNzPzxicj4NCjxicj4NCiZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyBJIHBvaW50ZWQgb3V0
IHRvIHRoZSBBcHBsaWNhYmlsaXR5IFN0YXRlbWVudDo8YnI+DQo8YnI+DQombmJzcDsgJm5ic3A7
ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7IEkgdGhpbmsgdGhhdCBh
cHBlbmRpeCBCIG5lZWRzIHRvIGJlIHJlbW92ZWQuIEVzc2VudGlhbGx5LCBpdCBtYWtlcyBjbGFp
bXMgdGhhdCBpdCBpczxicj4NCiZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5i
c3A7ICZuYnNwOyAmbmJzcDsgcG9zc2libGUgdG8gZG8gbXVsdGktaG9taW5nIOKAlCBidXQgbmVp
dGhlciBzcGVjaWZpZXMgaG93IGl0IGlzIGRvbmUsIG5vciBnaXZlczxicj4NCiZuYnNwOyAmbmJz
cDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgcG9pbnRlcnMgdG8g
ZG9jdW1lbnRzIHRoYXQganVzdGlmeSB0aGUgY2xhaW0uPGJyPg0KPGJyPg0KJm5ic3A7ICZuYnNw
OyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyBBT0RWdjIgZG9lcyBu
b3Qgc3VwcG9ydCBtdWx0aS1ob21pbmcg4oCUIHRoYXTigJlzIGNsZWFyLCBhbmQgaXQgaXMgZmlu
ZSB0aGF0IGl0IGlzPGJyPg0KJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJz
cDsgJm5ic3A7ICZuYnNwOyBjYWxsZWQgb3V0IGhlcmUuIFRoYW5rIHlvdSBmb3IgdGhhdC48YnI+
DQo8YnI+DQombmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsg
Jm5ic3A7IE5vdywgd2l0aCB0aGF0IGJlaW5nIHNhaWQsIEkgYW0gdG9ybiBiZXR3ZWVuIGJlaW5n
IHNhdGlzZmllZCB0aGF0IGl0IGlzIGNhbGxlZCBvdXQgb248YnI+DQombmJzcDsgJm5ic3A7ICZu
YnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7IG9uZSBoYW5kLCBhbmQgd2Fu
dGluZyB0byBoYXZlIOKAnG11bHRpIGhvbWluZ+KAnSBvbiB0aGUgb3RoZXIgaGFuZC4gUkZDNzE4
MSBzdXBwb3J0czxicj4NCiZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7
ICZuYnNwOyAmbmJzcDsgbXVsdGktaG9taW5nLCBGV0lXLjxicj4NCjxicj4NCiZuYnNwOyAmbmJz
cDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgSSBiZWxpZXZlIHRo
YXQgdGhpcyBhbHNvIHdvdWxkIG1lcml0IHNvbWUgZXhwbGljaXQgZGlzY3Vzc2lvbiBieSB0aGUg
V0csIGluIG9yZGVyIHRvPGJyPg0KJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAm
bmJzcDsgJm5ic3A7ICZuYnNwOyB1bmRlcnN0YW5kIGlmIHRoaXMgZGVzaWduIGRlY2lzaW9uIGlz
IGFjY2VwdGFibGU/PGJyPg0KPGJyPg0KJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7IEkgc2Vl
IHRoYXQgQXBwZW5kaXggQiBzdGlsbCBpcyBpbiB0aGUgZG9jdW1lbnQsIGFuZCBJIGRvIG5vdCBy
ZWNhbGwgaGF2aW5nIHNlZW4gdGhpcyBkaXNjdXNzZWQ8YnI+DQombmJzcDsgJm5ic3A7ICZuYnNw
OyAmbmJzcDsgb24gdGhlIG1haWxpbmcgbGlzdC4gU2ltcGx5IHJlbW92aW5nIHRoZSByZWZlcmVu
Y2UgZnJvbSB0aGUgQXBwbGljYWJpbGl0eSBTdGF0ZW1lbnQgdG8gQXBwZW5kaXggQjxicj4NCiZu
YnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyBkb2VzIG5vdCBhZGRyZXNzIHRoZSBpc3N1ZSB0aGF0
IEkgcmFpc2VkIGluIG15IHByZXZpb3VzIHJldmlldy48YnI+DQo8YnI+DQpUbyA0LjEsIEkgbWFk
ZSB0aGUgZm9sbG93aW5nIGNvbW1lbnQ6PGJyPg0KPGJyPg0KJm5ic3A7ICZuYnNwOyAmbmJzcDsg
Jm5ic3A7ICZxdW90O0lzIHRoaXMgYSBzaG91bGQsIG9yIGEgU0hPVUxEPyBJZiB0aGUgbGF0dGVy
LCBzaG91bGQgaXQgYmUgYSBNVVNUPzxicj4NCjxicj4NCiZuYnNwOyAmbmJzcDsgJm5ic3A7ICZu
YnNwOyAmbmJzcDsgSW4gZ2VuZXJhbCwgdGhlcmUgYXJlIGEgbG90IG9mIHN1Y2gg4oCcbWF5YmUg
bm9ybWF0aXZlIGxhbmd1YWdl4oCdIHRocm91Z2ggdGhlPGJyPg0KJm5ic3A7ICZuYnNwOyAmbmJz
cDsgJm5ic3A7ICZuYnNwO2RvY3VtZW50LCBhbmQgSSB3b3VsZCBtdWNoIGxpa2UgdG8gc2VlIGFu
IGVkaXRvcmlhbCBwYXNzIOKAlCBlc3NlbnRpYWxseSBhbGw8YnI+DQombmJzcDsgJm5ic3A7ICZu
YnNwOyAmbmJzcDsgJm5ic3A7bWF5L3Nob3VsZC8gbXVzdCBhbmQgZnJpZW5kcyBjYXJlZnVsbHkg
ZXZhbHVhdGVkIGFzIGlmIHRoZXkgc2hvdWxkIGJlY29tZTxicj4NCiZuYnNwOyAmbmJzcDsgJm5i
c3A7ICZuYnNwOyAmbmJzcDsyMTE5LXRlcm1zLCBhbmQgLi4uIG1vcmUgaW1wb3J0YW50bHkgKGl0
IGhhcyBiZWVuIGNhbGxlZCBvdXQgYmVmb3JlLCBmd2l3KTxicj4NCiZuYnNwOyAmbmJzcDsgJm5i
c3A7ICZuYnNwOyAmbmJzcDtxdWl0ZSBhIGJpdCBvZiBzaG91bGQvU0hPVUxEIHdoaWNoIG91Z2h0
IHRvIGJlIHRyYW5zZm9ybWVkIGludG8gTVVTVC48YnI+DQo8YnI+DQombmJzcDsgJm5ic3A7ICZu
YnNwOyAmbmJzcDsgR2VuZXJhbGx5LCBhaW1pbmcgZm9yIGEgdmVyeSBhIGxvdyBudW1iZXIgb2Yg
U0hPVUxEIGlzIGEgZ29vZCBkZXNpZ24gbWV0cmljIGZvciBhIGRvY3VtZW504oCdPGJyPg0KPGJy
Pg0KQXNpZGUgZnJvbSB0aGUgZ2VuZXJhbCBjb21tZW50IG9uIDIxMTktbGFuZ3VhZ2UsIHdoeSBp
cyB0aGlzIGEgU0hPVUxEPzxicj4NCjxicj4NClRvIDQuMiwgSSBtYWRlIHRoZSBmb2xsb3dpbmcg
Y29tbWVudDo8YnI+DQo8YnI+DQombmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgQXMgaW5kaWNh
dGVkIGVhcmxpZXIsIEkgYmVsaWV2ZSB0aGF0IHRoZSB0ZXJtIOKAnFJvdXRlciBDbGllbnTigJ0g
aXMgaWxsIGNob3Nlbi48YnI+DQombmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgSSBiZWxpZXZl
IHRoYXQgaXQgaXMgbW9yZSBhcHByb3ByaWF0ZWx5IGFuIOKAnEF0dGFjaGVkIE5ldHdvcmsgU2V0
4oCdIHNpbmNlIOKAlDxicj4NCiZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyBhcyBpbmRpY2F0
ZWQgcHJldmlvdXNseSDigJQgdGhlIHRlcm0g4oCcUm91dGVyIENsaWVudOKAnSBpcyBhbWJpZ3Vv
dXMuIEkgYW0gcGxlYXNlZDxicj4NCiZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyB0byBzZWUs
IHRob3VnaCwgdGhhdCB0aGlzIOKAnFJvdXRlciBDbGllbnQgTGlzdOKAnSBpbiByZWFsaXR5IGlz
IGFuIOKAnEF0dGFjaGVkIE5ldHdvcmsgU2V04oCdPGJyPg0KJm5ic3A7ICZuYnNwOyAmbmJzcDsg
Jm5ic3A7IGFuZCBzbyB0aGF0IGNoYW5nZSBzaG91bGQgYmUgKHJlbGF0aXZlbHkpIGVhc3kuPGJy
Pg0KPGJyPg0KVGhlIGFib3ZlIGNvbW1lbnQgc3RpbGwgaXMgYXBwbGljYWJsZSB0byB0aGlzIHJl
dmlzaW9uLDxicj4NCjxicj4NClRvIDQuMiwgSSBtYWRlIHRoZSBmb2xsb3dpbmcgY29tbWVudDo8
YnI+DQo8YnI+DQombmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgQWxzbywgSSByZWNvbW1lbmQg
dG8gbm90IHNheSDigJxzdWJuZXTigJ0g4oCUIGhvdyBhYm91dCByZXBocmFzaW5nIHRvIOKAnElm
IGEgcHJlZml4PGJyPg0KJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7IGlzIGluY2x1ZGVkIGlu
IHRoZSBhdHRhY2hlZCBuZXR3b3JrIHNldCBvZiBhbiBBT0RWdjIgcm91dGVyLCB0aGVuIHRoYXQg
QU9EVnYyPGJyPg0KJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7IHJvdXRlciBNVVNUIHByb3Zp
ZGUgY29ubmVjdGl2aXR5IGZvciwgaS5lLiBhbnN3ZXIgdG8gUlJFUXMgYW5kIG1haW50YWluPGJy
Pg0KJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7IHNlcXVlbmNlIG51bWJlcnMgZm9yLCBhbGwg
YWRkcmVzc2VzIGZyb20gd2l0aGluIHRoYXQgcHJlZml4LuKAnTxicj4NCjxicj4NCkkgbm90ZSB0
aGF0IHdoaWxlIHRoZSB0ZXJtIGhhcyBiZWVuIHJlbW92ZWQgZnJvbSBzZWN0aW9uIDQsIHRoZXJl
4oCZcmUgNCBsaW5nZXJpbmcgaW5zdGFuY2VzIG9mIHRoaXMgdGVybSBpbiB0aGUgZG9jdW1lbnQs
IHRoYXQgY291bGQgZWFzaWx5IGJlIHJlbW92ZWQuPGJyPg0KPGJyPg0KSSBBbHNvIG1hZGUgYSBj
b21tZW50IGFib3V0IEFwcGVuZGl4IEIgaW4gbXkgcHJldmlvdXMgcmV2aWV3LCB3aGljaCBpcyBy
ZWZlcmVuY2VkIGhlcmUuIFRoYXQgY29tbWVudCBzdGlsbCBhcHBsaWVzLjxicj4NCjxicj4NClRv
IFNlY3Rpb24gNC4zLCBJIG5vdGljZWQ6PGJyPg0KPGJyPg0KJm5ic3A7ICZuYnNwOyAmbmJzcDsg
Jm5ic3A7IERvZXMgc2VjdGlvbiA2LjIgZGVzY3JpYmUgaG93IHRvIG1vbml0b3IgYW4gZXN0YWJs
aXNoZWQgYWRqYWNlbmN5PGJyPg0KJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7IG9ubHksIG9y
IGhvdyB0byBkaXNjb3ZlciBuZWlnaGJvdXJpbmcgQU9EVnYyIHJvdXRlcnM/IExvb2tpbmcgaW4g
Ni4yLCBJIHNlZTxicj4NCjxicj4NCiZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsg
Jm5ic3A7ICZuYnNwOyAmbmJzcDsg4oCcTm90IGV2ZXJ5IHBhaXIgb2YgbmVpZ2hib3Jpbmcgcm91
dGVycyB3aWxsIG5lY2Vzc2FyaWx5IGZvcm0gYW4gYWRqYWNlbmN5LOKAnSDigJQ8YnI+DQombmJz
cDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNw
O3NvIGl0IGxpa2VseSBpc27igJl0IDYuMiB0aGF0IHRlbGxzIG1lIGhvdyB0byBtYWludGFpbiB0
aGlzIHRhYmxlPzxicj4NCjxicj4NCiZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyBJbiBzaG9y
dCwg4oCcQSBuZWlnaGJvdXIgdGFibGUgTVVTVCBiZSBtYWludGFpbmVk4oCdIOKAlCB3aGVyZSBj
YW4gSSBmaW5kIGluZm9ybWF0aW9uIG9uIGhvdyB0byBkbyB0aGlzPzxicj4NCjxicj4NCiZuYnNw
OyAmbmJzcDsgJm5ic3A7ICZuYnNwOyBTZWN0aW9uIDYuMiBzdGF0ZXM6PGJyPg0KPGJyPg0KJm5i
c3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyDigJxU
aGUgZGVmYXVsdCBhcHByb2FjaCBmb3IgbW9uaXRvcmluZyBiaWRpcmVjdGlvbmFsIGNvbm5lY3Rp
dml0eSB0byB0aGUgbmV4dCBob3AgdG93YXJkPGJyPg0KJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5i
c3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDtPcmlnQWRkciBpcyB0byByZXF1
ZXN0IGFja25vd2xlZGdlbWVudCBvZiBSb3V0ZSBSZXBseSBtZXNzYWdlcy7igJ08YnI+DQo8YnI+
DQombmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7
IFRoYXQgY2VydGFpbmx5IHdpbGwgdGVsbCBtZSBpZiBhIGxpbmsgb3ZlciB3aGljaCBhbiBSUkVQ
IGlzIHNlbnQgaXMgYmktZGlyZWN0aW9uYWwsPGJyPg0KJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5i
c3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyBidXQgd2lsbCBub3QgbWFpbnRhaW4gYSDi
gJxuZWlnaGJvciB0YWJsZeKAnS48YnI+DQo8YnI+DQombmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJz
cDsgU28gaG93IGlzIHRoaXMgZG9uZT8gT3IsIGlzIHRoZSDigJxOZWlnaGJvciBUYWJsZeKAnSBu
b3Qgc3VwcG9zZWQgdG8gY29udGFpbiB0aGU8YnI+DQombmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJz
cDsgY29tcGxldGUgc2V0IG9mIG5laWdoYm91cnM/IFdoYXQgaW5mb3JtYXRpb24g4oCcLi4uTVVT
VCBiZSBtYWludGFpbmVk4oCdIHRoZW4sIGluIHRoaXMgdGFibGU/PGJyPg0KPGJyPg0KJm5ic3A7
ICZuYnNwOyAmbmJzcDsgJm5ic3A7IFRoaXMgaXMgdmVyeSB1bmNsZWFyLCBJIHdvdWxkIG5vdCBr
bm93IGhvdyB0byBpbXBsZW1lbnQgYSBtZWNoYW5pc20gdGhhdCBwb3B1bGF0ZXMgdGhpczxicj4N
CiZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyDigJxOZWlnaGJvciBUYWJsZeKAnSB3aXRoIHRo
ZSBuZWVkZWQgaW5mb3JtYXRpb24gaGVyZS48YnI+DQo8YnI+DQpJIHNlZSBubyAocmVsZXZhbnQp
IGNoYW5nZXMgdG8gNi4yIG5vciB0byA0LjMgc28gSSBhc3N1bWUgdGhhdCB0aGlzIGNvbW1lbnQg
aGFzIG5vdCBiZWVuIGFkZHJlc3NlZDxicj4NCjxicj4NCkkgYW0gdGhyb3dpbmcgdGhpcyBpbiBo
ZXJlLCBhcyBJIGFtIHN1cmUgdGhhdCBJIGNvbW1lbnRlZCBvbiB0aGF0IGluIHRoZSBwcmV2aW91
cyByZXZpZXcsIGJ1dCBJIGRvIG5vdCBzZWUgdGhhdCBhZGRyZXNzZWQ6IGlzIEFwcGVuZGl4IEMg
bm9ybWF0aXZlLCBvciBub3Q/IEl0IHJlcHJlc2VudHMg4oCcIGEgc2Vjb25kIHNwZWNpZmljYXRp
b24gb2YgdGhlIHByb3RvY29sLCBpbiBhIGRpZmZlcmVudCBsYW5ndWFnZeKAnSBmcm9tIHRoZSBt
YWluIHBhcnQgb2YNCiB0aGUgc3BlY2lmaWNhdGlvbi4gSSBoYXZlIG5vdCB3YWxrZWQgdGhyb3Vn
aCBhbmQgbWFkZSAyMDAlIHN1cmUgdGhhdCBib3RoIGFyZSBwZXJmZWN0bHkgYWxpZ25lZCBhbmQg
dGhhdCB0aGVyZSBhcmUgbm8gYW1iaWd1aXRpZXMsIGJ1dCBoYXZpbmcgdHdvIGRpZmZlcmVudCBz
cGVjaWZpY2F0aW9ucyBvZiBhIHByb3RvY29sIGlzIGEgcmVjaXBlIGZvciBkaXNhc3Rlci4mbmJz
cDsgUGxlYXNlIGVpdGhlciBtYWtlIDIwMDAlIHN1cmUgdGhhdCB0aGV5IGFyZQ0KIHNwZWNpZnlp
bmcgdGhlIHNhbWUgdGhpbmcgd2l0aG91dCBhbWJpZ3VpdGllcywgb3IgcmVtb3ZlIG9uZS48YnI+
DQo8YnI+DQpUbyBzZWN0aW9uIDQuNCwgSSB3cm90ZTo8YnI+DQo8YnI+DQombmJzcDsgJm5ic3A7
ICZuYnNwOyAmbmJzcDsgJnF1b3Q7d291bGQgbGlrZSB0byBuaXQtcGljayB0aGF0OiB0aGUgcm91
dGVyIGNhbiBtYWludGFpbiB0aGlzIHNlcXVlbmNlIG51bWJlciBpbiB3aGF0ZXZlcjxicj4NCiZu
YnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDtmb3JtYXQgaXQgcGxlYXNlcyDigJQgYnV0
LCB3aGVuIGl0IGluY2x1ZGVzIGl0IGluIGNvbnRyb2wgbWVzc2FnZXMsIGl0IG11c3QgYmU8YnI+
DQombmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7cmVwcmVzZW50YWJsZSBpbiBhIHNw
ZWNpZmllZCBmb3JtYXQsIHJlc3BlY3RpbmcgY2VydGFpbiBydWxlcy7igJ08YnI+DQo8YnI+DQpJ
IHNlZSB0aGF0IHRoZXJlIHdlcmUgbm8gY2hhbmdlcyBmb2xsb3dpbmcgdGhpcyBjb21tZW50Ljxi
cj4NCjxicj4NClRvIHNlY3Rpb24gNC40IEkgYXNrZWQgZm9yIGNsYXJpZmljYXRpb24gYXMgdG8g
aWYgc2VxdWVuY2UgbnVtYmVycyB3ZXJlIHBlciBpbnRlcmZhY2Ugb3IgcGVyIHJvdXRlciwgYXMg
dGhlIHNwZWNpZmljYXRpb24gd2FzIHVuY2xlYXIgb24gdGhhdC4gVGhlIHdvcmRzIGhhcyBjaGFu
Z2VkLCBidXQgaXQgc3RpbGwgaXMgdW5jbGVhcjogaG93IG1hbnkgc2VxdWVuY2UgbnVtYmVycyBk
b2VzIGEgcm91dGVyIG1haW50YWluPyBPbmU/IE9uZSBwZXIgaW50ZXJmYWNlPzxicj4NCjxicj4N
CkluIG15IHByZXZpb3VzIHJldmlldywgSSBleHByZXNzZWQgdGhhdCBpdCB3b3VsZCBiZSBwcmVm
ZXJlbnRpYWwgdG8gdXNlIOKAnGEgbm90YXRpb24gb2YgU2V0c+KAnSByYXRoZXIgdGhhbiB0YWJs
ZXMuIEkgc2VlIHRoYXQgdGhpcyBoYXMgbm90IGNoYW5nZWQuPGJyPg0KPGJyPg0KSSBtYWRlIGEg
Y29tbWVudCBvbiBub2RlIGFuZCBhZGRyZXNzLCBsZXQgbWUgcGljayB0aGlzIHVwIGFnYWluLiBU
aGUgZm9sbG93aW5nOjxicj4NCjxicj4NCiZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyBSdGVN
c2cuT3JpZ0FkZHI8YnI+DQombmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNw
OyAmbmJzcDsgQW4gSVAgYWRkcmVzcyBvZiB0aGUgbm9kZSB3aGljaCByZXF1aXJlcyB0aGUgcm91
dGUsIGkuZS4sIHRoZTxicj4NCiZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5i
c3A7ICZuYnNwOyBzb3VyY2UgYWRkcmVzcyBvZiB0aGUgSVAgcGFja2V0IHRyaWdnZXJpbmcgdGhl
IHJvdXRlIHJlcXVlc3QuPGJyPg0KPGJyPg0Kd291bGQgYmUgbW9yZSBjb21wYWN0IGFuZCBjbGVh
ciBpZiBnZXR0aW5nIHJpZCBvZiB0aGUgdGVybSDigJxub2Rl4oCdIGFuZCBzYWlkOjxicj4NCjxi
cj4NClJ0ZU1zZy5PcmlnQWRkcjxicj4NCiZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyBUaGUg
c291cmNlIGFkZHJlc3Mgb2YgdGhlIElQIHBhY2tldCB0cmlnZ2VyaW5nIHRoZSByb3V0ZSByZXF1
ZXN0Ljxicj4NCjxicj4NCjxicj4NClRvIHNlY3Rpb24gNC42LCBhbmQgSSAoYW5kIG90aGVycykg
aGF2ZSBjb21tZW50ZWQgb24gdGhpcyBiZWZvcmU6PGJyPg0KPGJyPg0KJm5ic3A7ICZuYnNwO0Fs
bCBBT0RWdjIgcm91dGVycyBNVVNUIG1haW50YWluIGEgcm91dGUgdGFibGUuJm5ic3A7IFRoZSBy
b3V0ZSB0YWJsZTxicj4NCiZuYnNwOyAmbmJzcDtlbnRyeSBpcyBhIGNvbmNlcHR1YWwgZGF0YSBz
dHJ1Y3R1cmUuJm5ic3A7IEltcGxlbWVudGF0aW9ucyBNQVkgdXNlIGFueTxicj4NCiZuYnNwOyAm
bmJzcDtpbnRlcm5hbCByZXByZXNlbnRhdGlvbiBidXQgTVVTVCBjb250YWluIHRoZSBmb2xsb3dp
bmcgaW5mb3JtYXRpb246PGJyPg0KPGJyPg0KSW4gb3JkZXIgdG8gYXZvaWQgY29uZnVzaW9uLCBy
ZW5hbWUgdGhpcyB0byDigJxSb3V0aW5nIEluZm9ybWF0aW9uIEJhc2XigJ0gb3Ig4oCcUm91dGlu
ZyBTZXTigJ0g4oCUIGEgUm91dGluZyBUYWJsZSBpcyBhbiBvcGVyYXRpbmcgc3lzdGVtIGNvbnN0
cnVjdCwgd2hlcmVvbiBvcGVyYXRpb25zIGRpcmVjdGx5IGluZmx1ZW5jZSBwYWNrZXQgZm9yd2Fy
ZGluZy4gV2hhdCB5b3UgYXJlIGRlZmluaW5nIGhlcmUgaXMgYSBSSUIvYW4gUlMuPGJyPg0KPGJy
Pg0KVGhlIGNvbmZ1c2lvbiB0aGF0IEkgcG9pbnRlZCBvdXQgaW4gbXkgcHJldmlvdXMgcmV2aWV3
IG9uIOKAnElQIGFkZHJlc3PigJ0gYW5kIOKAnEFkZHJlc3PigJ0gYmVpbmcgdXNlZCBhIGJpdCBo
YXBoYXphcmRseSBwZXJzaXN0cywgZndpdy4gSXQgbWFrZXMgbWUgdGhpbmssIGNhbiBhIHJvdXRl
ciBzZW5kIGFuIFJSRVEgZm9yIGEgcHJlZml4Pzxicj4NCjxicj4NCkkgYWxzbyBjYWxsZWQgdGhp
cyBvdXQgaW4gbXkgcHJldmlvdXMgcmV2aWV3IGFzIGluY29ycmVjdCwgYW5kIGRlc3BpdGUgd29y
ZHNtaXRoaW5nIGl0IHN0aWxsIGlzOjxicj4NCjxicj4NCiZuYnNwOyAmbmJzcDsgJm5ic3A7ICZu
YnNwOyBSb3V0ZS5OZXh0SG9wPGJyPg0KJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNw
OyAmbmJzcDsgJm5ic3A7IFRoZSBzb3VyY2UgSVAgYWRkcmVzcyBvZiB0aGUgbWVzc2FnZSBhZHZl
cnRpc2luZyB0aGUgcm91dGUgdG88YnI+DQombmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5i
c3A7ICZuYnNwOyAmbmJzcDsgUm91dGUuQWRkcmVzcywgaS5lLiBhbiBJUCBhZGRyZXNzIG9mIHRo
ZSBBT0RWdjIgcm91dGVyIHVzZWQgZm9yPGJyPg0KJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7
ICZuYnNwOyAmbmJzcDsgJm5ic3A7IHRoZSBuZXh0IGhvcCBvbiB0aGUgcGF0aCB0b3dhcmQgUm91
dGUuQWRkcmVzcy48YnI+DQo8YnI+DQpJZiB0aGF0IOKAnG1lc3NhZ2XigJ0gaXMgYW4gUkZDNTQ0
NCBlbnRpdHksIHRoZW4gaXQgZG9lcyB0byBoYXZlIGEg4oCcc291cmNlIElQIEFkZHJlc3PigJ0g
4oCUIHRoZSBlbmNhcHN1bGF0aW5nIElQIGRhdGFncmFtIGNvbnRhaW5pbmcgdGhlIHBhY2tldCBj
b250YWluaW5nIHRoZSBtZXNzYWdlIGRvZXMuIEFuZCB0aGUgbWVzc2FnZSBNQVkgaGF2ZSBhbiBP
cmlnaW5hdG9yIEFkZHJlc3M8YnI+DQo8YnI+DQo8YnI+DQpBcyBJIGluZGljYXRlZCwgSSBhbSB3
YWxraW5nIHRocm91Z2ggbXkgcHJldmlvdXMgcmV2aWV3IGFuZCByZXRhaW5pbmcgdGhvc2UgY29t
bWVudHMgdGhhdCBJIHN0aWxsIHRoaW5rIG5lZWQgYXR0ZW50aW9uIOKAlCBhbmQgdGhpcyBpcyDi
gJxjcm9zc2luZyBvZmYgZnJvbSBwYXJ0IDEgb2YgbXkgcHJldmlvdXMgcmV2aWV34oCdIG9ubHku
IE1vcmUgdG8gZm9sbG93Ljxicj4NCjxicj4NClRob21hczxicj4NCjxicj4NCl9fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fPGJyPg0KbWFuZXQgbWFpbGluZyBs
aXN0PGJyPg0KPGEgaHJlZj0ibWFpbHRvOm1hbmV0QGlldGYub3JnIj5tYW5ldEBpZXRmLm9yZzwv
YT48YnI+DQo8YSBocmVmPSJodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL21h
bmV0IiB0YXJnZXQ9Il9ibGFuayI+aHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5m
by9tYW5ldDwvYT48bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+
PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPHA+KioqKioqKioqKioqKioq
KioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKio8YnI+
ClRoaXMgZW1haWwgYW5kIGFueSBhdHRhY2htZW50cyBhcmUgY29uZmlkZW50aWFsIHRvIHRoZSBp
bnRlbmRlZDxicj4KcmVjaXBpZW50IGFuZCBtYXkgYWxzbyBiZSBwcml2aWxlZ2VkLiBJZiB5b3Ug
YXJlIG5vdCB0aGUgaW50ZW5kZWQ8YnI+CnJlY2lwaWVudCBwbGVhc2UgZGVsZXRlIGl0IGZyb20g
eW91ciBzeXN0ZW0gYW5kIG5vdGlmeSB0aGUgc2VuZGVyLjxicj4KWW91IHNob3VsZCBub3QgY29w
eSBpdCBvciB1c2UgaXQgZm9yIGFueSBwdXJwb3NlIG5vciBkaXNjbG9zZSBvcjxicj4KZGlzdHJp
YnV0ZSBpdHMgY29udGVudHMgdG8gYW55IG90aGVyIHBlcnNvbi48YnI+CioqKioqKioqKioqKioq
KioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqPC9w
PjwvYm9keT4NCjwvaHRtbD4NCg==

--_000_B31EEDDDB8ED7E4A93FDF12A4EECD30D7D76BF1CGLKXM0002VGREEN_--



From nobody Wed Dec  2 14:27:48 2015
Return-Path: <Kathleen.Moriarty.ietf@gmail.com>
X-Original-To: manet@ietf.org
Delivered-To: manet@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 14F021B2E2A; Wed,  2 Dec 2015 14:13:23 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "Kathleen Moriarty" <Kathleen.Moriarty.ietf@gmail.com>
To: "The IESG" <iesg@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.11.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20151202221323.4668.69742.idtracker@ietfa.amsl.com>
Date: Wed, 02 Dec 2015 14:13:23 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/zsC2jj5onS6ubxJyaKGIiqfHazw>
X-Mailman-Approved-At: Wed, 02 Dec 2015 14:27:46 -0800
Cc: manet@ietf.org, draft-ietf-manet-olsrv2-dat-metric@ietf.org, manet-chairs@ietf.org
Subject: [manet] Kathleen Moriarty's No Objection on draft-ietf-manet-olsrv2-dat-metric-10: (with COMMENT)
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
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: <https://mailarchive.ietf.org/arch/browse/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: Wed, 02 Dec 2015 22:13:23 -0000

Kathleen Moriarty has entered the following ballot position for
draft-ietf-manet-olsrv2-dat-metric-10: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-manet-olsrv2-dat-metric/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

This is just a comment as the text is mostly there, but I feel like it
could be stated more clearly...

In the Security considerations section, the first part of the discussion
could call out "Denial of Service" attacks explicitly in addition to the
description that is included that describes altering traffic patterns.  I
would recommend making this a distinct paragraph for readability.

The next part of the security considerations section (starts with the
last sentence of the first paragraph) seems it could also be a result of
the lack of integrity protections on this measurement technique.  It
might help to state that first and that active attacks may result as a
consequence, leaving in the active attacks you already describe and the
solution already included starting with the second sentence of the second
paragraph.  If that's not the case, please just let me know why.

How is warning about MiTM attacks out-of-scope?  It seems these are
possible, and even mentioned with rogue routers.  Wouldn't it be easier
to state that without session encryption, MiTM is a threat?  If this is
acknowledged, then at least the consideration is there for the reader to
understand.  Addressing the threat may be out-of-scope, but warning about
it shouldn't be.  This last comment is much closer to a discuss, so I'd
appreciate a response.

Thank you!



From nobody Wed Dec  2 14:27:50 2015
Return-Path: <ben@nostrum.com>
X-Original-To: manet@ietf.org
Delivered-To: manet@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 938391AC428; Wed,  2 Dec 2015 14:17:12 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "Ben Campbell" <ben@nostrum.com>
To: "The IESG" <iesg@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.11.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20151202221712.3505.78561.idtracker@ietfa.amsl.com>
Date: Wed, 02 Dec 2015 14:17:12 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/0TfWa9hnWU9JRWqaBiMPbCDLuEE>
X-Mailman-Approved-At: Wed, 02 Dec 2015 14:27:46 -0800
Cc: manet@ietf.org, draft-ietf-manet-olsrv2-dat-metric@ietf.org, manet-chairs@ietf.org
Subject: [manet] Ben Campbell's No Objection on draft-ietf-manet-olsrv2-dat-metric-10: (with COMMENT)
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
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: <https://mailarchive.ietf.org/arch/browse/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: Wed, 02 Dec 2015 22:17:12 -0000

Ben Campbell has entered the following ballot position for
draft-ietf-manet-olsrv2-dat-metric-10: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-manet-olsrv2-dat-metric/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

- section 1, last paragraph:
The first part of this paragraph sounds like justification for making
this standards track. It would be useful to discuss why this is
experimental.  Is there an expectation some version of this may be
republished in the standards track in the future? Is there a need for
deployment experience prior to standardization?

Editorial Comments:

- Abstract:
Please expand OLSRv2 on first mention in abstract. (In addition to the
existing expansion in the body.)

- section 4, 1st paragraph:
s/metric/metrics



From nobody Thu Dec  3 00:10:50 2015
Return-Path: <hrogge@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 A3D5E1AD376; Thu,  3 Dec 2015 00:10:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 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, 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 hInakxurOP4o; Thu,  3 Dec 2015 00:10:44 -0800 (PST)
Received: from mail-wm0-x229.google.com (mail-wm0-x229.google.com [IPv6:2a00:1450:400c:c09::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 187A81B2A30; Thu,  3 Dec 2015 00:10:44 -0800 (PST)
Received: by wmww144 with SMTP id w144so11011100wmw.0; Thu, 03 Dec 2015 00:10:42 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=JFEZ3UExRx3sZf2HbWy/521yUIouUYiLBCJiLfqP90A=; b=zAWV83UnUmH9qrx1tqMx4v/UL2BKyWGb34GRVoM4tLsgLq8auNvo95bAkQRSh3ki// jPQLjuTlKBxlKSZ1dC2xEGD3jMVXXTPcS9xWJ3yCoilouQbdrmGNUbZ6iFqcW0dBzsqJ x/+qvfFQi5FDAD45VXyL4HjEEz9gjENWDwvA4SuTQ8eJSmRKp/apzEzEYRPc7KfQB+JJ YGab7AM3xJYKFyWnW0gglC1VDcT2GaZPUJEZ4SgekI8LXOX2cnkqqSDjjBDGQnAVDErd y0wKE4xm4+Af4R8tOuGva1DMqo1XZjGPgnznYFV/T0Cd78+jfsQYzvH34qrPPf4/vlWB RbYA==
X-Received: by 10.194.2.193 with SMTP id 1mr9683684wjw.26.1449130242685; Thu, 03 Dec 2015 00:10:42 -0800 (PST)
MIME-Version: 1.0
Received: by 10.27.94.70 with HTTP; Thu, 3 Dec 2015 00:10:13 -0800 (PST)
In-Reply-To: <20151202221323.4668.69742.idtracker@ietfa.amsl.com>
References: <20151202221323.4668.69742.idtracker@ietfa.amsl.com>
From: Henning Rogge <hrogge@gmail.com>
Date: Thu, 3 Dec 2015 09:10:13 +0100
Message-ID: <CAGnRvupncZMKj=iquh78+jiT5aTF2rbc43svznuxHc5F47GzBw@mail.gmail.com>
To: Kathleen Moriarty <Kathleen.Moriarty.ietf@gmail.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/eUDmzi_VAwTTdNTDAY8ibol7MOU>
Cc: manet-chairs@ietf.org, MANET IETF <manet@ietf.org>, The IESG <iesg@ietf.org>, draft-ietf-manet-olsrv2-dat-metric@ietf.org
Subject: Re: [manet] Kathleen Moriarty's No Objection on draft-ietf-manet-olsrv2-dat-metric-10: (with COMMENT)
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: <https://mailarchive.ietf.org/arch/browse/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: Thu, 03 Dec 2015 08:10:45 -0000

On Wed, Dec 2, 2015 at 11:13 PM, Kathleen Moriarty
<Kathleen.Moriarty.ietf@gmail.com> wrote:
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
>
> This is just a comment as the text is mostly there, but I feel like it
> could be stated more clearly...
>
> In the Security considerations section, the first part of the discussion
> could call out "Denial of Service" attacks explicitly in addition to the
> description that is included that describes altering traffic patterns.  I
> would recommend making this a distinct paragraph for readability.
>
> The next part of the security considerations section (starts with the
> last sentence of the first paragraph) seems it could also be a result of
> the lack of integrity protections on this measurement technique.  It
> might help to state that first and that active attacks may result as a
> consequence, leaving in the active attacks you already describe and the
> solution already included starting with the second sentence of the second
> paragraph.  If that's not the case, please just let me know why.
>
> How is warning about MiTM attacks out-of-scope?  It seems these are
> possible, and even mentioned with rogue routers.  Wouldn't it be easier
> to state that without session encryption, MiTM is a threat?  If this is
> acknowledged, then at least the consideration is there for the reader to
> understand.  Addressing the threat may be out-of-scope, but warning about
> it shouldn't be.  This last comment is much closer to a discuss, so I'd
> appreciate a response.

MITM attacks are always a threat, even with TLS support. As long as
both sides support "no-TLS", a MITM can easily downgrade the
connection.

Henning Rogge


From nobody Thu Dec  3 01:08:35 2015
Return-Path: <pmc-psc-publicity@iit.cnr.it>
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 5556A1B3303 for <manet@ietfa.amsl.com>; Thu,  3 Dec 2015 01:08:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.32
X-Spam-Level: 
X-Spam-Status: No, score=-2.32 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FROM_MISSP_EH_MATCH=0.001, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_FROM_MISSP_DKIM=0.01, T_RP_MATCHES_RCVD=-0.01] 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 5tocA6nDqE5V for <manet@ietfa.amsl.com>; Thu,  3 Dec 2015 01:08:31 -0800 (PST)
Received: from mxbk.iit.cnr.it (mxbk.iit.cnr.it [146.48.98.159]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2EAC51B3301 for <manet@ietf.org>; Thu,  3 Dec 2015 01:08:30 -0800 (PST)
Received: from turig.iit.cnr.it (turig.iit.cnr.it [146.48.98.70]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mxbk.iit.cnr.it (Postfix) with ESMTPSA id 6B17EC0816 for <manet@ietf.org>; Thu,  3 Dec 2015 10:08:27 +0100 (CET)
Date: Thu, 03 Dec 2015 10:32:01 +0100
From: Andrea Passarella<pmc-psc-publicity@iit.cnr.it>
To: manet@ietf.org
Message-ID: <56600c11.w7YWdVbl0QnlY9op%pmc-psc-publicity@iit.cnr.it>
User-Agent: Heirloom mailx 12.4 7/29/08
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/mLogLhf7kXqE5KC419k0GaujPms>
Subject: [manet] NEW DEADLINE 31st DECEMBER: SI of Elsevier Pervasive and Mobile Computing on Pervasive Social Computing
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: <https://mailarchive.ietf.org/arch/browse/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: Thu, 03 Dec 2015 09:08:34 -0000

********
*
*  NEW SUBMISSION DEADLINE: 31st DECEMBER 2015
*
********

CALL FOR PAPERS

Elsevier - Pervasive and Mobile Computing
Special Issue on
Pervasive Social Computing
http://www.journals.elsevier.com/pervasive-and-mobile-computing/call-for-papers/

NEW Submission Deadline: 31 December 2015

Pervasive Social Computing represents a new paradigm resulting from
the convergence of Pervasive Mobile Computing with Social Networking;
it aims to take advantage of human social relationships to enable the
attainment of users' tasks in different domains. On the one hand, the
impressive diffusion of Online Social Networking platforms is making
OSNs a pervasive tool for maintaining social relationships between
people. On the other hand, the diffusion of mobile personal devices
with rich networking and computing capabilities is fostering novel
patterns of users interactions through social networks, also depending
on the dynamic context and locations of the users. Last but not least,
pervasive mobile technologies enable completely novel types of social
networking applications and services, such as Mobile Social Networks.
The enormous potential of Pervasive Social Computing is leading
scientific communities in different disciplines, from computer science
to social science, communication science and economy, to analyze,
study and provide new theories, models, methods, technological
solutions and case studies. Interestingly, more and more Pervasive
Mobile Computing technologies are designed using inter-disciplinary
approaches, that exploit models of the users personal and social
behavior to design algorithms, protocols, services and applications.

The special issue aims to encourage the multidisciplinary discussion
involving academics, researchers and professionals on theories,
approaches, analysis, design and evaluation of services and networking
solutions for Pervasive Social Computing. Researchers are increasingly
interested in addressing a wide range of Pervasive Social Computing
challenges residing in Social networks and Social Computing systems
including: their architecture, algorithms and protocols for social
networking services, the creation of new analysis models, the
monitoring of emerging trends, studies on trust, privacy and security
issues and their potential applications.

The list of topics includes, but is not limited to:
- Security, privacy and trust in Pervasive Social Computing systems
- Innovative Pervasive Social Computing services and applications
- Architectures, algorithms and protocols for Pervasive Social
  Computing systems
- Mobile networking solutions for Pervasive Social Computing
- Context modeling, reasoning and context awareness in Pervasive
  Social Computing
- Pervasive sensing technologies applied to Pervasive Social Computing
- Opportunistic networking for Pervasive Social Computing
- Innovative Mobile Social Networking technologies and services
- Inter-disciplinary approaches to the design of Pervasive Social
  Computing systems
- Analysis of users social interactions in mobile and pervasive social
  networks
- Novel Online Social Networking services and users' behaviors enabled
  by pervasive mobile networks
- Real experiences and experiments with Pervasive Social Computing
  systems and applications
- Opportunistic and transient social interactions in Pervasive Social
  Computing systems
- Social and economic models for Pervasive Social Computing systems
- Pervasive and social collaboration tools
- Impacts of Pervasive Social Computing on users' behaviour in
  different domains (e.g. e-business, e-market, e-learning, e-health)

Schedule
NEW Submission deadline: December 31st, 2015
Initial feedback to authors: March 31st, 2016
Revised papers due: May 15th, 2016
Final authors notification: June 30th, 2016
Expected Publication of the Special Issue: 4th Quarter 2016

Guest Editors
Patrizia Grifoni, IRPPS-CNR, Italy
Fernando Ferri, IRPPS-CNR, Italy
Alessia D'Andrea, IRPPS-CNR, Italy
Tiziana Guzzo, IRPPS-CNR, Italy
Andrea Passarella, IIT-CNR, Italy

Instructions for submission 
All submissions have to be prepared according to the Guide for Authors
as published in the Journal website at http://www.ees.elsevier.com/pmc/.
Authors should select "SI: PSC", from the "Choose Article Type"
pull-down menu during the submission process. All contributions must
not have been previously published or be under consideration for
publication elsewhere. A submission based on one or more papers that
appeared elsewhere has to comprise major value-added extensions over
what appeared previously (at least 30% new and significant material).
Authors are requested to attach to the submitted paper their relevant,
previously published articles and a summary document explaining the
enhancements made in the journal version. In addition, such papers
must be referenced, and the difference clearly explained, in the
submitted paper.

For further information, please contact the guest editors at pmc-psc at iit.cnr.it


From nobody Thu Dec  3 01:35:26 2015
Return-Path: <hrogge@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 EF8B61ACD0B; Thu,  3 Dec 2015 01:35:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 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, 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 OpGScbZLX5eg; Thu,  3 Dec 2015 01:35:21 -0800 (PST)
Received: from mail-wm0-x22f.google.com (mail-wm0-x22f.google.com [IPv6:2a00:1450:400c:c09::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1B9D71ACD00; Thu,  3 Dec 2015 01:35:21 -0800 (PST)
Received: by wmuu63 with SMTP id u63so13001737wmu.0; Thu, 03 Dec 2015 01:35:19 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=JvxZT49Ze8my6dBx1RkTsH55KHS7klOZ1uG/ohlFkbI=; b=WbOYXZunCwuruLbHhag2Q5DAuD/hyw3ZOzImV+ucr73+TevqDM94W0xmq99kPDgfph mpcg2vOVoaV3cZ0K/b3rZZYf2I1VqgE84bvxPAwNtKbe6wS7g07GwLv5t3aUH8IC/a/S FegM8BcW7g+ydeUeGL+93YHGhBqc6tCsEflMvlO1oHnrBuz7tpqyz8dAdgMCFN5sUmeg M0W96k2skZKn9M0AstOwDPT06w8RQvgvuOA0VljC/ofxiASV4apWNkIb+EW63A5YsFn+ SaTN6XZfSQ2G5CJOByNv5aldlvIZkmU1I3csm0euw9GAv4ikg721DG1p5qdDWPQnjSjs Xj3A==
X-Received: by 10.28.68.213 with SMTP id r204mr48150675wma.35.1449135319738; Thu, 03 Dec 2015 01:35:19 -0800 (PST)
MIME-Version: 1.0
Received: by 10.27.94.70 with HTTP; Thu, 3 Dec 2015 01:34:50 -0800 (PST)
In-Reply-To: <20151202221712.3505.78561.idtracker@ietfa.amsl.com>
References: <20151202221712.3505.78561.idtracker@ietfa.amsl.com>
From: Henning Rogge <hrogge@gmail.com>
Date: Thu, 3 Dec 2015 10:34:50 +0100
Message-ID: <CAGnRvurhqzAoNK_PQo6d3nVe9T0Buo3YFgSUfL0ibSP9+GB7MQ@mail.gmail.com>
To: Ben Campbell <ben@nostrum.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/Z8JmEO8VS6hCUsH4W11nSqswQWQ>
Cc: manet-chairs@ietf.org, MANET IETF <manet@ietf.org>, The IESG <iesg@ietf.org>, draft-ietf-manet-olsrv2-dat-metric@ietf.org
Subject: Re: [manet] Ben Campbell's No Objection on draft-ietf-manet-olsrv2-dat-metric-10: (with COMMENT)
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: <https://mailarchive.ietf.org/arch/browse/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: Thu, 03 Dec 2015 09:35:23 -0000

On Wed, Dec 2, 2015 at 11:17 PM, Ben Campbell <ben@nostrum.com> wrote:
> Ben Campbell has entered the following ballot position for
> draft-ietf-manet-olsrv2-dat-metric-10: No Objection
>
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
>
> - section 1, last paragraph:
> The first part of this paragraph sounds like justification for making
> this standards track. It would be useful to discuss why this is
> experimental.  Is there an expectation some version of this may be
> republished in the standards track in the future? Is there a need for
> deployment experience prior to standardization?

While I think the metric should work well, I think it should get more
testing by other parties in different scenarios and mesh topologies.
This is the first metric published in the Manet WG, I don't feel
comfortable to push it to standard track without more data.

There is also the possibility that someone will come up with a better
idea to calculate the packet loss over time than the "queue of
counters" in the DAT metric. Something that detects a "relevant"
metric change would be great and would allow the metric to change its
value faster without producing more noise.

> Editorial Comments:
>
> - Abstract:
> Please expand OLSRv2 on first mention in abstract. (In addition to the
> existing expansion in the body.)
>
> - section 4, 1st paragraph:
> s/metric/metrics
>
>
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www.ietf.org/mailman/listinfo/manet


From nobody Thu Dec  3 02:36:13 2015
Return-Path: <emmanuel.baccelli@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 C52751B334D; Thu,  3 Dec 2015 02:36:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.277
X-Spam-Level: 
X-Spam-Status: No, score=-1.277 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=no
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 FiVO3yWswLk0; Thu,  3 Dec 2015 02:36:09 -0800 (PST)
Received: from mail-ig0-x22f.google.com (mail-ig0-x22f.google.com [IPv6:2607:f8b0:4001:c05::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F1AE81B3346; Thu,  3 Dec 2015 02:36:08 -0800 (PST)
Received: by igcph11 with SMTP id ph11so7999416igc.1; Thu, 03 Dec 2015 02:36:08 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=ICVDqL/USLDT5MXS2UAxhzrStankz6zNnJPeVs3qtbQ=; b=l3gtsMkWauSQAVzla8gwCvy7t0ZIvrWu7QSKjcmojOY0P/xUYmVG7u2GIAKG33pPxi USYrGZ8sGO2XSpxNqNtEhs8OgHRNi47eKs5d3isxMZvsxpPcqEEI0LI1+JbpUmlnKU1h TNs2ReRY08jia0TuCM/vFUMMpplHQbTXo6tUAvbzheV8YR3ne1/QUJkHIIz1OToQ2/tT KaS+gc5DD+LzCGeJhYKWnGkdwQNh7na81xUQ4cpZYqd9lzgGFBM6CIwphQrZyuWM6PM8 Qg1uXMjMhOb605nnzFDTP0ppshUFKRMFIbva824DtWaz5ok0rMltnSFSsaEQlNv78p/W Aujg==
X-Received: by 10.50.150.69 with SMTP id ug5mr33343586igb.97.1449138968369; Thu, 03 Dec 2015 02:36:08 -0800 (PST)
MIME-Version: 1.0
Sender: emmanuel.baccelli@gmail.com
Received: by 10.79.104.199 with HTTP; Thu, 3 Dec 2015 02:35:49 -0800 (PST)
In-Reply-To: <CAGnRvurhqzAoNK_PQo6d3nVe9T0Buo3YFgSUfL0ibSP9+GB7MQ@mail.gmail.com>
References: <20151202221712.3505.78561.idtracker@ietfa.amsl.com> <CAGnRvurhqzAoNK_PQo6d3nVe9T0Buo3YFgSUfL0ibSP9+GB7MQ@mail.gmail.com>
From: Emmanuel Baccelli <Emmanuel.Baccelli@inria.fr>
Date: Thu, 3 Dec 2015 11:35:49 +0100
X-Google-Sender-Auth: 5pzjIU0engzxfzsU2_BkOmfbu2I
Message-ID: <CANK0pbb6-ojxVm+zF1wedLyDYPc29TCohvYiKyrD6GbnDyeoLw@mail.gmail.com>
To: Ben Campbell <ben@nostrum.com>
Content-Type: multipart/alternative; boundary=001a113413c0709f750525fbf59d
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/TDNNXalgW8yEPprzU6QsZFVSgiM>
Cc: manet-chairs@ietf.org, MANET IETF <manet@ietf.org>, The IESG <iesg@ietf.org>, draft-ietf-manet-olsrv2-dat-metric@ietf.org
Subject: Re: [manet] Ben Campbell's No Objection on draft-ietf-manet-olsrv2-dat-metric-10: (with COMMENT)
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: <https://mailarchive.ietf.org/arch/browse/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: Thu, 03 Dec 2015 10:36:10 -0000

--001a113413c0709f750525fbf59d
Content-Type: text/plain; charset=UTF-8

On Thu, Dec 3, 2015 at 10:34 AM, Henning Rogge <hrogge@gmail.com> wrote:

> On Wed, Dec 2, 2015 at 11:17 PM, Ben Campbell <ben@nostrum.com> wrote:
> > Ben Campbell has entered the following ballot position for
> > draft-ietf-manet-olsrv2-dat-metric-10: No Objection
> >
> > ----------------------------------------------------------------------
> > COMMENT:
> > ----------------------------------------------------------------------
> >
> > - section 1, last paragraph:
> > The first part of this paragraph sounds like justification for making
> > this standards track. It would be useful to discuss why this is
> > experimental.  Is there an expectation some version of this may be
> > republished in the standards track in the future? Is there a need for
> > deployment experience prior to standardization?
>
> While I think the metric should work well, I think it should get more
> testing by other parties in different scenarios and mesh topologies.
> This is the first metric published in the Manet WG, I don't feel
> comfortable to push it to standard track without more data.
>
>
I agree with Henning. More experiments are needed before going standards
track with this.



> There is also the possibility that someone will come up with a better
> idea to calculate the packet loss over time than the "queue of
> counters" in the DAT metric. Something that detects a "relevant"
> metric change would be great and would allow the metric to change its
> value faster without producing more noise.
>
> > Editorial Comments:
> >
> > - Abstract:
> > Please expand OLSRv2 on first mention in abstract. (In addition to the
> > existing expansion in the body.)
> >
> > - section 4, 1st paragraph:
> > s/metric/metrics
> >
> >
> > _______________________________________________
> > manet mailing list
> > manet@ietf.org
> > https://www.ietf.org/mailman/listinfo/manet
>

--001a113413c0709f750525fbf59d
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><div class=3D"gmail_quo=
te">On Thu, Dec 3, 2015 at 10:34 AM, Henning Rogge <span dir=3D"ltr">&lt;<a=
 href=3D"mailto:hrogge@gmail.com" target=3D"_blank">hrogge@gmail.com</a>&gt=
;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 =
.8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=3D"">On Wed, =
Dec 2, 2015 at 11:17 PM, Ben Campbell &lt;<a href=3D"mailto:ben@nostrum.com=
">ben@nostrum.com</a>&gt; wrote:<br>
&gt; Ben Campbell has entered the following ballot position for<br>
&gt; draft-ietf-manet-olsrv2-dat-metric-10: No Objection<br>
&gt;<br>
</span><span class=3D"">&gt; ----------------------------------------------=
------------------------<br>
&gt; COMMENT:<br>
&gt; ----------------------------------------------------------------------=
<br>
&gt;<br>
&gt; - section 1, last paragraph:<br>
&gt; The first part of this paragraph sounds like justification for making<=
br>
&gt; this standards track. It would be useful to discuss why this is<br>
&gt; experimental.=C2=A0 Is there an expectation some version of this may b=
e<br>
&gt; republished in the standards track in the future? Is there a need for<=
br>
&gt; deployment experience prior to standardization?<br>
<br>
</span>While I think the metric should work well, I think it should get mor=
e<br>
testing by other parties in different scenarios and mesh topologies.<br>
This is the first metric published in the Manet WG, I don&#39;t feel<br>
comfortable to push it to standard track without more data.<br>
<br></blockquote><div><br></div><div>I agree with Henning. More experiments=
 are needed before going standards track with this.</div><div><br></div><di=
v>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;=
border-left:1px #ccc solid;padding-left:1ex">
There is also the possibility that someone will come up with a better<br>
idea to calculate the packet loss over time than the &quot;queue of<br>
counters&quot; in the DAT metric. Something that detects a &quot;relevant&q=
uot;<br>
metric change would be great and would allow the metric to change its<br>
value faster without producing more noise.<br>
<span class=3D""><br>
&gt; Editorial Comments:<br>
&gt;<br>
&gt; - Abstract:<br>
&gt; Please expand OLSRv2 on first mention in abstract. (In addition to the=
<br>
&gt; existing expansion in the body.)<br>
&gt;<br>
&gt; - section 4, 1st paragraph:<br>
&gt; s/metric/metrics<br>
&gt;<br>
&gt;<br>
</span>&gt; _______________________________________________<br>
&gt; manet mailing list<br>
&gt; <a href=3D"mailto:manet@ietf.org">manet@ietf.org</a><br>
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/manet" rel=3D"norefer=
rer" target=3D"_blank">https://www.ietf.org/mailman/listinfo/manet</a><br>
</blockquote></div><br></div></div>

--001a113413c0709f750525fbf59d--


From nobody Thu Dec  3 02:48:57 2015
Return-Path: <chris.dearlove@baesystems.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 5431C1B3373; Thu,  3 Dec 2015 02:48:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.909
X-Spam-Level: 
X-Spam-Status: No, score=-6.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, T_RP_MATCHES_RCVD=-0.01] 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 XgrLYXpGQ0zi; Thu,  3 Dec 2015 02:48:51 -0800 (PST)
Received: from ukmta1.baesystems.com (ukmta1.baesystems.com [20.133.0.55]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6053C1B3371; Thu,  3 Dec 2015 02:48:50 -0800 (PST)
X-IronPort-AV: E=Sophos; i="5.20,377,1444690800"; d="scan'208,217"; a="31776657"
Received: from unknown (HELO baemasmds017.greenlnk.net) ([10.15.207.104]) by ukmta1.baesystems.com with ESMTP; 03 Dec 2015 10:48:48 +0000
X-IronPort-AV: E=Sophos;i="5.20,377,1444690800";  d="scan'208,217";a="122707527"
Received: from glkxh0004v.greenlnk.net ([10.109.2.35]) by baemasmds017.greenlnk.net with ESMTP; 03 Dec 2015 10:48:48 +0000
Received: from GLKXM0002V.GREENLNK.net ([169.254.5.2]) by GLKXH0004V.GREENLNK.net ([10.109.2.35]) with mapi id 14.03.0248.002; Thu, 3 Dec 2015 10:48:48 +0000
From: "Dearlove, Christopher (UK)" <chris.dearlove@baesystems.com>
To: Emmanuel Baccelli <Emmanuel.Baccelli@inria.fr>, Ben Campbell <ben@nostrum.com>
Thread-Topic: [manet] Ben Campbell's No Objection on draft-ietf-manet-olsrv2-dat-metric-10: (with COMMENT)
Thread-Index: AQHRLVC3o3XCHsCg8UmafpfRQ5G95Z65ARQAgAARCoCAAAMZ8A==
Date: Thu, 3 Dec 2015 10:48:47 +0000
Message-ID: <B31EEDDDB8ED7E4A93FDF12A4EECD30D7D76C086@GLKXM0002V.GREENLNK.net>
References: <20151202221712.3505.78561.idtracker@ietfa.amsl.com> <CAGnRvurhqzAoNK_PQo6d3nVe9T0Buo3YFgSUfL0ibSP9+GB7MQ@mail.gmail.com> <CANK0pbb6-ojxVm+zF1wedLyDYPc29TCohvYiKyrD6GbnDyeoLw@mail.gmail.com>
In-Reply-To: <CANK0pbb6-ojxVm+zF1wedLyDYPc29TCohvYiKyrD6GbnDyeoLw@mail.gmail.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.109.62.6]
Content-Type: multipart/alternative; boundary="_000_B31EEDDDB8ED7E4A93FDF12A4EECD30D7D76C086GLKXM0002VGREEN_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/cFsnIuA2st14PajH-jNPpZbA678>
Cc: "draft-ietf-manet-olsrv2-dat-metric@ietf.org" <draft-ietf-manet-olsrv2-dat-metric@ietf.org>, MANET IETF <manet@ietf.org>, The IESG <iesg@ietf.org>, "manet-chairs@ietf.org" <manet-chairs@ietf.org>
Subject: Re: [manet] Ben Campbell's No Objection on draft-ietf-manet-olsrv2-dat-metric-10: (with COMMENT)
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: <https://mailarchive.ietf.org/arch/browse/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: Thu, 03 Dec 2015 10:48:53 -0000

--_000_B31EEDDDB8ED7E4A93FDF12A4EECD30D7D76C086GLKXM0002VGREEN_
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64

QW5vdGhlciDigJxJIGFncmVlIHdpdGggSGVubmluZ+KAnS4gVGhhdOKAmXMgYmFzZWQgaW4gcGFy
dGljdWxhciBvbiBteSB1bmRlcnN0YW5kaW5nIHRoYXQgYWx0aG91Z2ggdGhpcyBpcyByZWxhdGVk
IHRvIGEgbWV0cmljIHdoaWNoIHRoZXJlIGlzIGV4cGVyaWVuY2Ugd2l0aCBpbiB0aGUgRnJlaWZ1
bmsgbmV0d29yaywgaXTigJlzIG5vdCB0aGUgc2FtZS4NCg0KDQpGcm9tOiBtYW5ldCBbbWFpbHRv
Om1hbmV0LWJvdW5jZXNAaWV0Zi5vcmddIE9uIEJlaGFsZiBPZiBFbW1hbnVlbCBCYWNjZWxsaQ0K
U2VudDogMDMgRGVjZW1iZXIgMjAxNSAxMDozNg0KVG86IEJlbiBDYW1wYmVsbA0KQ2M6IG1hbmV0
LWNoYWlyc0BpZXRmLm9yZzsgTUFORVQgSUVURjsgVGhlIElFU0c7IGRyYWZ0LWlldGYtbWFuZXQt
b2xzcnYyLWRhdC1tZXRyaWNAaWV0Zi5vcmcNClN1YmplY3Q6IFJlOiBbbWFuZXRdIEJlbiBDYW1w
YmVsbCdzIE5vIE9iamVjdGlvbiBvbiBkcmFmdC1pZXRmLW1hbmV0LW9sc3J2Mi1kYXQtbWV0cmlj
LTEwOiAod2l0aCBDT01NRU5UKQ0KDQpPbiBUaHUsIERlYyAzLCAyMDE1IGF0IDEwOjM0IEFNLCBI
ZW5uaW5nIFJvZ2dlIDxocm9nZ2VAZ21haWwuY29tPG1haWx0bzpocm9nZ2VAZ21haWwuY29tPj4g
d3JvdGU6DQpPbiBXZWQsIERlYyAyLCAyMDE1IGF0IDExOjE3IFBNLCBCZW4gQ2FtcGJlbGwgPGJl
bkBub3N0cnVtLmNvbTxtYWlsdG86YmVuQG5vc3RydW0uY29tPj4gd3JvdGU6DQo+IEJlbiBDYW1w
YmVsbCBoYXMgZW50ZXJlZCB0aGUgZm9sbG93aW5nIGJhbGxvdCBwb3NpdGlvbiBmb3INCj4gZHJh
ZnQtaWV0Zi1tYW5ldC1vbHNydjItZGF0LW1ldHJpYy0xMDogTm8gT2JqZWN0aW9uDQo+DQo+IC0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0NCj4gQ09NTUVOVDoNCj4gLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQ0KPg0KPiAtIHNlY3Rpb24g
MSwgbGFzdCBwYXJhZ3JhcGg6DQo+IFRoZSBmaXJzdCBwYXJ0IG9mIHRoaXMgcGFyYWdyYXBoIHNv
dW5kcyBsaWtlIGp1c3RpZmljYXRpb24gZm9yIG1ha2luZw0KPiB0aGlzIHN0YW5kYXJkcyB0cmFj
ay4gSXQgd291bGQgYmUgdXNlZnVsIHRvIGRpc2N1c3Mgd2h5IHRoaXMgaXMNCj4gZXhwZXJpbWVu
dGFsLiAgSXMgdGhlcmUgYW4gZXhwZWN0YXRpb24gc29tZSB2ZXJzaW9uIG9mIHRoaXMgbWF5IGJl
DQo+IHJlcHVibGlzaGVkIGluIHRoZSBzdGFuZGFyZHMgdHJhY2sgaW4gdGhlIGZ1dHVyZT8gSXMg
dGhlcmUgYSBuZWVkIGZvcg0KPiBkZXBsb3ltZW50IGV4cGVyaWVuY2UgcHJpb3IgdG8gc3RhbmRh
cmRpemF0aW9uPw0KDQpXaGlsZSBJIHRoaW5rIHRoZSBtZXRyaWMgc2hvdWxkIHdvcmsgd2VsbCwg
SSB0aGluayBpdCBzaG91bGQgZ2V0IG1vcmUNCnRlc3RpbmcgYnkgb3RoZXIgcGFydGllcyBpbiBk
aWZmZXJlbnQgc2NlbmFyaW9zIGFuZCBtZXNoIHRvcG9sb2dpZXMuDQpUaGlzIGlzIHRoZSBmaXJz
dCBtZXRyaWMgcHVibGlzaGVkIGluIHRoZSBNYW5ldCBXRywgSSBkb24ndCBmZWVsDQpjb21mb3J0
YWJsZSB0byBwdXNoIGl0IHRvIHN0YW5kYXJkIHRyYWNrIHdpdGhvdXQgbW9yZSBkYXRhLg0KDQpJ
IGFncmVlIHdpdGggSGVubmluZy4gTW9yZSBleHBlcmltZW50cyBhcmUgbmVlZGVkIGJlZm9yZSBn
b2luZyBzdGFuZGFyZHMgdHJhY2sgd2l0aCB0aGlzLg0KDQoNClRoZXJlIGlzIGFsc28gdGhlIHBv
c3NpYmlsaXR5IHRoYXQgc29tZW9uZSB3aWxsIGNvbWUgdXAgd2l0aCBhIGJldHRlcg0KaWRlYSB0
byBjYWxjdWxhdGUgdGhlIHBhY2tldCBsb3NzIG92ZXIgdGltZSB0aGFuIHRoZSAicXVldWUgb2YN
CmNvdW50ZXJzIiBpbiB0aGUgREFUIG1ldHJpYy4gU29tZXRoaW5nIHRoYXQgZGV0ZWN0cyBhICJy
ZWxldmFudCINCm1ldHJpYyBjaGFuZ2Ugd291bGQgYmUgZ3JlYXQgYW5kIHdvdWxkIGFsbG93IHRo
ZSBtZXRyaWMgdG8gY2hhbmdlIGl0cw0KdmFsdWUgZmFzdGVyIHdpdGhvdXQgcHJvZHVjaW5nIG1v
cmUgbm9pc2UuDQoNCj4gRWRpdG9yaWFsIENvbW1lbnRzOg0KPg0KPiAtIEFic3RyYWN0Og0KPiBQ
bGVhc2UgZXhwYW5kIE9MU1J2MiBvbiBmaXJzdCBtZW50aW9uIGluIGFic3RyYWN0LiAoSW4gYWRk
aXRpb24gdG8gdGhlDQo+IGV4aXN0aW5nIGV4cGFuc2lvbiBpbiB0aGUgYm9keS4pDQo+DQo+IC0g
c2VjdGlvbiA0LCAxc3QgcGFyYWdyYXBoOg0KPiBzL21ldHJpYy9tZXRyaWNzDQo+DQo+DQo+IF9f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQo+IG1hbmV0IG1h
aWxpbmcgbGlzdA0KPiBtYW5ldEBpZXRmLm9yZzxtYWlsdG86bWFuZXRAaWV0Zi5vcmc+DQo+IGh0
dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vbWFuZXQNCg0KKioqKioqKioqKioq
KioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioK
VGhpcyBlbWFpbCBhbmQgYW55IGF0dGFjaG1lbnRzIGFyZSBjb25maWRlbnRpYWwgdG8gdGhlIGlu
dGVuZGVkCnJlY2lwaWVudCBhbmQgbWF5IGFsc28gYmUgcHJpdmlsZWdlZC4gSWYgeW91IGFyZSBu
b3QgdGhlIGludGVuZGVkCnJlY2lwaWVudCBwbGVhc2UgZGVsZXRlIGl0IGZyb20geW91ciBzeXN0
ZW0gYW5kIG5vdGlmeSB0aGUgc2VuZGVyLgpZb3Ugc2hvdWxkIG5vdCBjb3B5IGl0IG9yIHVzZSBp
dCBmb3IgYW55IHB1cnBvc2Ugbm9yIGRpc2Nsb3NlIG9yCmRpc3RyaWJ1dGUgaXRzIGNvbnRlbnRz
IHRvIGFueSBvdGhlciBwZXJzb24uCioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioq
KioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqCg==

--_000_B31EEDDDB8ED7E4A93FDF12A4EECD30D7D76C086GLKXM0002VGREEN_
Content-Type: text/html; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTQgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
Q2FsaWJyaTsNCglwYW5vc2UtMToyIDE1IDUgMiAyIDIgNCAzIDIgNDt9DQpAZm9udC1mYWNlDQoJ
e2ZvbnQtZmFtaWx5OlRhaG9tYTsNCglwYW5vc2UtMToyIDExIDYgNCAzIDUgNCA0IDIgNDt9DQov
KiBTdHlsZSBEZWZpbml0aW9ucyAqLw0KcC5Nc29Ob3JtYWwsIGxpLk1zb05vcm1hbCwgZGl2Lk1z
b05vcm1hbA0KCXttYXJnaW46MGNtOw0KCW1hcmdpbi1ib3R0b206LjAwMDFwdDsNCglmb250LXNp
emU6MTIuMHB0Ow0KCWZvbnQtZmFtaWx5OiJUaW1lcyBOZXcgUm9tYW4iLCJzZXJpZiI7fQ0KYTps
aW5rLCBzcGFuLk1zb0h5cGVybGluaw0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJY29sb3I6
Ymx1ZTsNCgl0ZXh0LWRlY29yYXRpb246dW5kZXJsaW5lO30NCmE6dmlzaXRlZCwgc3Bhbi5Nc29I
eXBlcmxpbmtGb2xsb3dlZA0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJY29sb3I6cHVycGxl
Ow0KCXRleHQtZGVjb3JhdGlvbjp1bmRlcmxpbmU7fQ0Kc3Bhbi5FbWFpbFN0eWxlMTkNCgl7bXNv
LXN0eWxlLXR5cGU6cGVyc29uYWwtcmVwbHk7DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLCJzYW5z
LXNlcmlmIjsNCgljb2xvcjojMUY0OTdEO30NCi5Nc29DaHBEZWZhdWx0DQoJe21zby1zdHlsZS10
eXBlOmV4cG9ydC1vbmx5Ow0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIiwic2Fucy1zZXJpZiI7DQoJ
bXNvLWZhcmVhc3QtbGFuZ3VhZ2U6RU4tVVM7fQ0KQHBhZ2UgV29yZFNlY3Rpb24xDQoJe3NpemU6
NjEyLjBwdCA3OTIuMHB0Ow0KCW1hcmdpbjo3Mi4wcHQgNzIuMHB0IDcyLjBwdCA3Mi4wcHQ7fQ0K
ZGl2LldvcmRTZWN0aW9uMQ0KCXtwYWdlOldvcmRTZWN0aW9uMTt9DQotLT48L3N0eWxlPjwhLS1b
aWYgZ3RlIG1zbyA5XT48eG1sPg0KPG86c2hhcGVkZWZhdWx0cyB2OmV4dD0iZWRpdCIgc3BpZG1h
eD0iMTAyNiIgLz4NCjwveG1sPjwhW2VuZGlmXS0tPjwhLS1baWYgZ3RlIG1zbyA5XT48eG1sPg0K
PG86c2hhcGVsYXlvdXQgdjpleHQ9ImVkaXQiPg0KPG86aWRtYXAgdjpleHQ9ImVkaXQiIGRhdGE9
IjEiIC8+DQo8L286c2hhcGVsYXlvdXQ+PC94bWw+PCFbZW5kaWZdLS0+DQo8L2hlYWQ+DQo8Ym9k
eSBsYW5nPSJFTi1HQiIgbGluaz0iYmx1ZSIgdmxpbms9InB1cnBsZSI+DQo8ZGl2IGNsYXNzPSJX
b3JkU2VjdGlvbjEiPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6
ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlm
JnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPkFub3RoZXIg4oCcSSBhZ3JlZSB3aXRoIEhlbm5pbmfigJ0u
IFRoYXTigJlzIGJhc2VkIGluIHBhcnRpY3VsYXIgb24gbXkgdW5kZXJzdGFuZGluZyB0aGF0IGFs
dGhvdWdoIHRoaXMgaXMgcmVsYXRlZCB0byBhIG1ldHJpYyB3aGljaCB0aGVyZSBpcyBleHBlcmll
bmNlIHdpdGggaW4gdGhlDQogRnJlaWZ1bmsgbmV0d29yaywgaXTigJlzIG5vdCB0aGUgc2FtZS48
bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0i
Zm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3Nh
bnMtc2VyaWYmcXVvdDs7Y29sb3I6IzFGNDk3RCI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9w
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9u
dC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9y
OiMxRjQ5N0QiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiPjxiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZh
bWlseTomcXVvdDtUYWhvbWEmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90OyI+RnJvbTo8L3Nw
YW4+PC9iPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZh
bWlseTomcXVvdDtUYWhvbWEmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90OyI+IG1hbmV0IFtt
YWlsdG86bWFuZXQtYm91bmNlc0BpZXRmLm9yZ10NCjxiPk9uIEJlaGFsZiBPZiA8L2I+RW1tYW51
ZWwgQmFjY2VsbGk8YnI+DQo8Yj5TZW50OjwvYj4gMDMgRGVjZW1iZXIgMjAxNSAxMDozNjxicj4N
CjxiPlRvOjwvYj4gQmVuIENhbXBiZWxsPGJyPg0KPGI+Q2M6PC9iPiBtYW5ldC1jaGFpcnNAaWV0
Zi5vcmc7IE1BTkVUIElFVEY7IFRoZSBJRVNHOyBkcmFmdC1pZXRmLW1hbmV0LW9sc3J2Mi1kYXQt
bWV0cmljQGlldGYub3JnPGJyPg0KPGI+U3ViamVjdDo8L2I+IFJlOiBbbWFuZXRdIEJlbiBDYW1w
YmVsbCdzIE5vIE9iamVjdGlvbiBvbiBkcmFmdC1pZXRmLW1hbmV0LW9sc3J2Mi1kYXQtbWV0cmlj
LTEwOiAod2l0aCBDT01NRU5UKTxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxkaXY+DQo8ZGl2Pg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8ZGl2Pg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCI+T24gVGh1LCBEZWMgMywgMjAxNSBhdCAxMDozNCBBTSwgSGVubmluZyBS
b2dnZSAmbHQ7PGEgaHJlZj0ibWFpbHRvOmhyb2dnZUBnbWFpbC5jb20iIHRhcmdldD0iX2JsYW5r
Ij5ocm9nZ2VAZ21haWwuY29tPC9hPiZndDsgd3JvdGU6PG86cD48L286cD48L3A+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2luLWJvdHRvbToxMi4wcHQiPk9uIFdlZCwgRGVjIDIs
IDIwMTUgYXQgMTE6MTcgUE0sIEJlbiBDYW1wYmVsbCAmbHQ7PGEgaHJlZj0ibWFpbHRvOmJlbkBu
b3N0cnVtLmNvbSI+YmVuQG5vc3RydW0uY29tPC9hPiZndDsgd3JvdGU6PGJyPg0KJmd0OyBCZW4g
Q2FtcGJlbGwgaGFzIGVudGVyZWQgdGhlIGZvbGxvd2luZyBiYWxsb3QgcG9zaXRpb24gZm9yPGJy
Pg0KJmd0OyBkcmFmdC1pZXRmLW1hbmV0LW9sc3J2Mi1kYXQtbWV0cmljLTEwOiBObyBPYmplY3Rp
b248YnI+DQomZ3Q7PGJyPg0KJmd0OyAtLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tPGJyPg0KJmd0OyBDT01NRU5UOjxi
cj4NCiZndDsgLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLTxicj4NCiZndDs8YnI+DQomZ3Q7IC0gc2VjdGlvbiAxLCBs
YXN0IHBhcmFncmFwaDo8YnI+DQomZ3Q7IFRoZSBmaXJzdCBwYXJ0IG9mIHRoaXMgcGFyYWdyYXBo
IHNvdW5kcyBsaWtlIGp1c3RpZmljYXRpb24gZm9yIG1ha2luZzxicj4NCiZndDsgdGhpcyBzdGFu
ZGFyZHMgdHJhY2suIEl0IHdvdWxkIGJlIHVzZWZ1bCB0byBkaXNjdXNzIHdoeSB0aGlzIGlzPGJy
Pg0KJmd0OyBleHBlcmltZW50YWwuJm5ic3A7IElzIHRoZXJlIGFuIGV4cGVjdGF0aW9uIHNvbWUg
dmVyc2lvbiBvZiB0aGlzIG1heSBiZTxicj4NCiZndDsgcmVwdWJsaXNoZWQgaW4gdGhlIHN0YW5k
YXJkcyB0cmFjayBpbiB0aGUgZnV0dXJlPyBJcyB0aGVyZSBhIG5lZWQgZm9yPGJyPg0KJmd0OyBk
ZXBsb3ltZW50IGV4cGVyaWVuY2UgcHJpb3IgdG8gc3RhbmRhcmRpemF0aW9uPzxicj4NCjxicj4N
CldoaWxlIEkgdGhpbmsgdGhlIG1ldHJpYyBzaG91bGQgd29yayB3ZWxsLCBJIHRoaW5rIGl0IHNo
b3VsZCBnZXQgbW9yZTxicj4NCnRlc3RpbmcgYnkgb3RoZXIgcGFydGllcyBpbiBkaWZmZXJlbnQg
c2NlbmFyaW9zIGFuZCBtZXNoIHRvcG9sb2dpZXMuPGJyPg0KVGhpcyBpcyB0aGUgZmlyc3QgbWV0
cmljIHB1Ymxpc2hlZCBpbiB0aGUgTWFuZXQgV0csIEkgZG9uJ3QgZmVlbDxicj4NCmNvbWZvcnRh
YmxlIHRvIHB1c2ggaXQgdG8gc3RhbmRhcmQgdHJhY2sgd2l0aG91dCBtb3JlIGRhdGEuPG86cD48
L286cD48L3A+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48
L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5JIGFncmVlIHdpdGggSGVu
bmluZy4gTW9yZSBleHBlcmltZW50cyBhcmUgbmVlZGVkIGJlZm9yZSBnb2luZyBzdGFuZGFyZHMg
dHJhY2sgd2l0aCB0aGlzLjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIj4mbmJzcDs8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGJsb2NrcXVvdGUg
c3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci1sZWZ0OnNvbGlkICNDQ0NDQ0MgMS4wcHQ7cGFkZGlu
ZzowY20gMGNtIDBjbSA2LjBwdDttYXJnaW4tbGVmdDo0LjhwdDttYXJnaW4tcmlnaHQ6MGNtIj4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiPlRoZXJlIGlzIGFsc28gdGhlIHBvc3NpYmlsaXR5IHRoYXQg
c29tZW9uZSB3aWxsIGNvbWUgdXAgd2l0aCBhIGJldHRlcjxicj4NCmlkZWEgdG8gY2FsY3VsYXRl
IHRoZSBwYWNrZXQgbG9zcyBvdmVyIHRpbWUgdGhhbiB0aGUgJnF1b3Q7cXVldWUgb2Y8YnI+DQpj
b3VudGVycyZxdW90OyBpbiB0aGUgREFUIG1ldHJpYy4gU29tZXRoaW5nIHRoYXQgZGV0ZWN0cyBh
ICZxdW90O3JlbGV2YW50JnF1b3Q7PGJyPg0KbWV0cmljIGNoYW5nZSB3b3VsZCBiZSBncmVhdCBh
bmQgd291bGQgYWxsb3cgdGhlIG1ldHJpYyB0byBjaGFuZ2UgaXRzPGJyPg0KdmFsdWUgZmFzdGVy
IHdpdGhvdXQgcHJvZHVjaW5nIG1vcmUgbm9pc2UuPGJyPg0KPGJyPg0KJmd0OyBFZGl0b3JpYWwg
Q29tbWVudHM6PGJyPg0KJmd0Ozxicj4NCiZndDsgLSBBYnN0cmFjdDo8YnI+DQomZ3Q7IFBsZWFz
ZSBleHBhbmQgT0xTUnYyIG9uIGZpcnN0IG1lbnRpb24gaW4gYWJzdHJhY3QuIChJbiBhZGRpdGlv
biB0byB0aGU8YnI+DQomZ3Q7IGV4aXN0aW5nIGV4cGFuc2lvbiBpbiB0aGUgYm9keS4pPGJyPg0K
Jmd0Ozxicj4NCiZndDsgLSBzZWN0aW9uIDQsIDFzdCBwYXJhZ3JhcGg6PGJyPg0KJmd0OyBzL21l
dHJpYy9tZXRyaWNzPGJyPg0KJmd0Ozxicj4NCiZndDs8YnI+DQomZ3Q7IF9fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fPGJyPg0KJmd0OyBtYW5ldCBtYWlsaW5n
IGxpc3Q8YnI+DQomZ3Q7IDxhIGhyZWY9Im1haWx0bzptYW5ldEBpZXRmLm9yZyI+bWFuZXRAaWV0
Zi5vcmc8L2E+PGJyPg0KJmd0OyA8YSBocmVmPSJodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFu
L2xpc3RpbmZvL21hbmV0IiB0YXJnZXQ9Il9ibGFuayI+aHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFp
bG1hbi9saXN0aW5mby9tYW5ldDwvYT48bzpwPjwvbzpwPjwvcD4NCjwvYmxvY2txdW90ZT4NCjwv
ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4N
CjwvZGl2Pg0KPC9kaXY+DQo8cD4qKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioq
KioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKjxicj4KVGhpcyBlbWFpbCBhbmQgYW55IGF0
dGFjaG1lbnRzIGFyZSBjb25maWRlbnRpYWwgdG8gdGhlIGludGVuZGVkPGJyPgpyZWNpcGllbnQg
YW5kIG1heSBhbHNvIGJlIHByaXZpbGVnZWQuIElmIHlvdSBhcmUgbm90IHRoZSBpbnRlbmRlZDxi
cj4KcmVjaXBpZW50IHBsZWFzZSBkZWxldGUgaXQgZnJvbSB5b3VyIHN5c3RlbSBhbmQgbm90aWZ5
IHRoZSBzZW5kZXIuPGJyPgpZb3Ugc2hvdWxkIG5vdCBjb3B5IGl0IG9yIHVzZSBpdCBmb3IgYW55
IHB1cnBvc2Ugbm9yIGRpc2Nsb3NlIG9yPGJyPgpkaXN0cmlidXRlIGl0cyBjb250ZW50cyB0byBh
bnkgb3RoZXIgcGVyc29uLjxicj4KKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioq
KioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKio8L3A+PC9ib2R5Pg0KPC9odG1sPg0K

--_000_B31EEDDDB8ED7E4A93FDF12A4EECD30D7D76C086GLKXM0002VGREEN_--


From nobody Thu Dec  3 03:00:20 2015
Return-Path: <jch@pps.univ-paris-diderot.fr>
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 1882C1B337B for <manet@ietfa.amsl.com>; Thu,  3 Dec 2015 03:00:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.55
X-Spam-Level: 
X-Spam-Status: No, score=-1.55 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_FR=0.35] autolearn=no
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 bwpYRF6YKuCj for <manet@ietfa.amsl.com>; Thu,  3 Dec 2015 03:00:17 -0800 (PST)
Received: from korolev.univ-paris7.fr (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7F0471A879A for <manet@ietf.org>; Thu,  3 Dec 2015 03:00:17 -0800 (PST)
Received: from potemkin.univ-paris7.fr (potemkin.univ-paris7.fr [IPv6:2001:660:3301:8000::1:1]) by korolev.univ-paris7.fr (8.14.4/8.14.4/relay1/56228) with ESMTP id tB3B0F9Y017406 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 3 Dec 2015 12:00:15 +0100
Received: from mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [81.194.30.253]) by potemkin.univ-paris7.fr (8.14.4/8.14.4/relay2/56228) with ESMTP id tB3B0FS4003192; Thu, 3 Dec 2015 12:00:15 +0100
Received: from mailhub.math.univ-paris-diderot.fr (localhost [127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTP id 5CCA861FA7; Thu,  3 Dec 2015 12:00:15 +0100 (CET)
X-Virus-Scanned: amavisd-new at math.univ-paris-diderot.fr
Received: from mailhub.math.univ-paris-diderot.fr ([127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [127.0.0.1]) (amavisd-new, port 10023) with ESMTP id ASlqkiyn-xcP; Thu,  3 Dec 2015 12:00:14 +0100 (CET)
Received: from lanthane.pps.univ-paris-diderot.fr (unknown [172.23.36.54]) (Authenticated sender: jch) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTPSA id 0FEEB61F9A; Thu,  3 Dec 2015 12:00:14 +0100 (CET)
Received: from localhost ([::1] helo=lanthane.pps.univ-paris-diderot.fr) by lanthane.pps.univ-paris-diderot.fr with esmtp (Exim 4.86) (envelope-from <jch@pps.univ-paris-diderot.fr>) id 1a4RcT-0002rD-S0; Thu, 03 Dec 2015 12:00:13 +0100
Date: Thu, 03 Dec 2015 12:00:13 +0100
Message-ID: <7ipoynpzk2.wl-jch@pps.univ-paris-diderot.fr>
From: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
To: Henning Rogge <hrogge@gmail.com>
In-Reply-To: <CAGnRvurhqzAoNK_PQo6d3nVe9T0Buo3YFgSUfL0ibSP9+GB7MQ@mail.gmail.com>
References: <20151202221712.3505.78561.idtracker@ietfa.amsl.com> <CAGnRvurhqzAoNK_PQo6d3nVe9T0Buo3YFgSUfL0ibSP9+GB7MQ@mail.gmail.com>
User-Agent: Wanderlust/2.15.9
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]); Thu, 03 Dec 2015 12:00:15 +0100 (CET)
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (potemkin.univ-paris7.fr [194.254.61.141]); Thu, 03 Dec 2015 12:00:15 +0100 (CET)
X-Miltered: at korolev with ID 566020BF.002 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-Miltered: at potemkin with ID 566020BF.000 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 566020BF.002 from potemkin.univ-paris7.fr/potemkin.univ-paris7.fr/null/potemkin.univ-paris7.fr/<jch@pps.univ-paris-diderot.fr>
X-j-chkmail-Enveloppe: 566020BF.000 from mailhub.math.univ-paris-diderot.fr/mailhub.math.univ-paris-diderot.fr/null/mailhub.math.univ-paris-diderot.fr/<jch@pps.univ-paris-diderot.fr>
X-j-chkmail-Score: MSGID : 566020BF.002 on korolev.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Score: MSGID : 566020BF.000 on potemkin.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Status: Ham
X-j-chkmail-Status: Ham
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/UCwsDY18uP7bWmPptGQP3-iBQi8>
Cc: MANET IETF <manet@ietf.org>
Subject: Re: [manet] Ben Campbell's No Objection on draft-ietf-manet-olsrv2-dat-metric-10: (with COMMENT)
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: <https://mailarchive.ietf.org/arch/browse/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: Thu, 03 Dec 2015 11:00:19 -0000

> Something that detects a "relevant" metric change would be great and
> would allow the metric to change its value faster without producing more
> noise.

Could you please explain?


From nobody Thu Dec  3 03:14:16 2015
Return-Path: <hrogge@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 CE7C61B33AE for <manet@ietfa.amsl.com>; Thu,  3 Dec 2015 03:14:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 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, 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 Pm_JZNiQqETr for <manet@ietfa.amsl.com>; Thu,  3 Dec 2015 03:14:13 -0800 (PST)
Received: from mail-wm0-x22a.google.com (mail-wm0-x22a.google.com [IPv6:2a00:1450:400c:c09::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 587071B33AD for <manet@ietf.org>; Thu,  3 Dec 2015 03:14:13 -0800 (PST)
Received: by wmvv187 with SMTP id v187so21710225wmv.1 for <manet@ietf.org>; Thu, 03 Dec 2015 03:14:12 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=IKgfrhWJXJ8XaxdeaicI7mtgZeHrUwqBp1Iwp9bQ4vQ=; b=uJ1xCT52loPmteNe2Gp6CVvje1pCcZO/WC4uPrdRmqKneGn96AiYHWbfaisFVjM2HA /Y5TIaS/MC8You25zYDvSHwVCBCpUZX8XhYsnKjYvkhoC/M/5xsZUnuTiW8NZ3pqHeyi 5cFxfgEojjHkK/s9u8/NO3P9GdNQYbRoxm7CQZGS+r+SvEkpSLCrduRbwLa9IaItQXuy zbTgBFf81T0kahgRkCwAqsVBJNKdyj8KVxOorAJIlN4Lmrv81Kxw48Ri6AvcyCxi/jb3 4e1+83PdfMzK2nEXUdRtQA5LY7iRaMrJ/wLRNs31iUxVM24UCIUoFY3iNUps/BNjHyT0 P9UQ==
X-Received: by 10.28.64.11 with SMTP id n11mr47972743wma.37.1449141251943; Thu, 03 Dec 2015 03:14:11 -0800 (PST)
MIME-Version: 1.0
Received: by 10.27.94.70 with HTTP; Thu, 3 Dec 2015 03:13:42 -0800 (PST)
In-Reply-To: <7ipoynpzk2.wl-jch@pps.univ-paris-diderot.fr>
References: <20151202221712.3505.78561.idtracker@ietfa.amsl.com> <CAGnRvurhqzAoNK_PQo6d3nVe9T0Buo3YFgSUfL0ibSP9+GB7MQ@mail.gmail.com> <7ipoynpzk2.wl-jch@pps.univ-paris-diderot.fr>
From: Henning Rogge <hrogge@gmail.com>
Date: Thu, 3 Dec 2015 12:13:42 +0100
Message-ID: <CAGnRvuqyE0zgLn_daLi8vrHkWeowTybFw4hrcQGGT-S=c=h_8w@mail.gmail.com>
To: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/ivZZpSt2xcGhSIFS4Y_IgatYsPY>
Cc: MANET IETF <manet@ietf.org>
Subject: Re: [manet] Ben Campbell's No Objection on draft-ietf-manet-olsrv2-dat-metric-10: (with COMMENT)
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: <https://mailarchive.ietf.org/arch/browse/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: Thu, 03 Dec 2015 11:14:15 -0000

On Thu, Dec 3, 2015 at 12:00 PM, Juliusz Chroboczek
<jch@pps.univ-paris-diderot.fr> wrote:
>> Something that detects a "relevant" metric change would be great and
>> would allow the metric to change its value faster without producing more
>> noise.
>
> Could you please explain?

DAT metric uses the average of the packet loss event over a time
period. While this helps to reduce the variance of the input, it also
makes the metric slow to react to changes.

In a mobile environment links might change very quickly, which means
using the average over 60 seconds (as an example) will give you a bad
result.

I am still working on a more "statistical based" approach, but its not
complete at the moment.

Henning Rogge


From nobody Thu Dec  3 03:37:32 2015
Return-Path: <Ietf@thomasclausen.org>
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 C64C21B33D9 for <manet@ietfa.amsl.com>; Thu,  3 Dec 2015 03:37:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level: 
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, J_CHICKENPOX_52=0.6, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-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 7xqz-2pHagb1 for <manet@ietfa.amsl.com>; Thu,  3 Dec 2015 03:37:25 -0800 (PST)
Received: from maila2.tigertech.net (maila2.tigertech.net [208.80.4.152]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CC35A1A884B for <manet@ietf.org>; Thu,  3 Dec 2015 03:37:23 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by maila2.tigertech.net (Postfix) with ESMTP id 894CE2409BC; Thu,  3 Dec 2015 03:37:23 -0800 (PST)
X-Virus-Scanned: Debian amavisd-new at maila2.tigertech.net
Received: from [192.168.147.111] (mtg91-1-82-227-24-173.fbx.proxad.net [82.227.24.173]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by maila2.tigertech.net (Postfix) with ESMTPSA id 2CA222406AB; Thu,  3 Dec 2015 03:37:22 -0800 (PST)
Mime-Version: 1.0 (Mac OS X Mail 9.1 \(3096.5\))
Content-Type: multipart/alternative; boundary="Apple-Mail=_0C0AEDA7-A581-4C36-8823-F8C99D4FD18D"
From: ietf@thomasclausen.org
In-Reply-To: <CAAePS4AtbPekzU=m7aut08yHwZPmk-TiCdG4vvfNZtSWPowx=Q@mail.gmail.com>
Date: Thu, 3 Dec 2015 12:37:09 +0100
Sendlaterdate: Thu, 3 Dec 2015 12:37:09 +0100
Message-Id: <913A0048-2EF9-41D5-9F6E-6715923CE9CA@thomasclausen.org>
References: <241ccb422cb941bda2617d7be275c649@VAUSDITCHM2.idirect.net> <9948DF10-0B9B-404E-BA09-C90CDE209756@thomasclausen.org> <DCC7ED56-7ED9-4610-91A0-3D70620B9823@gmail.com> <CAAePS4DtpBrWtgBbnWjLZN07mcyH=hmK0pzPvCrjwwLiTuXc2Q@mail.gmail.com> <CAAePS4AtbPekzU=m7aut08yHwZPmk-TiCdG4vvfNZtSWPowx=Q@mail.gmail.com>
To: Victoria Mercieca <vmercieca0@gmail.com>
X-Mailer: Apple Mail (2.3096.5)
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/oRaVABVn_DYkzuM-ifI5hUCpnyI>
Cc: manet <manet@ietf.org>
Subject: Re: [manet] draft-ietf-manet-aodvv2-12 and draft-ietf-manet-dlep-17
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: <https://mailarchive.ietf.org/arch/browse/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: Thu, 03 Dec 2015 11:37:30 -0000

--Apple-Mail=_0C0AEDA7-A581-4C36-8823-F8C99D4FD18D
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Victoria,

> On Nov 19, 2015, at 17:09, Victoria Mercieca <vmercieca0@gmail.com> =
wrote:
> Hi Thomas and Christopher,
> Thank you for your comments.  If I may address just one point for =
starters - regeneration vs forwarding. We use the term regeneration =
since forwarding seems inappropriate when the message content changes at =
each hop.
>=20
> The changes we make to the message content are:
>=20
> 1) We change the metric so that each router along the path learns a =
route from the message, with the metric associated with the path up to =
that point
> 2) AckReq only applies between hops, so needs to be removed at each =
hop, and a new AckReq element may need to be added for the next hop.
> 3) ValidityTime could potentially be added by any intermediate router =
that wishes to limit the time it will forward packets on the route.
> 4) Stripping out Unreachable Addresses from RERR which did not affect =
our route set.
>=20
> Can we really use the term "forwarding" if we are changing the metric =
value, adding a validity time, adding/removing AckReq or removing =
addresses and their associated TLVs?
>=20
> Further, in reply to the comment about use of the msg-hop-count and =
msg-hop-limit fields, I think it does not matter that a message only =
travels one hop in that particular form, with that exact set of =
information enclosed. Hop limit and hop count are part of the message =
and used by the routing protocol, and so they refer to the multi-hop =
path that the AODVv2 message will follow, indicating when not to =
regenerate any further. So AODVv2 uses these fields as suggested in =
RFC5444 Appendix B, to limit the number of hops across which it will =
regenerate a packet so as to "prevent messages from endlessly =
circulating in a MANET=E2=80=9D.
>=20

Mmmh=E2=80=A6based on what you describe in the above:=20

	1)	a router receiving a control message may chose to =
respond by doing any=20
		(and possibly more than one) of:

			a)	ignore the message
			b)	process the message
			c)	generate a new control message, possibly =
integrating the state
				acquired through b.

	2)	consequently, your protocol control messages are only =
ever exchanged=20
		between neighboring routers

1c) is what you call =E2=80=9Cregenerate=E2=80=9D a control message - =
akin to any other DV protocol, which (possibly) shares its distance =
vector with its neighbors after having processed a received message.=20

While I=E2=80=99m not sure that I particularly like the word =
=E2=80=9Cregenerate=E2=80=9D, I=E2=80=99m not too hung up on that =E2=80=94=
 but, at the very least it does deserve a precise definition somewhere =
in the specification since, at least, I stumbled over its =
interpretation.

But, either way, as according to your model messages are never =
forwarded, but always are intended for receipt by a router which is a =
direct neighbor, then a <msg-hop-limit>  >1 (which applies to the =
message) seems inappropriate.=20

Actually, according to that model, I would even say that receipt of a =
message with a <msg-hop-count>  >1 should be interpreted as a =
malfunction.

As you refer to RFC5444 appendix B, do note that Appendix B of RFC5444 =
(and, note the errata 4003) talks about:

      <msg-hop-limit> field, if present, contains the number of hops on
      which the message is allowed to travel before being discarded by a
      MANET router.  The <msg-hop-limit> is set by the message
      originator and is used to prevent messages from endlessly
      circulating in a MANET.=20

Specifically =E2=80=9Cset by the message originator=E2=80=9D and =
=E2=80=9Cnumber of hops on which the message is allowed to travel=E2=80=9D=
 =E2=80=94 with your control messages traveling just one hop, I believe =
that setting <msg-hop-limit> =3D 1 is correct.

Best,

Thomas
> Kind regards,
> Victoria.
>=20
>=20
> On Wed, Nov 18, 2015 at 8:49 AM, Christopher Dearlove =
<christopher.dearlove@gmail.com <mailto:christopher.dearlove@gmail.com>> =
wrote:
> I've not had time to look at either yet, though I hope to review DLEP =
very soon.
>=20
> But this has made me think about the RFC 6621 reference in AODVv2. =
It's always been clear this has been rather a throwaway comment that =
needed thought, but until now I hadn't really given it any.
>=20
> And it doesn't work. RFC 6621 is fundamentally unusable here. Let's =
consider each on turn.=20
>=20
> AODVv2 is in the RFC 5444 structure. As has been noted on many =
occasions, AOVDVv2 gets to use messages, but packets are not in its =
competence.
>=20
> RFC 6621 is about packets. But not even RFC 5444 packets but IP =
packets. It's about whether or not to forward them. But RFC 5444 packets =
aren't just not forwarded in unchanged IP packets, they aren't even =
forwarded at all. They are each a single hop construct, and if a message =
is forwarded (which is by the routing protocol, as far as RFC 5444 is =
concerned, it's a new message) it will be in a new packet, with possibly =
new companions.
>=20
> If AODVv2 wants to use a more efficient flooding process, it needs one =
at the message level. Now an example of that exists - the mechanism on =
RFC 7181. Unfortunately we didn't break that out as a separate draft (we =
would have liked to, but there were reasons we didn't).
>=20
> And even if (by reference or other means) it were used - or some =
related mechanism such as a CDS - that processing/forwarding mechanism =
assumes you have defined MPRs (or similarly, that you have defined a =
CDS). And that needs a local exchange of information, such as NHDP's =
HELLO messages (and the rest of NHDP) augmented with RFC 7181's MPR TLV =
(though only the flooding bit is needed).
>=20
> In other words, taking some real work to define. And also raising a =
question for the WG - why do we want a reactive protocol? The main =
attraction as I see it is the "if you're not doing anything, you're not =
transmitting" property. Which adding this voids. Of course maybe the WG =
doesn't value that. Or it is acceptable as an option. But if so it needs =
to be an option that all routers use, or none. And if all, compatibly. =
(MPR flooding allows different MPR selection algorithms - but only as =
long as they satisfy the fundamental MPR algorithm properties.)
>=20
> In short, RFC 6621 must go. The alternative is nothing, or significant =
work.
>=20
> -- =20
> Christopher Dearlove
> christopher.dearlove@gmail.com <mailto:christopher.dearlove@gmail.com> =
(iPhone)
> chris@mnemosyne.demon.co.uk <mailto:chris@mnemosyne.demon.co.uk> =
(home)
>=20
> On 18 Nov 2015, at 01:35, Thomas Clausen <ietf@thomasclausen.org =
<mailto:ietf@thomasclausen.org>> wrote:
>=20
>> Dear all,
>>=20
>> I have started looking through the recently updated =
draft-ietf-manet-aodvv2-12. A lot has changed, and I regret not to have =
had a blow-by-bow comeback to the previous review comments  - would have =
made it a somewhat easier task to check if all have been addressed or =
not.
>>=20
>> But, I will work through it and produce a detailed review - but from =
my first quick read-through there're a couple of issue that jumped at me =
as worth bringing forward on a more global level already.
>>=20
>> The first relates to  how RREQs are forwarded -- or, more generally, =
are not.
>>=20
>> The protocol currently talks about "message is regenerated" rather =
than "forwarded". I have understood that this means that a RREQ is =
actually not an "end to end" entity, but is a "hop by hop" entity.=20
>>=20
>> First, that is a curious design choice, is there any reason why this =
is so considered?
>>=20
>> Second, if a RREQ message is hop-by-hop only, then I do not think =
that the use of the RFC5444 hop-limit/hop-count fields is appropriate.
>>=20
>> Third, the statement in section 6.5 on the use of RFC6621 is =
incorrect in two ways: RFC6621 does specify how messages are *forwarded* =
(but, as discussed above, you are not forwarding messages).
>>=20
>> More seriously, this paragraph is incorrect:
>>=20
>>> "Implementations MAY choose to employ techniques to reduce the =
number of multicast messages sent. Use of [RFC6621 =
<https://tools.ietf.org/html/rfc6621>] in deployments is recommended. =
Employing [RFC6621 <https://tools.ietf.org/html/rfc6621>] in a subset of =
the operational AODVv2 routers in a network, or configuring different =
algorithms on different routers, will not cause interoperability issues, =
but will reduce the effectiveness of the multicast reduction scheme."
>>=20
>>=20
>> Different routers using different relay selection algorithms in the =
same network will not *just* cause loss of efficiency, but *will* cause =
interoperability issues.
>>=20
>> For example if "router A" decides to suppress its message relaying =
because it estimates that "router B" provides sufficient coverage - and =
conversely "router B" suppresses relaying for the same reason: neither A =
nor B would relay, and so any routers reachable only via A and B would =
not be covered.
>>=20
>> This is not a far-sought example: it can be as simple as A and B =
simply using self-selecting relay algorithms with different =
tie-breakers.
>>=20
>> In short: I think that the whole message flooding/regeneration part =
requires serious work.
>>=20
>> The second issue is that I also suspect that there is some issue with =
buffering, or rather with how it is specified; starting in section 6.6, =
I am not sure that leaving that as "a matter of policy at each router" =
is entirely right.=20
>>=20
>> Also on buffering, I am wondering if the "start delivering buffered =
packets" conditions (penultimate paragraph in 6.6, and of course through =
the processing sections) is sufficient; I suspect that the condition =
"When a valid route is installed" is not sufficient - that there are =
situations where a routing table entry is installed, but the complete =
route is not available or is not bidirectional?This obviously is related =
to RREP_Ack being hop-by-hop and not end-to-end....
>>=20
>> Either way, the parts of the specification that relate to buffering =
contain a mixture of normative and non-normative verbiage (a lot of =
"can" but also a lot of MUST/SHOULD) which I think could do with a =
tightening up.=20
>>=20
>> But....is buffering even something that should be specified by this =
document? It does not impact interoperability and it interferes =
substantially with transport and congestion control, and I am not sure =
that we understand the consequences (I am not convinced that the claims =
in the document on benefits to TCP are substantiated or even true).
>>=20
>> As I indicated, a complete review will follow, but I thought that =
these was a global enough topics to call out and get engineered right.
>>=20
>> Thomas
>>=20
>> PS: I remain convinced that the security considerations section is =
insufficient ; I will try to articulate my thoughts on why that is, but =
for starters looking at the recently raised (by somebody else, the Chris =
replied) AODV security questions would probably be helpful
>>=20
>> On 10 Nov 2015, at 02:10, Ratliff, Stanley <sratliff@idirect.net =
<mailto:sratliff@idirect.net>> wrote:
>>=20
>>> Hello WG participants =E2=80=93
>>>=20
>>> =20
>>>=20
>>> The above referenced drafts were posted Oct. 13 (for AODVv2), and =
Oct. 16 (DLEP). The co-authors and the chairs ask that you please take =
some time to review and comment on the new submissions.
>>>=20
>>> =20
>>>=20
>>> Regards,
>>>=20
>>> Stan
>>>=20
>>> =20
>>>=20
>>> =20
>>>=20
>>>=20
>>> _____________________________________________________
>>> This electronic message and any files transmitted with it contains
>>> information from iDirect, which may be privileged, proprietary
>>> and/or confidential. It is intended solely for the use of the =
individual
>>> or entity to whom they are addressed. If you are not the original
>>> recipient or the person responsible for delivering the email to the
>>> intended recipient, be advised that you have received this email
>>> in error, and that any use, dissemination, forwarding, printing, or
>>> copying of this email is strictly prohibited. If you received this =
email
>>> in error, please delete it and immediately notify the sender.
>>> _____________________________________________________
>>> _______________________________________________
>>> manet mailing list
>>> manet@ietf.org <mailto:manet@ietf.org>
>>> https://www.ietf.org/mailman/listinfo/manet =
<https://www.ietf.org/mailman/listinfo/manet>
>> _______________________________________________
>> manet mailing list
>> manet@ietf.org <mailto:manet@ietf.org>
>> https://www.ietf.org/mailman/listinfo/manet =
<https://www.ietf.org/mailman/listinfo/manet>
>=20
> _______________________________________________
> manet mailing list
> manet@ietf.org <mailto:manet@ietf.org>
> https://www.ietf.org/mailman/listinfo/manet =
<https://www.ietf.org/mailman/listinfo/manet>
>=20
>=20
>=20
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www.ietf.org/mailman/listinfo/manet


--Apple-Mail=_0C0AEDA7-A581-4C36-8823-F8C99D4FD18D
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D"">Victoria,<div class=3D""><br class=3D""><div><blockquote =
type=3D"cite" class=3D""><div class=3D"">On Nov 19, 2015, at 17:09, =
Victoria Mercieca &lt;<a href=3D"mailto:vmercieca0@gmail.com" =
class=3D"">vmercieca0@gmail.com</a>&gt; wrote:</div><div class=3D""><div =
dir=3D"ltr" class=3D"">Hi Thomas and Christopher,<br class=3D""><div =
class=3D"gmail_quote"><div dir=3D"ltr" class=3D""><p dir=3D"ltr" =
class=3D"">Thank you for your comments.&nbsp; If I may address just one=20=

point for starters - regeneration vs forwarding. We use the term=20
regeneration since forwarding seems inappropriate when the message=20
content changes at each hop.</p><p dir=3D"ltr" class=3D"">The changes we =
make to the message content are:</p><p dir=3D"ltr" class=3D"">1) We =
change the metric so that each router along the path=20
learns a route from the message, with the metric associated with the=20
path up to that point<br class=3D"">
2) AckReq only applies between hops, so needs to be removed at each hop,
 and a new AckReq element may need to be added for the next hop.<br =
class=3D"">
3) ValidityTime could potentially be added by any intermediate router=20
that wishes to limit the time it will forward packets on the route.<br =
class=3D"">
4) Stripping out Unreachable Addresses from RERR which did not affect =
our route set.</p><p dir=3D"ltr" class=3D"">Can we really use the term =
"forwarding" if we are changing=20
the metric value, adding a validity time, adding/removing AckReq or=20
removing addresses and their associated =
TLVs?</p></div></div></div></div></blockquote><blockquote type=3D"cite" =
class=3D""><div class=3D""><div dir=3D"ltr" class=3D""><div =
class=3D"gmail_quote"><div dir=3D"ltr" class=3D""><p dir=3D"ltr" =
class=3D"">Further, in reply to the comment about use of the=20
msg-hop-count and msg-hop-limit fields, I think it does not matter that =
a
=20
message only travels one hop in that particular form, with that exact=20
set of information enclosed. Hop limit and hop count are part of the=20
message=20
and used by the routing protocol, and so they=20
refer to the multi-hop path that the AODVv2 message will follow,=20
indicating when not to regenerate any further. So=20
AODVv2 uses these fields as suggested in RFC5444 Appendix B, to limit=20
the number of hops across which it will regenerate a packet so as to=20
"prevent messages from endlessly circulating in a MANET=E2=80=9D. =
</p></div></div></div></div></blockquote><div><br =
class=3D""></div>Mmmh=E2=80=A6based on what you describe in the =
above:&nbsp;</div><div><br class=3D""></div><div><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</span>1)<span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</span>a router =
receiving a control message may chose to respond by doing =
any&nbsp;</div><div><span class=3D"Apple-tab-span" =
style=3D"white-space:pre">		</span>(and possibly more than =
one) of:</div><div><br class=3D""></div><div><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">			=
</span>a)<span class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</span>ignore the message</div><div><span class=3D"Apple-tab-span" =
style=3D"white-space:pre">			</span>b)<span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</span>process =
the&nbsp;message</div><div><span class=3D"Apple-tab-span" =
style=3D"white-space:pre">			</span>c)<span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</span>generate =
a new control message, possibly integrating the state</div><div><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">				=
</span>acquired through b.</div><div><br class=3D""></div><div><div><span =
class=3D"Apple-tab-span" style=3D"white-space: pre;">	</span>2)<span =
class=3D"Apple-tab-span" style=3D"white-space: pre;">	=
</span>consequently,&nbsp;your protocol control messages are only ever =
exchanged&nbsp;</div><div><span class=3D"Apple-tab-span" =
style=3D"white-space:pre">		</span>between neighboring =
routers</div><div class=3D""><br class=3D""></div></div><div>1c) is what =
you call =E2=80=9Cregenerate=E2=80=9D a control message - akin to any =
other DV protocol, which (possibly) shares its distance vector with its =
neighbors after having processed a received message.&nbsp;</div><div><br =
class=3D""></div><div>While I=E2=80=99m not sure that I particularly =
like the word =E2=80=9Cregenerate=E2=80=9D, I=E2=80=99m not too hung up =
on that =E2=80=94 but, at the very least it does deserve a precise =
definition somewhere in the specification since, at least, I stumbled =
over its interpretation.</div><div><br class=3D""></div><div>But, either =
way, as according to your model <b class=3D"">messages</b> are never =
forwarded, but always are intended for receipt by a router which is a =
direct neighbor, then a &lt;msg-hop-limit&gt; &nbsp;&gt;1 (which applies =
to the <b class=3D"">message</b>) seems =
inappropriate.&nbsp;</div><div><br class=3D""></div><div>Actually, =
according to that model, I would even say that receipt of a <b =
class=3D"">message</b> with a &lt;msg-hop-count&gt; &nbsp;&gt;1 should =
be interpreted as a malfunction.</div><div><br class=3D""></div><div>As =
you refer to RFC5444 appendix B, do note that Appendix B of RFC5444 =
(and, note the errata 4003) talks about:</div><div><br =
class=3D""></div><div><pre class=3D"newpage" style=3D"font-size: 13px; =
margin-top: 0px; margin-bottom: 0px; page-break-before: always;">      =
&lt;msg-hop-limit&gt; field, if present, contains the number of hops on
      which the message is allowed to travel before being discarded by a
      MANET router.  The &lt;msg-hop-limit&gt; is set by the message
      originator and is used to prevent messages from endlessly
      circulating in a MANET. </pre><div class=3D""><br =
class=3D""></div></div><div>Specifically =E2=80=9Cset by the <b =
class=3D"">message</b> originator=E2=80=9D and =E2=80=9Cnumber of hops =
on which the <b class=3D"">message</b> is allowed to travel=E2=80=9D =E2=80=
=94 with your control messages traveling just one hop, I believe that =
setting &lt;msg-hop-limit&gt; =3D 1 is correct.</div><div><br =
class=3D""></div><div>Best,</div><div><br =
class=3D""></div><div>Thomas</div><div><blockquote type=3D"cite" =
class=3D""><div class=3D""><div dir=3D"ltr" class=3D""><div =
class=3D"gmail_quote"><div dir=3D"ltr" class=3D""><p dir=3D"ltr" =
class=3D"">Kind regards,<br class=3D"">
Victoria.</p></div><div class=3D"HOEnZb"><div class=3D"h5"><div =
class=3D"gmail_extra"><br class=3D""><div class=3D"gmail_quote">On Wed, =
Nov 18, 2015 at 8:49 AM, Christopher Dearlove <span dir=3D"ltr" =
class=3D"">&lt;<a href=3D"mailto:christopher.dearlove@gmail.com" =
target=3D"_blank" class=3D"">christopher.dearlove@gmail.com</a>&gt;</span>=
 wrote:<br class=3D""><blockquote class=3D"gmail_quote" style=3D"margin:0 =
0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir=3D"auto" =
class=3D""><div class=3D"">I've not had time to look at either yet, =
though I hope to review DLEP very soon.</div><div class=3D""><br =
class=3D""></div><div class=3D"">But this has made me think about the =
RFC 6621 reference in AODVv2. It's always been clear this has been =
rather a throwaway comment that needed thought, but until now I hadn't =
really given it any.</div><div class=3D""><br class=3D""></div><div =
class=3D"">And it doesn't work. RFC 6621 is fundamentally unusable here. =
Let's consider each on turn.&nbsp;</div><div class=3D""><br =
class=3D""></div><div class=3D"">AODVv2 is in the RFC 5444 structure. As =
has been noted on many occasions, AOVDVv2 gets to use messages, but =
packets are not in its competence.</div><div class=3D""><br =
class=3D""></div><div class=3D"">RFC 6621 is about packets. But not even =
RFC 5444 packets but IP packets. It's about whether or not to forward =
them. But RFC 5444 packets aren't just not forwarded in unchanged IP =
packets, they aren't even forwarded at all. They are each a single hop =
construct, and if a message is forwarded (which is by the routing =
protocol, as far as RFC 5444 is concerned, it's a new message) it will =
be in a new packet, with possibly new companions.</div><div class=3D""><br=
 class=3D""></div><div class=3D"">If AODVv2 wants to use a more =
efficient flooding process, it needs one at the message level. Now an =
example of that exists - the mechanism on RFC 7181. Unfortunately we =
didn't break that out as a separate draft (we would have liked to, but =
there were reasons we didn't).</div><div class=3D""><br =
class=3D""></div><div class=3D"">And even if (by reference or other =
means) it were used - or some related mechanism such as a CDS - that =
processing/forwarding mechanism assumes you have defined MPRs (or =
similarly, that you have defined a CDS). And that needs a local exchange =
of information, such as NHDP's HELLO messages (and the rest of NHDP) =
augmented with RFC 7181's MPR TLV (though only the flooding bit is =
needed).</div><div class=3D""><br class=3D""></div><div class=3D"">In =
other words, taking some real work to define. And also raising a =
question for the WG - why do we want a reactive protocol? The main =
attraction as I see it is the "if you're not doing anything, you're not =
transmitting" property. Which adding this voids. Of course maybe the WG =
doesn't value that. Or it is acceptable as an option. But if so it needs =
to be an option that all routers use, or none. And if all, compatibly. =
(MPR flooding allows different MPR selection algorithms - but only as =
long as they satisfy the fundamental MPR algorithm =
properties.)</div><div class=3D""><br class=3D""></div><div class=3D"">In =
short, RFC 6621 must go. The alternative is nothing, or significant =
work.<br class=3D""><br class=3D""><div class=3D"">-- &nbsp;<span =
class=3D""><font color=3D"#888888" class=3D""><div class=3D"">Christopher =
Dearlove</div><div class=3D""><a =
href=3D"mailto:christopher.dearlove@gmail.com" target=3D"_blank" =
class=3D"">christopher.dearlove@gmail.com</a> (iPhone)</div><div =
class=3D""><a href=3D"mailto:chris@mnemosyne.demon.co.uk" =
target=3D"_blank" class=3D"">chris@mnemosyne.demon.co.uk</a> =
(home)</div></font></span></div></div><div class=3D""><div class=3D""><div=
 class=3D""><br class=3D"">On 18 Nov 2015, at 01:35, Thomas Clausen =
&lt;<a href=3D"mailto:ietf@thomasclausen.org" target=3D"_blank" =
class=3D"">ietf@thomasclausen.org</a>&gt; wrote:<br class=3D""><br =
class=3D""></div><blockquote type=3D"cite" class=3D""><div class=3D"">
<div class=3D"">Dear all,</div><div class=3D""><br class=3D""></div><div =
class=3D"">I have started looking through the recently =
updated&nbsp;draft-ietf-manet-aodvv2-12. A lot has changed, and I regret =
not to have had a blow-by-bow comeback to the previous review comments =
&nbsp;- would have made it a somewhat easier task to check if all have =
been addressed or not.</div><div class=3D""><br class=3D""></div><div =
class=3D"">But, I will work through it and produce a detailed review - =
but from my first quick read-through there're a couple of issue that =
jumped at me as worth bringing forward on a more global level =
already.</div><div class=3D""><br class=3D""></div><div class=3D"">The =
first relates to &nbsp;how RREQs are forwarded -- or, more generally, =
are not.</div><div class=3D""><br class=3D""></div><div class=3D"">The =
protocol currently talks about "message is regenerated" rather than =
"forwarded". I have understood that this means that a RREQ is actually =
not an "end to end" entity, but is a "hop by hop" =
entity.&nbsp;</div><div class=3D""><br class=3D""></div><div =
class=3D"">First, that is a curious design choice, is there any reason =
why this is so considered?</div><div class=3D""><br class=3D""></div><div =
class=3D"">Second, if a RREQ message is hop-by-hop only, then I do not =
think that the use of the RFC5444 hop-limit/hop-count fields is =
appropriate.</div><div class=3D""><br class=3D""></div><div =
class=3D"">Third, the statement in section 6.5 on the use of RFC6621 is =
incorrect in two ways: RFC6621 does specify how messages are *forwarded* =
(but, as discussed above, you are not forwarding messages).</div><div =
class=3D""><br class=3D""></div><div class=3D"">More seriously, this =
paragraph <span style=3D"background-color:rgba(255,255,255,0)" =
class=3D"">is incorrect</span>:</div><div class=3D""><pre =
style=3D"margin-top:0px;margin-bottom:0px" class=3D""><font =
face=3D"UICTFontTextStyleTallBody" class=3D""><span =
style=3D"white-space:normal;background-color:rgba(255,255,255,0)" =
class=3D""><br class=3D""></span></font></pre><pre =
style=3D"margin-top:0px;margin-bottom:0px" class=3D""><blockquote =
type=3D"cite" class=3D""><font face=3D"UICTFontTextStyleTallBody" =
class=3D""><span =
style=3D"white-space:normal;background-color:rgba(255,255,255,0)" =
class=3D"">"Implementations MAY choose to employ techniques to reduce =
the number
   of multicast messages sent.  Use of [<a =
href=3D"https://tools.ietf.org/html/rfc6621" title=3D"&quot;Simplified =
Multicast Forwarding&quot;" target=3D"_blank" class=3D"">RFC6621</a>] in =
deployments is
   recommended.  Employing [<a =
href=3D"https://tools.ietf.org/html/rfc6621" title=3D"&quot;Simplified =
Multicast Forwarding&quot;" target=3D"_blank" class=3D"">RFC6621</a>] in =
a subset of the operational
   AODVv2 routers in a network, or configuring different algorithms on
   different routers, will not cause interoperability issues, but will
   reduce the effectiveness of the multicast reduction =
scheme."</span></font><span style=3D"font-size:19px" class=3D"">
</span></blockquote></pre></div><div class=3D""><br class=3D""></div><div =
class=3D"">Different routers using different relay selection algorithms =
in the same network will not *just* cause loss of efficiency, but *will* =
cause interoperability issues.</div><div class=3D""><br =
class=3D""></div><div class=3D"">For example if "router A" decides to =
suppress its message relaying because it estimates that "router B" =
provides sufficient coverage - and conversely "router B" suppresses =
relaying for the same reason: neither A nor B would relay, and so any =
routers reachable only via A and B would not be covered.</div><div =
class=3D""><br class=3D""></div><div class=3D"">This is not a far-sought =
example: it can be as simple as A and B simply using self-selecting =
relay algorithms with different tie-breakers.</div><div class=3D""><br =
class=3D""></div><div class=3D"">In short: I think that the whole =
message flooding/regeneration part requires serious work.</div><div =
class=3D""><br class=3D""></div><div class=3D""><div class=3D""><span =
style=3D"background-color:rgba(255,255,255,0)" class=3D"">The second =
issue is that I also suspect that there is some issue with buffering, or =
rather with how it is specified; starting in section 6.6, I am not sure =
that leaving that as "a matter of policy at each router" is entirely =
right.&nbsp;</span></div><div class=3D""><span =
style=3D"background-color:rgba(255,255,255,0)" class=3D""><br =
class=3D""></span></div><div class=3D""><span =
style=3D"background-color:rgba(255,255,255,0)" class=3D"">Also on =
buffering, I am wondering if the "start delivering buffered packets" =
conditions (penultimate paragraph in 6.6, and of course through the =
processing sections) is sufficient; I suspect that the condition "When a =
valid route is installed" is not sufficient - that there are situations =
where a routing table entry is installed, but the complete route is not =
available or is not bidirectional?This obviously is related to RREP_Ack =
being hop-by-hop and not end-to-end....</span></div><div class=3D""><span =
style=3D"background-color:rgba(255,255,255,0)" class=3D""><br =
class=3D""></span></div><div class=3D""><span =
style=3D"background-color:rgba(255,255,255,0)" class=3D"">Either way, =
the parts of the specification that relate to buffering contain a =
mixture of normative and non-normative verbiage (a lot of "can" but also =
a lot of MUST/SHOULD) which I think could do with a tightening =
up.&nbsp;</span></div><div class=3D""><span =
style=3D"background-color:rgba(255,255,255,0)" class=3D""><br =
class=3D""></span></div><div class=3D""><span =
style=3D"background-color:rgba(255,255,255,0)" class=3D"">But....is =
buffering even something that should be specified by this document? It =
does not impact interoperability and it interferes substantially with =
transport and congestion control, and I am not sure that we understand =
the consequences (I am not convinced that the claims in the document on =
benefits to TCP are substantiated or even true).</span></div><div =
class=3D""><span style=3D"background-color:rgba(255,255,255,0)" =
class=3D""><br class=3D""></span><div class=3D"">As I indicated, a =
complete review will follow, but I thought that these was a global =
enough topics to call out and get engineered =
right.</div></div></div><div class=3D""><br class=3D""></div><div =
class=3D"">Thomas</div><div class=3D""><br class=3D""></div><div =
class=3D"">PS: I remain convinced that the security considerations =
section is insufficient ; I will try to articulate my thoughts on why =
that is, but for starters looking at the recently raised (by somebody =
else, the Chris replied) AODV security questions would probably be =
helpful</div><div class=3D""><div class=3D""></div></div><div =
class=3D""><br class=3D"">On 10 Nov 2015, at 02:10, Ratliff, Stanley =
&lt;<a href=3D"mailto:sratliff@idirect.net" target=3D"_blank" =
class=3D"">sratliff@idirect.net</a>&gt; wrote:<br class=3D""><br =
class=3D""></div><blockquote type=3D"cite" class=3D""><div class=3D"">






<div class=3D""><p class=3D"MsoNormal">Hello WG participants =E2=80=93 =
<u class=3D""></u><u class=3D""></u></p><p class=3D"MsoNormal"><u =
class=3D""></u>&nbsp;<u class=3D""></u></p><p class=3D"MsoNormal" =
style=3D"text-autospace:none"><span =
style=3D"font-size:12.0pt;font-family:&quot;Times New Roman&quot;,serif" =
class=3D"">The above referenced drafts were posted Oct. 13 (for AODVv2), =
and Oct. 16 (DLEP). The co-authors and the chairs ask that you please =
take some
 time to review and comment on the new submissions. <u class=3D""></u><u =
class=3D""></u></span></p><p class=3D"MsoNormal" =
style=3D"text-autospace:none"><span =
style=3D"font-size:12.0pt;font-family:&quot;Times New Roman&quot;,serif" =
class=3D""><u class=3D""></u>&nbsp;<u class=3D""></u></span></p><p =
class=3D"MsoNormal" style=3D"text-autospace:none"><span =
style=3D"font-size:12.0pt;font-family:&quot;Times New Roman&quot;,serif" =
class=3D"">Regards,<u class=3D""></u><u class=3D""></u></span></p><p =
class=3D"MsoNormal" style=3D"text-autospace:none"><span =
style=3D"font-size:12.0pt;font-family:&quot;Times New Roman&quot;,serif" =
class=3D"">Stan<u class=3D""></u><u class=3D""></u></span></p><p =
class=3D"MsoNormal" style=3D"text-autospace:none"><span =
style=3D"font-size:12.0pt;font-family:&quot;Times New Roman&quot;,serif" =
class=3D""><u class=3D""></u>&nbsp;<u class=3D""></u></span></p><p =
class=3D"MsoNormal"><u class=3D""></u>&nbsp;<u class=3D""></u></p>
</div>
<br class=3D""><span =
style=3D"font-size:8pt;font-family:Arial,sans-serif;color:#003366" =
class=3D"">_____________________________________________________<br =
class=3D"">This electronic message and any files transmitted with it =
contains<br class=3D"">information from iDirect, which may be =
privileged, proprietary<br class=3D"">and/or confidential. It is =
intended solely for the use of the individual<br class=3D"">or entity to =
whom they are addressed. If you are not the original<br =
class=3D"">recipient or the person responsible for delivering the email =
to the<br class=3D"">intended recipient, be advised that you have =
received this email<br class=3D"">in error, and that any use, =
dissemination, forwarding, printing, or<br class=3D"">copying of this =
email is strictly prohibited. If you received this email<br class=3D"">in =
error, please delete it and immediately notify the sender.<br =
class=3D"">_____________________________________________________</span>

</div></blockquote><blockquote type=3D"cite" class=3D""><div =
class=3D""><span =
class=3D"">_______________________________________________</span><br =
class=3D""><span class=3D"">manet mailing list</span><br class=3D""><span =
class=3D""><a href=3D"mailto:manet@ietf.org" target=3D"_blank" =
class=3D"">manet@ietf.org</a></span><br class=3D""><span class=3D""><a =
href=3D"https://www.ietf.org/mailman/listinfo/manet" target=3D"_blank" =
class=3D"">https://www.ietf.org/mailman/listinfo/manet</a></span><br =
class=3D""></div></blockquote></div></blockquote><blockquote type=3D"cite"=
 class=3D""><div class=3D""><span =
class=3D"">_______________________________________________</span><br =
class=3D""><span class=3D"">manet mailing list</span><br class=3D""><span =
class=3D""><a href=3D"mailto:manet@ietf.org" target=3D"_blank" =
class=3D"">manet@ietf.org</a></span><br class=3D""><span class=3D""><a =
href=3D"https://www.ietf.org/mailman/listinfo/manet" target=3D"_blank" =
class=3D"">https://www.ietf.org/mailman/listinfo/manet</a></span><br =
class=3D""></div></blockquote></div></div></div><br =
class=3D"">_______________________________________________<br class=3D"">
manet mailing list<br class=3D"">
<a href=3D"mailto:manet@ietf.org" target=3D"_blank" =
class=3D"">manet@ietf.org</a><br class=3D"">
<a href=3D"https://www.ietf.org/mailman/listinfo/manet" rel=3D"noreferrer"=
 target=3D"_blank" =
class=3D"">https://www.ietf.org/mailman/listinfo/manet</a><br class=3D"">
<br class=3D""></blockquote></div><br class=3D""></div>
</div></div></div><br class=3D""></div>
_______________________________________________<br class=3D"">manet =
mailing list<br class=3D""><a href=3D"mailto:manet@ietf.org" =
class=3D"">manet@ietf.org</a><br =
class=3D"">https://www.ietf.org/mailman/listinfo/manet<br =
class=3D""></div></blockquote></div><br class=3D""></div></body></html>=

--Apple-Mail=_0C0AEDA7-A581-4C36-8823-F8C99D4FD18D--


From nobody Thu Dec  3 03:43:38 2015
Return-Path: <jch@pps.univ-paris-diderot.fr>
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 3EE971B33FF for <manet@ietfa.amsl.com>; Thu,  3 Dec 2015 03:43:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.55
X-Spam-Level: 
X-Spam-Status: No, score=-1.55 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_FR=0.35] autolearn=no
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 wiA-xodetaBl for <manet@ietfa.amsl.com>; Thu,  3 Dec 2015 03:43:35 -0800 (PST)
Received: from korolev.univ-paris7.fr (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D0E2A1B33FD for <manet@ietf.org>; Thu,  3 Dec 2015 03:43:34 -0800 (PST)
Received: from mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [81.194.30.253]) by korolev.univ-paris7.fr (8.14.4/8.14.4/relay1/56228) with ESMTP id tB3BhWPg010817; Thu, 3 Dec 2015 12:43:32 +0100
Received: from mailhub.math.univ-paris-diderot.fr (localhost [127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTP id C9CFF61FBC; Thu,  3 Dec 2015 12:43:32 +0100 (CET)
X-Virus-Scanned: amavisd-new at math.univ-paris-diderot.fr
Received: from mailhub.math.univ-paris-diderot.fr ([127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [127.0.0.1]) (amavisd-new, port 10023) with ESMTP id liBcNOpTs5pJ; Thu,  3 Dec 2015 12:43:31 +0100 (CET)
Received: from lanthane.pps.univ-paris-diderot.fr (unknown [172.23.36.54]) (Authenticated sender: jch) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTPSA id 2231461F9A; Thu,  3 Dec 2015 12:43:31 +0100 (CET)
Received: from localhost ([::1] helo=lanthane.pps.univ-paris-diderot.fr) by lanthane.pps.univ-paris-diderot.fr with esmtp (Exim 4.86) (envelope-from <jch@pps.univ-paris-diderot.fr>) id 1a4SIM-0002us-TG; Thu, 03 Dec 2015 12:43:30 +0100
Date: Thu, 03 Dec 2015 12:43:30 +0100
Message-ID: <7iio4fpxjx.wl-jch@pps.univ-paris-diderot.fr>
From: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
To: Henning Rogge <hrogge@gmail.com>
In-Reply-To: <CAGnRvuqyE0zgLn_daLi8vrHkWeowTybFw4hrcQGGT-S=c=h_8w@mail.gmail.com>
References: <20151202221712.3505.78561.idtracker@ietfa.amsl.com> <CAGnRvurhqzAoNK_PQo6d3nVe9T0Buo3YFgSUfL0ibSP9+GB7MQ@mail.gmail.com> <7ipoynpzk2.wl-jch@pps.univ-paris-diderot.fr> <CAGnRvuqyE0zgLn_daLi8vrHkWeowTybFw4hrcQGGT-S=c=h_8w@mail.gmail.com>
User-Agent: Wanderlust/2.15.9
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (korolev.univ-paris7.fr [194.254.61.138]); Thu, 03 Dec 2015 12:43:32 +0100 (CET)
X-Miltered: at korolev with ID 56602AE4.007 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 56602AE4.007 from mailhub.math.univ-paris-diderot.fr/mailhub.math.univ-paris-diderot.fr/null/mailhub.math.univ-paris-diderot.fr/<jch@pps.univ-paris-diderot.fr>
X-j-chkmail-Score: MSGID : 56602AE4.007 on korolev.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Status: Ham
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/APtLb9wPZkoZyYwd5yM2B5XXYR0>
Cc: MANET IETF <manet@ietf.org>
Subject: Re: [manet] Ben Campbell's No Objection on draft-ietf-manet-olsrv2-dat-metric-10: (with COMMENT)
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: <https://mailarchive.ietf.org/arch/browse/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: Thu, 03 Dec 2015 11:43:36 -0000

>> Could you please explain?

> DAT metric uses the average of the packet loss event over a time
> period. While this helps to reduce the variance of the input, it also
> makes the metric slow to react to changes.

Right.

> I am still working on a more "statistical based" approach, but its not
> complete at the moment.

Have you looked at Section III.E of

  http://arxiv.org/pdf/1403.3488.pdf

-- Juliusz


From nobody Thu Dec  3 03:50:37 2015
Return-Path: <ietf@thomasclausen.org>
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 AB72D1B3402; Thu,  3 Dec 2015 03:50:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level: 
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, J_CHICKENPOX_35=0.6, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-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 hG8qqjYeCzsh; Thu,  3 Dec 2015 03:50:33 -0800 (PST)
Received: from maila2.tigertech.net (maila2.tigertech.net [208.80.4.152]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E7D6D1B33FA; Thu,  3 Dec 2015 03:50:33 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by maila2.tigertech.net (Postfix) with ESMTP id D492224089D; Thu,  3 Dec 2015 03:50:33 -0800 (PST)
X-Virus-Scanned: Debian amavisd-new at maila2.tigertech.net
Received: from [192.168.147.111] (mtg91-1-82-227-24-173.fbx.proxad.net [82.227.24.173]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by maila2.tigertech.net (Postfix) with ESMTPSA id 63F6524061E; Thu,  3 Dec 2015 03:50:32 -0800 (PST)
Mime-Version: 1.0 (Mac OS X Mail 9.1 \(3096.5\))
Content-Type: multipart/alternative; boundary="Apple-Mail=_540AA258-5A96-464A-9197-ED2BD97D152C"
From: ietf@thomasclausen.org
In-Reply-To: <CAGnRvurhqzAoNK_PQo6d3nVe9T0Buo3YFgSUfL0ibSP9+GB7MQ@mail.gmail.com>
Date: Thu, 3 Dec 2015 12:50:30 +0100
Sendlaterdate: Thu, 3 Dec 2015 12:50:30 +0100
Message-Id: <F3A2FB23-3BC2-43AB-B943-A9A39AF8168B@thomasclausen.org>
References: <20151202221712.3505.78561.idtracker@ietfa.amsl.com> <CAGnRvurhqzAoNK_PQo6d3nVe9T0Buo3YFgSUfL0ibSP9+GB7MQ@mail.gmail.com>
To: Henning Rogge <hrogge@gmail.com>
X-Mailer: Apple Mail (2.3096.5)
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/usZGUL6efKYIW6rsegC2rBHs81I>
Cc: Ben Campbell <ben@nostrum.com>, manet <manet@ietf.org>, The IESG <iesg@ietf.org>, draft-ietf-manet-olsrv2-dat-metric@ietf.org
Subject: Re: [manet] Ben Campbell's No Objection on draft-ietf-manet-olsrv2-dat-metric-10: (with COMMENT)
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: <https://mailarchive.ietf.org/arch/browse/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: Thu, 03 Dec 2015 11:50:35 -0000

--Apple-Mail=_540AA258-5A96-464A-9197-ED2BD97D152C
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Henning,

If I understood you correctly last we spoke on this matter:

	1)	DAT derived from a metric, with which you have great =
deployment experience
		when combined with OLSR(v2) =E2=80=94  but it is a =
derivative of, and not exactly=20
		that which you have deployed.

	2)	=E2=80=9CGreat deployment experience=E2=80=9D refers to =
one (large and long lasting)=20
		deployment, but (as far as we know) DAT has not been =
tested in multiple
		diverse deployments, certainly not exhaustively.

While I am confident that DAT is awesome (having played with it a =
little, but only in the lab), I do applaud your recommendation to go =
through an experimental phase before aiming for std.track.

I would be surprised, though, if in 1-2 years time we would not feel =
happy move it (possibly with some nits fixed) to std. track.

Best,

Thomas


> On Dec 3, 2015, at 10:34, Henning Rogge <hrogge@gmail.com =
<mailto:hrogge@gmail.com>> wrote:
>=20
> On Wed, Dec 2, 2015 at 11:17 PM, Ben Campbell <ben@nostrum.com =
<mailto:ben@nostrum.com>> wrote:
>> Ben Campbell has entered the following ballot position for
>> draft-ietf-manet-olsrv2-dat-metric-10: No Objection
>>=20
>> =
----------------------------------------------------------------------
>> COMMENT:
>> =
----------------------------------------------------------------------
>>=20
>> - section 1, last paragraph:
>> The first part of this paragraph sounds like justification for making
>> this standards track. It would be useful to discuss why this is
>> experimental.  Is there an expectation some version of this may be
>> republished in the standards track in the future? Is there a need for
>> deployment experience prior to standardization?
>=20
> While I think the metric should work well, I think it should get more
> testing by other parties in different scenarios and mesh topologies.
> This is the first metric published in the Manet WG, I don't feel
> comfortable to push it to standard track without more data.
>=20
> There is also the possibility that someone will come up with a better
> idea to calculate the packet loss over time than the "queue of
> counters" in the DAT metric. Something that detects a "relevant"
> metric change would be great and would allow the metric to change its
> value faster without producing more noise.
>=20
>> Editorial Comments:
>>=20
>> - Abstract:
>> Please expand OLSRv2 on first mention in abstract. (In addition to =
the
>> existing expansion in the body.)
>>=20
>> - section 4, 1st paragraph:
>> s/metric/metrics
>>=20
>>=20
>> _______________________________________________
>> manet mailing list
>> manet@ietf.org <mailto:manet@ietf.org>
>> https://www.ietf.org/mailman/listinfo/manet =
<https://www.ietf.org/mailman/listinfo/manet>
>=20
> _______________________________________________
> manet mailing list
> manet@ietf.org <mailto:manet@ietf.org>
> https://www.ietf.org/mailman/listinfo/manet =
<https://www.ietf.org/mailman/listinfo/manet>


--Apple-Mail=_540AA258-5A96-464A-9197-ED2BD97D152C
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dutf-8"><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dutf-8"><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D"">Henning,<div class=3D""><br class=3D""></div><div class=3D"">If=
 I understood you correctly last we spoke on this matter:</div><div =
class=3D""><br class=3D""></div><div class=3D""><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</span>1)<span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</span>DAT&nbsp;derived from a metric, with which you have great =
deployment experience</div><div class=3D""><span class=3D"Apple-tab-span" =
style=3D"white-space:pre">		</span>when combined with =
OLSR(v2) =E2=80=94 &nbsp;but it is a derivative of, and not <i =
class=3D"">exactly</i>&nbsp;</div><div class=3D""><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">		=
</span>that which you have deployed.</div><div class=3D""><br =
class=3D""></div><div class=3D""><span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span>2)<span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span>=E2=80=9CGreat deployment =
experience=E2=80=9D refers to one (large and long =
lasting)&nbsp;</div><div class=3D""><span class=3D"Apple-tab-span" =
style=3D"white-space:pre">		</span>deployment, but (as far =
as we know) DAT has not been tested in multiple</div><div class=3D""><span=
 class=3D"Apple-tab-span" style=3D"white-space:pre">		=
</span>diverse deployments, certainly not exhaustively.</div><div =
class=3D""><br class=3D""></div><div class=3D"">While I am confident =
that DAT is awesome (having played with it a little, but only in the =
lab), I do applaud your recommendation to go through an experimental =
phase before aiming for std.track.</div><div class=3D""><br =
class=3D""></div><div class=3D"">I would be surprised, though, if in 1-2 =
years time we would not feel happy move it (possibly with some nits =
fixed) to std. track.</div><div class=3D""><br class=3D""></div><div =
class=3D"">Best,</div><div class=3D""><br class=3D""></div><div =
class=3D"">Thomas</div><div class=3D""><br class=3D""></div><div =
class=3D""><br class=3D""></div><div class=3D""><div =
class=3D""><blockquote type=3D"cite" class=3D""><div class=3D"">On Dec =
3, 2015, at 10:34, Henning Rogge &lt;<a href=3D"mailto:hrogge@gmail.com" =
class=3D"">hrogge@gmail.com</a>&gt; wrote:</div><br =
class=3D"Apple-interchange-newline"><div class=3D""><div class=3D"">On =
Wed, Dec 2, 2015 at 11:17 PM, Ben Campbell &lt;<a =
href=3D"mailto:ben@nostrum.com" class=3D"">ben@nostrum.com</a>&gt; =
wrote:<br class=3D""><blockquote type=3D"cite" class=3D"">Ben Campbell =
has entered the following ballot position for<br =
class=3D"">draft-ietf-manet-olsrv2-dat-metric-10: No Objection<br =
class=3D""><br =
class=3D"">---------------------------------------------------------------=
-------<br class=3D"">COMMENT:<br =
class=3D"">---------------------------------------------------------------=
-------<br class=3D""><br class=3D"">- section 1, last paragraph:<br =
class=3D"">The first part of this paragraph sounds like justification =
for making<br class=3D"">this standards track. It would be useful to =
discuss why this is<br class=3D"">experimental. &nbsp;Is there an =
expectation some version of this may be<br class=3D"">republished in the =
standards track in the future? Is there a need for<br =
class=3D"">deployment experience prior to standardization?<br =
class=3D""></blockquote><br class=3D"">While I think the metric should =
work well, I think it should get more<br class=3D"">testing by other =
parties in different scenarios and mesh topologies.<br class=3D"">This =
is the first metric published in the Manet WG, I don't feel<br =
class=3D"">comfortable to push it to standard track without more =
data.<br class=3D""><br class=3D"">There is also the possibility that =
someone will come up with a better<br class=3D"">idea to calculate the =
packet loss over time than the "queue of<br class=3D"">counters" in the =
DAT metric. Something that detects a "relevant"<br class=3D"">metric =
change would be great and would allow the metric to change its<br =
class=3D"">value faster without producing more noise.<br class=3D""><br =
class=3D""><blockquote type=3D"cite" class=3D"">Editorial Comments:<br =
class=3D""><br class=3D"">- Abstract:<br class=3D"">Please expand OLSRv2 =
on first mention in abstract. (In addition to the<br class=3D"">existing =
expansion in the body.)<br class=3D""><br class=3D"">- section 4, 1st =
paragraph:<br class=3D"">s/metric/metrics<br class=3D""><br class=3D""><br=
 class=3D"">_______________________________________________<br =
class=3D"">manet mailing list<br class=3D""><a =
href=3D"mailto:manet@ietf.org" class=3D"">manet@ietf.org</a><br =
class=3D""><a href=3D"https://www.ietf.org/mailman/listinfo/manet" =
class=3D"">https://www.ietf.org/mailman/listinfo/manet</a><br =
class=3D""></blockquote><br =
class=3D"">_______________________________________________<br =
class=3D"">manet mailing list<br class=3D""><a =
href=3D"mailto:manet@ietf.org" class=3D"">manet@ietf.org</a><br =
class=3D""><a href=3D"https://www.ietf.org/mailman/listinfo/manet" =
class=3D"">https://www.ietf.org/mailman/listinfo/manet</a><br =
class=3D""></div></div></blockquote></div><br =
class=3D""></div></body></html>=

--Apple-Mail=_540AA258-5A96-464A-9197-ED2BD97D152C--


From nobody Thu Dec  3 04:03:03 2015
Return-Path: <hrogge@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 B59C51B343C for <manet@ietfa.amsl.com>; Thu,  3 Dec 2015 04:03:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 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, 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 nY7BRhWyTzTB for <manet@ietfa.amsl.com>; Thu,  3 Dec 2015 04:02:57 -0800 (PST)
Received: from mail-wm0-x234.google.com (mail-wm0-x234.google.com [IPv6:2a00:1450:400c:c09::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 398471B342E for <manet@ietf.org>; Thu,  3 Dec 2015 04:02:57 -0800 (PST)
Received: by wmvv187 with SMTP id v187so23655458wmv.1 for <manet@ietf.org>; Thu, 03 Dec 2015 04:02:55 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=izeun/TRZn0OhDKbetxOwQqbpphLAs5rth3k3wXxKyA=; b=YNoDhjjgUPPoVOwFxqSWH7ptGE4KW2JscGxLy9vGzvbU6pcB83D5jChCP3X+iQAK3l lJ1S4E5eww8O15pjRUYFh/PVhTLaoAXqgtFM9XKUWy1E4/Qi5CbcToHuqDNmXDmFf4bv 2OIV6C4gvQEvJstsogSzNSpfExbw9mu2Dy9zgem9zHJLL9pR96zMKZpG2ExK8un7GFX2 dlHzBsBfw14BaH5Z/JzsKn2B0yrMzq03ICsmyG8hnwIbjdpuXTGm6VskswSkDC2dDTL5 mPOtHZQyktfVXNsBnGlf//zoAgq3/WKJOzsHC3l2PHInPiTVsoQEJZ23fVetNhrj0ESv p/9Q==
X-Received: by 10.28.64.11 with SMTP id n11mr48228218wma.37.1449144175844; Thu, 03 Dec 2015 04:02:55 -0800 (PST)
MIME-Version: 1.0
Received: by 10.27.94.70 with HTTP; Thu, 3 Dec 2015 04:02:26 -0800 (PST)
In-Reply-To: <7iio4fpxjx.wl-jch@pps.univ-paris-diderot.fr>
References: <20151202221712.3505.78561.idtracker@ietfa.amsl.com> <CAGnRvurhqzAoNK_PQo6d3nVe9T0Buo3YFgSUfL0ibSP9+GB7MQ@mail.gmail.com> <7ipoynpzk2.wl-jch@pps.univ-paris-diderot.fr> <CAGnRvuqyE0zgLn_daLi8vrHkWeowTybFw4hrcQGGT-S=c=h_8w@mail.gmail.com> <7iio4fpxjx.wl-jch@pps.univ-paris-diderot.fr>
From: Henning Rogge <hrogge@gmail.com>
Date: Thu, 3 Dec 2015 13:02:26 +0100
Message-ID: <CAGnRvuosqTQ4v+4n42nP04Nz3OjebN+o1La04tu-WFfNyXkRuw@mail.gmail.com>
To: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/m-IQ838gutpW7NMojfEYmp-lo-g>
Cc: MANET IETF <manet@ietf.org>
Subject: Re: [manet] Ben Campbell's No Objection on draft-ietf-manet-olsrv2-dat-metric-10: (with COMMENT)
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: <https://mailarchive.ietf.org/arch/browse/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: Thu, 03 Dec 2015 12:03:01 -0000

On Thu, Dec 3, 2015 at 12:43 PM, Juliusz Chroboczek
<jch@pps.univ-paris-diderot.fr> wrote:
>>> Could you please explain?
>
>> DAT metric uses the average of the packet loss event over a time
>> period. While this helps to reduce the variance of the input, it also
>> makes the metric slow to react to changes.
>
> Right.
>
>> I am still working on a more "statistical based" approach, but its not
>> complete at the moment.
>
> Have you looked at Section III.E of
>
>   http://arxiv.org/pdf/1403.3488.pdf

We have experimented with exponential average for an ETX metric with
the OLSR.org olsrd implementation in the past and the results were...
not good.

The problem with using EWMA for frame/packet loss (as far as I
understand it) is that the input is purely binary... which means that
the EWMA is much more unstable than for "continuous input" like a
delay metric.

That is why we moved from EWMA to the current "fixed time average".

Henning


From nobody Thu Dec  3 04:25:18 2015
Return-Path: <Ietf@thomasclausen.org>
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 52FB01B3463 for <manet@ietfa.amsl.com>; Thu,  3 Dec 2015 04:25:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.401
X-Spam-Level: 
X-Spam-Status: No, score=-1.401 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, J_CHICKENPOX_35=0.6, J_CHICKENPOX_52=0.6, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=no
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 2KzqtXiLJtXs for <manet@ietfa.amsl.com>; Thu,  3 Dec 2015 04:25:11 -0800 (PST)
Received: from maila2.tigertech.net (maila2.tigertech.net [208.80.4.152]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B121F1A885C for <manet@ietf.org>; Thu,  3 Dec 2015 04:25:11 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by maila2.tigertech.net (Postfix) with ESMTP id 9E92624089D; Thu,  3 Dec 2015 04:25:11 -0800 (PST)
X-Virus-Scanned: Debian amavisd-new at maila2.tigertech.net
Received: from [192.168.147.111] (mtg91-1-82-227-24-173.fbx.proxad.net [82.227.24.173]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by maila2.tigertech.net (Postfix) with ESMTPSA id 3DA312406AB; Thu,  3 Dec 2015 04:25:10 -0800 (PST)
Mime-Version: 1.0 (Mac OS X Mail 9.1 \(3096.5\))
Content-Type: multipart/alternative; boundary="Apple-Mail=_202CAEA2-C510-4B37-B96E-0F632E4A0A8B"
From: ietf@thomasclausen.org
In-Reply-To: <CAAePS4AtbPekzU=m7aut08yHwZPmk-TiCdG4vvfNZtSWPowx=Q@mail.gmail.com>
Date: Thu, 3 Dec 2015 13:21:55 +0100
Sendlaterdate: Thu, 3 Dec 2015 13:21:55 +0100
Message-Id: <8228CBB8-BCB5-4ED9-9E0C-F76CD63D2DFC@thomasclausen.org>
References: <241ccb422cb941bda2617d7be275c649@VAUSDITCHM2.idirect.net> <9948DF10-0B9B-404E-BA09-C90CDE209756@thomasclausen.org> <DCC7ED56-7ED9-4610-91A0-3D70620B9823@gmail.com> <CAAePS4DtpBrWtgBbnWjLZN07mcyH=hmK0pzPvCrjwwLiTuXc2Q@mail.gmail.com> <CAAePS4AtbPekzU=m7aut08yHwZPmk-TiCdG4vvfNZtSWPowx=Q@mail.gmail.com>
To: Victoria Mercieca <vmercieca0@gmail.com>
X-Mailer: Apple Mail (2.3096.5)
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/q_jek_EXHyFTx6HDvTuqGt482Po>
Cc: manet <manet@ietf.org>
Subject: Re: [manet] draft-ietf-manet-aodvv2-12 and draft-ietf-manet-dlep-17
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: <https://mailarchive.ietf.org/arch/browse/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: Thu, 03 Dec 2015 12:25:16 -0000

--Apple-Mail=_202CAEA2-C510-4B37-B96E-0F632E4A0A8B
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Dear Victoria,

Responding twice to this email, intentionally as I want to address two =
different aspects independently=E2=80=A6.

> On Nov 19, 2015, at 17:09, Victoria Mercieca <vmercieca0@gmail.com> =
wrote:
>=20
>=20
> Hi Thomas and Christopher,
>=20
> Thank you for your comments.  If I may address just one point for =
starters - regeneration vs forwarding. We use the term regeneration =
since forwarding seems inappropriate when the message content changes at =
each hop.
>=20
> The changes we make to the message content are:
>=20
> 1) We change the metric so that each router along the path learns a =
route from the message, with the metric associated with the path up to =
that point
> 2) AckReq only applies between hops, so needs to be removed at each =
hop, and a new AckReq element may need to be added for the next hop.
> 3) ValidityTime could potentially be added by any intermediate router =
that wishes to limit the time it will forward packets on the route.
> 4) Stripping out Unreachable Addresses from RERR which did not affect =
our route set.
>=20
> Can we really use the term "forwarding" if we are changing the metric =
value, adding a validity time, adding/removing AckReq or removing =
addresses and their associated TLVs?
>=20
OK, so assume that I understand regeneration as per my previous email, =
as meaning =E2=80=9Cgenerate a new message and send to my neighbors, =
based on what I learned when processing a received message=E2=80=9D =E2=80=
=94 just like any distance vector protocol does.

In that model, what you write makes sense: each originator of a control =
message (i.e., whoever generates or regenerates it) is free to include =
the information it desires, such as the 4 points you list above. No =
issues with that.

However, and this joins what I pointed out in a previous email, you =
write in the applicability statement:

   Providing security for a reactive routing protocol can be difficult.

While we can discuss if the nature of =E2=80=9Creactive routing =
protocol=E2=80=9D generates particular difficulties, we certainly can =
agree that this protocol has the same =E2=80=9Cdifficulties=E2=80=9D as =
a distance vector protocol: routing topology information (by definition) =
not being exchanged end-to-end, but between neighbors (who do =
calculations and generate their own announcements =E2=80=94 =
regeneration, as you call it).=20

This means that a specific security model of transitive trust must be =
assumed, no? I trust Victoria, therefore when Victoria says =E2=80=9CStan =
told me=E2=80=9D then I trust that she actually verified that "it was =
indeed Stan who told her =E2=80=A6=E2=80=9D =E2=80=94 and either way, I =
have no way of verifying?

I did not see the trust model / trust assumption discussed in the =
specification (specifically not in applicability and in section 13, both =
of where it should be called out), but I think that this is actually a =
crucial point to get right, in order to approach developing the MTI =
security mechanisms.

Anyways, that observation actually contrasts strongly with what the =
applicability statement then goes on to say, namely:

   AODVv2 provides for message integrity and security against replay
   attacks by using integrity check values, timestamps and sequence
   numbers, as described in Section 13 =
<https://tools.ietf.org/html/draft-ietf-manet-aodvv2-12#section-13>.

This is true only in as much as messages are indeed exchanged between =
neighbors: when you =E2=80=9Cregenerate=E2=80=9D a message, i.e., =
generate a new message in response to receipt of a message, you generate =
brand new payload (but possibly including some of the data from the =
received message, of course): thus, any ICVs =E2=80=9Cfrom farther away =
than the neighbor=E2=80=9D will be useless (or, if you zero out the =
parts that you change, these parts will not be protected).

The above sentence, quoted from the applicability statement, and that =
which transpires from section 13, seems - certainly, absent the trust =
model assumed - to suggest that end-to-end protection/validation is =
provided. But, this is not the case.

Finally to the applicability statement, a question:

   If security associations can be
   established, encryption can be used for AODVv2 messages to ensure
   that only trusted routers participate in routing operations.

What you want to say here is that =E2=80=9Cif all trusted routers have a =
shared secret, then we=E2=80=99re able to use that shared secret to =
ignore non-trusted routers=E2=80=9D, right?=20
While =E2=80=9Csecurity associations=E2=80=9D that do not pass through a =
shared secret probably can be thought up, it=E2=80=99s not trivial and I =
did not find any discussion of that in the document?

Having, on the topic of security, re-read Section 13, which starts:

   This section describes various security considerations and potential
   avenues to secure AODVv2 routing. =20

While this is an honest description of what follows, I remain convinced =
that this is not sufficient. So let me ask as precisely as I can:

	o	what is the MTI security mechanism that a conformant =
implementation must provide?=20
		Specifically:
			-	which are the processing steps (for =
example in section 7.2.1=20
				and section 7.2.2 for RREP - and =
similarly for the other message=20
				types) that define that security =
mechanism

	o	what protection is offered by that MTI security =
mechanism? And what remains
		vulnerable.

If this specification targets std.track, then it should include =
(reasonably solid, but definitely well specified) MTI security.

Best

Thomas

> Further, in reply to the comment about use of the msg-hop-count and =
msg-hop-limit fields, I think it does not matter that a message only =
travels one hop in that particular form, with that exact set of =
information enclosed. Hop limit and hop count are part of the message =
and used by the routing protocol, and so they refer to the multi-hop =
path that the AODVv2 message will follow, indicating when not to =
regenerate any further. So AODVv2 uses these fields as suggested in =
RFC5444 Appendix B, to limit the number of hops across which it will =
regenerate a packet so as to "prevent messages from endlessly =
circulating in a MANET".
>=20
> Kind regards,
> Victoria.
>=20
>=20
> On Wed, Nov 18, 2015 at 8:49 AM, Christopher Dearlove =
<christopher.dearlove@gmail.com <mailto:christopher.dearlove@gmail.com>> =
wrote:
> I've not had time to look at either yet, though I hope to review DLEP =
very soon.
>=20
> But this has made me think about the RFC 6621 reference in AODVv2. =
It's always been clear this has been rather a throwaway comment that =
needed thought, but until now I hadn't really given it any.
>=20
> And it doesn't work. RFC 6621 is fundamentally unusable here. Let's =
consider each on turn.=20
>=20
> AODVv2 is in the RFC 5444 structure. As has been noted on many =
occasions, AOVDVv2 gets to use messages, but packets are not in its =
competence.
>=20
> RFC 6621 is about packets. But not even RFC 5444 packets but IP =
packets. It's about whether or not to forward them. But RFC 5444 packets =
aren't just not forwarded in unchanged IP packets, they aren't even =
forwarded at all. They are each a single hop construct, and if a message =
is forwarded (which is by the routing protocol, as far as RFC 5444 is =
concerned, it's a new message) it will be in a new packet, with possibly =
new companions.
>=20
> If AODVv2 wants to use a more efficient flooding process, it needs one =
at the message level. Now an example of that exists - the mechanism on =
RFC 7181. Unfortunately we didn't break that out as a separate draft (we =
would have liked to, but there were reasons we didn't).
>=20
> And even if (by reference or other means) it were used - or some =
related mechanism such as a CDS - that processing/forwarding mechanism =
assumes you have defined MPRs (or similarly, that you have defined a =
CDS). And that needs a local exchange of information, such as NHDP's =
HELLO messages (and the rest of NHDP) augmented with RFC 7181's MPR TLV =
(though only the flooding bit is needed).
>=20
> In other words, taking some real work to define. And also raising a =
question for the WG - why do we want a reactive protocol? The main =
attraction as I see it is the "if you're not doing anything, you're not =
transmitting" property. Which adding this voids. Of course maybe the WG =
doesn't value that. Or it is acceptable as an option. But if so it needs =
to be an option that all routers use, or none. And if all, compatibly. =
(MPR flooding allows different MPR selection algorithms - but only as =
long as they satisfy the fundamental MPR algorithm properties.)
>=20
> In short, RFC 6621 must go. The alternative is nothing, or significant =
work.
>=20
> -- =20
> Christopher Dearlove
> christopher.dearlove@gmail.com <mailto:christopher.dearlove@gmail.com> =
(iPhone)
> chris@mnemosyne.demon.co.uk <mailto:chris@mnemosyne.demon.co.uk> =
(home)
>=20
> On 18 Nov 2015, at 01:35, Thomas Clausen <ietf@thomasclausen.org =
<mailto:ietf@thomasclausen.org>> wrote:
>=20
>> Dear all,
>>=20
>> I have started looking through the recently updated =
draft-ietf-manet-aodvv2-12. A lot has changed, and I regret not to have =
had a blow-by-bow comeback to the previous review comments  - would have =
made it a somewhat easier task to check if all have been addressed or =
not.
>>=20
>> But, I will work through it and produce a detailed review - but from =
my first quick read-through there're a couple of issue that jumped at me =
as worth bringing forward on a more global level already.
>>=20
>> The first relates to  how RREQs are forwarded -- or, more generally, =
are not.
>>=20
>> The protocol currently talks about "message is regenerated" rather =
than "forwarded". I have understood that this means that a RREQ is =
actually not an "end to end" entity, but is a "hop by hop" entity.=20
>>=20
>> First, that is a curious design choice, is there any reason why this =
is so considered?
>>=20
>> Second, if a RREQ message is hop-by-hop only, then I do not think =
that the use of the RFC5444 hop-limit/hop-count fields is appropriate.
>>=20
>> Third, the statement in section 6.5 on the use of RFC6621 is =
incorrect in two ways: RFC6621 does specify how messages are *forwarded* =
(but, as discussed above, you are not forwarding messages).
>>=20
>> More seriously, this paragraph is incorrect:
>>=20
>>> "Implementations MAY choose to employ techniques to reduce the =
number of multicast messages sent. Use of [RFC6621 =
<https://tools.ietf.org/html/rfc6621>] in deployments is recommended. =
Employing [RFC6621 <https://tools.ietf.org/html/rfc6621>] in a subset of =
the operational AODVv2 routers in a network, or configuring different =
algorithms on different routers, will not cause interoperability issues, =
but will reduce the effectiveness of the multicast reduction scheme."
>>=20
>>=20
>> Different routers using different relay selection algorithms in the =
same network will not *just* cause loss of efficiency, but *will* cause =
interoperability issues.
>>=20
>> For example if "router A" decides to suppress its message relaying =
because it estimates that "router B" provides sufficient coverage - and =
conversely "router B" suppresses relaying for the same reason: neither A =
nor B would relay, and so any routers reachable only via A and B would =
not be covered.
>>=20
>> This is not a far-sought example: it can be as simple as A and B =
simply using self-selecting relay algorithms with different =
tie-breakers.
>>=20
>> In short: I think that the whole message flooding/regeneration part =
requires serious work.
>>=20
>> The second issue is that I also suspect that there is some issue with =
buffering, or rather with how it is specified; starting in section 6.6, =
I am not sure that leaving that as "a matter of policy at each router" =
is entirely right.=20
>>=20
>> Also on buffering, I am wondering if the "start delivering buffered =
packets" conditions (penultimate paragraph in 6.6, and of course through =
the processing sections) is sufficient; I suspect that the condition =
"When a valid route is installed" is not sufficient - that there are =
situations where a routing table entry is installed, but the complete =
route is not available or is not bidirectional?This obviously is related =
to RREP_Ack being hop-by-hop and not end-to-end....
>>=20
>> Either way, the parts of the specification that relate to buffering =
contain a mixture of normative and non-normative verbiage (a lot of =
"can" but also a lot of MUST/SHOULD) which I think could do with a =
tightening up.=20
>>=20
>> But....is buffering even something that should be specified by this =
document? It does not impact interoperability and it interferes =
substantially with transport and congestion control, and I am not sure =
that we understand the consequences (I am not convinced that the claims =
in the document on benefits to TCP are substantiated or even true).
>>=20
>> As I indicated, a complete review will follow, but I thought that =
these was a global enough topics to call out and get engineered right.
>>=20
>> Thomas
>>=20
>> PS: I remain convinced that the security considerations section is =
insufficient ; I will try to articulate my thoughts on why that is, but =
for starters looking at the recently raised (by somebody else, the Chris =
replied) AODV security questions would probably be helpful
>>=20
>> On 10 Nov 2015, at 02:10, Ratliff, Stanley <sratliff@idirect.net =
<mailto:sratliff@idirect.net>> wrote:
>>=20
>>> Hello WG participants =E2=80=93
>>>=20
>>> =20
>>>=20
>>> The above referenced drafts were posted Oct. 13 (for AODVv2), and =
Oct. 16 (DLEP). The co-authors and the chairs ask that you please take =
some time to review and comment on the new submissions.
>>>=20
>>> =20
>>>=20
>>> Regards,
>>>=20
>>> Stan
>>>=20
>>> =20
>>>=20
>>> =20
>>>=20
>>>=20
>>> _____________________________________________________
>>> This electronic message and any files transmitted with it contains
>>> information from iDirect, which may be privileged, proprietary
>>> and/or confidential. It is intended solely for the use of the =
individual
>>> or entity to whom they are addressed. If you are not the original
>>> recipient or the person responsible for delivering the email to the
>>> intended recipient, be advised that you have received this email
>>> in error, and that any use, dissemination, forwarding, printing, or
>>> copying of this email is strictly prohibited. If you received this =
email
>>> in error, please delete it and immediately notify the sender.
>>> _____________________________________________________
>>> _______________________________________________
>>> manet mailing list
>>> manet@ietf.org <mailto:manet@ietf.org>
>>> https://www.ietf.org/mailman/listinfo/manet =
<https://www.ietf.org/mailman/listinfo/manet>
>> _______________________________________________
>> manet mailing list
>> manet@ietf.org <mailto:manet@ietf.org>
>> https://www.ietf.org/mailman/listinfo/manet =
<https://www.ietf.org/mailman/listinfo/manet>
>=20
> _______________________________________________
> manet mailing list
> manet@ietf.org <mailto:manet@ietf.org>
> https://www.ietf.org/mailman/listinfo/manet =
<https://www.ietf.org/mailman/listinfo/manet>
>=20
>=20
>=20
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www.ietf.org/mailman/listinfo/manet


--Apple-Mail=_202CAEA2-C510-4B37-B96E-0F632E4A0A8B
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D"">Dear Victoria,<div class=3D""><br class=3D""></div><div =
class=3D"">Responding twice to this email, intentionally as I want to =
address two different aspects independently=E2=80=A6.</div><div =
class=3D""><br class=3D""></div><div class=3D""><div><blockquote =
type=3D"cite" class=3D""><div class=3D"">On Nov 19, 2015, at 17:09, =
Victoria Mercieca &lt;<a href=3D"mailto:vmercieca0@gmail.com" =
class=3D"">vmercieca0@gmail.com</a>&gt; wrote:</div><br =
class=3D"Apple-interchange-newline"><div class=3D""><div dir=3D"ltr" =
class=3D""><br class=3D""><div class=3D"gmail_quote"><div dir=3D"ltr" =
class=3D""><p dir=3D"ltr" class=3D"">Hi Thomas and Christopher,</p><p =
dir=3D"ltr" class=3D"">Thank you for your comments.&nbsp; If I may =
address just one=20
point for starters - regeneration vs forwarding. We use the term=20
regeneration since forwarding seems inappropriate when the message=20
content changes at each hop.</p><p dir=3D"ltr" class=3D"">The changes we =
make to the message content are:</p><p dir=3D"ltr" class=3D"">1) We =
change the metric so that each router along the path=20
learns a route from the message, with the metric associated with the=20
path up to that point<br class=3D"">
2) AckReq only applies between hops, so needs to be removed at each hop,
 and a new AckReq element may need to be added for the next hop.<br =
class=3D"">
3) ValidityTime could potentially be added by any intermediate router=20
that wishes to limit the time it will forward packets on the route.<br =
class=3D"">
4) Stripping out Unreachable Addresses from RERR which did not affect =
our route set.</p><p dir=3D"ltr" class=3D"">Can we really use the term =
"forwarding" if we are changing=20
the metric value, adding a validity time, adding/removing AckReq or=20
removing addresses and their associated =
TLVs?</p></div></div></div></div></blockquote>OK, so assume that I =
understand regeneration as per my previous email, as meaning =E2=80=9Cgene=
rate a new message and send to my neighbors, based on what I learned =
when processing a received message=E2=80=9D =E2=80=94 just like any =
distance vector protocol does.</div><div><br class=3D""></div><div>In =
that model, what you write makes sense: each originator of a control =
message (i.e., whoever generates or regenerates it) is free to include =
the information it desires, such as the 4 points you list above. No =
issues with that.</div><div><br class=3D""></div><div>However, and this =
joins what I pointed out in a previous email, you write in the =
applicability statement:</div><div><br class=3D""></div><div><pre =
class=3D"newpage" style=3D"font-size: 13px; margin-top: 0px; =
margin-bottom: 0px; page-break-before: always;">   Providing security =
for a reactive routing protocol can be difficult.</pre><pre =
class=3D"newpage" style=3D"font-size: 13px; margin-top: 0px; =
margin-bottom: 0px; page-break-before: always;"><span =
style=3D"font-family: Helvetica; font-size: 12px; white-space: normal;" =
class=3D""><br class=3D""></span></pre><pre class=3D"newpage" =
style=3D"margin-top: 0px; margin-bottom: 0px; page-break-before: =
always;"><font face=3D"Helvetica" class=3D""><span style=3D"white-space: =
normal;" class=3D"">While we can discuss if the nature =
of&nbsp;=E2=80=9Creactive routing protocol=E2=80=9D generates particular =
difficulties, we certainly can agree that this protocol has the =
same&nbsp;=E2=80=9Cdifficulties=E2=80=9D as a distance vector protocol: =
routing&nbsp;topology information (by definition) not being exchanged =
end-to-end, but between neighbors (who do&nbsp;calculations and generate =
their own announcements&nbsp;=E2=80=94 regeneration, as you call =
it).&nbsp;</span></font></pre><pre class=3D"newpage" style=3D"margin-top: =
0px; margin-bottom: 0px; page-break-before: always;"><font =
face=3D"Helvetica" class=3D""><span style=3D"white-space: normal;" =
class=3D""><br class=3D""></span></font></pre><pre class=3D"newpage" =
style=3D"margin-top: 0px; margin-bottom: 0px; page-break-before: =
always;"><font face=3D"Helvetica" class=3D""><span style=3D"white-space: =
normal;" class=3D"">This means that a specific security model of =
transitive trust must be assumed, no? I trust Victoria,&nbsp;therefore =
when Victoria says&nbsp;=E2=80=9CStan told me=E2=80=9D&nbsp;then I trust =
that she&nbsp;actually verified that "it was indeed Stan who told =
her&nbsp;=E2=80=A6=E2=80=9D&nbsp;=E2=80=94 and either way, I have no way =
of verifying?</span></font></pre><pre class=3D"newpage" =
style=3D"margin-top: 0px; margin-bottom: 0px; page-break-before: =
always;"><font face=3D"Helvetica" class=3D""><span style=3D"white-space: =
normal;" class=3D""><br class=3D""></span></font></pre><pre =
class=3D"newpage" style=3D"margin-top: 0px; margin-bottom: 0px; =
page-break-before: always;"><font face=3D"Helvetica" class=3D""><span =
style=3D"white-space: normal;" class=3D"">I did not see the trust model =
/ trust assumption discussed in the specification (specifically not in =
applicability and in section 13, both of where it should be called out), =
but I think that this is actually a crucial point to get right, in order =
to approach developing the MTI security =
mechanisms.</span></font></pre><pre class=3D"newpage" style=3D"margin-top:=
 0px; margin-bottom: 0px; page-break-before: always;"><br =
class=3D""></pre><pre class=3D"newpage" style=3D"margin-top: 0px; =
margin-bottom: 0px; page-break-before: always;"><font face=3D"Helvetica" =
class=3D""><span style=3D"white-space: normal;" class=3D"">Anyways, that =
observation actually contrasts strongly with what the applicability =
statement then goes on to say, namely:</span></font></pre><pre =
class=3D"newpage" style=3D"margin-top: 0px; margin-bottom: 0px; =
page-break-before: always;">
   AODVv2 provides for message integrity and security against replay
   attacks by using integrity check values, timestamps and sequence
   numbers, as described in <a =
href=3D"https://tools.ietf.org/html/draft-ietf-manet-aodvv2-12#section-13"=
 style=3D"font-size: 13px;" class=3D"">Section 13</a><font size=3D"3" =
class=3D"">.</font></pre><pre class=3D"newpage" style=3D"margin-top: =
0px; margin-bottom: 0px; page-break-before: always;"><font size=3D"3" =
class=3D""><br class=3D""></font></pre><pre class=3D"newpage" =
style=3D"margin-top: 0px; margin-bottom: 0px; page-break-before: =
always;"><pre class=3D"newpage" style=3D"margin-top: 0px; margin-bottom: =
0px; page-break-before: always;"><font face=3D"Helvetica" class=3D""><span=
 style=3D"white-space: normal;" class=3D"">This is true only in as much =
as messages are indeed exchanged between neighbors: when =
you&nbsp;=E2=80=9Cregenerate=E2=80=9D a message, i.e., generate a =
new&nbsp;message in response to receipt of a message, you generate brand =
new payload (but possibly including some of&nbsp;the data from the =
received message, of course): thus, any ICVs&nbsp;=E2=80=9Cfrom farther =
away than the neighbor=E2=80=9D&nbsp;will be useless (or, if you zero =
out the parts that you change, these parts will not be =
protected).</span></font></pre><pre class=3D"newpage" style=3D"margin-top:=
 0px; margin-bottom: 0px; page-break-before: always;"><font =
face=3D"Helvetica" class=3D""><span style=3D"white-space: normal;" =
class=3D""><br class=3D""></span></font></pre><pre class=3D"newpage" =
style=3D"margin-top: 0px; margin-bottom: 0px; page-break-before: =
always;"><font face=3D"Helvetica" class=3D""><span style=3D"white-space: =
normal;" class=3D"">The above sentence, quoted from the applicability =
statement, and that which transpires from section 13, seems - certainly, =
absent the trust model assumed - to suggest that end-to-end =
protection/validation is provided. But, this is <b class=3D""><u =
class=3D"">not</u></b> the case.</span></font></pre><pre class=3D"newpage"=
 style=3D"margin-top: 0px; margin-bottom: 0px; page-break-before: =
always;"><font face=3D"Helvetica" class=3D""><span style=3D"white-space: =
normal;" class=3D""><br class=3D""></span></font></pre><pre =
class=3D"newpage" style=3D"margin-top: 0px; margin-bottom: 0px; =
page-break-before: always;"><font face=3D"Helvetica" class=3D""><span =
style=3D"white-space: normal;" class=3D"">Finally to the applicability =
statement, a question:</span></font></pre><pre class=3D"newpage" =
style=3D"margin-top: 0px; margin-bottom: 0px; page-break-before: =
always;"><br class=3D""></pre></pre><pre class=3D"newpage" =
style=3D"margin-top: 0px; margin-bottom: 0px; page-break-before: =
always;"><font size=3D"3" class=3D"">   If security associations can be
   established, encryption can be used for AODVv2 messages to ensure
   that only trusted routers participate in routing =
operations.</font></pre><div class=3D""><br =
class=3D""></div></div><div>What you want to say here is that =E2=80=9Cif =
all trusted routers have a shared secret, then we=E2=80=99re able to use =
that shared secret to ignore non-trusted routers=E2=80=9D, =
right?&nbsp;</div><div>While =E2=80=9Csecurity associations=E2=80=9D =
that do not pass through a shared secret probably can be thought up, =
it=E2=80=99s not trivial and I did not find any discussion of that in =
the document?</div><div><br class=3D""></div><div>Having, on the topic =
of security, re-read Section 13, which starts:</div><div><br =
class=3D""></div><div><pre class=3D"newpage" style=3D"font-size: 13px; =
margin-top: 0px; margin-bottom: 0px; page-break-before: always;">   This =
section describes various security considerations and potential
   avenues to secure AODVv2 routing.  </pre><div class=3D""><br =
class=3D""></div></div><div>While this is an honest description of what =
follows, I remain convinced that this is not sufficient. So let me ask =
as precisely as I can:</div><div><br class=3D""></div><div><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</span>o<span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</span>what is =
the MTI security mechanism that a conformant implementation must =
provide?&nbsp;</div><div><span class=3D"Apple-tab-span" =
style=3D"white-space:pre">		=
</span>Specifically:</div><div><span class=3D"Apple-tab-span" =
style=3D"white-space:pre">			</span>-<span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</span>which are =
the processing steps (for example in section 7.2.1&nbsp;</div><div><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">				=
</span>and section 7.2.2 for RREP - and similarly for the other =
message&nbsp;</div><div><span class=3D"Apple-tab-span" =
style=3D"white-space:pre">				</span>types) =
that define that security mechanism</div><div><br =
class=3D""></div><div><span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span>o<span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span>what protection is offered by =
that MTI security mechanism? And what remains</div><div><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">		=
</span>vulnerable.</div><div><br class=3D""></div><div>If this =
specification targets std.track, then it should include (reasonably =
solid, but definitely well specified) MTI security.</div><div><br =
class=3D""></div><div>Best</div><div><br =
class=3D""></div><div>Thomas</div><div><br =
class=3D""></div><div><blockquote type=3D"cite" class=3D""><div =
class=3D""><div dir=3D"ltr" class=3D""><div class=3D"gmail_quote"><div =
dir=3D"ltr" class=3D""><p dir=3D"ltr" class=3D"">Further, in reply to =
the comment about use of the=20
msg-hop-count and msg-hop-limit fields, I think it does not matter that =
a
=20
message only travels one hop in that particular form, with that exact=20
set of information enclosed. Hop limit and hop count are part of the=20
message=20
and used by the routing protocol, and so they=20
refer to the multi-hop path that the AODVv2 message will follow,=20
indicating when not to regenerate any further. So=20
AODVv2 uses these fields as suggested in RFC5444 Appendix B, to limit=20
the number of hops across which it will regenerate a packet so as to=20
"prevent messages from endlessly circulating in a MANET". </p><p =
dir=3D"ltr" class=3D"">Kind regards,<br class=3D"">
Victoria.</p></div><div class=3D"HOEnZb"><div class=3D"h5"><div =
class=3D"gmail_extra"><br class=3D""><div class=3D"gmail_quote">On Wed, =
Nov 18, 2015 at 8:49 AM, Christopher Dearlove <span dir=3D"ltr" =
class=3D"">&lt;<a href=3D"mailto:christopher.dearlove@gmail.com" =
target=3D"_blank" class=3D"">christopher.dearlove@gmail.com</a>&gt;</span>=
 wrote:<br class=3D""><blockquote class=3D"gmail_quote" style=3D"margin:0 =
0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir=3D"auto" =
class=3D""><div class=3D"">I've not had time to look at either yet, =
though I hope to review DLEP very soon.</div><div class=3D""><br =
class=3D""></div><div class=3D"">But this has made me think about the =
RFC 6621 reference in AODVv2. It's always been clear this has been =
rather a throwaway comment that needed thought, but until now I hadn't =
really given it any.</div><div class=3D""><br class=3D""></div><div =
class=3D"">And it doesn't work. RFC 6621 is fundamentally unusable here. =
Let's consider each on turn.&nbsp;</div><div class=3D""><br =
class=3D""></div><div class=3D"">AODVv2 is in the RFC 5444 structure. As =
has been noted on many occasions, AOVDVv2 gets to use messages, but =
packets are not in its competence.</div><div class=3D""><br =
class=3D""></div><div class=3D"">RFC 6621 is about packets. But not even =
RFC 5444 packets but IP packets. It's about whether or not to forward =
them. But RFC 5444 packets aren't just not forwarded in unchanged IP =
packets, they aren't even forwarded at all. They are each a single hop =
construct, and if a message is forwarded (which is by the routing =
protocol, as far as RFC 5444 is concerned, it's a new message) it will =
be in a new packet, with possibly new companions.</div><div class=3D""><br=
 class=3D""></div><div class=3D"">If AODVv2 wants to use a more =
efficient flooding process, it needs one at the message level. Now an =
example of that exists - the mechanism on RFC 7181. Unfortunately we =
didn't break that out as a separate draft (we would have liked to, but =
there were reasons we didn't).</div><div class=3D""><br =
class=3D""></div><div class=3D"">And even if (by reference or other =
means) it were used - or some related mechanism such as a CDS - that =
processing/forwarding mechanism assumes you have defined MPRs (or =
similarly, that you have defined a CDS). And that needs a local exchange =
of information, such as NHDP's HELLO messages (and the rest of NHDP) =
augmented with RFC 7181's MPR TLV (though only the flooding bit is =
needed).</div><div class=3D""><br class=3D""></div><div class=3D"">In =
other words, taking some real work to define. And also raising a =
question for the WG - why do we want a reactive protocol? The main =
attraction as I see it is the "if you're not doing anything, you're not =
transmitting" property. Which adding this voids. Of course maybe the WG =
doesn't value that. Or it is acceptable as an option. But if so it needs =
to be an option that all routers use, or none. And if all, compatibly. =
(MPR flooding allows different MPR selection algorithms - but only as =
long as they satisfy the fundamental MPR algorithm =
properties.)</div><div class=3D""><br class=3D""></div><div class=3D"">In =
short, RFC 6621 must go. The alternative is nothing, or significant =
work.<br class=3D""><br class=3D""><div class=3D"">-- &nbsp;<span =
class=3D""><font color=3D"#888888" class=3D""><div class=3D"">Christopher =
Dearlove</div><div class=3D""><a =
href=3D"mailto:christopher.dearlove@gmail.com" target=3D"_blank" =
class=3D"">christopher.dearlove@gmail.com</a> (iPhone)</div><div =
class=3D""><a href=3D"mailto:chris@mnemosyne.demon.co.uk" =
target=3D"_blank" class=3D"">chris@mnemosyne.demon.co.uk</a> =
(home)</div></font></span></div></div><div class=3D""><div class=3D""><div=
 class=3D""><br class=3D"">On 18 Nov 2015, at 01:35, Thomas Clausen =
&lt;<a href=3D"mailto:ietf@thomasclausen.org" target=3D"_blank" =
class=3D"">ietf@thomasclausen.org</a>&gt; wrote:<br class=3D""><br =
class=3D""></div><blockquote type=3D"cite" class=3D""><div class=3D"">
<div class=3D"">Dear all,</div><div class=3D""><br class=3D""></div><div =
class=3D"">I have started looking through the recently =
updated&nbsp;draft-ietf-manet-aodvv2-12. A lot has changed, and I regret =
not to have had a blow-by-bow comeback to the previous review comments =
&nbsp;- would have made it a somewhat easier task to check if all have =
been addressed or not.</div><div class=3D""><br class=3D""></div><div =
class=3D"">But, I will work through it and produce a detailed review - =
but from my first quick read-through there're a couple of issue that =
jumped at me as worth bringing forward on a more global level =
already.</div><div class=3D""><br class=3D""></div><div class=3D"">The =
first relates to &nbsp;how RREQs are forwarded -- or, more generally, =
are not.</div><div class=3D""><br class=3D""></div><div class=3D"">The =
protocol currently talks about "message is regenerated" rather than =
"forwarded". I have understood that this means that a RREQ is actually =
not an "end to end" entity, but is a "hop by hop" =
entity.&nbsp;</div><div class=3D""><br class=3D""></div><div =
class=3D"">First, that is a curious design choice, is there any reason =
why this is so considered?</div><div class=3D""><br class=3D""></div><div =
class=3D"">Second, if a RREQ message is hop-by-hop only, then I do not =
think that the use of the RFC5444 hop-limit/hop-count fields is =
appropriate.</div><div class=3D""><br class=3D""></div><div =
class=3D"">Third, the statement in section 6.5 on the use of RFC6621 is =
incorrect in two ways: RFC6621 does specify how messages are *forwarded* =
(but, as discussed above, you are not forwarding messages).</div><div =
class=3D""><br class=3D""></div><div class=3D"">More seriously, this =
paragraph <span style=3D"background-color:rgba(255,255,255,0)" =
class=3D"">is incorrect</span>:</div><div class=3D""><pre =
style=3D"margin-top:0px;margin-bottom:0px" class=3D""><font =
face=3D"UICTFontTextStyleTallBody" class=3D""><span =
style=3D"white-space:normal;background-color:rgba(255,255,255,0)" =
class=3D""><br class=3D""></span></font></pre><pre =
style=3D"margin-top:0px;margin-bottom:0px" class=3D""><blockquote =
type=3D"cite" class=3D""><font face=3D"UICTFontTextStyleTallBody" =
class=3D""><span =
style=3D"white-space:normal;background-color:rgba(255,255,255,0)" =
class=3D"">"Implementations MAY choose to employ techniques to reduce =
the number
   of multicast messages sent.  Use of [<a =
href=3D"https://tools.ietf.org/html/rfc6621" title=3D"&quot;Simplified =
Multicast Forwarding&quot;" target=3D"_blank" class=3D"">RFC6621</a>] in =
deployments is
   recommended.  Employing [<a =
href=3D"https://tools.ietf.org/html/rfc6621" title=3D"&quot;Simplified =
Multicast Forwarding&quot;" target=3D"_blank" class=3D"">RFC6621</a>] in =
a subset of the operational
   AODVv2 routers in a network, or configuring different algorithms on
   different routers, will not cause interoperability issues, but will
   reduce the effectiveness of the multicast reduction =
scheme."</span></font><span style=3D"font-size:19px" class=3D"">
</span></blockquote></pre></div><div class=3D""><br class=3D""></div><div =
class=3D"">Different routers using different relay selection algorithms =
in the same network will not *just* cause loss of efficiency, but *will* =
cause interoperability issues.</div><div class=3D""><br =
class=3D""></div><div class=3D"">For example if "router A" decides to =
suppress its message relaying because it estimates that "router B" =
provides sufficient coverage - and conversely "router B" suppresses =
relaying for the same reason: neither A nor B would relay, and so any =
routers reachable only via A and B would not be covered.</div><div =
class=3D""><br class=3D""></div><div class=3D"">This is not a far-sought =
example: it can be as simple as A and B simply using self-selecting =
relay algorithms with different tie-breakers.</div><div class=3D""><br =
class=3D""></div><div class=3D"">In short: I think that the whole =
message flooding/regeneration part requires serious work.</div><div =
class=3D""><br class=3D""></div><div class=3D""><div class=3D""><span =
style=3D"background-color:rgba(255,255,255,0)" class=3D"">The second =
issue is that I also suspect that there is some issue with buffering, or =
rather with how it is specified; starting in section 6.6, I am not sure =
that leaving that as "a matter of policy at each router" is entirely =
right.&nbsp;</span></div><div class=3D""><span =
style=3D"background-color:rgba(255,255,255,0)" class=3D""><br =
class=3D""></span></div><div class=3D""><span =
style=3D"background-color:rgba(255,255,255,0)" class=3D"">Also on =
buffering, I am wondering if the "start delivering buffered packets" =
conditions (penultimate paragraph in 6.6, and of course through the =
processing sections) is sufficient; I suspect that the condition "When a =
valid route is installed" is not sufficient - that there are situations =
where a routing table entry is installed, but the complete route is not =
available or is not bidirectional?This obviously is related to RREP_Ack =
being hop-by-hop and not end-to-end....</span></div><div class=3D""><span =
style=3D"background-color:rgba(255,255,255,0)" class=3D""><br =
class=3D""></span></div><div class=3D""><span =
style=3D"background-color:rgba(255,255,255,0)" class=3D"">Either way, =
the parts of the specification that relate to buffering contain a =
mixture of normative and non-normative verbiage (a lot of "can" but also =
a lot of MUST/SHOULD) which I think could do with a tightening =
up.&nbsp;</span></div><div class=3D""><span =
style=3D"background-color:rgba(255,255,255,0)" class=3D""><br =
class=3D""></span></div><div class=3D""><span =
style=3D"background-color:rgba(255,255,255,0)" class=3D"">But....is =
buffering even something that should be specified by this document? It =
does not impact interoperability and it interferes substantially with =
transport and congestion control, and I am not sure that we understand =
the consequences (I am not convinced that the claims in the document on =
benefits to TCP are substantiated or even true).</span></div><div =
class=3D""><span style=3D"background-color:rgba(255,255,255,0)" =
class=3D""><br class=3D""></span><div class=3D"">As I indicated, a =
complete review will follow, but I thought that these was a global =
enough topics to call out and get engineered =
right.</div></div></div><div class=3D""><br class=3D""></div><div =
class=3D"">Thomas</div><div class=3D""><br class=3D""></div><div =
class=3D"">PS: I remain convinced that the security considerations =
section is insufficient ; I will try to articulate my thoughts on why =
that is, but for starters looking at the recently raised (by somebody =
else, the Chris replied) AODV security questions would probably be =
helpful</div><div class=3D""><div class=3D""></div></div><div =
class=3D""><br class=3D"">On 10 Nov 2015, at 02:10, Ratliff, Stanley =
&lt;<a href=3D"mailto:sratliff@idirect.net" target=3D"_blank" =
class=3D"">sratliff@idirect.net</a>&gt; wrote:<br class=3D""><br =
class=3D""></div><blockquote type=3D"cite" class=3D""><div class=3D"">






<div class=3D""><p class=3D"MsoNormal">Hello WG participants =E2=80=93 =
<u class=3D""></u><u class=3D""></u></p><p class=3D"MsoNormal"><u =
class=3D""></u>&nbsp;<u class=3D""></u></p><p class=3D"MsoNormal" =
style=3D"text-autospace:none"><span =
style=3D"font-size:12.0pt;font-family:&quot;Times New Roman&quot;,serif" =
class=3D"">The above referenced drafts were posted Oct. 13 (for AODVv2), =
and Oct. 16 (DLEP). The co-authors and the chairs ask that you please =
take some
 time to review and comment on the new submissions. <u class=3D""></u><u =
class=3D""></u></span></p><p class=3D"MsoNormal" =
style=3D"text-autospace:none"><span =
style=3D"font-size:12.0pt;font-family:&quot;Times New Roman&quot;,serif" =
class=3D""><u class=3D""></u>&nbsp;<u class=3D""></u></span></p><p =
class=3D"MsoNormal" style=3D"text-autospace:none"><span =
style=3D"font-size:12.0pt;font-family:&quot;Times New Roman&quot;,serif" =
class=3D"">Regards,<u class=3D""></u><u class=3D""></u></span></p><p =
class=3D"MsoNormal" style=3D"text-autospace:none"><span =
style=3D"font-size:12.0pt;font-family:&quot;Times New Roman&quot;,serif" =
class=3D"">Stan<u class=3D""></u><u class=3D""></u></span></p><p =
class=3D"MsoNormal" style=3D"text-autospace:none"><span =
style=3D"font-size:12.0pt;font-family:&quot;Times New Roman&quot;,serif" =
class=3D""><u class=3D""></u>&nbsp;<u class=3D""></u></span></p><p =
class=3D"MsoNormal"><u class=3D""></u>&nbsp;<u class=3D""></u></p>
</div>
<br class=3D""><span =
style=3D"font-size:8pt;font-family:Arial,sans-serif;color:#003366" =
class=3D"">_____________________________________________________<br =
class=3D"">This electronic message and any files transmitted with it =
contains<br class=3D"">information from iDirect, which may be =
privileged, proprietary<br class=3D"">and/or confidential. It is =
intended solely for the use of the individual<br class=3D"">or entity to =
whom they are addressed. If you are not the original<br =
class=3D"">recipient or the person responsible for delivering the email =
to the<br class=3D"">intended recipient, be advised that you have =
received this email<br class=3D"">in error, and that any use, =
dissemination, forwarding, printing, or<br class=3D"">copying of this =
email is strictly prohibited. If you received this email<br class=3D"">in =
error, please delete it and immediately notify the sender.<br =
class=3D"">_____________________________________________________</span>

</div></blockquote><blockquote type=3D"cite" class=3D""><div =
class=3D""><span =
class=3D"">_______________________________________________</span><br =
class=3D""><span class=3D"">manet mailing list</span><br class=3D""><span =
class=3D""><a href=3D"mailto:manet@ietf.org" target=3D"_blank" =
class=3D"">manet@ietf.org</a></span><br class=3D""><span class=3D""><a =
href=3D"https://www.ietf.org/mailman/listinfo/manet" target=3D"_blank" =
class=3D"">https://www.ietf.org/mailman/listinfo/manet</a></span><br =
class=3D""></div></blockquote></div></blockquote><blockquote type=3D"cite"=
 class=3D""><div class=3D""><span =
class=3D"">_______________________________________________</span><br =
class=3D""><span class=3D"">manet mailing list</span><br class=3D""><span =
class=3D""><a href=3D"mailto:manet@ietf.org" target=3D"_blank" =
class=3D"">manet@ietf.org</a></span><br class=3D""><span class=3D""><a =
href=3D"https://www.ietf.org/mailman/listinfo/manet" target=3D"_blank" =
class=3D"">https://www.ietf.org/mailman/listinfo/manet</a></span><br =
class=3D""></div></blockquote></div></div></div><br =
class=3D"">_______________________________________________<br class=3D"">
manet mailing list<br class=3D"">
<a href=3D"mailto:manet@ietf.org" target=3D"_blank" =
class=3D"">manet@ietf.org</a><br class=3D"">
<a href=3D"https://www.ietf.org/mailman/listinfo/manet" rel=3D"noreferrer"=
 target=3D"_blank" =
class=3D"">https://www.ietf.org/mailman/listinfo/manet</a><br class=3D"">
<br class=3D""></blockquote></div><br class=3D""></div>
</div></div></div><br class=3D""></div>
_______________________________________________<br class=3D"">manet =
mailing list<br class=3D""><a href=3D"mailto:manet@ietf.org" =
class=3D"">manet@ietf.org</a><br =
class=3D"">https://www.ietf.org/mailman/listinfo/manet<br =
class=3D""></div></blockquote></div><br class=3D""></div></body></html>=

--Apple-Mail=_202CAEA2-C510-4B37-B96E-0F632E4A0A8B--



From nobody Thu Dec  3 05:19:08 2015
Return-Path: <kathleen.moriarty.ietf@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 0B16B1A854B; Thu,  3 Dec 2015 05:19:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 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, 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 O3mBr47ukD33; Thu,  3 Dec 2015 05:19:02 -0800 (PST)
Received: from mail-qk0-x22d.google.com (mail-qk0-x22d.google.com [IPv6:2607:f8b0:400d:c09::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 371D51A86DF; Thu,  3 Dec 2015 05:19:00 -0800 (PST)
Received: by qkfo3 with SMTP id o3so29520740qkf.1; Thu, 03 Dec 2015 05:18:59 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=from:content-type:mime-version:subject:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=5Ts2VWQ339Zqsq58KUbdCFzClwkatxznn4r7XFFoYn0=; b=noJ5gtZkCDahLa5xE7BfyhOTLT+++V+TB1JIyVSGugFklKQRE3UdX70+un10oaVq+W CQUjWj5AOq0VI2ae/fi+3UgdNBleb1fZ7uqyVXZWDUlvUjXI0s17r15YJ1XJcQw830wr +Jv0cZaGy/YQHI9N1SHoJoleuhNEXpWF0TwkMgKR+pDbA9evCmxxMYnFqcbwmCAROJdN ssZg1yF1VQIfl0E3PaNdNiu7enVCdyRJFCpRQiAK0yDbWGDlbExzH2CPxmIu6BWK0Bym G3vjQD5FYE4JNtNzjhS/ZcsKc4iJL31v/OHDnVFXJDFmvZPEm3OFC5ElhC+swkymlcIC mquw==
X-Received: by 10.55.214.151 with SMTP id p23mr1351280qkl.8.1449148739383; Thu, 03 Dec 2015 05:18:59 -0800 (PST)
Received: from [172.20.3.0] ([65.200.157.66]) by smtp.gmail.com with ESMTPSA id 200sm3248043qhm.18.2015.12.03.05.18.58 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 03 Dec 2015 05:18:58 -0800 (PST)
From: Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com>
X-Google-Original-From: Kathleen Moriarty <Kathleen.Moriarty.ietf@gmail.com>
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (1.0)
X-Mailer: iPhone Mail (12H143)
In-Reply-To: <CAGnRvupncZMKj=iquh78+jiT5aTF2rbc43svznuxHc5F47GzBw@mail.gmail.com>
Date: Thu, 3 Dec 2015 08:18:57 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <710E4C55-A9D1-4DFA-928E-EEA0E75F485F@gmail.com>
References: <20151202221323.4668.69742.idtracker@ietfa.amsl.com> <CAGnRvupncZMKj=iquh78+jiT5aTF2rbc43svznuxHc5F47GzBw@mail.gmail.com>
To: Henning Rogge <hrogge@gmail.com>
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/4pSrLhDFvbnfw_V63QgTnZxtm5I>
Cc: "manet-chairs@ietf.org" <manet-chairs@ietf.org>, MANET IETF <manet@ietf.org>, The IESG <iesg@ietf.org>, "draft-ietf-manet-olsrv2-dat-metric@ietf.org" <draft-ietf-manet-olsrv2-dat-metric@ietf.org>
Subject: Re: [manet] Kathleen Moriarty's No Objection on draft-ietf-manet-olsrv2-dat-metric-10: (with COMMENT)
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: <https://mailarchive.ietf.org/arch/browse/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: Thu, 03 Dec 2015 13:19:04 -0000

Hi Henning,

Sent from my iPhone

> On Dec 3, 2015, at 3:10 AM, Henning Rogge <hrogge@gmail.com> wrote:
>=20
> On Wed, Dec 2, 2015 at 11:13 PM, Kathleen Moriarty
> <Kathleen.Moriarty.ietf@gmail.com> wrote:
>> ----------------------------------------------------------------------
>> COMMENT:
>> ----------------------------------------------------------------------
>>=20
>> This is just a comment as the text is mostly there, but I feel like it
>> could be stated more clearly...
>>=20
>> In the Security considerations section, the first part of the discussion
>> could call out "Denial of Service" attacks explicitly in addition to the
>> description that is included that describes altering traffic patterns.  I=

>> would recommend making this a distinct paragraph for readability.
>>=20
>> The next part of the security considerations section (starts with the
>> last sentence of the first paragraph) seems it could also be a result of
>> the lack of integrity protections on this measurement technique.  It
>> might help to state that first and that active attacks may result as a
>> consequence, leaving in the active attacks you already describe and the
>> solution already included starting with the second sentence of the second=

>> paragraph.  If that's not the case, please just let me know why.
>>=20
>> How is warning about MiTM attacks out-of-scope?  It seems these are
>> possible, and even mentioned with rogue routers.  Wouldn't it be easier
>> to state that without session encryption, MiTM is a threat?  If this is
>> acknowledged, then at least the consideration is there for the reader to
>> understand.  Addressing the threat may be out-of-scope, but warning about=

>> it shouldn't be.  This last comment is much closer to a discuss, so I'd
>> appreciate a response.
>=20
> MITM attacks are always a threat, even with TLS support. As long as
> both sides support "no-TLS", a MITM can easily downgrade the
> connection.

Sure, but that wasn't my request, it was to update the text to reflect the t=
hreat.  There's a lot that can be done to reduce the threat and the reader n=
eeds to be aware of such threats in the security considerations section.

Thanks,
Kathleen=20
>=20
> Henning Rogge


From nobody Thu Dec  3 05:26:34 2015
Return-Path: <chris.dearlove@baesystems.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 C2D8D1A871B for <manet@ietfa.amsl.com>; Thu,  3 Dec 2015 05:26:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.709
X-Spam-Level: 
X-Spam-Status: No, score=-5.709 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, J_CHICKENPOX_35=0.6, J_CHICKENPOX_52=0.6, RCVD_IN_DNSWL_HI=-5, T_RP_MATCHES_RCVD=-0.01] 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 wTTZ9WkwAfMO for <manet@ietfa.amsl.com>; Thu,  3 Dec 2015 05:26:26 -0800 (PST)
Received: from ukmta3.baesystems.com (ukmta3.baesystems.com [20.133.40.55]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A27FA1A8718 for <manet@ietf.org>; Thu,  3 Dec 2015 05:26:25 -0800 (PST)
X-IronPort-AV: E=Sophos; i="5.20,378,1444690800"; d="scan'208,217"; a="25224129"
Received: from unknown (HELO baemasodc005.greenlnk.net) ([10.108.52.29]) by ukmta3.baesystems.com with ESMTP; 03 Dec 2015 13:26:23 +0000
X-IronPort-AV: E=Sophos;i="5.20,378,1444690800";  d="scan'208,217";a="126021093"
Received: from glkxh0001v.greenlnk.net ([10.109.2.32]) by baemasodc005.greenlnk.net with ESMTP; 03 Dec 2015 13:26:24 +0000
Received: from GLKXM0002V.GREENLNK.net ([169.254.5.2]) by GLKXH0001V.GREENLNK.net ([10.109.2.32]) with mapi id 14.03.0248.002; Thu, 3 Dec 2015 13:26:23 +0000
From: "Dearlove, Christopher (UK)" <chris.dearlove@baesystems.com>
To: "ietf@thomasclausen.org" <ietf@thomasclausen.org>, Victoria Mercieca <vmercieca0@gmail.com>
Thread-Topic: [manet] draft-ietf-manet-aodvv2-12 and draft-ietf-manet-dlep-17
Thread-Index: AQHRLcWzXmm34XboyU2tJAb2q+76mJ65Ph+g
Date: Thu, 3 Dec 2015 13:26:22 +0000
Message-ID: <B31EEDDDB8ED7E4A93FDF12A4EECD30D7D76C1DB@GLKXM0002V.GREENLNK.net>
References: <241ccb422cb941bda2617d7be275c649@VAUSDITCHM2.idirect.net> <9948DF10-0B9B-404E-BA09-C90CDE209756@thomasclausen.org> <DCC7ED56-7ED9-4610-91A0-3D70620B9823@gmail.com> <CAAePS4DtpBrWtgBbnWjLZN07mcyH=hmK0pzPvCrjwwLiTuXc2Q@mail.gmail.com> <CAAePS4AtbPekzU=m7aut08yHwZPmk-TiCdG4vvfNZtSWPowx=Q@mail.gmail.com> <8228CBB8-BCB5-4ED9-9E0C-F76CD63D2DFC@thomasclausen.org>
In-Reply-To: <8228CBB8-BCB5-4ED9-9E0C-F76CD63D2DFC@thomasclausen.org>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.109.62.6]
Content-Type: multipart/alternative; boundary="_000_B31EEDDDB8ED7E4A93FDF12A4EECD30D7D76C1DBGLKXM0002VGREEN_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/k5qgrpv6cRHPRsnJwn0OUEUVQsQ>
Cc: manet <manet@ietf.org>
Subject: Re: [manet] draft-ietf-manet-aodvv2-12 and draft-ietf-manet-dlep-17
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: <https://mailarchive.ietf.org/arch/browse/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: Thu, 03 Dec 2015 13:26:33 -0000

--_000_B31EEDDDB8ED7E4A93FDF12A4EECD30D7D76C1DBGLKXM0002VGREEN_
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64

SWYgeW91IGdvIGRvd24gdGhpcyByb3V0ZSBvZiBhc3N1bWluZyB0cmFuc2l0aXZlIHRydXN0LCB0
aGVuIHlvdSBtaWdodCBhcyB3ZWxsIHVzZSA3MTgy4oCZcyBwYWNrZXQgSUNWIGFuZCB0aW1lc3Rh
bXAgcmF0aGVyIHRoYW4gbWVzc2FnZSBJQ1YgYW5kIHRpbWVzdGFtcC4NCg0KVGhlcmUgaXMgYSBj
b21wbGljYXRpb24gKG1vc3RseSBvbmUgb2YgcHJlc2VudGF0aW9uKSB0aGF0IHRoZSA1NDQ0IG11
bHRpcGxleGVyIChyYXRoZXIgdGhhbiBBT0RWdjIpIG5lZWRzIHRvIGRvIHRoaXMsIGF0IGxlYXN0
IGZvciBwYWNrZXRzIGNvbnRhaW5pbmcgQU9EVnYyIG1lc3NhZ2VzIChidXQgYXQgd2hpY2ggcG9p
bnQsIHByb2JhYmx5IGFsbCA1NDQ0IHBhY2tldHMpLiBTbyB5b3UgZWl0aGVyLCBkZXBlbmRpbmcg
b24geW91ciBwb2ludCBvZiB2aWV3LCBuZWVkIHRvIHJlcXVlc3QgaXQgdG8gZG8gdGhhdCwgb3Ig
KGFkbWluaXN0cmF0aXZlbHkpIGRlY2xpbmUgdG8gb3BlcmF0ZSBleGNlcHQgb3ZlciBhIDU0NDQg
bXVsdGlwbGV4ZXIgdGhhdCBpcyBkb2luZyB0aGlzLg0KDQpUaGUgYWR2YW50YWdlIGlzIG9uZSBv
ZiBzYXZlZCBzcGFjZSBhbmQgdGltZSB3aGVuIHBhY2tldHMgY29udGFpbiBtb3JlIHRoYW4gb25l
IG1lc3NhZ2UuIFBsdXMgc2xpZ2h0bHkgYmV0dGVyIHByb3RlY3Rpb24gKGhvcCBjb3VudCBhbmQg
bGltaXQgYXJlIGNvdmVyZWQpIGJ1dCB3aGljaCBwcm9iYWJseSBkb2VzbuKAmXQgbWF0dGVyIGhl
cmUuDQoNCklmIG1lc3NhZ2VzIGFyZSBjaGFuZ2VkL3JlcGxhY2VkIG9uIGEgb25lLXRvLW9uZSBi
YXNpcyBhcyBmb3J3YXJkZWQsIHRoZW4gdGhlIG9ubHkgc29sdXRpb25zIEkgY2FuIHNlZSBhcmUg
aG9wIGJ5IGhvcCB0cmFuc2l0aXZlIHRydXN0IChwYWNrZXRzIG9yIG1lc3NhZ2VzIHBlciBob3Ap
LCBvciBzb21ldGhpbmcgY29tcGxpY2F0ZWQgaW52b2x2aW5nIGFnZ3JlZ2F0aW9uIGFuZCBrbm93
bGVkZ2Ugb2YgY2hhbmdlcy4gQnV0IHRoZSBsYXR0ZXIgd291bGQgYmUgYSByZXNlYXJjaCB0YXNr
IHRvIGRldmVsb3AsIHNvIGxldOKAmXMgbm90IHRyeSB0aGF0Lg0KDQoNCkZyb206IG1hbmV0IFtt
YWlsdG86bWFuZXQtYm91bmNlc0BpZXRmLm9yZ10gT24gQmVoYWxmIE9mIGlldGZAdGhvbWFzY2xh
dXNlbi5vcmcNClNlbnQ6IDAzIERlY2VtYmVyIDIwMTUgMTI6MjINClRvOiBWaWN0b3JpYSBNZXJj
aWVjYQ0KQ2M6IG1hbmV0DQpTdWJqZWN0OiBSZTogW21hbmV0XSBkcmFmdC1pZXRmLW1hbmV0LWFv
ZHZ2Mi0xMiBhbmQgZHJhZnQtaWV0Zi1tYW5ldC1kbGVwLTE3DQoNCkRlYXIgVmljdG9yaWEsDQoN
ClJlc3BvbmRpbmcgdHdpY2UgdG8gdGhpcyBlbWFpbCwgaW50ZW50aW9uYWxseSBhcyBJIHdhbnQg
dG8gYWRkcmVzcyB0d28gZGlmZmVyZW50IGFzcGVjdHMgaW5kZXBlbmRlbnRseeKApi4NCg0KT24g
Tm92IDE5LCAyMDE1LCBhdCAxNzowOSwgVmljdG9yaWEgTWVyY2llY2EgPHZtZXJjaWVjYTBAZ21h
aWwuY29tPG1haWx0bzp2bWVyY2llY2EwQGdtYWlsLmNvbT4+IHdyb3RlOg0KDQoNCkhpIFRob21h
cyBhbmQgQ2hyaXN0b3BoZXIsDQpUaGFuayB5b3UgZm9yIHlvdXIgY29tbWVudHMuICBJZiBJIG1h
eSBhZGRyZXNzIGp1c3Qgb25lIHBvaW50IGZvciBzdGFydGVycyAtIHJlZ2VuZXJhdGlvbiB2cyBm
b3J3YXJkaW5nLiBXZSB1c2UgdGhlIHRlcm0gcmVnZW5lcmF0aW9uIHNpbmNlIGZvcndhcmRpbmcg
c2VlbXMgaW5hcHByb3ByaWF0ZSB3aGVuIHRoZSBtZXNzYWdlIGNvbnRlbnQgY2hhbmdlcyBhdCBl
YWNoIGhvcC4NClRoZSBjaGFuZ2VzIHdlIG1ha2UgdG8gdGhlIG1lc3NhZ2UgY29udGVudCBhcmU6
DQoxKSBXZSBjaGFuZ2UgdGhlIG1ldHJpYyBzbyB0aGF0IGVhY2ggcm91dGVyIGFsb25nIHRoZSBw
YXRoIGxlYXJucyBhIHJvdXRlIGZyb20gdGhlIG1lc3NhZ2UsIHdpdGggdGhlIG1ldHJpYyBhc3Nv
Y2lhdGVkIHdpdGggdGhlIHBhdGggdXAgdG8gdGhhdCBwb2ludA0KMikgQWNrUmVxIG9ubHkgYXBw
bGllcyBiZXR3ZWVuIGhvcHMsIHNvIG5lZWRzIHRvIGJlIHJlbW92ZWQgYXQgZWFjaCBob3AsIGFu
ZCBhIG5ldyBBY2tSZXEgZWxlbWVudCBtYXkgbmVlZCB0byBiZSBhZGRlZCBmb3IgdGhlIG5leHQg
aG9wLg0KMykgVmFsaWRpdHlUaW1lIGNvdWxkIHBvdGVudGlhbGx5IGJlIGFkZGVkIGJ5IGFueSBp
bnRlcm1lZGlhdGUgcm91dGVyIHRoYXQgd2lzaGVzIHRvIGxpbWl0IHRoZSB0aW1lIGl0IHdpbGwg
Zm9yd2FyZCBwYWNrZXRzIG9uIHRoZSByb3V0ZS4NCjQpIFN0cmlwcGluZyBvdXQgVW5yZWFjaGFi
bGUgQWRkcmVzc2VzIGZyb20gUkVSUiB3aGljaCBkaWQgbm90IGFmZmVjdCBvdXIgcm91dGUgc2V0
Lg0KQ2FuIHdlIHJlYWxseSB1c2UgdGhlIHRlcm0gImZvcndhcmRpbmciIGlmIHdlIGFyZSBjaGFu
Z2luZyB0aGUgbWV0cmljIHZhbHVlLCBhZGRpbmcgYSB2YWxpZGl0eSB0aW1lLCBhZGRpbmcvcmVt
b3ZpbmcgQWNrUmVxIG9yIHJlbW92aW5nIGFkZHJlc3NlcyBhbmQgdGhlaXIgYXNzb2NpYXRlZCBU
TFZzPw0KT0ssIHNvIGFzc3VtZSB0aGF0IEkgdW5kZXJzdGFuZCByZWdlbmVyYXRpb24gYXMgcGVy
IG15IHByZXZpb3VzIGVtYWlsLCBhcyBtZWFuaW5nIOKAnGdlbmVyYXRlIGEgbmV3IG1lc3NhZ2Ug
YW5kIHNlbmQgdG8gbXkgbmVpZ2hib3JzLCBiYXNlZCBvbiB3aGF0IEkgbGVhcm5lZCB3aGVuIHBy
b2Nlc3NpbmcgYSByZWNlaXZlZCBtZXNzYWdl4oCdIOKAlCBqdXN0IGxpa2UgYW55IGRpc3RhbmNl
IHZlY3RvciBwcm90b2NvbCBkb2VzLg0KDQpJbiB0aGF0IG1vZGVsLCB3aGF0IHlvdSB3cml0ZSBt
YWtlcyBzZW5zZTogZWFjaCBvcmlnaW5hdG9yIG9mIGEgY29udHJvbCBtZXNzYWdlIChpLmUuLCB3
aG9ldmVyIGdlbmVyYXRlcyBvciByZWdlbmVyYXRlcyBpdCkgaXMgZnJlZSB0byBpbmNsdWRlIHRo
ZSBpbmZvcm1hdGlvbiBpdCBkZXNpcmVzLCBzdWNoIGFzIHRoZSA0IHBvaW50cyB5b3UgbGlzdCBh
Ym92ZS4gTm8gaXNzdWVzIHdpdGggdGhhdC4NCg0KSG93ZXZlciwgYW5kIHRoaXMgam9pbnMgd2hh
dCBJIHBvaW50ZWQgb3V0IGluIGEgcHJldmlvdXMgZW1haWwsIHlvdSB3cml0ZSBpbiB0aGUgYXBw
bGljYWJpbGl0eSBzdGF0ZW1lbnQ6DQoNCg0KICAgUHJvdmlkaW5nIHNlY3VyaXR5IGZvciBhIHJl
YWN0aXZlIHJvdXRpbmcgcHJvdG9jb2wgY2FuIGJlIGRpZmZpY3VsdC4NCg0KDQpXaGlsZSB3ZSBj
YW4gZGlzY3VzcyBpZiB0aGUgbmF0dXJlIG9mIOKAnHJlYWN0aXZlIHJvdXRpbmcgcHJvdG9jb2zi
gJ0gZ2VuZXJhdGVzIHBhcnRpY3VsYXIgZGlmZmljdWx0aWVzLCB3ZSBjZXJ0YWlubHkgY2FuIGFn
cmVlIHRoYXQgdGhpcyBwcm90b2NvbCBoYXMgdGhlIHNhbWUg4oCcZGlmZmljdWx0aWVz4oCdIGFz
IGEgZGlzdGFuY2UgdmVjdG9yIHByb3RvY29sOiByb3V0aW5nIHRvcG9sb2d5IGluZm9ybWF0aW9u
IChieSBkZWZpbml0aW9uKSBub3QgYmVpbmcgZXhjaGFuZ2VkIGVuZC10by1lbmQsIGJ1dCBiZXR3
ZWVuIG5laWdoYm9ycyAod2hvIGRvIGNhbGN1bGF0aW9ucyBhbmQgZ2VuZXJhdGUgdGhlaXIgb3du
IGFubm91bmNlbWVudHMg4oCUIHJlZ2VuZXJhdGlvbiwgYXMgeW91IGNhbGwgaXQpLg0KDQoNClRo
aXMgbWVhbnMgdGhhdCBhIHNwZWNpZmljIHNlY3VyaXR5IG1vZGVsIG9mIHRyYW5zaXRpdmUgdHJ1
c3QgbXVzdCBiZSBhc3N1bWVkLCBubz8gSSB0cnVzdCBWaWN0b3JpYSwgdGhlcmVmb3JlIHdoZW4g
VmljdG9yaWEgc2F5cyDigJxTdGFuIHRvbGQgbWXigJ0gdGhlbiBJIHRydXN0IHRoYXQgc2hlIGFj
dHVhbGx5IHZlcmlmaWVkIHRoYXQgIml0IHdhcyBpbmRlZWQgU3RhbiB3aG8gdG9sZCBoZXIg4oCm
4oCdIOKAlCBhbmQgZWl0aGVyIHdheSwgSSBoYXZlIG5vIHdheSBvZiB2ZXJpZnlpbmc/DQoNCg0K
SSBkaWQgbm90IHNlZSB0aGUgdHJ1c3QgbW9kZWwgLyB0cnVzdCBhc3N1bXB0aW9uIGRpc2N1c3Nl
ZCBpbiB0aGUgc3BlY2lmaWNhdGlvbiAoc3BlY2lmaWNhbGx5IG5vdCBpbiBhcHBsaWNhYmlsaXR5
IGFuZCBpbiBzZWN0aW9uIDEzLCBib3RoIG9mIHdoZXJlIGl0IHNob3VsZCBiZSBjYWxsZWQgb3V0
KSwgYnV0IEkgdGhpbmsgdGhhdCB0aGlzIGlzIGFjdHVhbGx5IGEgY3J1Y2lhbCBwb2ludCB0byBn
ZXQgcmlnaHQsIGluIG9yZGVyIHRvIGFwcHJvYWNoIGRldmVsb3BpbmcgdGhlIE1USSBzZWN1cml0
eSBtZWNoYW5pc21zLg0KDQoNCkFueXdheXMsIHRoYXQgb2JzZXJ2YXRpb24gYWN0dWFsbHkgY29u
dHJhc3RzIHN0cm9uZ2x5IHdpdGggd2hhdCB0aGUgYXBwbGljYWJpbGl0eSBzdGF0ZW1lbnQgdGhl
biBnb2VzIG9uIHRvIHNheSwgbmFtZWx5Og0KDQoNCg0KICAgQU9EVnYyIHByb3ZpZGVzIGZvciBt
ZXNzYWdlIGludGVncml0eSBhbmQgc2VjdXJpdHkgYWdhaW5zdCByZXBsYXkNCg0KICAgYXR0YWNr
cyBieSB1c2luZyBpbnRlZ3JpdHkgY2hlY2sgdmFsdWVzLCB0aW1lc3RhbXBzIGFuZCBzZXF1ZW5j
ZQ0KDQogICBudW1iZXJzLCBhcyBkZXNjcmliZWQgaW4gU2VjdGlvbiAxMzxodHRwczovL3Rvb2xz
LmlldGYub3JnL2h0bWwvZHJhZnQtaWV0Zi1tYW5ldC1hb2R2djItMTIjc2VjdGlvbi0xMz4uDQoN
Cg0KVGhpcyBpcyB0cnVlIG9ubHkgaW4gYXMgbXVjaCBhcyBtZXNzYWdlcyBhcmUgaW5kZWVkIGV4
Y2hhbmdlZCBiZXR3ZWVuIG5laWdoYm9yczogd2hlbiB5b3Ug4oCccmVnZW5lcmF0ZeKAnSBhIG1l
c3NhZ2UsIGkuZS4sIGdlbmVyYXRlIGEgbmV3IG1lc3NhZ2UgaW4gcmVzcG9uc2UgdG8gcmVjZWlw
dCBvZiBhIG1lc3NhZ2UsIHlvdSBnZW5lcmF0ZSBicmFuZCBuZXcgcGF5bG9hZCAoYnV0IHBvc3Np
Ymx5IGluY2x1ZGluZyBzb21lIG9mIHRoZSBkYXRhIGZyb20gdGhlIHJlY2VpdmVkIG1lc3NhZ2Us
IG9mIGNvdXJzZSk6IHRodXMsIGFueSBJQ1ZzIOKAnGZyb20gZmFydGhlciBhd2F5IHRoYW4gdGhl
IG5laWdoYm9y4oCdIHdpbGwgYmUgdXNlbGVzcyAob3IsIGlmIHlvdSB6ZXJvIG91dCB0aGUgcGFy
dHMgdGhhdCB5b3UgY2hhbmdlLCB0aGVzZSBwYXJ0cyB3aWxsIG5vdCBiZSBwcm90ZWN0ZWQpLg0K
DQoNClRoZSBhYm92ZSBzZW50ZW5jZSwgcXVvdGVkIGZyb20gdGhlIGFwcGxpY2FiaWxpdHkgc3Rh
dGVtZW50LCBhbmQgdGhhdCB3aGljaCB0cmFuc3BpcmVzIGZyb20gc2VjdGlvbiAxMywgc2VlbXMg
LSBjZXJ0YWlubHksIGFic2VudCB0aGUgdHJ1c3QgbW9kZWwgYXNzdW1lZCAtIHRvIHN1Z2dlc3Qg
dGhhdCBlbmQtdG8tZW5kIHByb3RlY3Rpb24vdmFsaWRhdGlvbiBpcyBwcm92aWRlZC4gQnV0LCB0
aGlzIGlzIG5vdCB0aGUgY2FzZS4NCg0KDQpGaW5hbGx5IHRvIHRoZSBhcHBsaWNhYmlsaXR5IHN0
YXRlbWVudCwgYSBxdWVzdGlvbjoNCg0KDQogICBJZiBzZWN1cml0eSBhc3NvY2lhdGlvbnMgY2Fu
IGJlDQoNCiAgIGVzdGFibGlzaGVkLCBlbmNyeXB0aW9uIGNhbiBiZSB1c2VkIGZvciBBT0RWdjIg
bWVzc2FnZXMgdG8gZW5zdXJlDQoNCiAgIHRoYXQgb25seSB0cnVzdGVkIHJvdXRlcnMgcGFydGlj
aXBhdGUgaW4gcm91dGluZyBvcGVyYXRpb25zLg0KDQpXaGF0IHlvdSB3YW50IHRvIHNheSBoZXJl
IGlzIHRoYXQg4oCcaWYgYWxsIHRydXN0ZWQgcm91dGVycyBoYXZlIGEgc2hhcmVkIHNlY3JldCwg
dGhlbiB3ZeKAmXJlIGFibGUgdG8gdXNlIHRoYXQgc2hhcmVkIHNlY3JldCB0byBpZ25vcmUgbm9u
LXRydXN0ZWQgcm91dGVyc+KAnSwgcmlnaHQ/DQpXaGlsZSDigJxzZWN1cml0eSBhc3NvY2lhdGlv
bnPigJ0gdGhhdCBkbyBub3QgcGFzcyB0aHJvdWdoIGEgc2hhcmVkIHNlY3JldCBwcm9iYWJseSBj
YW4gYmUgdGhvdWdodCB1cCwgaXTigJlzIG5vdCB0cml2aWFsIGFuZCBJIGRpZCBub3QgZmluZCBh
bnkgZGlzY3Vzc2lvbiBvZiB0aGF0IGluIHRoZSBkb2N1bWVudD8NCg0KSGF2aW5nLCBvbiB0aGUg
dG9waWMgb2Ygc2VjdXJpdHksIHJlLXJlYWQgU2VjdGlvbiAxMywgd2hpY2ggc3RhcnRzOg0KDQoN
CiAgIFRoaXMgc2VjdGlvbiBkZXNjcmliZXMgdmFyaW91cyBzZWN1cml0eSBjb25zaWRlcmF0aW9u
cyBhbmQgcG90ZW50aWFsDQoNCiAgIGF2ZW51ZXMgdG8gc2VjdXJlIEFPRFZ2MiByb3V0aW5nLg0K
DQpXaGlsZSB0aGlzIGlzIGFuIGhvbmVzdCBkZXNjcmlwdGlvbiBvZiB3aGF0IGZvbGxvd3MsIEkg
cmVtYWluIGNvbnZpbmNlZCB0aGF0IHRoaXMgaXMgbm90IHN1ZmZpY2llbnQuIFNvIGxldCBtZSBh
c2sgYXMgcHJlY2lzZWx5IGFzIEkgY2FuOg0KDQogICAgICAgICAgICBvICAgICAgICAgIHdoYXQg
aXMgdGhlIE1USSBzZWN1cml0eSBtZWNoYW5pc20gdGhhdCBhIGNvbmZvcm1hbnQgaW1wbGVtZW50
YXRpb24gbXVzdCBwcm92aWRlPw0KICAgICAgICAgICAgICAgICAgICAgICAgU3BlY2lmaWNhbGx5
Og0KICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgLSAgICAgICAgICAgd2hpY2gg
YXJlIHRoZSBwcm9jZXNzaW5nIHN0ZXBzIChmb3IgZXhhbXBsZSBpbiBzZWN0aW9uIDcuMi4xDQog
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICBhbmQgc2VjdGlv
biA3LjIuMiBmb3IgUlJFUCAtIGFuZCBzaW1pbGFybHkgZm9yIHRoZSBvdGhlciBtZXNzYWdlDQog
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICB0eXBlcykgdGhh
dCBkZWZpbmUgdGhhdCBzZWN1cml0eSBtZWNoYW5pc20NCg0KICAgICAgICAgICAgbyAgICAgICAg
ICB3aGF0IHByb3RlY3Rpb24gaXMgb2ZmZXJlZCBieSB0aGF0IE1USSBzZWN1cml0eSBtZWNoYW5p
c20/IEFuZCB3aGF0IHJlbWFpbnMNCiAgICAgICAgICAgICAgICAgICAgICAgIHZ1bG5lcmFibGUu
DQoNCklmIHRoaXMgc3BlY2lmaWNhdGlvbiB0YXJnZXRzIHN0ZC50cmFjaywgdGhlbiBpdCBzaG91
bGQgaW5jbHVkZSAocmVhc29uYWJseSBzb2xpZCwgYnV0IGRlZmluaXRlbHkgd2VsbCBzcGVjaWZp
ZWQpIE1USSBzZWN1cml0eS4NCg0KQmVzdA0KDQpUaG9tYXMNCg0KRnVydGhlciwgaW4gcmVwbHkg
dG8gdGhlIGNvbW1lbnQgYWJvdXQgdXNlIG9mIHRoZSBtc2ctaG9wLWNvdW50IGFuZCBtc2ctaG9w
LWxpbWl0IGZpZWxkcywgSSB0aGluayBpdCBkb2VzIG5vdCBtYXR0ZXIgdGhhdCBhIG1lc3NhZ2Ug
b25seSB0cmF2ZWxzIG9uZSBob3AgaW4gdGhhdCBwYXJ0aWN1bGFyIGZvcm0sIHdpdGggdGhhdCBl
eGFjdCBzZXQgb2YgaW5mb3JtYXRpb24gZW5jbG9zZWQuIEhvcCBsaW1pdCBhbmQgaG9wIGNvdW50
IGFyZSBwYXJ0IG9mIHRoZSBtZXNzYWdlIGFuZCB1c2VkIGJ5IHRoZSByb3V0aW5nIHByb3RvY29s
LCBhbmQgc28gdGhleSByZWZlciB0byB0aGUgbXVsdGktaG9wIHBhdGggdGhhdCB0aGUgQU9EVnYy
IG1lc3NhZ2Ugd2lsbCBmb2xsb3csIGluZGljYXRpbmcgd2hlbiBub3QgdG8gcmVnZW5lcmF0ZSBh
bnkgZnVydGhlci4gU28gQU9EVnYyIHVzZXMgdGhlc2UgZmllbGRzIGFzIHN1Z2dlc3RlZCBpbiBS
RkM1NDQ0IEFwcGVuZGl4IEIsIHRvIGxpbWl0IHRoZSBudW1iZXIgb2YgaG9wcyBhY3Jvc3Mgd2hp
Y2ggaXQgd2lsbCByZWdlbmVyYXRlIGEgcGFja2V0IHNvIGFzIHRvICJwcmV2ZW50IG1lc3NhZ2Vz
IGZyb20gZW5kbGVzc2x5IGNpcmN1bGF0aW5nIGluIGEgTUFORVQiLg0KS2luZCByZWdhcmRzLA0K
VmljdG9yaWEuDQoNCk9uIFdlZCwgTm92IDE4LCAyMDE1IGF0IDg6NDkgQU0sIENocmlzdG9waGVy
IERlYXJsb3ZlIDxjaHJpc3RvcGhlci5kZWFybG92ZUBnbWFpbC5jb208bWFpbHRvOmNocmlzdG9w
aGVyLmRlYXJsb3ZlQGdtYWlsLmNvbT4+IHdyb3RlOg0KSSd2ZSBub3QgaGFkIHRpbWUgdG8gbG9v
ayBhdCBlaXRoZXIgeWV0LCB0aG91Z2ggSSBob3BlIHRvIHJldmlldyBETEVQIHZlcnkgc29vbi4N
Cg0KQnV0IHRoaXMgaGFzIG1hZGUgbWUgdGhpbmsgYWJvdXQgdGhlIFJGQyA2NjIxIHJlZmVyZW5j
ZSBpbiBBT0RWdjIuIEl0J3MgYWx3YXlzIGJlZW4gY2xlYXIgdGhpcyBoYXMgYmVlbiByYXRoZXIg
YSB0aHJvd2F3YXkgY29tbWVudCB0aGF0IG5lZWRlZCB0aG91Z2h0LCBidXQgdW50aWwgbm93IEkg
aGFkbid0IHJlYWxseSBnaXZlbiBpdCBhbnkuDQoNCkFuZCBpdCBkb2Vzbid0IHdvcmsuIFJGQyA2
NjIxIGlzIGZ1bmRhbWVudGFsbHkgdW51c2FibGUgaGVyZS4gTGV0J3MgY29uc2lkZXIgZWFjaCBv
biB0dXJuLg0KDQpBT0RWdjIgaXMgaW4gdGhlIFJGQyA1NDQ0IHN0cnVjdHVyZS4gQXMgaGFzIGJl
ZW4gbm90ZWQgb24gbWFueSBvY2Nhc2lvbnMsIEFPVkRWdjIgZ2V0cyB0byB1c2UgbWVzc2FnZXMs
IGJ1dCBwYWNrZXRzIGFyZSBub3QgaW4gaXRzIGNvbXBldGVuY2UuDQoNClJGQyA2NjIxIGlzIGFi
b3V0IHBhY2tldHMuIEJ1dCBub3QgZXZlbiBSRkMgNTQ0NCBwYWNrZXRzIGJ1dCBJUCBwYWNrZXRz
LiBJdCdzIGFib3V0IHdoZXRoZXIgb3Igbm90IHRvIGZvcndhcmQgdGhlbS4gQnV0IFJGQyA1NDQ0
IHBhY2tldHMgYXJlbid0IGp1c3Qgbm90IGZvcndhcmRlZCBpbiB1bmNoYW5nZWQgSVAgcGFja2V0
cywgdGhleSBhcmVuJ3QgZXZlbiBmb3J3YXJkZWQgYXQgYWxsLiBUaGV5IGFyZSBlYWNoIGEgc2lu
Z2xlIGhvcCBjb25zdHJ1Y3QsIGFuZCBpZiBhIG1lc3NhZ2UgaXMgZm9yd2FyZGVkICh3aGljaCBp
cyBieSB0aGUgcm91dGluZyBwcm90b2NvbCwgYXMgZmFyIGFzIFJGQyA1NDQ0IGlzIGNvbmNlcm5l
ZCwgaXQncyBhIG5ldyBtZXNzYWdlKSBpdCB3aWxsIGJlIGluIGEgbmV3IHBhY2tldCwgd2l0aCBw
b3NzaWJseSBuZXcgY29tcGFuaW9ucy4NCg0KSWYgQU9EVnYyIHdhbnRzIHRvIHVzZSBhIG1vcmUg
ZWZmaWNpZW50IGZsb29kaW5nIHByb2Nlc3MsIGl0IG5lZWRzIG9uZSBhdCB0aGUgbWVzc2FnZSBs
ZXZlbC4gTm93IGFuIGV4YW1wbGUgb2YgdGhhdCBleGlzdHMgLSB0aGUgbWVjaGFuaXNtIG9uIFJG
QyA3MTgxLiBVbmZvcnR1bmF0ZWx5IHdlIGRpZG4ndCBicmVhayB0aGF0IG91dCBhcyBhIHNlcGFy
YXRlIGRyYWZ0ICh3ZSB3b3VsZCBoYXZlIGxpa2VkIHRvLCBidXQgdGhlcmUgd2VyZSByZWFzb25z
IHdlIGRpZG4ndCkuDQoNCkFuZCBldmVuIGlmIChieSByZWZlcmVuY2Ugb3Igb3RoZXIgbWVhbnMp
IGl0IHdlcmUgdXNlZCAtIG9yIHNvbWUgcmVsYXRlZCBtZWNoYW5pc20gc3VjaCBhcyBhIENEUyAt
IHRoYXQgcHJvY2Vzc2luZy9mb3J3YXJkaW5nIG1lY2hhbmlzbSBhc3N1bWVzIHlvdSBoYXZlIGRl
ZmluZWQgTVBScyAob3Igc2ltaWxhcmx5LCB0aGF0IHlvdSBoYXZlIGRlZmluZWQgYSBDRFMpLiBB
bmQgdGhhdCBuZWVkcyBhIGxvY2FsIGV4Y2hhbmdlIG9mIGluZm9ybWF0aW9uLCBzdWNoIGFzIE5I
RFAncyBIRUxMTyBtZXNzYWdlcyAoYW5kIHRoZSByZXN0IG9mIE5IRFApIGF1Z21lbnRlZCB3aXRo
IFJGQyA3MTgxJ3MgTVBSIFRMViAodGhvdWdoIG9ubHkgdGhlIGZsb29kaW5nIGJpdCBpcyBuZWVk
ZWQpLg0KDQpJbiBvdGhlciB3b3JkcywgdGFraW5nIHNvbWUgcmVhbCB3b3JrIHRvIGRlZmluZS4g
QW5kIGFsc28gcmFpc2luZyBhIHF1ZXN0aW9uIGZvciB0aGUgV0cgLSB3aHkgZG8gd2Ugd2FudCBh
IHJlYWN0aXZlIHByb3RvY29sPyBUaGUgbWFpbiBhdHRyYWN0aW9uIGFzIEkgc2VlIGl0IGlzIHRo
ZSAiaWYgeW91J3JlIG5vdCBkb2luZyBhbnl0aGluZywgeW91J3JlIG5vdCB0cmFuc21pdHRpbmci
IHByb3BlcnR5LiBXaGljaCBhZGRpbmcgdGhpcyB2b2lkcy4gT2YgY291cnNlIG1heWJlIHRoZSBX
RyBkb2Vzbid0IHZhbHVlIHRoYXQuIE9yIGl0IGlzIGFjY2VwdGFibGUgYXMgYW4gb3B0aW9uLiBC
dXQgaWYgc28gaXQgbmVlZHMgdG8gYmUgYW4gb3B0aW9uIHRoYXQgYWxsIHJvdXRlcnMgdXNlLCBv
ciBub25lLiBBbmQgaWYgYWxsLCBjb21wYXRpYmx5LiAoTVBSIGZsb29kaW5nIGFsbG93cyBkaWZm
ZXJlbnQgTVBSIHNlbGVjdGlvbiBhbGdvcml0aG1zIC0gYnV0IG9ubHkgYXMgbG9uZyBhcyB0aGV5
IHNhdGlzZnkgdGhlIGZ1bmRhbWVudGFsIE1QUiBhbGdvcml0aG0gcHJvcGVydGllcy4pDQoNCklu
IHNob3J0LCBSRkMgNjYyMSBtdXN0IGdvLiBUaGUgYWx0ZXJuYXRpdmUgaXMgbm90aGluZywgb3Ig
c2lnbmlmaWNhbnQgd29yay4NCi0tDQpDaHJpc3RvcGhlciBEZWFybG92ZQ0KY2hyaXN0b3BoZXIu
ZGVhcmxvdmVAZ21haWwuY29tPG1haWx0bzpjaHJpc3RvcGhlci5kZWFybG92ZUBnbWFpbC5jb20+
IChpUGhvbmUpDQpjaHJpc0BtbmVtb3N5bmUuZGVtb24uY28udWs8bWFpbHRvOmNocmlzQG1uZW1v
c3luZS5kZW1vbi5jby51az4gKGhvbWUpDQoNCk9uIDE4IE5vdiAyMDE1LCBhdCAwMTozNSwgVGhv
bWFzIENsYXVzZW4gPGlldGZAdGhvbWFzY2xhdXNlbi5vcmc8bWFpbHRvOmlldGZAdGhvbWFzY2xh
dXNlbi5vcmc+PiB3cm90ZToNCkRlYXIgYWxsLA0KDQpJIGhhdmUgc3RhcnRlZCBsb29raW5nIHRo
cm91Z2ggdGhlIHJlY2VudGx5IHVwZGF0ZWQgZHJhZnQtaWV0Zi1tYW5ldC1hb2R2djItMTIuIEEg
bG90IGhhcyBjaGFuZ2VkLCBhbmQgSSByZWdyZXQgbm90IHRvIGhhdmUgaGFkIGEgYmxvdy1ieS1i
b3cgY29tZWJhY2sgdG8gdGhlIHByZXZpb3VzIHJldmlldyBjb21tZW50cyAgLSB3b3VsZCBoYXZl
IG1hZGUgaXQgYSBzb21ld2hhdCBlYXNpZXIgdGFzayB0byBjaGVjayBpZiBhbGwgaGF2ZSBiZWVu
IGFkZHJlc3NlZCBvciBub3QuDQoNCkJ1dCwgSSB3aWxsIHdvcmsgdGhyb3VnaCBpdCBhbmQgcHJv
ZHVjZSBhIGRldGFpbGVkIHJldmlldyAtIGJ1dCBmcm9tIG15IGZpcnN0IHF1aWNrIHJlYWQtdGhy
b3VnaCB0aGVyZSdyZSBhIGNvdXBsZSBvZiBpc3N1ZSB0aGF0IGp1bXBlZCBhdCBtZSBhcyB3b3J0
aCBicmluZ2luZyBmb3J3YXJkIG9uIGEgbW9yZSBnbG9iYWwgbGV2ZWwgYWxyZWFkeS4NCg0KVGhl
IGZpcnN0IHJlbGF0ZXMgdG8gIGhvdyBSUkVRcyBhcmUgZm9yd2FyZGVkIC0tIG9yLCBtb3JlIGdl
bmVyYWxseSwgYXJlIG5vdC4NCg0KVGhlIHByb3RvY29sIGN1cnJlbnRseSB0YWxrcyBhYm91dCAi
bWVzc2FnZSBpcyByZWdlbmVyYXRlZCIgcmF0aGVyIHRoYW4gImZvcndhcmRlZCIuIEkgaGF2ZSB1
bmRlcnN0b29kIHRoYXQgdGhpcyBtZWFucyB0aGF0IGEgUlJFUSBpcyBhY3R1YWxseSBub3QgYW4g
ImVuZCB0byBlbmQiIGVudGl0eSwgYnV0IGlzIGEgImhvcCBieSBob3AiIGVudGl0eS4NCg0KRmly
c3QsIHRoYXQgaXMgYSBjdXJpb3VzIGRlc2lnbiBjaG9pY2UsIGlzIHRoZXJlIGFueSByZWFzb24g
d2h5IHRoaXMgaXMgc28gY29uc2lkZXJlZD8NCg0KU2Vjb25kLCBpZiBhIFJSRVEgbWVzc2FnZSBp
cyBob3AtYnktaG9wIG9ubHksIHRoZW4gSSBkbyBub3QgdGhpbmsgdGhhdCB0aGUgdXNlIG9mIHRo
ZSBSRkM1NDQ0IGhvcC1saW1pdC9ob3AtY291bnQgZmllbGRzIGlzIGFwcHJvcHJpYXRlLg0KDQpU
aGlyZCwgdGhlIHN0YXRlbWVudCBpbiBzZWN0aW9uIDYuNSBvbiB0aGUgdXNlIG9mIFJGQzY2MjEg
aXMgaW5jb3JyZWN0IGluIHR3byB3YXlzOiBSRkM2NjIxIGRvZXMgc3BlY2lmeSBob3cgbWVzc2Fn
ZXMgYXJlICpmb3J3YXJkZWQqIChidXQsIGFzIGRpc2N1c3NlZCBhYm92ZSwgeW91IGFyZSBub3Qg
Zm9yd2FyZGluZyBtZXNzYWdlcykuDQoNCk1vcmUgc2VyaW91c2x5LCB0aGlzIHBhcmFncmFwaCBp
cyBpbmNvcnJlY3Q6DQoNCg0KDQoiSW1wbGVtZW50YXRpb25zIE1BWSBjaG9vc2UgdG8gZW1wbG95
IHRlY2huaXF1ZXMgdG8gcmVkdWNlIHRoZSBudW1iZXIgb2YgbXVsdGljYXN0IG1lc3NhZ2VzIHNl
bnQuIFVzZSBvZiBbUkZDNjYyMTxodHRwczovL3Rvb2xzLmlldGYub3JnL2h0bWwvcmZjNjYyMT5d
IGluIGRlcGxveW1lbnRzIGlzIHJlY29tbWVuZGVkLiBFbXBsb3lpbmcgW1JGQzY2MjE8aHR0cHM6
Ly90b29scy5pZXRmLm9yZy9odG1sL3JmYzY2MjE+XSBpbiBhIHN1YnNldCBvZiB0aGUgb3BlcmF0
aW9uYWwgQU9EVnYyIHJvdXRlcnMgaW4gYSBuZXR3b3JrLCBvciBjb25maWd1cmluZyBkaWZmZXJl
bnQgYWxnb3JpdGhtcyBvbiBkaWZmZXJlbnQgcm91dGVycywgd2lsbCBub3QgY2F1c2UgaW50ZXJv
cGVyYWJpbGl0eSBpc3N1ZXMsIGJ1dCB3aWxsIHJlZHVjZSB0aGUgZWZmZWN0aXZlbmVzcyBvZiB0
aGUgbXVsdGljYXN0IHJlZHVjdGlvbiBzY2hlbWUuIg0KDQpEaWZmZXJlbnQgcm91dGVycyB1c2lu
ZyBkaWZmZXJlbnQgcmVsYXkgc2VsZWN0aW9uIGFsZ29yaXRobXMgaW4gdGhlIHNhbWUgbmV0d29y
ayB3aWxsIG5vdCAqanVzdCogY2F1c2UgbG9zcyBvZiBlZmZpY2llbmN5LCBidXQgKndpbGwqIGNh
dXNlIGludGVyb3BlcmFiaWxpdHkgaXNzdWVzLg0KDQpGb3IgZXhhbXBsZSBpZiAicm91dGVyIEEi
IGRlY2lkZXMgdG8gc3VwcHJlc3MgaXRzIG1lc3NhZ2UgcmVsYXlpbmcgYmVjYXVzZSBpdCBlc3Rp
bWF0ZXMgdGhhdCAicm91dGVyIEIiIHByb3ZpZGVzIHN1ZmZpY2llbnQgY292ZXJhZ2UgLSBhbmQg
Y29udmVyc2VseSAicm91dGVyIEIiIHN1cHByZXNzZXMgcmVsYXlpbmcgZm9yIHRoZSBzYW1lIHJl
YXNvbjogbmVpdGhlciBBIG5vciBCIHdvdWxkIHJlbGF5LCBhbmQgc28gYW55IHJvdXRlcnMgcmVh
Y2hhYmxlIG9ubHkgdmlhIEEgYW5kIEIgd291bGQgbm90IGJlIGNvdmVyZWQuDQoNClRoaXMgaXMg
bm90IGEgZmFyLXNvdWdodCBleGFtcGxlOiBpdCBjYW4gYmUgYXMgc2ltcGxlIGFzIEEgYW5kIEIg
c2ltcGx5IHVzaW5nIHNlbGYtc2VsZWN0aW5nIHJlbGF5IGFsZ29yaXRobXMgd2l0aCBkaWZmZXJl
bnQgdGllLWJyZWFrZXJzLg0KDQpJbiBzaG9ydDogSSB0aGluayB0aGF0IHRoZSB3aG9sZSBtZXNz
YWdlIGZsb29kaW5nL3JlZ2VuZXJhdGlvbiBwYXJ0IHJlcXVpcmVzIHNlcmlvdXMgd29yay4NCg0K
VGhlIHNlY29uZCBpc3N1ZSBpcyB0aGF0IEkgYWxzbyBzdXNwZWN0IHRoYXQgdGhlcmUgaXMgc29t
ZSBpc3N1ZSB3aXRoIGJ1ZmZlcmluZywgb3IgcmF0aGVyIHdpdGggaG93IGl0IGlzIHNwZWNpZmll
ZDsgc3RhcnRpbmcgaW4gc2VjdGlvbiA2LjYsIEkgYW0gbm90IHN1cmUgdGhhdCBsZWF2aW5nIHRo
YXQgYXMgImEgbWF0dGVyIG9mIHBvbGljeSBhdCBlYWNoIHJvdXRlciIgaXMgZW50aXJlbHkgcmln
aHQuDQoNCg0KQWxzbyBvbiBidWZmZXJpbmcsIEkgYW0gd29uZGVyaW5nIGlmIHRoZSAic3RhcnQg
ZGVsaXZlcmluZyBidWZmZXJlZCBwYWNrZXRzIiBjb25kaXRpb25zIChwZW51bHRpbWF0ZSBwYXJh
Z3JhcGggaW4gNi42LCBhbmQgb2YgY291cnNlIHRocm91Z2ggdGhlIHByb2Nlc3Npbmcgc2VjdGlv
bnMpIGlzIHN1ZmZpY2llbnQ7IEkgc3VzcGVjdCB0aGF0IHRoZSBjb25kaXRpb24gIldoZW4gYSB2
YWxpZCByb3V0ZSBpcyBpbnN0YWxsZWQiIGlzIG5vdCBzdWZmaWNpZW50IC0gdGhhdCB0aGVyZSBh
cmUgc2l0dWF0aW9ucyB3aGVyZSBhIHJvdXRpbmcgdGFibGUgZW50cnkgaXMgaW5zdGFsbGVkLCBi
dXQgdGhlIGNvbXBsZXRlIHJvdXRlIGlzIG5vdCBhdmFpbGFibGUgb3IgaXMgbm90IGJpZGlyZWN0
aW9uYWw/VGhpcyBvYnZpb3VzbHkgaXMgcmVsYXRlZCB0byBSUkVQX0FjayBiZWluZyBob3AtYnkt
aG9wIGFuZCBub3QgZW5kLXRvLWVuZC4uLi4NCg0KDQpFaXRoZXIgd2F5LCB0aGUgcGFydHMgb2Yg
dGhlIHNwZWNpZmljYXRpb24gdGhhdCByZWxhdGUgdG8gYnVmZmVyaW5nIGNvbnRhaW4gYSBtaXh0
dXJlIG9mIG5vcm1hdGl2ZSBhbmQgbm9uLW5vcm1hdGl2ZSB2ZXJiaWFnZSAoYSBsb3Qgb2YgImNh
biIgYnV0IGFsc28gYSBsb3Qgb2YgTVVTVC9TSE9VTEQpIHdoaWNoIEkgdGhpbmsgY291bGQgZG8g
d2l0aCBhIHRpZ2h0ZW5pbmcgdXAuDQoNCg0KQnV0Li4uLmlzIGJ1ZmZlcmluZyBldmVuIHNvbWV0
aGluZyB0aGF0IHNob3VsZCBiZSBzcGVjaWZpZWQgYnkgdGhpcyBkb2N1bWVudD8gSXQgZG9lcyBu
b3QgaW1wYWN0IGludGVyb3BlcmFiaWxpdHkgYW5kIGl0IGludGVyZmVyZXMgc3Vic3RhbnRpYWxs
eSB3aXRoIHRyYW5zcG9ydCBhbmQgY29uZ2VzdGlvbiBjb250cm9sLCBhbmQgSSBhbSBub3Qgc3Vy
ZSB0aGF0IHdlIHVuZGVyc3RhbmQgdGhlIGNvbnNlcXVlbmNlcyAoSSBhbSBub3QgY29udmluY2Vk
IHRoYXQgdGhlIGNsYWltcyBpbiB0aGUgZG9jdW1lbnQgb24gYmVuZWZpdHMgdG8gVENQIGFyZSBz
dWJzdGFudGlhdGVkIG9yIGV2ZW4gdHJ1ZSkuDQoNCg0KQXMgSSBpbmRpY2F0ZWQsIGEgY29tcGxl
dGUgcmV2aWV3IHdpbGwgZm9sbG93LCBidXQgSSB0aG91Z2h0IHRoYXQgdGhlc2Ugd2FzIGEgZ2xv
YmFsIGVub3VnaCB0b3BpY3MgdG8gY2FsbCBvdXQgYW5kIGdldCBlbmdpbmVlcmVkIHJpZ2h0Lg0K
DQpUaG9tYXMNCg0KUFM6IEkgcmVtYWluIGNvbnZpbmNlZCB0aGF0IHRoZSBzZWN1cml0eSBjb25z
aWRlcmF0aW9ucyBzZWN0aW9uIGlzIGluc3VmZmljaWVudCA7IEkgd2lsbCB0cnkgdG8gYXJ0aWN1
bGF0ZSBteSB0aG91Z2h0cyBvbiB3aHkgdGhhdCBpcywgYnV0IGZvciBzdGFydGVycyBsb29raW5n
IGF0IHRoZSByZWNlbnRseSByYWlzZWQgKGJ5IHNvbWVib2R5IGVsc2UsIHRoZSBDaHJpcyByZXBs
aWVkKSBBT0RWIHNlY3VyaXR5IHF1ZXN0aW9ucyB3b3VsZCBwcm9iYWJseSBiZSBoZWxwZnVsDQoN
Ck9uIDEwIE5vdiAyMDE1LCBhdCAwMjoxMCwgUmF0bGlmZiwgU3RhbmxleSA8c3JhdGxpZmZAaWRp
cmVjdC5uZXQ8bWFpbHRvOnNyYXRsaWZmQGlkaXJlY3QubmV0Pj4gd3JvdGU6DQpIZWxsbyBXRyBw
YXJ0aWNpcGFudHMg4oCTDQoNClRoZSBhYm92ZSByZWZlcmVuY2VkIGRyYWZ0cyB3ZXJlIHBvc3Rl
ZCBPY3QuIDEzIChmb3IgQU9EVnYyKSwgYW5kIE9jdC4gMTYgKERMRVApLiBUaGUgY28tYXV0aG9y
cyBhbmQgdGhlIGNoYWlycyBhc2sgdGhhdCB5b3UgcGxlYXNlIHRha2Ugc29tZSB0aW1lIHRvIHJl
dmlldyBhbmQgY29tbWVudCBvbiB0aGUgbmV3IHN1Ym1pc3Npb25zLg0KDQpSZWdhcmRzLA0KU3Rh
bg0KDQoNCg0KX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX18NClRoaXMgZWxlY3Ryb25pYyBtZXNzYWdlIGFuZCBhbnkgZmlsZXMgdHJhbnNtaXR0ZWQg
d2l0aCBpdCBjb250YWlucw0KaW5mb3JtYXRpb24gZnJvbSBpRGlyZWN0LCB3aGljaCBtYXkgYmUg
cHJpdmlsZWdlZCwgcHJvcHJpZXRhcnkNCmFuZC9vciBjb25maWRlbnRpYWwuIEl0IGlzIGludGVu
ZGVkIHNvbGVseSBmb3IgdGhlIHVzZSBvZiB0aGUgaW5kaXZpZHVhbA0Kb3IgZW50aXR5IHRvIHdo
b20gdGhleSBhcmUgYWRkcmVzc2VkLiBJZiB5b3UgYXJlIG5vdCB0aGUgb3JpZ2luYWwNCnJlY2lw
aWVudCBvciB0aGUgcGVyc29uIHJlc3BvbnNpYmxlIGZvciBkZWxpdmVyaW5nIHRoZSBlbWFpbCB0
byB0aGUNCmludGVuZGVkIHJlY2lwaWVudCwgYmUgYWR2aXNlZCB0aGF0IHlvdSBoYXZlIHJlY2Vp
dmVkIHRoaXMgZW1haWwNCmluIGVycm9yLCBhbmQgdGhhdCBhbnkgdXNlLCBkaXNzZW1pbmF0aW9u
LCBmb3J3YXJkaW5nLCBwcmludGluZywgb3INCmNvcHlpbmcgb2YgdGhpcyBlbWFpbCBpcyBzdHJp
Y3RseSBwcm9oaWJpdGVkLiBJZiB5b3UgcmVjZWl2ZWQgdGhpcyBlbWFpbA0KaW4gZXJyb3IsIHBs
ZWFzZSBkZWxldGUgaXQgYW5kIGltbWVkaWF0ZWx5IG5vdGlmeSB0aGUgc2VuZGVyLg0KX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCl9fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQptYW5ldCBtYWlsaW5nIGxp
c3QNCm1hbmV0QGlldGYub3JnPG1haWx0bzptYW5ldEBpZXRmLm9yZz4NCmh0dHBzOi8vd3d3Lmll
dGYub3JnL21haWxtYW4vbGlzdGluZm8vbWFuZXQNCl9fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fDQptYW5ldCBtYWlsaW5nIGxpc3QNCm1hbmV0QGlldGYub3Jn
PG1haWx0bzptYW5ldEBpZXRmLm9yZz4NCmh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlz
dGluZm8vbWFuZXQNCg0KX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX18NCm1hbmV0IG1haWxpbmcgbGlzdA0KbWFuZXRAaWV0Zi5vcmc8bWFpbHRvOm1hbmV0QGll
dGYub3JnPg0KaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9tYW5ldA0KDQoN
Cl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQptYW5ldCBt
YWlsaW5nIGxpc3QNCm1hbmV0QGlldGYub3JnPG1haWx0bzptYW5ldEBpZXRmLm9yZz4NCmh0dHBz
Oi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vbWFuZXQNCg0KKioqKioqKioqKioqKioq
KioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioKVGhp
cyBlbWFpbCBhbmQgYW55IGF0dGFjaG1lbnRzIGFyZSBjb25maWRlbnRpYWwgdG8gdGhlIGludGVu
ZGVkCnJlY2lwaWVudCBhbmQgbWF5IGFsc28gYmUgcHJpdmlsZWdlZC4gSWYgeW91IGFyZSBub3Qg
dGhlIGludGVuZGVkCnJlY2lwaWVudCBwbGVhc2UgZGVsZXRlIGl0IGZyb20geW91ciBzeXN0ZW0g
YW5kIG5vdGlmeSB0aGUgc2VuZGVyLgpZb3Ugc2hvdWxkIG5vdCBjb3B5IGl0IG9yIHVzZSBpdCBm
b3IgYW55IHB1cnBvc2Ugbm9yIGRpc2Nsb3NlIG9yCmRpc3RyaWJ1dGUgaXRzIGNvbnRlbnRzIHRv
IGFueSBvdGhlciBwZXJzb24uCioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioq
KioqKioqKioqKioqKioqKioqKioqKioqKioqKioqCg==

--_000_B31EEDDDB8ED7E4A93FDF12A4EECD30D7D76C1DBGLKXM0002VGREEN_
Content-Type: text/html; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTQgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
SGVsdmV0aWNhOw0KCXBhbm9zZS0xOjIgMTEgNiA0IDIgMiAyIDIgMiA0O30NCkBmb250LWZhY2UN
Cgl7Zm9udC1mYW1pbHk6SGVsdmV0aWNhOw0KCXBhbm9zZS0xOjIgMTEgNiA0IDIgMiAyIDIgMiA0
O30NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6Q2FsaWJyaTsNCglwYW5vc2UtMToyIDE1IDUg
MiAyIDIgNCAzIDIgNDt9DQpAZm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5OlRhaG9tYTsNCglwYW5v
c2UtMToyIDExIDYgNCAzIDUgNCA0IDIgNDt9DQpAZm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5OkNv
bnNvbGFzOw0KCXBhbm9zZS0xOjIgMTEgNiA5IDIgMiA0IDMgMiA0O30NCkBmb250LWZhY2UNCgl7
Zm9udC1mYW1pbHk6VUlDVEZvbnRUZXh0U3R5bGVUYWxsQm9keTsNCglwYW5vc2UtMTowIDAgMCAw
IDAgMCAwIDAgMCAwO30NCi8qIFN0eWxlIERlZmluaXRpb25zICovDQpwLk1zb05vcm1hbCwgbGku
TXNvTm9ybWFsLCBkaXYuTXNvTm9ybWFsDQoJe21hcmdpbjowY207DQoJbWFyZ2luLWJvdHRvbTou
MDAwMXB0Ow0KCWZvbnQtc2l6ZToxMi4wcHQ7DQoJZm9udC1mYW1pbHk6IlRpbWVzIE5ldyBSb21h
biIsInNlcmlmIjt9DQphOmxpbmssIHNwYW4uTXNvSHlwZXJsaW5rDQoJe21zby1zdHlsZS1wcmlv
cml0eTo5OTsNCgljb2xvcjpibHVlOw0KCXRleHQtZGVjb3JhdGlvbjp1bmRlcmxpbmU7fQ0KYTp2
aXNpdGVkLCBzcGFuLk1zb0h5cGVybGlua0ZvbGxvd2VkDQoJe21zby1zdHlsZS1wcmlvcml0eTo5
OTsNCgljb2xvcjpwdXJwbGU7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZTt9DQpwcmUNCgl7
bXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0KCW1zby1zdHlsZS1saW5rOiJIVE1MIFByZWZvcm1hdHRl
ZCBDaGFyIjsNCgltYXJnaW46MGNtOw0KCW1hcmdpbi1ib3R0b206LjAwMDFwdDsNCglmb250LXNp
emU6MTAuMHB0Ow0KCWZvbnQtZmFtaWx5OiJDb3VyaWVyIE5ldyI7fQ0Kc3Bhbi5IVE1MUHJlZm9y
bWF0dGVkQ2hhcg0KCXttc28tc3R5bGUtbmFtZToiSFRNTCBQcmVmb3JtYXR0ZWQgQ2hhciI7DQoJ
bXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0KCW1zby1zdHlsZS1saW5rOiJIVE1MIFByZWZvcm1hdHRl
ZCI7DQoJZm9udC1mYW1pbHk6Q29uc29sYXM7fQ0Kc3Bhbi5hcHBsZS10YWItc3Bhbg0KCXttc28t
c3R5bGUtbmFtZTphcHBsZS10YWItc3Bhbjt9DQpzcGFuLkVtYWlsU3R5bGUyMg0KCXttc28tc3R5
bGUtdHlwZTpwZXJzb25hbC1yZXBseTsNCglmb250LWZhbWlseToiQ2FsaWJyaSIsInNhbnMtc2Vy
aWYiOw0KCWNvbG9yOiMxRjQ5N0Q7fQ0KLk1zb0NocERlZmF1bHQNCgl7bXNvLXN0eWxlLXR5cGU6
ZXhwb3J0LW9ubHk7DQoJZm9udC1zaXplOjEwLjBwdDt9DQpAcGFnZSBXb3JkU2VjdGlvbjENCgl7
c2l6ZTo2MTIuMHB0IDc5Mi4wcHQ7DQoJbWFyZ2luOjcyLjBwdCA3Mi4wcHQgNzIuMHB0IDcyLjBw
dDt9DQpkaXYuV29yZFNlY3Rpb24xDQoJe3BhZ2U6V29yZFNlY3Rpb24xO30NCi0tPjwvc3R5bGU+
PCEtLVtpZiBndGUgbXNvIDldPjx4bWw+DQo8bzpzaGFwZWRlZmF1bHRzIHY6ZXh0PSJlZGl0IiBz
cGlkbWF4PSIxMDI2IiAvPg0KPC94bWw+PCFbZW5kaWZdLS0+PCEtLVtpZiBndGUgbXNvIDldPjx4
bWw+DQo8bzpzaGFwZWxheW91dCB2OmV4dD0iZWRpdCI+DQo8bzppZG1hcCB2OmV4dD0iZWRpdCIg
ZGF0YT0iMSIgLz4NCjwvbzpzaGFwZWxheW91dD48L3htbD48IVtlbmRpZl0tLT4NCjwvaGVhZD4N
Cjxib2R5IGxhbmc9IkVOLUdCIiBsaW5rPSJibHVlIiB2bGluaz0icHVycGxlIj4NCjxkaXYgY2xh
c3M9IldvcmRTZWN0aW9uMSI+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9u
dC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMt
c2VyaWYmcXVvdDs7Y29sb3I6IzFGNDk3RCI+SWYgeW91IGdvIGRvd24gdGhpcyByb3V0ZSBvZiBh
c3N1bWluZyB0cmFuc2l0aXZlIHRydXN0LCB0aGVuIHlvdSBtaWdodCBhcyB3ZWxsIHVzZSA3MTgy
4oCZcyBwYWNrZXQgSUNWIGFuZCB0aW1lc3RhbXAgcmF0aGVyIHRoYW4gbWVzc2FnZSBJQ1YgYW5k
IHRpbWVzdGFtcC48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48
c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1
b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6IzFGNDk3RCI+PG86cD4mbmJzcDs8L286
cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6
ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlm
JnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPlRoZXJlIGlzIGEgY29tcGxpY2F0aW9uIChtb3N0bHkgb25l
IG9mIHByZXNlbnRhdGlvbikgdGhhdCB0aGUgNTQ0NCBtdWx0aXBsZXhlciAocmF0aGVyIHRoYW4g
QU9EVnYyKSBuZWVkcyB0byBkbyB0aGlzLCBhdCBsZWFzdCBmb3IgcGFja2V0cyBjb250YWluaW5n
IEFPRFZ2Mg0KIG1lc3NhZ2VzIChidXQgYXQgd2hpY2ggcG9pbnQsIHByb2JhYmx5IGFsbCA1NDQ0
IHBhY2tldHMpLiBTbyB5b3UgZWl0aGVyLCBkZXBlbmRpbmcgb24geW91ciBwb2ludCBvZiB2aWV3
LCBuZWVkIHRvIHJlcXVlc3QgaXQgdG8gZG8gdGhhdCwgb3IgKGFkbWluaXN0cmF0aXZlbHkpIGRl
Y2xpbmUgdG8gb3BlcmF0ZSBleGNlcHQgb3ZlciBhIDU0NDQgbXVsdGlwbGV4ZXIgdGhhdCBpcyBk
b2luZyB0aGlzLjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxz
cGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVv
dDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xvcjojMUY0OTdEIj48bzpwPiZuYnNwOzwvbzpw
Pjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXpl
OjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYm
cXVvdDs7Y29sb3I6IzFGNDk3RCI+VGhlIGFkdmFudGFnZSBpcyBvbmUgb2Ygc2F2ZWQgc3BhY2Ug
YW5kIHRpbWUgd2hlbiBwYWNrZXRzIGNvbnRhaW4gbW9yZSB0aGFuIG9uZSBtZXNzYWdlLiBQbHVz
IHNsaWdodGx5IGJldHRlciBwcm90ZWN0aW9uIChob3AgY291bnQgYW5kIGxpbWl0IGFyZSBjb3Zl
cmVkKSBidXQNCiB3aGljaCBwcm9iYWJseSBkb2VzbuKAmXQgbWF0dGVyIGhlcmUuPG86cD48L286
cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6
ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlm
JnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5
OiZxdW90O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xvcjojMUY0OTdE
Ij5JZiBtZXNzYWdlcyBhcmUgY2hhbmdlZC9yZXBsYWNlZCBvbiBhIG9uZS10by1vbmUgYmFzaXMg
YXMgZm9yd2FyZGVkLCB0aGVuIHRoZSBvbmx5IHNvbHV0aW9ucyBJIGNhbiBzZWUgYXJlIGhvcCBi
eSBob3AgdHJhbnNpdGl2ZSB0cnVzdCAocGFja2V0cyBvciBtZXNzYWdlcw0KIHBlciBob3ApLCBv
ciBzb21ldGhpbmcgY29tcGxpY2F0ZWQgaW52b2x2aW5nIGFnZ3JlZ2F0aW9uIGFuZCBrbm93bGVk
Z2Ugb2YgY2hhbmdlcy4gQnV0IHRoZSBsYXR0ZXIgd291bGQgYmUgYSByZXNlYXJjaCB0YXNrIHRv
IGRldmVsb3AsIHNvIGxldOKAmXMgbm90IHRyeSB0aGF0LjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQt
ZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xvcjoj
MUY0OTdEIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJp
JnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6IzFGNDk3RCI+PG86cD4mbmJzcDs8
L286cD48L3NwYW4+PC9wPg0KPGRpdj4NCjxkaXYgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci10
b3A6c29saWQgI0I1QzRERiAxLjBwdDtwYWRkaW5nOjMuMHB0IDBjbSAwY20gMGNtIj4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiPjxiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEw
LjBwdDtmb250LWZhbWlseTomcXVvdDtUYWhvbWEmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90
OyI+RnJvbTo8L3NwYW4+PC9iPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEw
LjBwdDtmb250LWZhbWlseTomcXVvdDtUYWhvbWEmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90
OyI+IG1hbmV0IFttYWlsdG86bWFuZXQtYm91bmNlc0BpZXRmLm9yZ10NCjxiPk9uIEJlaGFsZiBP
ZiA8L2I+aWV0ZkB0aG9tYXNjbGF1c2VuLm9yZzxicj4NCjxiPlNlbnQ6PC9iPiAwMyBEZWNlbWJl
ciAyMDE1IDEyOjIyPGJyPg0KPGI+VG86PC9iPiBWaWN0b3JpYSBNZXJjaWVjYTxicj4NCjxiPkNj
OjwvYj4gbWFuZXQ8YnI+DQo8Yj5TdWJqZWN0OjwvYj4gUmU6IFttYW5ldF0gZHJhZnQtaWV0Zi1t
YW5ldC1hb2R2djItMTIgYW5kIGRyYWZ0LWlldGYtbWFuZXQtZGxlcC0xNzxvOnA+PC9vOnA+PC9z
cGFuPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86
cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPkRlYXIgVmlj
dG9yaWEsPG86cD48L286cD48L3A+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4m
bmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5SZXNw
b25kaW5nIHR3aWNlIHRvIHRoaXMgZW1haWwsIGludGVudGlvbmFsbHkgYXMgSSB3YW50IHRvIGFk
ZHJlc3MgdHdvIGRpZmZlcmVudCBhc3BlY3RzIGluZGVwZW5kZW50bHnigKYuPG86cD48L286cD48
L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpw
PjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxkaXY+DQo8YmxvY2txdW90ZSBzdHlsZT0ibWFyZ2luLXRv
cDo1LjBwdDttYXJnaW4tYm90dG9tOjUuMHB0Ij4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij5PbiBOb3YgMTksIDIwMTUsIGF0IDE3OjA5LCBWaWN0b3JpYSBNZXJjaWVjYSAmbHQ7PGEgaHJl
Zj0ibWFpbHRvOnZtZXJjaWVjYTBAZ21haWwuY29tIj52bWVyY2llY2EwQGdtYWlsLmNvbTwvYT4m
Z3Q7IHdyb3RlOjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48
bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxkaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+
PG86cD4mbmJzcDs8L286cD48L3A+DQo8ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
IHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0
byI+SGkgVGhvbWFzIGFuZCBDaHJpc3RvcGhlciw8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRv
bS1hbHQ6YXV0byI+VGhhbmsgeW91IGZvciB5b3VyIGNvbW1lbnRzLiZuYnNwOyBJZiBJIG1heSBh
ZGRyZXNzIGp1c3Qgb25lIHBvaW50IGZvciBzdGFydGVycyAtIHJlZ2VuZXJhdGlvbiB2cyBmb3J3
YXJkaW5nLiBXZSB1c2UgdGhlIHRlcm0gcmVnZW5lcmF0aW9uIHNpbmNlIGZvcndhcmRpbmcgc2Vl
bXMgaW5hcHByb3ByaWF0ZSB3aGVuIHRoZQ0KIG1lc3NhZ2UgY29udGVudCBjaGFuZ2VzIGF0IGVh
Y2ggaG9wLjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1t
YXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj5UaGUgY2hhbmdl
cyB3ZSBtYWtlIHRvIHRoZSBtZXNzYWdlIGNvbnRlbnQgYXJlOjxvOnA+PC9vOnA+PC9wPg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJn
aW4tYm90dG9tLWFsdDphdXRvIj4xKSBXZSBjaGFuZ2UgdGhlIG1ldHJpYyBzbyB0aGF0IGVhY2gg
cm91dGVyIGFsb25nIHRoZSBwYXRoIGxlYXJucyBhIHJvdXRlIGZyb20gdGhlIG1lc3NhZ2UsIHdp
dGggdGhlIG1ldHJpYyBhc3NvY2lhdGVkIHdpdGggdGhlIHBhdGggdXAgdG8gdGhhdCBwb2ludDxi
cj4NCjIpIEFja1JlcSBvbmx5IGFwcGxpZXMgYmV0d2VlbiBob3BzLCBzbyBuZWVkcyB0byBiZSBy
ZW1vdmVkIGF0IGVhY2ggaG9wLCBhbmQgYSBuZXcgQWNrUmVxIGVsZW1lbnQgbWF5IG5lZWQgdG8g
YmUgYWRkZWQgZm9yIHRoZSBuZXh0IGhvcC48YnI+DQozKSBWYWxpZGl0eVRpbWUgY291bGQgcG90
ZW50aWFsbHkgYmUgYWRkZWQgYnkgYW55IGludGVybWVkaWF0ZSByb3V0ZXIgdGhhdCB3aXNoZXMg
dG8gbGltaXQgdGhlIHRpbWUgaXQgd2lsbCBmb3J3YXJkIHBhY2tldHMgb24gdGhlIHJvdXRlLjxi
cj4NCjQpIFN0cmlwcGluZyBvdXQgVW5yZWFjaGFibGUgQWRkcmVzc2VzIGZyb20gUkVSUiB3aGlj
aCBkaWQgbm90IGFmZmVjdCBvdXIgcm91dGUgc2V0LjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90
dG9tLWFsdDphdXRvIj5DYW4gd2UgcmVhbGx5IHVzZSB0aGUgdGVybSAmcXVvdDtmb3J3YXJkaW5n
JnF1b3Q7IGlmIHdlIGFyZSBjaGFuZ2luZyB0aGUgbWV0cmljIHZhbHVlLCBhZGRpbmcgYSB2YWxp
ZGl0eSB0aW1lLCBhZGRpbmcvcmVtb3ZpbmcgQWNrUmVxIG9yIHJlbW92aW5nIGFkZHJlc3NlcyBh
bmQgdGhlaXIgYXNzb2NpYXRlZCBUTFZzPzxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8L2Rpdj4N
CjwvZGl2Pg0KPC9kaXY+DQo8L2Jsb2NrcXVvdGU+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5PSywg
c28gYXNzdW1lIHRoYXQgSSB1bmRlcnN0YW5kIHJlZ2VuZXJhdGlvbiBhcyBwZXIgbXkgcHJldmlv
dXMgZW1haWwsIGFzIG1lYW5pbmcg4oCcZ2VuZXJhdGUgYSBuZXcgbWVzc2FnZSBhbmQgc2VuZCB0
byBteSBuZWlnaGJvcnMsIGJhc2VkIG9uIHdoYXQgSSBsZWFybmVkIHdoZW4gcHJvY2Vzc2luZyBh
IHJlY2VpdmVkIG1lc3NhZ2XigJ0g4oCUIGp1c3QgbGlrZSBhbnkgZGlzdGFuY2UgdmVjdG9yIHBy
b3RvY29sIGRvZXMuPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiPkluIHRoYXQgbW9kZWwsIHdoYXQgeW91IHdyaXRlIG1ha2VzIHNlbnNlOiBlYWNo
IG9yaWdpbmF0b3Igb2YgYSBjb250cm9sIG1lc3NhZ2UgKGkuZS4sIHdob2V2ZXIgZ2VuZXJhdGVz
IG9yIHJlZ2VuZXJhdGVzIGl0KSBpcyBmcmVlIHRvIGluY2x1ZGUgdGhlIGluZm9ybWF0aW9uIGl0
IGRlc2lyZXMsIHN1Y2ggYXMgdGhlIDQgcG9pbnRzIHlvdSBsaXN0IGFib3ZlLiBObyBpc3N1ZXMg
d2l0aCB0aGF0LjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIj5Ib3dldmVyLCBhbmQgdGhpcyBqb2lucyB3aGF0IEkgcG9pbnRlZCBvdXQgaW4gYSBw
cmV2aW91cyBlbWFpbCwgeW91IHdyaXRlIGluIHRoZSBhcHBsaWNhYmlsaXR5IHN0YXRlbWVudDo8
bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+
Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHByZSBzdHlsZT0icGFnZS1icmVhay1i
ZWZvcmU6YWx3YXlzIj4mbmJzcDsmbmJzcDsgUHJvdmlkaW5nIHNlY3VyaXR5IGZvciBhIHJlYWN0
aXZlIHJvdXRpbmcgcHJvdG9jb2wgY2FuIGJlIGRpZmZpY3VsdC48bzpwPjwvbzpwPjwvcHJlPg0K
PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZTo5LjBwdDtmb250LWZhbWlseTomcXVvdDtIZWx2ZXRpY2Em
cXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90Ozttc28tZmFyZWFzdC1sYW5ndWFnZTpFTi1HQiI+
PGJyIGNsZWFyPSJhbGwiIHN0eWxlPSJwYWdlLWJyZWFrLWJlZm9yZTphbHdheXMiPg0KPC9zcGFu
Pg0KPHByZSBzdHlsZT0icGFnZS1icmVhay1iZWZvcmU6YWx3YXlzIj48c3BhbiBzdHlsZT0iZm9u
dC1mYW1pbHk6JnF1b3Q7SGVsdmV0aWNhJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDsiPldo
aWxlIHdlIGNhbiBkaXNjdXNzIGlmIHRoZSBuYXR1cmUgb2YmbmJzcDvigJxyZWFjdGl2ZSByb3V0
aW5nIHByb3RvY29s4oCdIGdlbmVyYXRlcyBwYXJ0aWN1bGFyIGRpZmZpY3VsdGllcywgd2UgY2Vy
dGFpbmx5IGNhbiBhZ3JlZSB0aGF0IHRoaXMgcHJvdG9jb2wgaGFzIHRoZSBzYW1lJm5ic3A74oCc
ZGlmZmljdWx0aWVz4oCdIGFzIGEgZGlzdGFuY2UgdmVjdG9yIHByb3RvY29sOiByb3V0aW5nJm5i
c3A7dG9wb2xvZ3kgaW5mb3JtYXRpb24gKGJ5IGRlZmluaXRpb24pIG5vdCBiZWluZyBleGNoYW5n
ZWQgZW5kLXRvLWVuZCwgYnV0IGJldHdlZW4gbmVpZ2hib3JzICh3aG8gZG8mbmJzcDtjYWxjdWxh
dGlvbnMgYW5kIGdlbmVyYXRlIHRoZWlyIG93biBhbm5vdW5jZW1lbnRzJm5ic3A74oCUIHJlZ2Vu
ZXJhdGlvbiwgYXMgeW91IGNhbGwgaXQpLiZuYnNwOzwvc3Bhbj48bzpwPjwvbzpwPjwvcHJlPg0K
PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7SGVsdmV0aWNh
JnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7bXNvLWZhcmVhc3QtbGFuZ3VhZ2U6RU4tR0Ii
PjxiciBjbGVhcj0iYWxsIiBzdHlsZT0icGFnZS1icmVhay1iZWZvcmU6YWx3YXlzIj4NCjwvc3Bh
bj4NCjxwcmUgc3R5bGU9InBhZ2UtYnJlYWstYmVmb3JlOmFsd2F5cyI+PHNwYW4gc3R5bGU9ImZv
bnQtZmFtaWx5OiZxdW90O0hlbHZldGljYSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7Ij5U
aGlzIG1lYW5zIHRoYXQgYSBzcGVjaWZpYyBzZWN1cml0eSBtb2RlbCBvZiB0cmFuc2l0aXZlIHRy
dXN0IG11c3QgYmUgYXNzdW1lZCwgbm8/IEkgdHJ1c3QgVmljdG9yaWEsJm5ic3A7dGhlcmVmb3Jl
IHdoZW4gVmljdG9yaWEgc2F5cyZuYnNwO+KAnFN0YW4gdG9sZCBtZeKAnSZuYnNwO3RoZW4gSSB0
cnVzdCB0aGF0IHNoZSZuYnNwO2FjdHVhbGx5IHZlcmlmaWVkIHRoYXQgJnF1b3Q7aXQgd2FzIGlu
ZGVlZCBTdGFuIHdobyB0b2xkIGhlciZuYnNwO+KApuKAnSZuYnNwO+KAlCBhbmQgZWl0aGVyIHdh
eSwgSSBoYXZlIG5vIHdheSBvZiB2ZXJpZnlpbmc/PC9zcGFuPjxvOnA+PC9vOnA+PC9wcmU+DQo8
c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtIZWx2ZXRpY2Em
cXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90Ozttc28tZmFyZWFzdC1sYW5ndWFnZTpFTi1HQiI+
PGJyIGNsZWFyPSJhbGwiIHN0eWxlPSJwYWdlLWJyZWFrLWJlZm9yZTphbHdheXMiPg0KPC9zcGFu
Pg0KPHByZSBzdHlsZT0icGFnZS1icmVhay1iZWZvcmU6YWx3YXlzIj48c3BhbiBzdHlsZT0iZm9u
dC1mYW1pbHk6JnF1b3Q7SGVsdmV0aWNhJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDsiPkkg
ZGlkIG5vdCBzZWUgdGhlIHRydXN0IG1vZGVsIC8gdHJ1c3QgYXNzdW1wdGlvbiBkaXNjdXNzZWQg
aW4gdGhlIHNwZWNpZmljYXRpb24gKHNwZWNpZmljYWxseSBub3QgaW4gYXBwbGljYWJpbGl0eSBh
bmQgaW4gc2VjdGlvbiAxMywgYm90aCBvZiB3aGVyZSBpdCBzaG91bGQgYmUgY2FsbGVkIG91dCks
IGJ1dCBJIHRoaW5rIHRoYXQgdGhpcyBpcyBhY3R1YWxseSBhIGNydWNpYWwgcG9pbnQgdG8gZ2V0
IHJpZ2h0LCBpbiBvcmRlciB0byBhcHByb2FjaCBkZXZlbG9waW5nIHRoZSBNVEkgc2VjdXJpdHkg
bWVjaGFuaXNtcy48L3NwYW4+PG86cD48L286cD48L3ByZT4NCjxzcGFuIHN0eWxlPSJmb250LXNp
emU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NvdXJpZXIgTmV3JnF1b3Q7O21zby1mYXJlYXN0
LWxhbmd1YWdlOkVOLUdCIj48YnIgY2xlYXI9ImFsbCIgc3R5bGU9InBhZ2UtYnJlYWstYmVmb3Jl
OmFsd2F5cyI+DQo8L3NwYW4+DQo8cHJlIHN0eWxlPSJwYWdlLWJyZWFrLWJlZm9yZTphbHdheXMi
PjxzcGFuIHN0eWxlPSJmb250LWZhbWlseTomcXVvdDtIZWx2ZXRpY2EmcXVvdDssJnF1b3Q7c2Fu
cy1zZXJpZiZxdW90OyI+QW55d2F5cywgdGhhdCBvYnNlcnZhdGlvbiBhY3R1YWxseSBjb250cmFz
dHMgc3Ryb25nbHkgd2l0aCB3aGF0IHRoZSBhcHBsaWNhYmlsaXR5IHN0YXRlbWVudCB0aGVuIGdv
ZXMgb24gdG8gc2F5LCBuYW1lbHk6PC9zcGFuPjxvOnA+PC9vOnA+PC9wcmU+DQo8cHJlIHN0eWxl
PSJwYWdlLWJyZWFrLWJlZm9yZTphbHdheXMiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wcmU+DQo8cHJl
IHN0eWxlPSJwYWdlLWJyZWFrLWJlZm9yZTphbHdheXMiPiZuYnNwOyZuYnNwOyBBT0RWdjIgcHJv
dmlkZXMgZm9yIG1lc3NhZ2UgaW50ZWdyaXR5IGFuZCBzZWN1cml0eSBhZ2FpbnN0IHJlcGxheTxv
OnA+PC9vOnA+PC9wcmU+DQo8cHJlIHN0eWxlPSJwYWdlLWJyZWFrLWJlZm9yZTphbHdheXMiPiZu
YnNwOyZuYnNwOyBhdHRhY2tzIGJ5IHVzaW5nIGludGVncml0eSBjaGVjayB2YWx1ZXMsIHRpbWVz
dGFtcHMgYW5kIHNlcXVlbmNlPG86cD48L286cD48L3ByZT4NCjxwcmUgc3R5bGU9InBhZ2UtYnJl
YWstYmVmb3JlOmFsd2F5cyI+Jm5ic3A7Jm5ic3A7IG51bWJlcnMsIGFzIGRlc2NyaWJlZCBpbiA8
YSBocmVmPSJodHRwczovL3Rvb2xzLmlldGYub3JnL2h0bWwvZHJhZnQtaWV0Zi1tYW5ldC1hb2R2
djItMTIjc2VjdGlvbi0xMyI+U2VjdGlvbiAxMzwvYT48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEy
LjBwdCI+Ljwvc3Bhbj48bzpwPjwvbzpwPjwvcHJlPg0KPHNwYW4gc3R5bGU9ImZvbnQtc2l6ZTox
Mi4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q291cmllciBOZXcmcXVvdDs7bXNvLWZhcmVhc3QtbGFu
Z3VhZ2U6RU4tR0IiPjxiciBjbGVhcj0iYWxsIiBzdHlsZT0icGFnZS1icmVhay1iZWZvcmU6YWx3
YXlzIj4NCjwvc3Bhbj4NCjxwcmUgc3R5bGU9InBhZ2UtYnJlYWstYmVmb3JlOmFsd2F5cyI+PHNw
YW4gc3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90O0hlbHZldGljYSZxdW90OywmcXVvdDtzYW5zLXNl
cmlmJnF1b3Q7Ij5UaGlzIGlzIHRydWUgb25seSBpbiBhcyBtdWNoIGFzIG1lc3NhZ2VzIGFyZSBp
bmRlZWQgZXhjaGFuZ2VkIGJldHdlZW4gbmVpZ2hib3JzOiB3aGVuIHlvdSZuYnNwO+KAnHJlZ2Vu
ZXJhdGXigJ0gYSBtZXNzYWdlLCBpLmUuLCBnZW5lcmF0ZSBhIG5ldyZuYnNwO21lc3NhZ2UgaW4g
cmVzcG9uc2UgdG8gcmVjZWlwdCBvZiBhIG1lc3NhZ2UsIHlvdSBnZW5lcmF0ZSBicmFuZCBuZXcg
cGF5bG9hZCAoYnV0IHBvc3NpYmx5IGluY2x1ZGluZyBzb21lIG9mJm5ic3A7dGhlIGRhdGEgZnJv
bSB0aGUgcmVjZWl2ZWQgbWVzc2FnZSwgb2YgY291cnNlKTogdGh1cywgYW55IElDVnMmbmJzcDvi
gJxmcm9tIGZhcnRoZXIgYXdheSB0aGFuIHRoZSBuZWlnaGJvcuKAnSZuYnNwO3dpbGwgYmUgdXNl
bGVzcyAob3IsIGlmIHlvdSB6ZXJvIG91dCB0aGUgcGFydHMgdGhhdCB5b3UgY2hhbmdlLCB0aGVz
ZSBwYXJ0cyB3aWxsIG5vdCBiZSBwcm90ZWN0ZWQpLjwvc3Bhbj48bzpwPjwvbzpwPjwvcHJlPg0K
PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7SGVsdmV0aWNh
JnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7bXNvLWZhcmVhc3QtbGFuZ3VhZ2U6RU4tR0Ii
PjxiciBjbGVhcj0iYWxsIiBzdHlsZT0icGFnZS1icmVhay1iZWZvcmU6YWx3YXlzIj4NCjwvc3Bh
bj4NCjxwcmUgc3R5bGU9InBhZ2UtYnJlYWstYmVmb3JlOmFsd2F5cyI+PHNwYW4gc3R5bGU9ImZv
bnQtZmFtaWx5OiZxdW90O0hlbHZldGljYSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7Ij5U
aGUgYWJvdmUgc2VudGVuY2UsIHF1b3RlZCBmcm9tIHRoZSBhcHBsaWNhYmlsaXR5IHN0YXRlbWVu
dCwgYW5kIHRoYXQgd2hpY2ggdHJhbnNwaXJlcyBmcm9tIHNlY3Rpb24gMTMsIHNlZW1zIC0gY2Vy
dGFpbmx5LCBhYnNlbnQgdGhlIHRydXN0IG1vZGVsIGFzc3VtZWQgLSB0byBzdWdnZXN0IHRoYXQg
ZW5kLXRvLWVuZCBwcm90ZWN0aW9uL3ZhbGlkYXRpb24gaXMgcHJvdmlkZWQuIEJ1dCwgdGhpcyBp
cyA8Yj48dT5ub3Q8L3U+PC9iPiB0aGUgY2FzZS48L3NwYW4+PG86cD48L286cD48L3ByZT4NCjxz
cGFuIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0hlbHZldGljYSZx
dW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O21zby1mYXJlYXN0LWxhbmd1YWdlOkVOLUdCIj48
YnIgY2xlYXI9ImFsbCIgc3R5bGU9InBhZ2UtYnJlYWstYmVmb3JlOmFsd2F5cyI+DQo8L3NwYW4+
DQo8cHJlIHN0eWxlPSJwYWdlLWJyZWFrLWJlZm9yZTphbHdheXMiPjxzcGFuIHN0eWxlPSJmb250
LWZhbWlseTomcXVvdDtIZWx2ZXRpY2EmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90OyI+Rmlu
YWxseSB0byB0aGUgYXBwbGljYWJpbGl0eSBzdGF0ZW1lbnQsIGEgcXVlc3Rpb246PC9zcGFuPjxv
OnA+PC9vOnA+PC9wcmU+DQo8c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWls
eTomcXVvdDtDb3VyaWVyIE5ldyZxdW90Ozttc28tZmFyZWFzdC1sYW5ndWFnZTpFTi1HQiI+PGJy
IGNsZWFyPSJhbGwiIHN0eWxlPSJwYWdlLWJyZWFrLWJlZm9yZTphbHdheXMiPg0KPC9zcGFuPg0K
PHByZSBzdHlsZT0icGFnZS1icmVhay1iZWZvcmU6YWx3YXlzIj48c3BhbiBzdHlsZT0iZm9udC1z
aXplOjEyLjBwdCI+Jm5ic3A7Jm5ic3A7IElmIHNlY3VyaXR5IGFzc29jaWF0aW9ucyBjYW4gYmU8
bzpwPjwvbzpwPjwvc3Bhbj48L3ByZT4NCjxwcmUgc3R5bGU9InBhZ2UtYnJlYWstYmVmb3JlOmFs
d2F5cyI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMi4wcHQiPiZuYnNwOyZuYnNwOyBlc3RhYmxp
c2hlZCwgZW5jcnlwdGlvbiBjYW4gYmUgdXNlZCBmb3IgQU9EVnYyIG1lc3NhZ2VzIHRvIGVuc3Vy
ZTxvOnA+PC9vOnA+PC9zcGFuPjwvcHJlPg0KPHByZSBzdHlsZT0icGFnZS1icmVhay1iZWZvcmU6
YWx3YXlzIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEyLjBwdCI+Jm5ic3A7ICZuYnNwO3RoYXQg
b25seSB0cnVzdGVkIHJvdXRlcnMgcGFydGljaXBhdGUgaW4gcm91dGluZyBvcGVyYXRpb25zLjwv
c3Bhbj48bzpwPjwvbzpwPjwvcHJlPg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+
Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9y
bWFsIj5XaGF0IHlvdSB3YW50IHRvIHNheSBoZXJlIGlzIHRoYXQg4oCcaWYgYWxsIHRydXN0ZWQg
cm91dGVycyBoYXZlIGEgc2hhcmVkIHNlY3JldCwgdGhlbiB3ZeKAmXJlIGFibGUgdG8gdXNlIHRo
YXQgc2hhcmVkIHNlY3JldCB0byBpZ25vcmUgbm9uLXRydXN0ZWQgcm91dGVyc+KAnSwgcmlnaHQ/
Jm5ic3A7PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij5XaGlsZSDigJxzZWN1cml0eSBhc3NvY2lhdGlvbnPigJ0gdGhhdCBkbyBub3QgcGFzcyB0aHJv
dWdoIGEgc2hhcmVkIHNlY3JldCBwcm9iYWJseSBjYW4gYmUgdGhvdWdodCB1cCwgaXTigJlzIG5v
dCB0cml2aWFsIGFuZCBJIGRpZCBub3QgZmluZCBhbnkgZGlzY3Vzc2lvbiBvZiB0aGF0IGluIHRo
ZSBkb2N1bWVudD88bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCI+SGF2aW5nLCBvbiB0aGUgdG9waWMgb2Ygc2VjdXJpdHksIHJlLXJlYWQgU2VjdGlv
biAxMywgd2hpY2ggc3RhcnRzOjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cHJl
IHN0eWxlPSJwYWdlLWJyZWFrLWJlZm9yZTphbHdheXMiPiZuYnNwOyZuYnNwOyBUaGlzIHNlY3Rp
b24gZGVzY3JpYmVzIHZhcmlvdXMgc2VjdXJpdHkgY29uc2lkZXJhdGlvbnMgYW5kIHBvdGVudGlh
bDxvOnA+PC9vOnA+PC9wcmU+DQo8cHJlIHN0eWxlPSJwYWdlLWJyZWFrLWJlZm9yZTphbHdheXMi
PiZuYnNwOyZuYnNwOyBhdmVudWVzIHRvIHNlY3VyZSBBT0RWdjIgcm91dGluZy4mbmJzcDsgPG86
cD48L286cD48L3ByZT4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwv
bzpwPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+V2hp
bGUgdGhpcyBpcyBhbiBob25lc3QgZGVzY3JpcHRpb24gb2Ygd2hhdCBmb2xsb3dzLCBJIHJlbWFp
biBjb252aW5jZWQgdGhhdCB0aGlzIGlzIG5vdCBzdWZmaWNpZW50LiBTbyBsZXQgbWUgYXNrIGFz
IHByZWNpc2VseSBhcyBJIGNhbjo8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gY2xhc3M9ImFwcGxlLXRhYi1zcGFuIj4mbmJzcDsmbmJz
cDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsg
PC9zcGFuPm88c3BhbiBjbGFzcz0iYXBwbGUtdGFiLXNwYW4iPiZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOw0KPC9zcGFuPndoYXQgaXMgdGhlIE1U
SSBzZWN1cml0eSBtZWNoYW5pc20gdGhhdCBhIGNvbmZvcm1hbnQgaW1wbGVtZW50YXRpb24gbXVz
dCBwcm92aWRlPyZuYnNwOzxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+PHNwYW4gY2xhc3M9ImFwcGxlLXRhYi1zcGFuIj4mbmJzcDsmbmJzcDsmbmJz
cDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsm
bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJz
cDsmbmJzcDsgPC9zcGFuPg0KU3BlY2lmaWNhbGx5OjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8
ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gY2xhc3M9ImFwcGxlLXRhYi1zcGFuIj4m
bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJz
cDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsm
bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJz
cDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsNCjwvc3Bhbj4tPHNwYW4gY2xh
c3M9ImFwcGxlLXRhYi1zcGFuIj4mbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsm
bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgPC9zcGFuPndoaWNoIGFyZSB0aGUgcHJvY2Vzc2luZyBz
dGVwcyAoZm9yIGV4YW1wbGUgaW4gc2VjdGlvbiA3LjIuMSZuYnNwOzxvOnA+PC9vOnA+PC9wPg0K
PC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gY2xhc3M9ImFwcGxlLXRh
Yi1zcGFuIj4mbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsm
bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJz
cDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsm
bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJz
cDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsm
bmJzcDsNCjwvc3Bhbj5hbmQgc2VjdGlvbiA3LjIuMiBmb3IgUlJFUCAtIGFuZCBzaW1pbGFybHkg
Zm9yIHRoZSBvdGhlciBtZXNzYWdlJm5ic3A7PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBjbGFzcz0iYXBwbGUtdGFiLXNwYW4iPiZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOw0KPC9zcGFu
PnR5cGVzKSB0aGF0IGRlZmluZSB0aGF0IHNlY3VyaXR5IG1lY2hhbmlzbTxvOnA+PC9vOnA+PC9w
Pg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48
L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBjbGFzcz0iYXBw
bGUtdGFiLXNwYW4iPiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyA8L3NwYW4+bzxzcGFuIGNsYXNzPSJhcHBsZS10YWItc3Bh
biI+Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7
DQo8L3NwYW4+d2hhdCBwcm90ZWN0aW9uIGlzIG9mZmVyZWQgYnkgdGhhdCBNVEkgc2VjdXJpdHkg
bWVjaGFuaXNtPyBBbmQgd2hhdCByZW1haW5zPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBjbGFzcz0iYXBwbGUtdGFiLXNwYW4iPiZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyA8L3NwYW4+DQp2dWxuZXJhYmxlLjxvOnA+PC9vOnA+PC9wPg0K
PC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+
DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5JZiB0aGlzIHNwZWNpZmljYXRp
b24gdGFyZ2V0cyBzdGQudHJhY2ssIHRoZW4gaXQgc2hvdWxkIGluY2x1ZGUgKHJlYXNvbmFibHkg
c29saWQsIGJ1dCBkZWZpbml0ZWx5IHdlbGwgc3BlY2lmaWVkKSBNVEkgc2VjdXJpdHkuPG86cD48
L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNw
OzwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPkJlc3Q8bzpw
PjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5i
c3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+VGhvbWFz
PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpw
PiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxibG9ja3F1b3RlIHN0eWxlPSJtYXJn
aW4tdG9wOjUuMHB0O21hcmdpbi1ib3R0b206NS4wcHQiPg0KPGRpdj4NCjxkaXY+DQo8ZGl2Pg0K
PGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0
bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+RnVydGhlciwgaW4gcmVwbHkgdG8gdGhlIGNv
bW1lbnQgYWJvdXQgdXNlIG9mIHRoZSBtc2ctaG9wLWNvdW50IGFuZCBtc2ctaG9wLWxpbWl0IGZp
ZWxkcywgSSB0aGluayBpdCBkb2VzIG5vdCBtYXR0ZXIgdGhhdCBhIG1lc3NhZ2Ugb25seSB0cmF2
ZWxzIG9uZSBob3AgaW4gdGhhdCBwYXJ0aWN1bGFyIGZvcm0sDQogd2l0aCB0aGF0IGV4YWN0IHNl
dCBvZiBpbmZvcm1hdGlvbiBlbmNsb3NlZC4gSG9wIGxpbWl0IGFuZCBob3AgY291bnQgYXJlIHBh
cnQgb2YgdGhlIG1lc3NhZ2UgYW5kIHVzZWQgYnkgdGhlIHJvdXRpbmcgcHJvdG9jb2wsIGFuZCBz
byB0aGV5IHJlZmVyIHRvIHRoZSBtdWx0aS1ob3AgcGF0aCB0aGF0IHRoZSBBT0RWdjIgbWVzc2Fn
ZSB3aWxsIGZvbGxvdywgaW5kaWNhdGluZyB3aGVuIG5vdCB0byByZWdlbmVyYXRlIGFueSBmdXJ0
aGVyLiBTbyBBT0RWdjINCiB1c2VzIHRoZXNlIGZpZWxkcyBhcyBzdWdnZXN0ZWQgaW4gUkZDNTQ0
NCBBcHBlbmRpeCBCLCB0byBsaW1pdCB0aGUgbnVtYmVyIG9mIGhvcHMgYWNyb3NzIHdoaWNoIGl0
IHdpbGwgcmVnZW5lcmF0ZSBhIHBhY2tldCBzbyBhcyB0byAmcXVvdDtwcmV2ZW50IG1lc3NhZ2Vz
IGZyb20gZW5kbGVzc2x5IGNpcmN1bGF0aW5nIGluIGEgTUFORVQmcXVvdDsuDQo8bzpwPjwvbzpw
PjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0
bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+S2luZCByZWdhcmRzLDxicj4NClZpY3Rvcmlh
LjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPGRpdj4NCjxkaXY+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9y
bWFsIj5PbiBXZWQsIE5vdiAxOCwgMjAxNSBhdCA4OjQ5IEFNLCBDaHJpc3RvcGhlciBEZWFybG92
ZSAmbHQ7PGEgaHJlZj0ibWFpbHRvOmNocmlzdG9waGVyLmRlYXJsb3ZlQGdtYWlsLmNvbSIgdGFy
Z2V0PSJfYmxhbmsiPmNocmlzdG9waGVyLmRlYXJsb3ZlQGdtYWlsLmNvbTwvYT4mZ3Q7IHdyb3Rl
OjxvOnA+PC9vOnA+PC9wPg0KPGRpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5JJ3Zl
IG5vdCBoYWQgdGltZSB0byBsb29rIGF0IGVpdGhlciB5ZXQsIHRob3VnaCBJIGhvcGUgdG8gcmV2
aWV3IERMRVAgdmVyeSBzb29uLjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIj5CdXQgdGhpcyBoYXMgbWFkZSBtZSB0aGluayBhYm91dCB0aGUgUkZD
IDY2MjEgcmVmZXJlbmNlIGluIEFPRFZ2Mi4gSXQncyBhbHdheXMgYmVlbiBjbGVhciB0aGlzIGhh
cyBiZWVuIHJhdGhlciBhIHRocm93YXdheSBjb21tZW50IHRoYXQgbmVlZGVkIHRob3VnaHQsIGJ1
dCB1bnRpbCBub3cgSSBoYWRuJ3QgcmVhbGx5IGdpdmVuIGl0IGFueS48bzpwPjwvbzpwPjwvcD4N
CjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9w
Pg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+QW5kIGl0IGRvZXNuJ3Qgd29y
ay4gUkZDIDY2MjEgaXMgZnVuZGFtZW50YWxseSB1bnVzYWJsZSBoZXJlLiBMZXQncyBjb25zaWRl
ciBlYWNoIG9uIHR1cm4uJm5ic3A7PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiPkFPRFZ2MiBpcyBpbiB0aGUgUkZDIDU0NDQgc3RydWN0dXJlLiBB
cyBoYXMgYmVlbiBub3RlZCBvbiBtYW55IG9jY2FzaW9ucywgQU9WRFZ2MiBnZXRzIHRvIHVzZSBt
ZXNzYWdlcywgYnV0IHBhY2tldHMgYXJlIG5vdCBpbiBpdHMgY29tcGV0ZW5jZS48bzpwPjwvbzpw
PjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9v
OnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+UkZDIDY2MjEgaXMg
YWJvdXQgcGFja2V0cy4gQnV0IG5vdCBldmVuIFJGQyA1NDQ0IHBhY2tldHMgYnV0IElQIHBhY2tl
dHMuIEl0J3MgYWJvdXQgd2hldGhlciBvciBub3QgdG8gZm9yd2FyZCB0aGVtLiBCdXQgUkZDIDU0
NDQgcGFja2V0cyBhcmVuJ3QganVzdCBub3QgZm9yd2FyZGVkIGluIHVuY2hhbmdlZCBJUCBwYWNr
ZXRzLCB0aGV5IGFyZW4ndCBldmVuIGZvcndhcmRlZCBhdCBhbGwuIFRoZXkgYXJlIGVhY2gNCiBh
IHNpbmdsZSBob3AgY29uc3RydWN0LCBhbmQgaWYgYSBtZXNzYWdlIGlzIGZvcndhcmRlZCAod2hp
Y2ggaXMgYnkgdGhlIHJvdXRpbmcgcHJvdG9jb2wsIGFzIGZhciBhcyBSRkMgNTQ0NCBpcyBjb25j
ZXJuZWQsIGl0J3MgYSBuZXcgbWVzc2FnZSkgaXQgd2lsbCBiZSBpbiBhIG5ldyBwYWNrZXQsIHdp
dGggcG9zc2libHkgbmV3IGNvbXBhbmlvbnMuPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRp
dj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPklmIEFPRFZ2MiB3YW50cyB0byB1c2UgYSBtb3JlIGVm
ZmljaWVudCBmbG9vZGluZyBwcm9jZXNzLCBpdCBuZWVkcyBvbmUgYXQgdGhlIG1lc3NhZ2UgbGV2
ZWwuIE5vdyBhbiBleGFtcGxlIG9mIHRoYXQgZXhpc3RzIC0gdGhlIG1lY2hhbmlzbSBvbiBSRkMg
NzE4MS4gVW5mb3J0dW5hdGVseSB3ZSBkaWRuJ3QgYnJlYWsgdGhhdCBvdXQgYXMgYSBzZXBhcmF0
ZSBkcmFmdCAod2Ugd291bGQgaGF2ZSBsaWtlZCB0bywNCiBidXQgdGhlcmUgd2VyZSByZWFzb25z
IHdlIGRpZG4ndCkuPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiPkFuZCBldmVuIGlmIChieSByZWZlcmVuY2Ugb3Igb3RoZXIgbWVhbnMpIGl0IHdl
cmUgdXNlZCAtIG9yIHNvbWUgcmVsYXRlZCBtZWNoYW5pc20gc3VjaCBhcyBhIENEUyAtIHRoYXQg
cHJvY2Vzc2luZy9mb3J3YXJkaW5nIG1lY2hhbmlzbSBhc3N1bWVzIHlvdSBoYXZlIGRlZmluZWQg
TVBScyAob3Igc2ltaWxhcmx5LCB0aGF0IHlvdSBoYXZlIGRlZmluZWQgYSBDRFMpLiBBbmQgdGhh
dCBuZWVkcyBhIGxvY2FsIGV4Y2hhbmdlDQogb2YgaW5mb3JtYXRpb24sIHN1Y2ggYXMgTkhEUCdz
IEhFTExPIG1lc3NhZ2VzIChhbmQgdGhlIHJlc3Qgb2YgTkhEUCkgYXVnbWVudGVkIHdpdGggUkZD
IDcxODEncyBNUFIgVExWICh0aG91Z2ggb25seSB0aGUgZmxvb2RpbmcgYml0IGlzIG5lZWRlZCku
PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpw
PiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPklu
IG90aGVyIHdvcmRzLCB0YWtpbmcgc29tZSByZWFsIHdvcmsgdG8gZGVmaW5lLiBBbmQgYWxzbyBy
YWlzaW5nIGEgcXVlc3Rpb24gZm9yIHRoZSBXRyAtIHdoeSBkbyB3ZSB3YW50IGEgcmVhY3RpdmUg
cHJvdG9jb2w/IFRoZSBtYWluIGF0dHJhY3Rpb24gYXMgSSBzZWUgaXQgaXMgdGhlICZxdW90O2lm
IHlvdSdyZSBub3QgZG9pbmcgYW55dGhpbmcsIHlvdSdyZSBub3QgdHJhbnNtaXR0aW5nJnF1b3Q7
IHByb3BlcnR5LiBXaGljaA0KIGFkZGluZyB0aGlzIHZvaWRzLiBPZiBjb3Vyc2UgbWF5YmUgdGhl
IFdHIGRvZXNuJ3QgdmFsdWUgdGhhdC4gT3IgaXQgaXMgYWNjZXB0YWJsZSBhcyBhbiBvcHRpb24u
IEJ1dCBpZiBzbyBpdCBuZWVkcyB0byBiZSBhbiBvcHRpb24gdGhhdCBhbGwgcm91dGVycyB1c2Us
IG9yIG5vbmUuIEFuZCBpZiBhbGwsIGNvbXBhdGlibHkuIChNUFIgZmxvb2RpbmcgYWxsb3dzIGRp
ZmZlcmVudCBNUFIgc2VsZWN0aW9uIGFsZ29yaXRobXMgLSBidXQgb25seSBhcw0KIGxvbmcgYXMg
dGhleSBzYXRpc2Z5IHRoZSBmdW5kYW1lbnRhbCBNUFIgYWxnb3JpdGhtIHByb3BlcnRpZXMuKTxv
OnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4m
bmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHls
ZT0ibWFyZ2luLWJvdHRvbToxMi4wcHQiPkluIHNob3J0LCBSRkMgNjYyMSBtdXN0IGdvLiBUaGUg
YWx0ZXJuYXRpdmUgaXMgbm90aGluZywgb3Igc2lnbmlmaWNhbnQgd29yay48bzpwPjwvbzpwPjwv
cD4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj4tLSAmbmJzcDs8c3BhbiBzdHlsZT0iY29s
b3I6Izg4ODg4OCI+PG86cD48L286cD48L3NwYW4+PC9wPg0KPGRpdj4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiPjxzcGFuIHN0eWxlPSJjb2xvcjojODg4ODg4Ij5DaHJpc3RvcGhlciBEZWFybG92ZTxv
OnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
PjxzcGFuIHN0eWxlPSJjb2xvcjojODg4ODg4Ij48YSBocmVmPSJtYWlsdG86Y2hyaXN0b3BoZXIu
ZGVhcmxvdmVAZ21haWwuY29tIiB0YXJnZXQ9Il9ibGFuayI+Y2hyaXN0b3BoZXIuZGVhcmxvdmVA
Z21haWwuY29tPC9hPiAoaVBob25lKTxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRp
dj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJjb2xvcjojODg4ODg4Ij48YSBo
cmVmPSJtYWlsdG86Y2hyaXNAbW5lbW9zeW5lLmRlbW9uLmNvLnVrIiB0YXJnZXQ9Il9ibGFuayI+
Y2hyaXNAbW5lbW9zeW5lLmRlbW9uLmNvLnVrPC9hPiAoaG9tZSk8bzpwPjwvbzpwPjwvc3Bhbj48
L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8ZGl2Pg0KPGRpdj4NCjxkaXY+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2luLWJvdHRvbToxMi4wcHQiPjxicj4NCk9uIDE4IE5v
diAyMDE1LCBhdCAwMTozNSwgVGhvbWFzIENsYXVzZW4gJmx0OzxhIGhyZWY9Im1haWx0bzppZXRm
QHRob21hc2NsYXVzZW4ub3JnIiB0YXJnZXQ9Il9ibGFuayI+aWV0ZkB0aG9tYXNjbGF1c2VuLm9y
ZzwvYT4mZ3Q7IHdyb3RlOjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8YmxvY2txdW90ZSBzdHls
ZT0ibWFyZ2luLXRvcDo1LjBwdDttYXJnaW4tYm90dG9tOjUuMHB0Ij4NCjxkaXY+DQo8ZGl2Pg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCI+RGVhciBhbGwsPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxk
aXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0K
PGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPkkgaGF2ZSBzdGFydGVkIGxvb2tpbmcgdGhyb3Vn
aCB0aGUgcmVjZW50bHkgdXBkYXRlZCZuYnNwO2RyYWZ0LWlldGYtbWFuZXQtYW9kdnYyLTEyLiBB
IGxvdCBoYXMgY2hhbmdlZCwgYW5kIEkgcmVncmV0IG5vdCB0byBoYXZlIGhhZCBhIGJsb3ctYnkt
Ym93IGNvbWViYWNrIHRvIHRoZSBwcmV2aW91cyByZXZpZXcgY29tbWVudHMgJm5ic3A7LSB3b3Vs
ZCBoYXZlIG1hZGUgaXQgYSBzb21ld2hhdCBlYXNpZXIgdGFzayB0byBjaGVjaw0KIGlmIGFsbCBo
YXZlIGJlZW4gYWRkcmVzc2VkIG9yIG5vdC48bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+QnV0LCBJIHdpbGwgd29yayB0aHJvdWdoIGl0IGFuZCBw
cm9kdWNlIGEgZGV0YWlsZWQgcmV2aWV3IC0gYnV0IGZyb20gbXkgZmlyc3QgcXVpY2sgcmVhZC10
aHJvdWdoIHRoZXJlJ3JlIGEgY291cGxlIG9mIGlzc3VlIHRoYXQganVtcGVkIGF0IG1lIGFzIHdv
cnRoIGJyaW5naW5nIGZvcndhcmQgb24gYSBtb3JlIGdsb2JhbCBsZXZlbCBhbHJlYWR5LjxvOnA+
PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJz
cDs8L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5UaGUgZmly
c3QgcmVsYXRlcyB0byAmbmJzcDtob3cgUlJFUXMgYXJlIGZvcndhcmRlZCAtLSBvciwgbW9yZSBn
ZW5lcmFsbHksIGFyZSBub3QuPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiPlRoZSBwcm90b2NvbCBjdXJyZW50bHkgdGFsa3MgYWJvdXQgJnF1b3Q7
bWVzc2FnZSBpcyByZWdlbmVyYXRlZCZxdW90OyByYXRoZXIgdGhhbiAmcXVvdDtmb3J3YXJkZWQm
cXVvdDsuIEkgaGF2ZSB1bmRlcnN0b29kIHRoYXQgdGhpcyBtZWFucyB0aGF0IGEgUlJFUSBpcyBh
Y3R1YWxseSBub3QgYW4gJnF1b3Q7ZW5kIHRvIGVuZCZxdW90OyBlbnRpdHksIGJ1dCBpcyBhICZx
dW90O2hvcCBieSBob3AmcXVvdDsgZW50aXR5LiZuYnNwOzxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+
DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rp
dj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5GaXJzdCwgdGhhdCBpcyBhIGN1cmlvdXMg
ZGVzaWduIGNob2ljZSwgaXMgdGhlcmUgYW55IHJlYXNvbiB3aHkgdGhpcyBpcyBzbyBjb25zaWRl
cmVkPzxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+
PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij5TZWNvbmQsIGlmIGEgUlJFUSBtZXNzYWdlIGlzIGhvcC1ieS1ob3Agb25seSwgdGhlbiBJIGRv
IG5vdCB0aGluayB0aGF0IHRoZSB1c2Ugb2YgdGhlIFJGQzU0NDQgaG9wLWxpbWl0L2hvcC1jb3Vu
dCBmaWVsZHMgaXMgYXBwcm9wcmlhdGUuPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiPlRoaXJkLCB0aGUgc3RhdGVtZW50IGluIHNlY3Rpb24gNi41
IG9uIHRoZSB1c2Ugb2YgUkZDNjYyMSBpcyBpbmNvcnJlY3QgaW4gdHdvIHdheXM6IFJGQzY2MjEg
ZG9lcyBzcGVjaWZ5IGhvdyBtZXNzYWdlcyBhcmUgKmZvcndhcmRlZCogKGJ1dCwgYXMgZGlzY3Vz
c2VkIGFib3ZlLCB5b3UgYXJlIG5vdCBmb3J3YXJkaW5nIG1lc3NhZ2VzKS48bzpwPjwvbzpwPjwv
cD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+
PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+TW9yZSBzZXJpb3VzbHks
IHRoaXMgcGFyYWdyYXBoIGlzIGluY29ycmVjdDo8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRp
dj4NCjxwcmU+PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90O1VJQ1RGb250VGV4dFN0eWxl
VGFsbEJvZHkmcXVvdDssJnF1b3Q7c2VyaWYmcXVvdDsiPjxicj48YnI+PC9zcGFuPjxvOnA+PC9v
OnA+PC9wcmU+DQo8YmxvY2txdW90ZSBzdHlsZT0ibWFyZ2luLXRvcDo1LjBwdDttYXJnaW4tYm90
dG9tOjUuMHB0Ij4NCjxwcmU+PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90O1VJQ1RGb250
VGV4dFN0eWxlVGFsbEJvZHkmcXVvdDssJnF1b3Q7c2VyaWYmcXVvdDsiPiZxdW90O0ltcGxlbWVu
dGF0aW9ucyBNQVkgY2hvb3NlIHRvIGVtcGxveSB0ZWNobmlxdWVzIHRvIHJlZHVjZSB0aGUgbnVt
YmVyIG9mIG11bHRpY2FzdCBtZXNzYWdlcyBzZW50LiBVc2Ugb2YgWzxhIGhyZWY9Imh0dHBzOi8v
dG9vbHMuaWV0Zi5vcmcvaHRtbC9yZmM2NjIxIiB0YXJnZXQ9Il9ibGFuayIgdGl0bGU9IiZxdW90
O1NpbXBsaWZpZWQgTXVsdGljYXN0IEZvcndhcmRpbmcmcXVvdDsiPlJGQzY2MjE8L2E+XSBpbiBk
ZXBsb3ltZW50cyBpcyByZWNvbW1lbmRlZC4gRW1wbG95aW5nIFs8YSBocmVmPSJodHRwczovL3Rv
b2xzLmlldGYub3JnL2h0bWwvcmZjNjYyMSIgdGFyZ2V0PSJfYmxhbmsiIHRpdGxlPSImcXVvdDtT
aW1wbGlmaWVkIE11bHRpY2FzdCBGb3J3YXJkaW5nJnF1b3Q7Ij5SRkM2NjIxPC9hPl0gaW4gYSBz
dWJzZXQgb2YgdGhlIG9wZXJhdGlvbmFsIEFPRFZ2MiByb3V0ZXJzIGluIGEgbmV0d29yaywgb3Ig
Y29uZmlndXJpbmcgZGlmZmVyZW50IGFsZ29yaXRobXMgb24gZGlmZmVyZW50IHJvdXRlcnMsIHdp
bGwgbm90IGNhdXNlIGludGVyb3BlcmFiaWxpdHkgaXNzdWVzLCBidXQgd2lsbCByZWR1Y2UgdGhl
IGVmZmVjdGl2ZW5lc3Mgb2YgdGhlIG11bHRpY2FzdCByZWR1Y3Rpb24gc2NoZW1lLiZxdW90Ozwv
c3Bhbj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjE0LjVwdCI+PG86cD48L286cD48L3NwYW4+PC9w
cmU+DQo8L2Jsb2NrcXVvdGU+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48
bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
PkRpZmZlcmVudCByb3V0ZXJzIHVzaW5nIGRpZmZlcmVudCByZWxheSBzZWxlY3Rpb24gYWxnb3Jp
dGhtcyBpbiB0aGUgc2FtZSBuZXR3b3JrIHdpbGwgbm90ICpqdXN0KiBjYXVzZSBsb3NzIG9mIGVm
ZmljaWVuY3ksIGJ1dCAqd2lsbCogY2F1c2UgaW50ZXJvcGVyYWJpbGl0eSBpc3N1ZXMuPG86cD48
L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNw
OzwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPkZvciBleGFt
cGxlIGlmICZxdW90O3JvdXRlciBBJnF1b3Q7IGRlY2lkZXMgdG8gc3VwcHJlc3MgaXRzIG1lc3Nh
Z2UgcmVsYXlpbmcgYmVjYXVzZSBpdCBlc3RpbWF0ZXMgdGhhdCAmcXVvdDtyb3V0ZXIgQiZxdW90
OyBwcm92aWRlcyBzdWZmaWNpZW50IGNvdmVyYWdlIC0gYW5kIGNvbnZlcnNlbHkgJnF1b3Q7cm91
dGVyIEImcXVvdDsgc3VwcHJlc3NlcyByZWxheWluZyBmb3IgdGhlIHNhbWUgcmVhc29uOiBuZWl0
aGVyIEEgbm9yIEIgd291bGQgcmVsYXksIGFuZCBzbw0KIGFueSByb3V0ZXJzIHJlYWNoYWJsZSBv
bmx5IHZpYSBBIGFuZCBCIHdvdWxkIG5vdCBiZSBjb3ZlcmVkLjxvOnA+PC9vOnA+PC9wPg0KPC9k
aXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8
L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5UaGlzIGlzIG5vdCBhIGZhci1zb3Vn
aHQgZXhhbXBsZTogaXQgY2FuIGJlIGFzIHNpbXBsZSBhcyBBIGFuZCBCIHNpbXBseSB1c2luZyBz
ZWxmLXNlbGVjdGluZyByZWxheSBhbGdvcml0aG1zIHdpdGggZGlmZmVyZW50IHRpZS1icmVha2Vy
cy48bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxv
OnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+
SW4gc2hvcnQ6IEkgdGhpbmsgdGhhdCB0aGUgd2hvbGUgbWVzc2FnZSBmbG9vZGluZy9yZWdlbmVy
YXRpb24gcGFydCByZXF1aXJlcyBzZXJpb3VzIHdvcmsuPG86cD48L286cD48L3A+DQo8L2Rpdj4N
CjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2
Pg0KPGRpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5UaGUgc2Vjb25kIGlzc3VlIGlz
IHRoYXQgSSBhbHNvIHN1c3BlY3QgdGhhdCB0aGVyZSBpcyBzb21lIGlzc3VlIHdpdGggYnVmZmVy
aW5nLCBvciByYXRoZXIgd2l0aCBob3cgaXQgaXMgc3BlY2lmaWVkOyBzdGFydGluZyBpbiBzZWN0
aW9uIDYuNiwgSSBhbSBub3Qgc3VyZSB0aGF0IGxlYXZpbmcgdGhhdCBhcyAmcXVvdDthIG1hdHRl
ciBvZiBwb2xpY3kgYXQgZWFjaCByb3V0ZXImcXVvdDsgaXMgZW50aXJlbHkgcmlnaHQuJm5ic3A7
PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48YnI+
DQo8YnI+DQo8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiPkFsc28gb24gYnVmZmVyaW5nLCBJIGFtIHdvbmRlcmluZyBpZiB0aGUgJnF1b3Q7c3RhcnQg
ZGVsaXZlcmluZyBidWZmZXJlZCBwYWNrZXRzJnF1b3Q7IGNvbmRpdGlvbnMgKHBlbnVsdGltYXRl
IHBhcmFncmFwaCBpbiA2LjYsIGFuZCBvZiBjb3Vyc2UgdGhyb3VnaCB0aGUgcHJvY2Vzc2luZyBz
ZWN0aW9ucykgaXMgc3VmZmljaWVudDsgSSBzdXNwZWN0IHRoYXQgdGhlIGNvbmRpdGlvbiAmcXVv
dDtXaGVuIGEgdmFsaWQgcm91dGUgaXMgaW5zdGFsbGVkJnF1b3Q7DQogaXMgbm90IHN1ZmZpY2ll
bnQgLSB0aGF0IHRoZXJlIGFyZSBzaXR1YXRpb25zIHdoZXJlIGEgcm91dGluZyB0YWJsZSBlbnRy
eSBpcyBpbnN0YWxsZWQsIGJ1dCB0aGUgY29tcGxldGUgcm91dGUgaXMgbm90IGF2YWlsYWJsZSBv
ciBpcyBub3QgYmlkaXJlY3Rpb25hbD9UaGlzIG9idmlvdXNseSBpcyByZWxhdGVkIHRvIFJSRVBf
QWNrIGJlaW5nIGhvcC1ieS1ob3AgYW5kIG5vdCBlbmQtdG8tZW5kLi4uLjxvOnA+PC9vOnA+PC9w
Pg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PGJyPg0KPGJyPg0KPG86cD48
L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5FaXRoZXIgd2F5
LCB0aGUgcGFydHMgb2YgdGhlIHNwZWNpZmljYXRpb24gdGhhdCByZWxhdGUgdG8gYnVmZmVyaW5n
IGNvbnRhaW4gYSBtaXh0dXJlIG9mIG5vcm1hdGl2ZSBhbmQgbm9uLW5vcm1hdGl2ZSB2ZXJiaWFn
ZSAoYSBsb3Qgb2YgJnF1b3Q7Y2FuJnF1b3Q7IGJ1dCBhbHNvIGEgbG90IG9mIE1VU1QvU0hPVUxE
KSB3aGljaCBJIHRoaW5rIGNvdWxkIGRvIHdpdGggYSB0aWdodGVuaW5nIHVwLiZuYnNwOzxvOnA+
PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PGJyPg0KPGJy
Pg0KPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5C
dXQuLi4uaXMgYnVmZmVyaW5nIGV2ZW4gc29tZXRoaW5nIHRoYXQgc2hvdWxkIGJlIHNwZWNpZmll
ZCBieSB0aGlzIGRvY3VtZW50PyBJdCBkb2VzIG5vdCBpbXBhY3QgaW50ZXJvcGVyYWJpbGl0eSBh
bmQgaXQgaW50ZXJmZXJlcyBzdWJzdGFudGlhbGx5IHdpdGggdHJhbnNwb3J0IGFuZCBjb25nZXN0
aW9uIGNvbnRyb2wsIGFuZCBJIGFtIG5vdCBzdXJlIHRoYXQgd2UgdW5kZXJzdGFuZCB0aGUgY29u
c2VxdWVuY2VzDQogKEkgYW0gbm90IGNvbnZpbmNlZCB0aGF0IHRoZSBjbGFpbXMgaW4gdGhlIGRv
Y3VtZW50IG9uIGJlbmVmaXRzIHRvIFRDUCBhcmUgc3Vic3RhbnRpYXRlZCBvciBldmVuIHRydWUp
LjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PGJy
Pg0KPGJyPg0KPG86cD48L286cD48L3A+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+QXMg
SSBpbmRpY2F0ZWQsIGEgY29tcGxldGUgcmV2aWV3IHdpbGwgZm9sbG93LCBidXQgSSB0aG91Z2h0
IHRoYXQgdGhlc2Ugd2FzIGEgZ2xvYmFsIGVub3VnaCB0b3BpY3MgdG8gY2FsbCBvdXQgYW5kIGdl
dCBlbmdpbmVlcmVkIHJpZ2h0LjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2
Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9k
aXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+VGhvbWFzPG86cD48L286cD48L3A+DQo8
L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4N
CjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPlBTOiBJIHJlbWFpbiBjb252aW5j
ZWQgdGhhdCB0aGUgc2VjdXJpdHkgY29uc2lkZXJhdGlvbnMgc2VjdGlvbiBpcyBpbnN1ZmZpY2ll
bnQgOyBJIHdpbGwgdHJ5IHRvIGFydGljdWxhdGUgbXkgdGhvdWdodHMgb24gd2h5IHRoYXQgaXMs
IGJ1dCBmb3Igc3RhcnRlcnMgbG9va2luZyBhdCB0aGUgcmVjZW50bHkgcmFpc2VkIChieSBzb21l
Ym9keSBlbHNlLCB0aGUgQ2hyaXMgcmVwbGllZCkgQU9EViBzZWN1cml0eSBxdWVzdGlvbnMNCiB3
b3VsZCBwcm9iYWJseSBiZSBoZWxwZnVsPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2luLWJvdHRvbToxMi4wcHQiPjxicj4NCk9u
IDEwIE5vdiAyMDE1LCBhdCAwMjoxMCwgUmF0bGlmZiwgU3RhbmxleSAmbHQ7PGEgaHJlZj0ibWFp
bHRvOnNyYXRsaWZmQGlkaXJlY3QubmV0IiB0YXJnZXQ9Il9ibGFuayI+c3JhdGxpZmZAaWRpcmVj
dC5uZXQ8L2E+Jmd0OyB3cm90ZTo8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGJsb2NrcXVvdGUg
c3R5bGU9Im1hcmdpbi10b3A6NS4wcHQ7bWFyZ2luLWJvdHRvbTo1LjBwdCI+DQo8ZGl2Pg0KPGRp
dj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bztt
c28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+SGVsbG8gV0cgcGFydGljaXBhbnRzIOKAkw0KPG86
cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3At
YWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPiZuYnNwOzxvOnA+PC9vOnA+PC9w
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21z
by1tYXJnaW4tYm90dG9tLWFsdDphdXRvO3RleHQtYXV0b3NwYWNlOm5vbmUiPg0KVGhlIGFib3Zl
IHJlZmVyZW5jZWQgZHJhZnRzIHdlcmUgcG9zdGVkIE9jdC4gMTMgKGZvciBBT0RWdjIpLCBhbmQg
T2N0LiAxNiAoRExFUCkuIFRoZSBjby1hdXRob3JzIGFuZCB0aGUgY2hhaXJzIGFzayB0aGF0IHlv
dSBwbGVhc2UgdGFrZSBzb21lIHRpbWUgdG8gcmV2aWV3IGFuZCBjb21tZW50IG9uIHRoZSBuZXcg
c3VibWlzc2lvbnMuDQo8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxl
PSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0bzt0ZXh0
LWF1dG9zcGFjZTpub25lIj4NCiZuYnNwOzxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFs
dDphdXRvO3RleHQtYXV0b3NwYWNlOm5vbmUiPg0KUmVnYXJkcyw8bzpwPjwvbzpwPjwvcD4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFy
Z2luLWJvdHRvbS1hbHQ6YXV0bzt0ZXh0LWF1dG9zcGFjZTpub25lIj4NClN0YW48bzpwPjwvbzpw
PjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0
bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0bzt0ZXh0LWF1dG9zcGFjZTpub25lIj4NCiZuYnNw
OzxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4t
dG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj4mbmJzcDs8bzpwPjwvbzpw
PjwvcD4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PGJyPg0KPHNwYW4gc3R5bGU9ImZv
bnQtc2l6ZTo4LjBwdDtmb250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OywmcXVvdDtzYW5zLXNl
cmlmJnF1b3Q7O2NvbG9yOiMwMDMzNjYiPl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fPGJyPg0KVGhpcyBlbGVjdHJvbmljIG1lc3NhZ2UgYW5kIGFu
eSBmaWxlcyB0cmFuc21pdHRlZCB3aXRoIGl0IGNvbnRhaW5zPGJyPg0KaW5mb3JtYXRpb24gZnJv
bSBpRGlyZWN0LCB3aGljaCBtYXkgYmUgcHJpdmlsZWdlZCwgcHJvcHJpZXRhcnk8YnI+DQphbmQv
b3IgY29uZmlkZW50aWFsLiBJdCBpcyBpbnRlbmRlZCBzb2xlbHkgZm9yIHRoZSB1c2Ugb2YgdGhl
IGluZGl2aWR1YWw8YnI+DQpvciBlbnRpdHkgdG8gd2hvbSB0aGV5IGFyZSBhZGRyZXNzZWQuIElm
IHlvdSBhcmUgbm90IHRoZSBvcmlnaW5hbDxicj4NCnJlY2lwaWVudCBvciB0aGUgcGVyc29uIHJl
c3BvbnNpYmxlIGZvciBkZWxpdmVyaW5nIHRoZSBlbWFpbCB0byB0aGU8YnI+DQppbnRlbmRlZCBy
ZWNpcGllbnQsIGJlIGFkdmlzZWQgdGhhdCB5b3UgaGF2ZSByZWNlaXZlZCB0aGlzIGVtYWlsPGJy
Pg0KaW4gZXJyb3IsIGFuZCB0aGF0IGFueSB1c2UsIGRpc3NlbWluYXRpb24sIGZvcndhcmRpbmcs
IHByaW50aW5nLCBvcjxicj4NCmNvcHlpbmcgb2YgdGhpcyBlbWFpbCBpcyBzdHJpY3RseSBwcm9o
aWJpdGVkLiBJZiB5b3UgcmVjZWl2ZWQgdGhpcyBlbWFpbDxicj4NCmluIGVycm9yLCBwbGVhc2Ug
ZGVsZXRlIGl0IGFuZCBpbW1lZGlhdGVseSBub3RpZnkgdGhlIHNlbmRlci48YnI+DQpfX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXzwvc3Bhbj4gPG86
cD48L286cD48L3A+DQo8L2Rpdj4NCjwvYmxvY2txdW90ZT4NCjxibG9ja3F1b3RlIHN0eWxlPSJt
YXJnaW4tdG9wOjUuMHB0O21hcmdpbi1ib3R0b206NS4wcHQiPg0KPGRpdj4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiPl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
PGJyPg0KbWFuZXQgbWFpbGluZyBsaXN0PGJyPg0KPGEgaHJlZj0ibWFpbHRvOm1hbmV0QGlldGYu
b3JnIiB0YXJnZXQ9Il9ibGFuayI+bWFuZXRAaWV0Zi5vcmc8L2E+PGJyPg0KPGEgaHJlZj0iaHR0
cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9tYW5ldCIgdGFyZ2V0PSJfYmxhbmsi
Pmh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vbWFuZXQ8L2E+PG86cD48L286
cD48L3A+DQo8L2Rpdj4NCjwvYmxvY2txdW90ZT4NCjwvZGl2Pg0KPC9ibG9ja3F1b3RlPg0KPGJs
b2NrcXVvdGUgc3R5bGU9Im1hcmdpbi10b3A6NS4wcHQ7bWFyZ2luLWJvdHRvbTo1LjBwdCI+DQo8
ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+X19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX188YnI+DQptYW5ldCBtYWlsaW5nIGxpc3Q8YnI+DQo8YSBocmVmPSJt
YWlsdG86bWFuZXRAaWV0Zi5vcmciIHRhcmdldD0iX2JsYW5rIj5tYW5ldEBpZXRmLm9yZzwvYT48
YnI+DQo8YSBocmVmPSJodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL21hbmV0
IiB0YXJnZXQ9Il9ibGFuayI+aHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9t
YW5ldDwvYT48bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPC9ibG9ja3F1b3RlPg0KPC9kaXY+DQo8
L2Rpdj4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdpbi1ib3R0b206
MTIuMHB0Ij48YnI+DQpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fXzxicj4NCm1hbmV0IG1haWxpbmcgbGlzdDxicj4NCjxhIGhyZWY9Im1haWx0bzptYW5ldEBp
ZXRmLm9yZyIgdGFyZ2V0PSJfYmxhbmsiPm1hbmV0QGlldGYub3JnPC9hPjxicj4NCjxhIGhyZWY9
Imh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vbWFuZXQiIHRhcmdldD0iX2Js
YW5rIj5odHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL21hbmV0PC9hPjxvOnA+
PC9vOnA+PC9wPg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpw
PjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1h
bCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPl9f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fPGJyPg0KbWFuZXQg
bWFpbGluZyBsaXN0PGJyPg0KPGEgaHJlZj0ibWFpbHRvOm1hbmV0QGlldGYub3JnIj5tYW5ldEBp
ZXRmLm9yZzwvYT48YnI+DQo8YSBocmVmPSJodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xp
c3RpbmZvL21hbmV0Ij5odHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL21hbmV0
PC9hPjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8L2Jsb2NrcXVvdGU+DQo8L2Rpdj4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjxw
PioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioq
KioqKioqKioqKioqPGJyPgpUaGlzIGVtYWlsIGFuZCBhbnkgYXR0YWNobWVudHMgYXJlIGNvbmZp
ZGVudGlhbCB0byB0aGUgaW50ZW5kZWQ8YnI+CnJlY2lwaWVudCBhbmQgbWF5IGFsc28gYmUgcHJp
dmlsZWdlZC4gSWYgeW91IGFyZSBub3QgdGhlIGludGVuZGVkPGJyPgpyZWNpcGllbnQgcGxlYXNl
IGRlbGV0ZSBpdCBmcm9tIHlvdXIgc3lzdGVtIGFuZCBub3RpZnkgdGhlIHNlbmRlci48YnI+Cllv
dSBzaG91bGQgbm90IGNvcHkgaXQgb3IgdXNlIGl0IGZvciBhbnkgcHVycG9zZSBub3IgZGlzY2xv
c2Ugb3I8YnI+CmRpc3RyaWJ1dGUgaXRzIGNvbnRlbnRzIHRvIGFueSBvdGhlciBwZXJzb24uPGJy
PgoqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioq
KioqKioqKioqKioqKjwvcD48L2JvZHk+DQo8L2h0bWw+DQo=

--_000_B31EEDDDB8ED7E4A93FDF12A4EECD30D7D76C1DBGLKXM0002VGREEN_--


From nobody Thu Dec  3 05:26:48 2015
Return-Path: <spencerdawkins.ietf@gmail.com>
X-Original-To: manet@ietf.org
Delivered-To: manet@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id A67131A8720; Thu,  3 Dec 2015 05:26:37 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "Spencer Dawkins" <spencerdawkins.ietf@gmail.com>
To: "The IESG" <iesg@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.11.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20151203132637.18435.63772.idtracker@ietfa.amsl.com>
Date: Thu, 03 Dec 2015 05:26:37 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/LPbsrIrL-UMZFdEhDSQYetaSsBo>
Cc: manet@ietf.org, draft-ietf-manet-olsrv2-dat-metric@ietf.org, manet-chairs@ietf.org
Subject: [manet] Spencer Dawkins' No Objection on draft-ietf-manet-olsrv2-dat-metric-10: (with COMMENT)
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
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: <https://mailarchive.ietf.org/arch/browse/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: Thu, 03 Dec 2015 13:26:37 -0000

Spencer Dawkins has entered the following ballot position for
draft-ietf-manet-olsrv2-dat-metric-10: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-manet-olsrv2-dat-metric/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

I agree with Kathleen's "Close to a Discuss" on warning about MitM
attacks. I'm fine with actually addressing the attacks being out of
scope, as I believe Kathleen is.



From nobody Thu Dec  3 05:38:57 2015
Return-Path: <jch@pps.univ-paris-diderot.fr>
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 3EF4C1A875D for <manet@ietfa.amsl.com>; Thu,  3 Dec 2015 05:38:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.55
X-Spam-Level: 
X-Spam-Status: No, score=-1.55 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_FR=0.35] autolearn=no
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 Rfn3TF6XD4re for <manet@ietfa.amsl.com>; Thu,  3 Dec 2015 05:38:54 -0800 (PST)
Received: from korolev.univ-paris7.fr (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 62EFF1A875C for <manet@ietf.org>; Thu,  3 Dec 2015 05:38:54 -0800 (PST)
Received: from mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [81.194.30.253]) by korolev.univ-paris7.fr (8.14.4/8.14.4/relay1/56228) with ESMTP id tB3DcqeO002302; Thu, 3 Dec 2015 14:38:52 +0100
Received: from mailhub.math.univ-paris-diderot.fr (localhost [127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTP id C85FC61F9A; Thu,  3 Dec 2015 14:38:52 +0100 (CET)
X-Virus-Scanned: amavisd-new at math.univ-paris-diderot.fr
Received: from mailhub.math.univ-paris-diderot.fr ([127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [127.0.0.1]) (amavisd-new, port 10023) with ESMTP id RBkd4_e7KIAB; Thu,  3 Dec 2015 14:38:51 +0100 (CET)
Received: from lanthane.pps.univ-paris-diderot.fr (unknown [172.23.36.54]) (Authenticated sender: jch) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTPSA id 73BBA61FA7; Thu,  3 Dec 2015 14:38:51 +0100 (CET)
Received: from localhost ([::1] helo=lanthane.pps.univ-paris-diderot.fr) by lanthane.pps.univ-paris-diderot.fr with esmtp (Exim 4.86) (envelope-from <jch@pps.univ-paris-diderot.fr>) id 1a4U5z-0002zC-9A; Thu, 03 Dec 2015 14:38:51 +0100
Date: Thu, 03 Dec 2015 14:38:51 +0100
Message-ID: <7ia8prps7o.wl-jch@pps.univ-paris-diderot.fr>
From: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
To: Henning Rogge <hrogge@gmail.com>
In-Reply-To: <CAGnRvuosqTQ4v+4n42nP04Nz3OjebN+o1La04tu-WFfNyXkRuw@mail.gmail.com>
References: <20151202221712.3505.78561.idtracker@ietfa.amsl.com> <CAGnRvurhqzAoNK_PQo6d3nVe9T0Buo3YFgSUfL0ibSP9+GB7MQ@mail.gmail.com> <7ipoynpzk2.wl-jch@pps.univ-paris-diderot.fr> <CAGnRvuqyE0zgLn_daLi8vrHkWeowTybFw4hrcQGGT-S=c=h_8w@mail.gmail.com> <7iio4fpxjx.wl-jch@pps.univ-paris-diderot.fr> <CAGnRvuosqTQ4v+4n42nP04Nz3OjebN+o1La04tu-WFfNyXkRuw@mail.gmail.com>
User-Agent: Wanderlust/2.15.9
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (korolev.univ-paris7.fr [194.254.61.138]); Thu, 03 Dec 2015 14:38:52 +0100 (CET)
X-Miltered: at korolev with ID 566045EC.003 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 566045EC.003 from mailhub.math.univ-paris-diderot.fr/mailhub.math.univ-paris-diderot.fr/null/mailhub.math.univ-paris-diderot.fr/<jch@pps.univ-paris-diderot.fr>
X-j-chkmail-Score: MSGID : 566045EC.003 on korolev.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Status: Ham
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/ntAuW1N8aHclruKKZ4VzYrEPozk>
Cc: MANET IETF <manet@ietf.org>
Subject: Re: [manet] Ben Campbell's No Objection on draft-ietf-manet-olsrv2-dat-metric-10: (with COMMENT)
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: <https://mailarchive.ietf.org/arch/browse/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: Thu, 03 Dec 2015 13:38:55 -0000

> The problem with using EWMA for frame/packet loss (as far as I
> understand it) is that the input is purely binary... which means that
> the EWMA is much more unstable

Yeah, makes sense -- the exponential average gives too much weight to the
latest sample.

-- Juliusz


From nobody Thu Dec  3 05:51:51 2015
Return-Path: <hrogge@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 43FF11A87BE for <manet@ietfa.amsl.com>; Thu,  3 Dec 2015 05:51:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 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, 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 qJY44G5UCBZx for <manet@ietfa.amsl.com>; Thu,  3 Dec 2015 05:51:49 -0800 (PST)
Received: from mail-wm0-x22b.google.com (mail-wm0-x22b.google.com [IPv6:2a00:1450:400c:c09::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 19B701A87BD for <manet@ietf.org>; Thu,  3 Dec 2015 05:51:49 -0800 (PST)
Received: by wmec201 with SMTP id c201so27934326wme.0 for <manet@ietf.org>; Thu, 03 Dec 2015 05:51:47 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=6CVZR3MMo1sRASjml0A6MNqzhTkf0e/j4TaPAHxUvfA=; b=AnWTxcaz96jzVE1cMfx1jILw8ix1nvRHMplDyeG/7yCreefBLr6vpcRLYmmY5awcex 77uu8oqwIMSfbYbsODvTjjYsHU2wRPrgnpfTf65PDJrCsLYC9tX5EUFNOR9olg9dIcvB JvPVwvP+3F0n+TFqV4+hCXMyaYd1dRMXbmMC6uOIGKY9MmAAu+gUgI2SVG0yPlllMQg/ Q5gxnCdYGYojZ3Xsh2HkEaHOdRyAkwFf56C22TIdcB+3BEEsQHzocXwEiAqyKZsncWkj 1tqb34s6Bl9UmUsZg8BroTMkDvg2KPH7ujwpAzi23k888AlaAWky2CkU5gUurfrn3GKK NRHg==
X-Received: by 10.194.95.65 with SMTP id di1mr10837811wjb.134.1449150707730; Thu, 03 Dec 2015 05:51:47 -0800 (PST)
MIME-Version: 1.0
Received: by 10.27.94.70 with HTTP; Thu, 3 Dec 2015 05:51:17 -0800 (PST)
In-Reply-To: <7ia8prps7o.wl-jch@pps.univ-paris-diderot.fr>
References: <20151202221712.3505.78561.idtracker@ietfa.amsl.com> <CAGnRvurhqzAoNK_PQo6d3nVe9T0Buo3YFgSUfL0ibSP9+GB7MQ@mail.gmail.com> <7ipoynpzk2.wl-jch@pps.univ-paris-diderot.fr> <CAGnRvuqyE0zgLn_daLi8vrHkWeowTybFw4hrcQGGT-S=c=h_8w@mail.gmail.com> <7iio4fpxjx.wl-jch@pps.univ-paris-diderot.fr> <CAGnRvuosqTQ4v+4n42nP04Nz3OjebN+o1La04tu-WFfNyXkRuw@mail.gmail.com> <7ia8prps7o.wl-jch@pps.univ-paris-diderot.fr>
From: Henning Rogge <hrogge@gmail.com>
Date: Thu, 3 Dec 2015 14:51:17 +0100
Message-ID: <CAGnRvuqQeN=2d1Q5HP3BG4_fibPXwGp087EQkETBVvypBERu=A@mail.gmail.com>
To: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/QXGnyYbrhW7_yy3XFktXyhScTqI>
Cc: MANET IETF <manet@ietf.org>
Subject: Re: [manet] Ben Campbell's No Objection on draft-ietf-manet-olsrv2-dat-metric-10: (with COMMENT)
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: <https://mailarchive.ietf.org/arch/browse/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: Thu, 03 Dec 2015 13:51:50 -0000

On Thu, Dec 3, 2015 at 2:38 PM, Juliusz Chroboczek
<jch@pps.univ-paris-diderot.fr> wrote:
>> The problem with using EWMA for frame/packet loss (as far as I
>> understand it) is that the input is purely binary... which means that
>> the EWMA is much more unstable
>
> Yeah, makes sense -- the exponential average gives too much weight to the
> latest sample.

Or it converges too slowly... or both.

Henning Rogge


From nobody Thu Dec  3 05:53:47 2015
Return-Path: <ietf@thomasclausen.org>
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 88E091A87DB for <manet@ietfa.amsl.com>; Thu,  3 Dec 2015 05:53:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.4
X-Spam-Level: 
X-Spam-Status: No, score=-1.4 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, J_CHICKENPOX_35=0.6, J_CHICKENPOX_52=0.6, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=no
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 ic5naY1VrbTa for <manet@ietfa.amsl.com>; Thu,  3 Dec 2015 05:53:35 -0800 (PST)
Received: from maila2.tigertech.net (maila2.tigertech.net [208.80.4.152]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 573631A87B2 for <manet@ietf.org>; Thu,  3 Dec 2015 05:53:35 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by maila2.tigertech.net (Postfix) with ESMTP id 08D29258AD9; Thu,  3 Dec 2015 05:53:35 -0800 (PST)
X-Virus-Scanned: Debian amavisd-new at maila2.tigertech.net
Received: from [129.104.75.136] (unknown [129.104.75.136]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by maila2.tigertech.net (Postfix) with ESMTPSA id 070C8253724; Thu,  3 Dec 2015 05:53:34 -0800 (PST)
Content-Type: multipart/alternative; boundary=Apple-Mail-3334563F-4409-47EB-A32E-FB71F07F45FA
Mime-Version: 1.0 (1.0)
From: Thomas Heide Clausen <ietf@thomasclausen.org>
X-Mailer: iPhone Mail (13B143)
In-Reply-To: <B31EEDDDB8ED7E4A93FDF12A4EECD30D7D76C1DB@GLKXM0002V.GREENLNK.net>
Date: Thu, 3 Dec 2015 14:53:32 +0100
Content-Transfer-Encoding: 7bit
Message-Id: <D2925838-C6F4-4E13-85F8-499651983056@thomasclausen.org>
References: <241ccb422cb941bda2617d7be275c649@VAUSDITCHM2.idirect.net> <9948DF10-0B9B-404E-BA09-C90CDE209756@thomasclausen.org> <DCC7ED56-7ED9-4610-91A0-3D70620B9823@gmail.com> <CAAePS4DtpBrWtgBbnWjLZN07mcyH=hmK0pzPvCrjwwLiTuXc2Q@mail.gmail.com> <CAAePS4AtbPekzU=m7aut08yHwZPmk-TiCdG4vvfNZtSWPowx=Q@mail.gmail.com> <8228CBB8-BCB5-4ED9-9E0C-F76CD63D2DFC@thomasclausen.org> <B31EEDDDB8ED7E4A93FDF12A4EECD30D7D76C1DB@GLKXM0002V.GREENLNK.net>
To: "Dearlove, Christopher (UK)" <chris.dearlove@baesystems.com>
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/xVVujsxDKxb4Ni6kseWjthtUc4k>
Cc: manet <manet@ietf.org>, Victoria Mercieca <vmercieca0@gmail.com>
Subject: Re: [manet] draft-ietf-manet-aodvv2-12 and draft-ietf-manet-dlep-17
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: <https://mailarchive.ietf.org/arch/browse/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: Thu, 03 Dec 2015 13:53:40 -0000

--Apple-Mail-3334563F-4409-47EB-A32E-FB71F07F45FA
Content-Type: text/plain;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable

That is exactly the thing -  the trust model assumed (& the protocol mechani=
cs) need to be understood before designing the necessary MTI security, and b=
efore deciding which bits (if any) from 7182 to use...

Thomas

> On 3 d=C3=A9c. 2015, at 14:26, Dearlove, Christopher (UK) <chris.dearlove@=
baesystems.com> wrote:
>=20
> If you go down this route of assuming transitive trust, then you might as w=
ell use 7182=E2=80=99s packet ICV and timestamp rather than message ICV and t=
imestamp.
> =20
> There is a complication (mostly one of presentation) that the 5444 multipl=
exer (rather than AODVv2) needs to do this, at least for packets containing A=
ODVv2 messages (but at which point, probably all 5444 packets). So you eithe=
r, depending on your point of view, need to request it to do that, or (admin=
istratively) decline to operate except over a 5444 multiplexer that is doing=
 this.
> =20
> The advantage is one of saved space and time when packets contain more tha=
n one message. Plus slightly better protection (hop count and limit are cove=
red) but which probably doesn=E2=80=99t matter here.
> =20
> If messages are changed/replaced on a one-to-one basis as forwarded, then t=
he only solutions I can see are hop by hop transitive trust (packets or mess=
ages per hop), or something complicated involving aggregation and knowledge o=
f changes. But the latter would be a research task to develop, so let=E2=80=99=
s not try that.
> =20
> =20
> From: manet [mailto:manet-bounces@ietf.org] On Behalf Of ietf@thomasclause=
n.org
> Sent: 03 December 2015 12:22
> To: Victoria Mercieca
> Cc: manet
> Subject: Re: [manet] draft-ietf-manet-aodvv2-12 and draft-ietf-manet-dlep-=
17
> =20
> Dear Victoria,
> =20
> Responding twice to this email, intentionally as I want to address two dif=
ferent aspects independently=E2=80=A6.
> =20
> On Nov 19, 2015, at 17:09, Victoria Mercieca <vmercieca0@gmail.com> wrote:=

> =20
> =20
> Hi Thomas and Christopher,
> Thank you for your comments.  If I may address just one point for starters=
 - regeneration vs forwarding. We use the term regeneration since forwarding=
 seems inappropriate when the message content changes at each hop.
> The changes we make to the message content are:
> 1) We change the metric so that each router along the path learns a route f=
rom the message, with the metric associated with the path up to that point
> 2) AckReq only applies between hops, so needs to be removed at each hop, a=
nd a new AckReq element may need to be added for the next hop.
> 3) ValidityTime could potentially be added by any intermediate router that=
 wishes to limit the time it will forward packets on the route.
> 4) Stripping out Unreachable Addresses from RERR which did not affect our r=
oute set.
> Can we really use the term "forwarding" if we are changing the metric valu=
e, adding a validity time, adding/removing AckReq or removing addresses and t=
heir associated TLVs?
> OK, so assume that I understand regeneration as per my previous email, as m=
eaning =E2=80=9Cgenerate a new message and send to my neighbors, based on wh=
at I learned when processing a received message=E2=80=9D =E2=80=94 just like=
 any distance vector protocol does.
> =20
> In that model, what you write makes sense: each originator of a control me=
ssage (i.e., whoever generates or regenerates it) is free to include the inf=
ormation it desires, such as the 4 points you list above. No issues with tha=
t.
> =20
> However, and this joins what I pointed out in a previous email, you write i=
n the applicability statement:
> =20
>    Providing security for a reactive routing protocol can be difficult.
>=20
>  While we can discuss if the nature of =E2=80=9Creactive routing protocol=E2=
=80=9D generates particular difficulties, we certainly can agree that this p=
rotocol has the same =E2=80=9Cdifficulties=E2=80=9D as a distance vector pro=
tocol: routing topology information (by definition) not being exchanged end-=
to-end, but between neighbors (who do calculations and generate their own an=
nouncements =E2=80=94 regeneration, as you call it).=20
>=20
>  This means that a specific security model of transitive trust must be ass=
umed, no? I trust Victoria, therefore when Victoria says =E2=80=9CStan told m=
e=E2=80=9D then I trust that she actually verified that "it was indeed Stan w=
ho told her =E2=80=A6=E2=80=9D =E2=80=94 and either way, I have no way of ve=
rifying?
>=20
>  I did not see the trust model / trust assumption discussed in the specifi=
cation (specifically not in applicability and in section 13, both of where i=
t should be called out), but I think that this is actually a crucial point t=
o get right, in order to approach developing the MTI security mechanisms.
>=20
>  Anyways, that observation actually contrasts strongly with what the appli=
cability statement then goes on to say, namely:
> =20
>    AODVv2 provides for message integrity and security against replay
>    attacks by using integrity check values, timestamps and sequence
>    numbers, as described in Section 13.
>=20
>  This is true only in as much as messages are indeed exchanged between nei=
ghbors: when you =E2=80=9Cregenerate=E2=80=9D a message, i.e., generate a ne=
w message in response to receipt of a message, you generate brand new payloa=
d (but possibly including some of the data from the received message, of cou=
rse): thus, any ICVs =E2=80=9Cfrom farther away than the neighbor=E2=80=9D w=
ill be useless (or, if you zero out the parts that you change, these parts w=
ill not be protected).
>=20
>  The above sentence, quoted from the applicability statement, and that whi=
ch transpires from section 13, seems - certainly, absent the trust model ass=
umed - to suggest that end-to-end protection/validation is provided. But, th=
is is not the case.
>=20
>  Finally to the applicability statement, a question:
>=20
>     If security associations can be
>    established, encryption can be used for AODVv2 messages to ensure
>    that only trusted routers participate in routing operations.
> =20
> What you want to say here is that =E2=80=9Cif all trusted routers have a s=
hared secret, then we=E2=80=99re able to use that shared secret to ignore no=
n-trusted routers=E2=80=9D, right?=20
> While =E2=80=9Csecurity associations=E2=80=9D that do not pass through a s=
hared secret probably can be thought up, it=E2=80=99s not trivial and I did n=
ot find any discussion of that in the document?
> =20
> Having, on the topic of security, re-read Section 13, which starts:
> =20
>    This section describes various security considerations and potential
>    avenues to secure AODVv2 routing. =20
> =20
> While this is an honest description of what follows, I remain convinced th=
at this is not sufficient. So let me ask as precisely as I can:
> =20
>             o          what is the MTI security mechanism that a conforman=
t implementation must provide?=20
>                         Specifically:
>                                     -           which are the processing s=
teps (for example in section 7.2.1=20
>                                                 and section 7.2.2 for RREP=
 - and similarly for the other message=20
>                                                 types) that define that se=
curity mechanism
> =20
>             o          what protection is offered by that MTI security mec=
hanism? And what remains
>                         vulnerable.
> =20
> If this specification targets std.track, then it should include (reasonabl=
y solid, but definitely well specified) MTI security.
> =20
> Best
> =20
> Thomas
> =20
> Further, in reply to the comment about use of the msg-hop-count and msg-ho=
p-limit fields, I think it does not matter that a message only travels one h=
op in that particular form, with that exact set of information enclosed. Hop=
 limit and hop count are part of the message and used by the routing protoco=
l, and so they refer to the multi-hop path that the AODVv2 message will foll=
ow, indicating when not to regenerate any further. So AODVv2 uses these fiel=
ds as suggested in RFC5444 Appendix B, to limit the number of hops across wh=
ich it will regenerate a packet so as to "prevent messages from endlessly ci=
rculating in a MANET".
> Kind regards,
> Victoria.
> =20
> On Wed, Nov 18, 2015 at 8:49 AM, Christopher Dearlove <christopher.dearlov=
e@gmail.com> wrote:
> I've not had time to look at either yet, though I hope to review DLEP very=
 soon.
> =20
> But this has made me think about the RFC 6621 reference in AODVv2. It's al=
ways been clear this has been rather a throwaway comment that needed thought=
, but until now I hadn't really given it any.
> =20
> And it doesn't work. RFC 6621 is fundamentally unusable here. Let's consid=
er each on turn.=20
> =20
> AODVv2 is in the RFC 5444 structure. As has been noted on many occasions, A=
OVDVv2 gets to use messages, but packets are not in its competence.
> =20
> RFC 6621 is about packets. But not even RFC 5444 packets but IP packets. I=
t's about whether or not to forward them. But RFC 5444 packets aren't just n=
ot forwarded in unchanged IP packets, they aren't even forwarded at all. The=
y are each a single hop construct, and if a message is forwarded (which is b=
y the routing protocol, as far as RFC 5444 is concerned, it's a new message)=
 it will be in a new packet, with possibly new companions.
> =20
> If AODVv2 wants to use a more efficient flooding process, it needs one at t=
he message level. Now an example of that exists - the mechanism on RFC 7181.=
 Unfortunately we didn't break that out as a separate draft (we would have l=
iked to, but there were reasons we didn't).
> =20
> And even if (by reference or other means) it were used - or some related m=
echanism such as a CDS - that processing/forwarding mechanism assumes you ha=
ve defined MPRs (or similarly, that you have defined a CDS). And that needs a=
 local exchange of information, such as NHDP's HELLO messages (and the rest o=
f NHDP) augmented with RFC 7181's MPR TLV (though only the flooding bit is n=
eeded).
> =20
> In other words, taking some real work to define. And also raising a questi=
on for the WG - why do we want a reactive protocol? The main attraction as I=
 see it is the "if you're not doing anything, you're not transmitting" prope=
rty. Which adding this voids. Of course maybe the WG doesn't value that. Or i=
t is acceptable as an option. But if so it needs to be an option that all ro=
uters use, or none. And if all, compatibly. (MPR flooding allows different M=
PR selection algorithms - but only as long as they satisfy the fundamental M=
PR algorithm properties.)
> =20
> In short, RFC 6621 must go. The alternative is nothing, or significant wor=
k.
>=20
> -- =20
> Christopher Dearlove
> christopher.dearlove@gmail.com (iPhone)
> chris@mnemosyne.demon.co.uk (home)
>=20
> On 18 Nov 2015, at 01:35, Thomas Clausen <ietf@thomasclausen.org> wrote:
>=20
> Dear all,
> =20
> I have started looking through the recently updated draft-ietf-manet-aodvv=
2-12. A lot has changed, and I regret not to have had a blow-by-bow comeback=
 to the previous review comments  - would have made it a somewhat easier tas=
k to check if all have been addressed or not.
> =20
> But, I will work through it and produce a detailed review - but from my fi=
rst quick read-through there're a couple of issue that jumped at me as worth=
 bringing forward on a more global level already.
> =20
> The first relates to  how RREQs are forwarded -- or, more generally, are n=
ot.
> =20
> The protocol currently talks about "message is regenerated" rather than "f=
orwarded". I have understood that this means that a RREQ is actually not an "=
end to end" entity, but is a "hop by hop" entity.=20
> =20
> First, that is a curious design choice, is there any reason why this is so=
 considered?
> =20
> Second, if a RREQ message is hop-by-hop only, then I do not think that the=
 use of the RFC5444 hop-limit/hop-count fields is appropriate.
> =20
> Third, the statement in section 6.5 on the use of RFC6621 is incorrect in t=
wo ways: RFC6621 does specify how messages are *forwarded* (but, as discusse=
d above, you are not forwarding messages).
> =20
> More seriously, this paragraph is incorrect:
>=20
>=20
> "Implementations MAY choose to employ techniques to reduce the number of m=
ulticast messages sent. Use of [RFC6621] in deployments is recommended. Empl=
oying [RFC6621] in a subset of the operational AODVv2 routers in a network, o=
r configuring different algorithms on different routers, will not cause inte=
roperability issues, but will reduce the effectiveness of the multicast redu=
ction scheme."
> =20
> Different routers using different relay selection algorithms in the same n=
etwork will not *just* cause loss of efficiency, but *will* cause interopera=
bility issues.
> =20
> For example if "router A" decides to suppress its message relaying because=
 it estimates that "router B" provides sufficient coverage - and conversely "=
router B" suppresses relaying for the same reason: neither A nor B would rel=
ay, and so any routers reachable only via A and B would not be covered.
> =20
> This is not a far-sought example: it can be as simple as A and B simply us=
ing self-selecting relay algorithms with different tie-breakers.
> =20
> In short: I think that the whole message flooding/regeneration part requir=
es serious work.
> =20
> The second issue is that I also suspect that there is some issue with buff=
ering, or rather with how it is specified; starting in section 6.6, I am not=
 sure that leaving that as "a matter of policy at each router" is entirely r=
ight.=20
>=20
>=20
> Also on buffering, I am wondering if the "start delivering buffered packet=
s" conditions (penultimate paragraph in 6.6, and of course through the proce=
ssing sections) is sufficient; I suspect that the condition "When a valid ro=
ute is installed" is not sufficient - that there are situations where a rout=
ing table entry is installed, but the complete route is not available or is n=
ot bidirectional?This obviously is related to RREP_Ack being hop-by-hop and n=
ot end-to-end....
>=20
>=20
> Either way, the parts of the specification that relate to buffering contai=
n a mixture of normative and non-normative verbiage (a lot of "can" but also=
 a lot of MUST/SHOULD) which I think could do with a tightening up.=20
>=20
>=20
> But....is buffering even something that should be specified by this docume=
nt? It does not impact interoperability and it interferes substantially with=
 transport and congestion control, and I am not sure that we understand the c=
onsequences (I am not convinced that the claims in the document on benefits t=
o TCP are substantiated or even true).
>=20
>=20
> As I indicated, a complete review will follow, but I thought that these wa=
s a global enough topics to call out and get engineered right.
> =20
> Thomas
> =20
> PS: I remain convinced that the security considerations section is insuffi=
cient ; I will try to articulate my thoughts on why that is, but for starter=
s looking at the recently raised (by somebody else, the Chris replied) AODV s=
ecurity questions would probably be helpful
>=20
> On 10 Nov 2015, at 02:10, Ratliff, Stanley <sratliff@idirect.net> wrote:
>=20
> Hello WG participants =E2=80=93
> =20
> The above referenced drafts were posted Oct. 13 (for AODVv2), and Oct. 16 (=
DLEP). The co-authors and the chairs ask that you please take some time to r=
eview and comment on the new submissions.
> =20
> Regards,
> Stan
> =20
> =20
>=20
> _____________________________________________________
> This electronic message and any files transmitted with it contains
> information from iDirect, which may be privileged, proprietary
> and/or confidential. It is intended solely for the use of the individual
> or entity to whom they are addressed. If you are not the original
> recipient or the person responsible for delivering the email to the
> intended recipient, be advised that you have received this email
> in error, and that any use, dissemination, forwarding, printing, or
> copying of this email is strictly prohibited. If you received this email
> in error, please delete it and immediately notify the sender.
> _____________________________________________________
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www.ietf.org/mailman/listinfo/manet
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www.ietf.org/mailman/listinfo/manet
>=20
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www.ietf.org/mailman/listinfo/manet
>=20
> =20
> =20
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www.ietf.org/mailman/listinfo/manet
> =20
> ********************************************************************
> 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.
> ********************************************************************

--Apple-Mail-3334563F-4409-47EB-A32E-FB71F07F45FA
Content-Type: text/html;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable

<html><head><meta http-equiv=3D"content-type" content=3D"text/html; charset=3D=
utf-8"></head><body dir=3D"auto"><div>That is exactly the thing - &nbsp;the t=
rust model assumed (&amp; the protocol mechanics) need to be understood befo=
re designing the necessary MTI security, and before deciding which bits (if a=
ny) from 7182 to use...<br><br></div><div id=3D"AppleMailSignature">Thomas</=
div><div><br>On 3 d=C3=A9c. 2015, at 14:26, Dearlove, Christopher (UK) &lt;<=
a href=3D"mailto:chris.dearlove@baesystems.com">chris.dearlove@baesystems.co=
m</a>&gt; wrote:<br><br></div><blockquote type=3D"cite"><div>

<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dutf-8">
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Helvetica;
	panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
	{font-family:Helvetica;
	panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
@font-face
	{font-family:UICTFontTextStyleTallBody;
	panose-1:0 0 0 0 0 0 0 0 0 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:Consolas;}
span.apple-tab-span
	{mso-style-name:apple-tab-span;}
span.EmailStyle22
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->


<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Cal=
ibri&quot;,&quot;sans-serif&quot;;color:#1F497D">If you go down this route o=
f assuming transitive trust, then you might as well use 7182=E2=80=99s packe=
t ICV and timestamp rather than message ICV and timestamp.<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Cal=
ibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span></p=
>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Cal=
ibri&quot;,&quot;sans-serif&quot;;color:#1F497D">There is a complication (mo=
stly one of presentation) that the 5444 multiplexer (rather than AODVv2) nee=
ds to do this, at least for packets containing AODVv2
 messages (but at which point, probably all 5444 packets). So you either, de=
pending on your point of view, need to request it to do that, or (administra=
tively) decline to operate except over a 5444 multiplexer that is doing this=
.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Cal=
ibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span></p=
>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Cal=
ibri&quot;,&quot;sans-serif&quot;;color:#1F497D">The advantage is one of sav=
ed space and time when packets contain more than one message. Plus slightly b=
etter protection (hop count and limit are covered) but
 which probably doesn=E2=80=99t matter here.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Cal=
ibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span></p=
>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Cal=
ibri&quot;,&quot;sans-serif&quot;;color:#1F497D">If messages are changed/rep=
laced on a one-to-one basis as forwarded, then the only solutions I can see a=
re hop by hop transitive trust (packets or messages
 per hop), or something complicated involving aggregation and knowledge of c=
hanges. But the latter would be a research task to develop, so let=E2=80=99s=
 not try that.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Cal=
ibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span></p=
>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Cal=
ibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span></p=
>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0=
cm 0cm">
<p class=3D"MsoNormal"><b><span lang=3D"EN-US" style=3D"font-size:10.0pt;fon=
t-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span la=
ng=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;=
sans-serif&quot;"> manet [<a href=3D"mailto:manet-bounces@ietf.org">mailto:m=
anet-bounces@ietf.org</a>]
<b>On Behalf Of </b><a href=3D"mailto:ietf@thomasclausen.org">ietf@thomascla=
usen.org</a><br>
<b>Sent:</b> 03 December 2015 12:22<br>
<b>To:</b> Victoria Mercieca<br>
<b>Cc:</b> manet<br>
<b>Subject:</b> Re: [manet] draft-ietf-manet-aodvv2-12 and draft-ietf-manet-=
dlep-17<o:p></o:p></span></p>
</div>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<p class=3D"MsoNormal">Dear Victoria,<o:p></o:p></p>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">Responding twice to this email, intentionally as I wa=
nt to address two different aspects independently=E2=80=A6.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<div>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class=3D"MsoNormal">On Nov 19, 2015, at 17:09, Victoria Mercieca &lt;<a h=
ref=3D"mailto:vmercieca0@gmail.com">vmercieca0@gmail.com</a>&gt; wrote:<o:p>=
</o:p></p>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-al=
t:auto">Hi Thomas and Christopher,<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-al=
t:auto">Thank you for your comments.&nbsp; If I may address just one point f=
or starters - regeneration vs forwarding. We use the term regeneration since=
 forwarding seems inappropriate when the
 message content changes at each hop.<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-al=
t:auto">The changes we make to the message content are:<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-al=
t:auto">1) We change the metric so that each router along the path learns a r=
oute from the message, with the metric associated with the path up to that p=
oint<br>
2) AckReq only applies between hops, so needs to be removed at each hop, and=
 a new AckReq element may need to be added for the next hop.<br>
3) ValidityTime could potentially be added by any intermediate router that w=
ishes to limit the time it will forward packets on the route.<br>
4) Stripping out Unreachable Addresses from RERR which did not affect our ro=
ute set.<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-al=
t:auto">Can we really use the term "forwarding" if we are changing the metri=
c value, adding a validity time, adding/removing AckReq or removing addresse=
s and their associated TLVs?<o:p></o:p></p>
</div>
</div>
</div>
</div>
</blockquote>
<p class=3D"MsoNormal">OK, so assume that I understand regeneration as per m=
y previous email, as meaning =E2=80=9Cgenerate a new message and send to my n=
eighbors, based on what I learned when processing a received message=E2=80=9D=
 =E2=80=94 just like any distance vector protocol does.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">In that model, what you write makes sense: each origi=
nator of a control message (i.e., whoever generates or regenerates it) is fr=
ee to include the information it desires, such as the 4 points you list abov=
e. No issues with that.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">However, and this joins what I pointed out in a previ=
ous email, you write in the applicability statement:<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<pre style=3D"page-break-before:always">&nbsp;&nbsp; Providing security for a=
 reactive routing protocol can be difficult.<o:p></o:p></pre>
<span style=3D"font-size:9.0pt;font-family:&quot;Helvetica&quot;,&quot;sans-=
serif&quot;;mso-fareast-language:EN-GB"><br clear=3D"all" style=3D"page-brea=
k-before:always">
</span>
<pre style=3D"page-break-before:always"><span style=3D"font-family:&quot;Hel=
vetica&quot;,&quot;sans-serif&quot;">While we can discuss if the nature of&n=
bsp;=E2=80=9Creactive routing protocol=E2=80=9D generates particular difficu=
lties, we certainly can agree that this protocol has the same&nbsp;=E2=80=9C=
difficulties=E2=80=9D as a distance vector protocol: routing&nbsp;topology i=
nformation (by definition) not being exchanged end-to-end, but between neigh=
bors (who do&nbsp;calculations and generate their own announcements&nbsp;=E2=
=80=94 regeneration, as you call it).&nbsp;</span><o:p></o:p></pre>
<span style=3D"font-size:10.0pt;font-family:&quot;Helvetica&quot;,&quot;sans=
-serif&quot;;mso-fareast-language:EN-GB"><br clear=3D"all" style=3D"page-bre=
ak-before:always">
</span>
<pre style=3D"page-break-before:always"><span style=3D"font-family:&quot;Hel=
vetica&quot;,&quot;sans-serif&quot;">This means that a specific security mod=
el of transitive trust must be assumed, no? I trust Victoria,&nbsp;therefore=
 when Victoria says&nbsp;=E2=80=9CStan told me=E2=80=9D&nbsp;then I trust th=
at she&nbsp;actually verified that "it was indeed Stan who told her&nbsp;=E2=
=80=A6=E2=80=9D&nbsp;=E2=80=94 and either way, I have no way of verifying?</=
span><o:p></o:p></pre>
<span style=3D"font-size:10.0pt;font-family:&quot;Helvetica&quot;,&quot;sans=
-serif&quot;;mso-fareast-language:EN-GB"><br clear=3D"all" style=3D"page-bre=
ak-before:always">
</span>
<pre style=3D"page-break-before:always"><span style=3D"font-family:&quot;Hel=
vetica&quot;,&quot;sans-serif&quot;">I did not see the trust model / trust a=
ssumption discussed in the specification (specifically not in applicability a=
nd in section 13, both of where it should be called out), but I think that t=
his is actually a crucial point to get right, in order to approach developin=
g the MTI security mechanisms.</span><o:p></o:p></pre>
<span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;;mso-fare=
ast-language:EN-GB"><br clear=3D"all" style=3D"page-break-before:always">
</span>
<pre style=3D"page-break-before:always"><span style=3D"font-family:&quot;Hel=
vetica&quot;,&quot;sans-serif&quot;">Anyways, that observation actually cont=
rasts strongly with what the applicability statement then goes on to say, na=
mely:</span><o:p></o:p></pre>
<pre style=3D"page-break-before:always"><o:p>&nbsp;</o:p></pre>
<pre style=3D"page-break-before:always">&nbsp;&nbsp; AODVv2 provides for mes=
sage integrity and security against replay<o:p></o:p></pre>
<pre style=3D"page-break-before:always">&nbsp;&nbsp; attacks by using integr=
ity check values, timestamps and sequence<o:p></o:p></pre>
<pre style=3D"page-break-before:always">&nbsp;&nbsp; numbers, as described i=
n <a href=3D"https://tools.ietf.org/html/draft-ietf-manet-aodvv2-12#section-=
13">Section 13</a><span style=3D"font-size:12.0pt">.</span><o:p></o:p></pre>=

<span style=3D"font-size:12.0pt;font-family:&quot;Courier New&quot;;mso-fare=
ast-language:EN-GB"><br clear=3D"all" style=3D"page-break-before:always">
</span>
<pre style=3D"page-break-before:always"><span style=3D"font-family:&quot;Hel=
vetica&quot;,&quot;sans-serif&quot;">This is true only in as much as message=
s are indeed exchanged between neighbors: when you&nbsp;=E2=80=9Cregenerate=E2=
=80=9D a message, i.e., generate a new&nbsp;message in response to receipt o=
f a message, you generate brand new payload (but possibly including some of&=
nbsp;the data from the received message, of course): thus, any ICVs&nbsp;=E2=
=80=9Cfrom farther away than the neighbor=E2=80=9D&nbsp;will be useless (or,=
 if you zero out the parts that you change, these parts will not be protecte=
d).</span><o:p></o:p></pre>
<span style=3D"font-size:10.0pt;font-family:&quot;Helvetica&quot;,&quot;sans=
-serif&quot;;mso-fareast-language:EN-GB"><br clear=3D"all" style=3D"page-bre=
ak-before:always">
</span>
<pre style=3D"page-break-before:always"><span style=3D"font-family:&quot;Hel=
vetica&quot;,&quot;sans-serif&quot;">The above sentence, quoted from the app=
licability statement, and that which transpires from section 13, seems - cer=
tainly, absent the trust model assumed - to suggest that end-to-end protecti=
on/validation is provided. But, this is <b><u>not</u></b> the case.</span><o=
:p></o:p></pre>
<span style=3D"font-size:10.0pt;font-family:&quot;Helvetica&quot;,&quot;sans=
-serif&quot;;mso-fareast-language:EN-GB"><br clear=3D"all" style=3D"page-bre=
ak-before:always">
</span>
<pre style=3D"page-break-before:always"><span style=3D"font-family:&quot;Hel=
vetica&quot;,&quot;sans-serif&quot;">Finally to the applicability statement,=
 a question:</span><o:p></o:p></pre>
<span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;;mso-fare=
ast-language:EN-GB"><br clear=3D"all" style=3D"page-break-before:always">
</span>
<pre style=3D"page-break-before:always"><span style=3D"font-size:12.0pt">&nb=
sp;&nbsp; If security associations can be<o:p></o:p></span></pre>
<pre style=3D"page-break-before:always"><span style=3D"font-size:12.0pt">&nb=
sp;&nbsp; established, encryption can be used for AODVv2 messages to ensure<=
o:p></o:p></span></pre>
<pre style=3D"page-break-before:always"><span style=3D"font-size:12.0pt">&nb=
sp; &nbsp;that only trusted routers participate in routing operations.</span=
><o:p></o:p></pre>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</div>
<div>
<p class=3D"MsoNormal">What you want to say here is that =E2=80=9Cif all tru=
sted routers have a shared secret, then we=E2=80=99re able to use that share=
d secret to ignore non-trusted routers=E2=80=9D, right?&nbsp;<o:p></o:p></p>=

</div>
<div>
<p class=3D"MsoNormal">While =E2=80=9Csecurity associations=E2=80=9D that do=
 not pass through a shared secret probably can be thought up, it=E2=80=99s n=
ot trivial and I did not find any discussion of that in the document?<o:p></=
o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">Having, on the topic of security, re-read Section 13,=
 which starts:<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<pre style=3D"page-break-before:always">&nbsp;&nbsp; This section describes v=
arious security considerations and potential<o:p></o:p></pre>
<pre style=3D"page-break-before:always">&nbsp;&nbsp; avenues to secure AODVv=
2 routing.&nbsp; <o:p></o:p></pre>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</div>
<div>
<p class=3D"MsoNormal">While this is an honest description of what follows, I=
 remain convinced that this is not sufficient. So let me ask as precisely as=
 I can:<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><span class=3D"apple-tab-span">&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span>o<span class=3D"apple-ta=
b-span">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span>what is the MTI security mechanism that a conformant implementation m=
ust provide?&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><span class=3D"apple-tab-span">&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span>
Specifically:<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><span class=3D"apple-tab-span">&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span>-<span class=3D"apple-tab-span">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp; </span>which are the processing steps (for example i=
n section 7.2.1&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><span class=3D"apple-tab-span">&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span>and section 7.2.2 for RREP - and similarly for the other message&nbsp=
;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><span class=3D"apple-tab-span">&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span>types) that define that security mechanism<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><span class=3D"apple-tab-span">&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span>o<span class=3D"apple-ta=
b-span">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span>what protection is offered by that MTI security mechanism? And what r=
emains<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><span class=3D"apple-tab-span">&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span>
vulnerable.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">If this specification targets std.track, then it shou=
ld include (reasonably solid, but definitely well specified) MTI security.<o=
:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">Best<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">Thomas<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<div>
<div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-al=
t:auto">Further, in reply to the comment about use of the msg-hop-count and m=
sg-hop-limit fields, I think it does not matter that a message only travels o=
ne hop in that particular form,
 with that exact set of information enclosed. Hop limit and hop count are pa=
rt of the message and used by the routing protocol, and so they refer to the=
 multi-hop path that the AODVv2 message will follow, indicating when not to r=
egenerate any further. So AODVv2
 uses these fields as suggested in RFC5444 Appendix B, to limit the number o=
f hops across which it will regenerate a packet so as to "prevent messages f=
rom endlessly circulating in a MANET".
<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-al=
t:auto">Kind regards,<br>
Victoria.<o:p></o:p></p>
</div>
<div>
<div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<p class=3D"MsoNormal">On Wed, Nov 18, 2015 at 8:49 AM, Christopher Dearlove=
 &lt;<a href=3D"mailto:christopher.dearlove@gmail.com" target=3D"_blank">chr=
istopher.dearlove@gmail.com</a>&gt; wrote:<o:p></o:p></p>
<div>
<div>
<p class=3D"MsoNormal">I've not had time to look at either yet, though I hop=
e to review DLEP very soon.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">But this has made me think about the RFC 6621 referen=
ce in AODVv2. It's always been clear this has been rather a throwaway commen=
t that needed thought, but until now I hadn't really given it any.<o:p></o:p=
></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">And it doesn't work. RFC 6621 is fundamentally unusab=
le here. Let's consider each on turn.&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">AODVv2 is in the RFC 5444 structure. As has been note=
d on many occasions, AOVDVv2 gets to use messages, but packets are not in it=
s competence.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">RFC 6621 is about packets. But not even RFC 5444 pack=
ets but IP packets. It's about whether or not to forward them. But RFC 5444 p=
ackets aren't just not forwarded in unchanged IP packets, they aren't even f=
orwarded at all. They are each
 a single hop construct, and if a message is forwarded (which is by the rout=
ing protocol, as far as RFC 5444 is concerned, it's a new message) it will b=
e in a new packet, with possibly new companions.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">If AODVv2 wants to use a more efficient flooding proc=
ess, it needs one at the message level. Now an example of that exists - the m=
echanism on RFC 7181. Unfortunately we didn't break that out as a separate d=
raft (we would have liked to,
 but there were reasons we didn't).<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">And even if (by reference or other means) it were use=
d - or some related mechanism such as a CDS - that processing/forwarding mec=
hanism assumes you have defined MPRs (or similarly, that you have defined a C=
DS). And that needs a local exchange
 of information, such as NHDP's HELLO messages (and the rest of NHDP) augmen=
ted with RFC 7181's MPR TLV (though only the flooding bit is needed).<o:p></=
o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">In other words, taking some real work to define. And a=
lso raising a question for the WG - why do we want a reactive protocol? The m=
ain attraction as I see it is the "if you're not doing anything, you're not t=
ransmitting" property. Which
 adding this voids. Of course maybe the WG doesn't value that. Or it is acce=
ptable as an option. But if so it needs to be an option that all routers use=
, or none. And if all, compatibly. (MPR flooding allows different MPR select=
ion algorithms - but only as
 long as they satisfy the fundamental MPR algorithm properties.)<o:p></o:p><=
/p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">In short, RFC 6621 mus=
t go. The alternative is nothing, or significant work.<o:p></o:p></p>
<div>
<p class=3D"MsoNormal">-- &nbsp;<span style=3D"color:#888888"><o:p></o:p></s=
pan></p>
<div>
<p class=3D"MsoNormal"><span style=3D"color:#888888">Christopher Dearlove<o:=
p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"color:#888888"><a href=3D"mailto:chris=
topher.dearlove@gmail.com" target=3D"_blank">christopher.dearlove@gmail.com<=
/a> (iPhone)<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"color:#888888"><a href=3D"mailto:chris=
@mnemosyne.demon.co.uk" target=3D"_blank">chris@mnemosyne.demon.co.uk</a> (h=
ome)<o:p></o:p></span></p>
</div>
</div>
</div>
<div>
<div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><br>
On 18 Nov 2015, at 01:35, Thomas Clausen &lt;<a href=3D"mailto:ietf@thomascl=
ausen.org" target=3D"_blank">ietf@thomasclausen.org</a>&gt; wrote:<o:p></o:p=
></p>
</div>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<div>
<p class=3D"MsoNormal">Dear all,<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">I have started looking through the recently updated&n=
bsp;draft-ietf-manet-aodvv2-12. A lot has changed, and I regret not to have h=
ad a blow-by-bow comeback to the previous review comments &nbsp;- would have=
 made it a somewhat easier task to check
 if all have been addressed or not.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">But, I will work through it and produce a detailed re=
view - but from my first quick read-through there're a couple of issue that j=
umped at me as worth bringing forward on a more global level already.<o:p></=
o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">The first relates to &nbsp;how RREQs are forwarded --=
 or, more generally, are not.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">The protocol currently talks about "message is regene=
rated" rather than "forwarded". I have understood that this means that a RRE=
Q is actually not an "end to end" entity, but is a "hop by hop" entity.&nbsp=
;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">First, that is a curious design choice, is there any r=
eason why this is so considered?<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">Second, if a RREQ message is hop-by-hop only, then I d=
o not think that the use of the RFC5444 hop-limit/hop-count fields is approp=
riate.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">Third, the statement in section 6.5 on the use of RFC=
6621 is incorrect in two ways: RFC6621 does specify how messages are *forwar=
ded* (but, as discussed above, you are not forwarding messages).<o:p></o:p><=
/p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">More seriously, this paragraph is incorrect:<o:p></o:=
p></p>
</div>
<div>
<pre><span style=3D"font-family:&quot;UICTFontTextStyleTallBody&quot;,&quot;=
serif&quot;"><br><br></span><o:p></o:p></pre>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<pre><span style=3D"font-family:&quot;UICTFontTextStyleTallBody&quot;,&quot;=
serif&quot;">"Implementations MAY choose to employ techniques to reduce the n=
umber of multicast messages sent. Use of [<a href=3D"https://tools.ietf.org/=
html/rfc6621" target=3D"_blank" title=3D"&quot;Simplified Multicast Forwardi=
ng&quot;">RFC6621</a>] in deployments is recommended. Employing [<a href=3D"=
https://tools.ietf.org/html/rfc6621" target=3D"_blank" title=3D"&quot;Simpli=
fied Multicast Forwarding&quot;">RFC6621</a>] in a subset of the operational=
 AODVv2 routers in a network, or configuring different algorithms on differe=
nt routers, will not cause interoperability issues, but will reduce the effe=
ctiveness of the multicast reduction scheme."</span><span style=3D"font-size=
:14.5pt"><o:p></o:p></span></pre>
</blockquote>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">Different routers using different relay selection alg=
orithms in the same network will not *just* cause loss of efficiency, but *w=
ill* cause interoperability issues.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">For example if "router A" decides to suppress its mes=
sage relaying because it estimates that "router B" provides sufficient cover=
age - and conversely "router B" suppresses relaying for the same reason: nei=
ther A nor B would relay, and so
 any routers reachable only via A and B would not be covered.<o:p></o:p></p>=

</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">This is not a far-sought example: it can be as simple=
 as A and B simply using self-selecting relay algorithms with different tie-=
breakers.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">In short: I think that the whole message flooding/reg=
eneration part requires serious work.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<div>
<p class=3D"MsoNormal">The second issue is that I also suspect that there is=
 some issue with buffering, or rather with how it is specified; starting in s=
ection 6.6, I am not sure that leaving that as "a matter of policy at each r=
outer" is entirely right.&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><br>
<br>
<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">Also on buffering, I am wondering if the "start deliv=
ering buffered packets" conditions (penultimate paragraph in 6.6, and of cou=
rse through the processing sections) is sufficient; I suspect that the condi=
tion "When a valid route is installed"
 is not sufficient - that there are situations where a routing table entry i=
s installed, but the complete route is not available or is not bidirectional=
?This obviously is related to RREP_Ack being hop-by-hop and not end-to-end..=
..<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><br>
<br>
<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">Either way, the parts of the specification that relat=
e to buffering contain a mixture of normative and non-normative verbiage (a l=
ot of "can" but also a lot of MUST/SHOULD) which I think could do with a tig=
htening up.&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><br>
<br>
<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">But....is buffering even something that should be spe=
cified by this document? It does not impact interoperability and it interfer=
es substantially with transport and congestion control, and I am not sure th=
at we understand the consequences
 (I am not convinced that the claims in the document on benefits to TCP are s=
ubstantiated or even true).<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><br>
<br>
<o:p></o:p></p>
<div>
<p class=3D"MsoNormal">As I indicated, a complete review will follow, but I t=
hought that these was a global enough topics to call out and get engineered r=
ight.<o:p></o:p></p>
</div>
</div>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">Thomas<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">PS: I remain convinced that the security consideratio=
ns section is insufficient ; I will try to articulate my thoughts on why tha=
t is, but for starters looking at the recently raised (by somebody else, the=
 Chris replied) AODV security questions
 would probably be helpful<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><br>
On 10 Nov 2015, at 02:10, Ratliff, Stanley &lt;<a href=3D"mailto:sratliff@id=
irect.net" target=3D"_blank">sratliff@idirect.net</a>&gt; wrote:<o:p></o:p><=
/p>
</div>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-al=
t:auto">Hello WG participants =E2=80=93
<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-al=
t:auto">&nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-al=
t:auto;text-autospace:none">
The above referenced drafts were posted Oct. 13 (for AODVv2), and Oct. 16 (D=
LEP). The co-authors and the chairs ask that you please take some time to re=
view and comment on the new submissions.
<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-al=
t:auto;text-autospace:none">
&nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-al=
t:auto;text-autospace:none">
Regards,<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-al=
t:auto;text-autospace:none">
Stan<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-al=
t:auto;text-autospace:none">
&nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-al=
t:auto">&nbsp;<o:p></o:p></p>
</div>
<p class=3D"MsoNormal"><br>
<span style=3D"font-size:8.0pt;font-family:&quot;Arial&quot;,&quot;sans-seri=
f&quot;;color:#003366">_____________________________________________________=
<br>
This electronic message and any files transmitted with it contains<br>
information from iDirect, which may be privileged, proprietary<br>
and/or confidential. It is intended solely for the use of the individual<br>=

or entity to whom they are addressed. If you are not the original<br>
recipient or the person responsible for delivering the email to the<br>
intended recipient, be advised that you have received this email<br>
in error, and that any use, dissemination, forwarding, printing, or<br>
copying of this email is strictly prohibited. If you received this email<br>=

in error, please delete it and immediately notify the sender.<br>
_____________________________________________________</span> <o:p></o:p></p>=

</div>
</blockquote>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class=3D"MsoNormal">_______________________________________________<br>
manet mailing list<br>
<a href=3D"mailto:manet@ietf.org" target=3D"_blank">manet@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/manet" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/manet</a><o:p></o:p></p>
</div>
</blockquote>
</div>
</blockquote>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class=3D"MsoNormal">_______________________________________________<br>
manet mailing list<br>
<a href=3D"mailto:manet@ietf.org" target=3D"_blank">manet@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/manet" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/manet</a><o:p></o:p></p>
</div>
</blockquote>
</div>
</div>
</div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><br>
_______________________________________________<br>
manet mailing list<br>
<a href=3D"mailto:manet@ietf.org" target=3D"_blank">manet@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/manet" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/manet</a><o:p></o:p></p>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</div>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<p class=3D"MsoNormal">_______________________________________________<br>
manet mailing list<br>
<a href=3D"mailto:manet@ietf.org">manet@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/manet">https://www.ietf.org=
/mailman/listinfo/manet</a><o:p></o:p></p>
</div>
</blockquote>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</div>
<p>********************************************************************<br>
This email and any attachments are confidential to the intended<br>
recipient and may also be privileged. If you are not the intended<br>
recipient please delete it from your system and notify the sender.<br>
You should not copy it or use it for any purpose nor disclose or<br>
distribute its contents to any other person.<br>
********************************************************************</p>

</div></blockquote></body></html>=

--Apple-Mail-3334563F-4409-47EB-A32E-FB71F07F45FA--


From nobody Thu Dec  3 06:10:15 2015
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: manet@ietf.org
Delivered-To: manet@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id B698D1A8868; Thu,  3 Dec 2015 06:10:14 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "Stephen Farrell" <stephen.farrell@cs.tcd.ie>
To: "The IESG" <iesg@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.11.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20151203141014.13172.85185.idtracker@ietfa.amsl.com>
Date: Thu, 03 Dec 2015 06:10:14 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/0sbUf4YVHT3sz2wRsPzCYuMv0Qc>
Cc: manet@ietf.org, draft-ietf-manet-olsrv2-dat-metric@ietf.org, manet-chairs@ietf.org
Subject: [manet] Stephen Farrell's No Objection on draft-ietf-manet-olsrv2-dat-metric-10: (with COMMENT)
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
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: <https://mailarchive.ietf.org/arch/browse/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: Thu, 03 Dec 2015 14:10:14 -0000

Stephen Farrell has entered the following ballot position for
draft-ietf-manet-olsrv2-dat-metric-10: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-manet-olsrv2-dat-metric/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------


- General: This seems mostly to be an abstract metric that could be
re-used e.g. in ROLL or HOMENET (if it's good:-) but with
OLSR-specific text and concepts mixed in here and there.  It'd have
been better were it possible to separate the abstract metric from
the OLSR-specifics to make the former easier to re-use later. It's
fine if determining if that would be useful is a part of the
experiment, but it might be good to mention it here.

- Section 6: In particular "fraction of the loss rate" isn't clear
to me, but maybe that's fine and it's known term of art to folks who
do metrics.

- Section 11: Wrt the MitM comments from other ADs - one possiblity
here might be to recommend that protocols making use of this metric
should be cognizant of, and include mitigtions for, MitM attacks of
this kind. (Just a suggestion, feel free to ignore if you prefer.) 

- Thanks for handling the secdir review [1] - I think that all the
issues there were resolved, but do say if some still need a bit
more chatting.

   [1] https://www.ietf.org/mail-archive/web/secdir/current/msg06185.html



From nobody Thu Dec  3 06:48:23 2015
Return-Path: <Ietf@thomasclausen.org>
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 E55741A8978 for <manet@ietfa.amsl.com>; Thu,  3 Dec 2015 06:48:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level: 
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, J_CHICKENPOX_57=0.6, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-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 hEi09iP0uDd4 for <manet@ietfa.amsl.com>; Thu,  3 Dec 2015 06:48:14 -0800 (PST)
Received: from maila2.tigertech.net (maila2.tigertech.net [208.80.4.152]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5BAA51A8982 for <manet@ietf.org>; Thu,  3 Dec 2015 06:48:14 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by maila2.tigertech.net (Postfix) with ESMTP id 46F3524061E; Thu,  3 Dec 2015 06:48:14 -0800 (PST)
X-Virus-Scanned: Debian amavisd-new at maila2.tigertech.net
Received: from [192.168.147.111] (mtg91-1-82-227-24-173.fbx.proxad.net [82.227.24.173]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by maila2.tigertech.net (Postfix) with ESMTPSA id 95521240230; Thu,  3 Dec 2015 06:48:12 -0800 (PST)
Mime-Version: 1.0 (Mac OS X Mail 9.1 \(3096.5\))
Content-Type: multipart/alternative; boundary="Apple-Mail=_ABC69C7A-63FD-4886-ADE1-DE7AE81ED1C2"
From: ietf@thomasclausen.org
In-Reply-To: <CAAePS4Dmv=j_ASKhsX+kenP-xaDUWUEFuzYGduxu+FR_C2R-MA@mail.gmail.com>
Date: Thu, 3 Dec 2015 15:48:14 +0100
Sendlaterdate: Thu, 3 Dec 2015 15:48:14 +0100
Message-Id: <C2EBA968-13E5-486A-8554-712BACC3392B@thomasclausen.org>
References: <F474BF24-D920-4A54-8F43-AB4B9FE939A8@thomasclausen.org> <CAAePS4Dmv=j_ASKhsX+kenP-xaDUWUEFuzYGduxu+FR_C2R-MA@mail.gmail.com>
To: Victoria Mercieca <vmercieca0@gmail.com>
X-Mailer: Apple Mail (2.3096.5)
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/gU7ktKCOpua60ZJuL8cKPGcx42Q>
Cc: manet <manet@ietf.org>
Subject: Re: [manet] Stuff from review of aodv-11 page 1-22 that are still not folded into -12
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: <https://mailarchive.ietf.org/arch/browse/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: Thu, 03 Dec 2015 14:48:22 -0000

--Apple-Mail=_ABC69C7A-63FD-4886-ADE1-DE7AE81ED1C2
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Dear Victoria,

> On Dec 2, 2015, at 15:24, Victoria Mercieca <vmercieca0@gmail.com> =
wrote:
>=20
> Hello Thomas,
>=20
> Thank you again for your time spent reviewing AODVv2. I apologise that =
we did not give a "point by point" response to your comments on draft 11 =
- I felt that since most of the comments were around a few major topics, =
it made sense to address the topic across the whole draft, rather than =
respond to every single comment in order. I did also try to start a =
discussion on the MANET list based on your comments from draft 11, but =
did not see any responses.=20
>=20

I saw the mail, but it seemed more of a =E2=80=9Csummary of my =
comments=E2=80=9D, which was a fine initiative =E2=80=94 but, I did not =
really have anything to contribute beyond my initial review.

Best,

Thomas

> Thank you again, we will discuss and intend to respond soon.
>=20
> Kind regards,
> Victoria.
>=20
>=20
>=20
> On Tue, Dec 1, 2015 at 7:21 PM, <ietf@thomasclausen.org =
<mailto:ietf@thomasclausen.org>> wrote:
> All,
>=20
> I am working through the revised I-D to see what comments that I made =
previously have been addressed, and which still do apply.
>=20
> As I sent my original review piecemeal, I=E2=80=99ll send my refresher =
in matching pieces (in part, in recognition that it is hard to get time =
to sit down and review the whole document in one go, and I do want to =
reply to the authors as quickly as possible)
>=20
> In doing so, I am noticing additional things (notably, but not =
exclusively, to section 7 and beyond, which I didn=E2=80=99t get through =
reviewing last time around) which needs attention. I=E2=80=99ll gather =
that in separate emails a bit later, once I=E2=80=99ve worked through =
the complete, updated spec.
>=20
> So onwards...
>=20
> Abstract:
>         I made the following comment, which still applies:
>=20
>                 =E2=80=9CThis is a little over-stating the =
applicability: these statements may
>                  be true in some scenarios (for example, when there =
are few
>                  concurrent traffic flows, and therefore few routes to =
repair, and
>                  therefore few flooding operations to contend for =
channel access).
>                  As a general statement, this last sentence is =
incorrect=E2=80=9D=E2=80=9D
>=20
> Overview (and elsewhere):
>=20
>         I made a comment previously that =E2=80=9CRouter client=E2=80=9D=
 is a poorly chosen
>         term, and have proposed alternatives. I=E2=80=99ve seen some =
attempts on the list
>         at rather than change the term, explain it =E2=80=94 some of =
which is in this document.
>         The =E2=80=9COverview=E2=80=9D still talks about =E2=80=9Ca =
router=E2=80=A6one of its clients=E2=80=9D - which is no less
>         confusing than last time Iw went through it.
>=20
>         I reiterate, why not use =E2=80=9CLocal Attached Network =
Set=E2=80=9D, which is the term used
>         by other documents from this WG?
>=20
> Overview:
>         The term =E2=80=9Cconfirming adjacency=E2=80=9D is gone, and =
is now replaced by
>         =E2=80=9Cconfirming bidirectionality=E2=80=9D - which, alas, =
still sounds like there is some active
>         monitoring (HELLO message exchange) going on. Unless that is =
the case,
>         then please be more specific here.
>=20
>         I note that the term adjacency is used through and through the =
document, btw.
>=20
>         I suggested in my last review:
>=20
>                 The overview must also include a paragraph on the =
intersections
>                 between this protocol and the forwarding plane =E2=80=94=
 this, as it is
>                 different (and more invasive) from that which is =
typically seen in
>                 routing protocols.
>=20
>                 Specifically, as a reactive protocol, it is required =
(at least) that the
>                 forwarding plane is modified :
>=20
>                 1) A =E2=80=9Cmiss=E2=80=9D when looking up a next hop =
for a data packet to be
>                    forwarded, is signalled to the AODVv2 process so as =
to permit
>                   that route discovery be launched;
>=20
>                 2) A =E2=80=9Cmiss=E2=80=9D when attempting to deliver =
a data packet to a next hop,
>                    which was recorded in the routing table, is =
signalled to the AODVv2
>                    process so as to permit that a route repair be =
initiated and/or a Route
>                    Error be generated.
>=20
>                 3) A =E2=80=9Chit=E2=80=9D when looking up a next hop =
for a data packet to be forwarded
>                     to a destination is signalled to the AODVv2 =
process so as to permit
>                     maintenance of =E2=80=9Cactive route=E2=80=9D =
Route State, timers and such.
>=20
>                 Note that these things are necessary to call out in =
the =E2=80=9Coverview=E2=80=9D and in
>                 the =E2=80=9Capplicability statement=E2=80=9D, both: =
it is not that they are negatives per se,
>                 but that they are important factors governing the =
applicability of this protocol:
>                 will a given platform permit such access to the =
forwarding plane, for example?
>                 Important to understand if for that platform this =
protocol is apple
>=20
>=20
>         I see that this was not addressed in the overview, nor in the =
applicability other than
>         by a forward reference to section 6.4. While it is positive =
that there is a section 6.4,
>         this does not exonerate the overview and the applicability =
statement for being
>         honest about the requirements (notably to the platform/os) =
that this protocol has
>         for being applicable
>=20
>         I suggested in my last review:
>=20
>                 =E2=80=9CIt is important to do more than this: 7182 =
does only provide =E2=80=9Ccontainers=E2=80=9D
>                  for ICVs and timestamps, and does not specify how to =
use them to obtain
>                  specific security properties. RFC7182 may be a tool =
that can be used, but
>                  *how* that tool is used is what determines the =
security properties.
>=20
>                 Therefore, saying that =E2=80=9Csecurity is dealt with =
by using RFC7182=E2=80=9D is either an
>                 incomplete statement, or is indicative of insufficient =
security considerations.=E2=80=9D
>=20
>         The actual sentence in the I-D has been changed, now it =
explicitly names the
>         two TLVs from 7182 that it uses. That is, alas, still not =
sufficient.
>=20
>         Making the aside that was discussed recently on the list, that =
(i) control messages
>         are not forwarded, and that (ii) they are modified in transit, =
the security/trust model
>         is somewhat different from that of 7181 and consequently for =
what 7182 was initially
>         written for. I think that  calling out the trust model, and =
how 7182 actually is used here,
>         might be what is called for.
>=20
>         Continuing with the aside, this *especially* as the =
applicability statement says:
>=20
>                 "Providing security for a reactive routing protocol =
can be difficult=E2=80=9D
>=20
>=20
> Terminology:
>=20
>         My last review suggested:
>                 =E2=80=9CThis has been brought up on the list several =
times in the past, without having
>                  been addressed.
>=20
>                 There are =E2=80=9Chosts=E2=80=9D and there are =
=E2=80=9Crouters=E2=80=9D =E2=80=94 whose roles are well defined.
>                 =E2=80=9CNode=E2=80=9D not so much =E2=80=94 which is =
clear from looking at the definition here: =E2=80=9Ceither
>                 AODVv2 routers or router clients=E2=80=9D (with =
=E2=80=9Crouter clients=E2=80=9D being defined as =E2=80=9Can
>                 AODVv2 router is also its own router client=E2=80=9D).
>=20
>                 This is very much related to the use of =E2=80=9CRouter =
Client=E2=80=9D, and both that term,
>                 and =E2=80=9Cnode=E2=80=9D indicative that some =
clarity is needed here.
>=20
>                 All a router cares about is =E2=80=9Can address=E2=80=9D=
. If that address is of a network, or
>                 a router, or an interface (and, if said interface is =
installed in a router or a host)
>                 doesn=E2=80=99t matter.
>=20
>                 So, =E2=80=9Can address=E2=80=9D is something that the =
routing protocol should care about
>                 finding paths to. Which means that each address that =
should be made
>                 reachable by the routing protocol should be advertised =
by (at least) one router
>                 in the network.
>=20
>                 One way of doing that would be to simply talk about =
=E2=80=9CAttached Networks=E2=80=9D as
>                 is done in RFC7181, wherein an address included in the =
=E2=80=9CAttached Network Set=E2=80=9D
>                 is advertised by an OLSRv2 router....in this case, the =
equivalent would be =E2=80=9Cfor each
>                 address in the Attached Network Set of an AODVv2 =
router the router MUST
>                 respond authoritatively to a RREQ, and MUST maintain =
the corresponding sequence number=E2=80=9D.
>=20
>                 The text, as it currently is, is really hard to read, =
and a re-edit along these lines would go a long way.=E2=80=9D
>=20
>         I note that the terms =E2=80=9CNode=E2=80=9D and =E2=80=9CRouter=
 Client=E2=80=9D are still used, in their original form,
>         and that other than some slight wordsmithing this comment has =
not been addressed in the document.
>=20
>         I reiterate that the need to use router, host, node, and =
router client in and by itself should
>         be an indicator that tightening up of terminology is required.
>=20
>=20
>         I made the following comment to Routable Unicast IP Address:
>=20
>                 =E2=80=9CAre there any technical reason why not simply =
*any* address could be
>                  considered by the routing protocol?
>=20
>                  My understanding, but correct me if I am wrong, is =
that all that is required is
>                  that all interfaces in a given AODVv2 routing domain =
has an unique address.
>=20
>                  That some of these addresses (by an IP addressing =
architecture document)
>                  has special semantics associated (such as are link =
locals, or are for private
>                  use, or are for example use only, or are for =
multicast) is out of scope here?
>=20
>         I see nothing has changed on the above, so let me be more =
explicit: the routing protocol itself
>         (probably) should not care about what kind of addresses are =
filled into it. Is an 192.16./16 address
>         appropriate? Not across the internet, but it may be in =
somebody=E2=80=99s private deployments. Should
>         the routing protocol be =E2=80=9Caddress police=E2=80=9D and =
is implementation of a =E2=80=9CI refuse to route these addresses=E2=80=A6=
=E2=80=9D
>         a requirement for claiming conformance? Suggest simply stating =
what the requirements are under
>         which the routing protocol will work =E2=80=94 and leave =
=E2=80=9Caddress assignment politics=E2=80=9D aside.
>=20
>         I also continued:
>=20
>                  Now, with that being said also, the WG wanted that =
RFC7181 supports not
>                  just multiple interfaces, but also the same address =
used on multiple interfaces
>                  of the same router. There were good reasons for that, =
and while it was not trivial
>                  to implement, it turned out to be the right thing to =
support. If there are technical
>                  reasons why this is not supported in AODVv2 (for =
example, if this cannot be
>                  made work because of <reason>) then that should be =
called out in the
>                  applicability statement also?
>=20
>                 Conversely, if it is possible in AODVv2, then I do not =
believe that it is clearly
>                 specified how (at least, in the =E2=80=9Cnaive=E2=80=9D =
on paper examples I drew up, something
>                 ended up not working). So either the protocol as-is =
does not support it (but
>                 could be made to?) or it is supported (but just need =
to be spelled out), or is
>                 not possible (and need to be disclaimed in the =
applicability statement).
>=20
>                 Stan Ratliff was a driving force in holding the WG=E2=80=
=99s collective feet to the fire
>                 in getting this support included in RFC7181, and would =
likely be the right
>                 person to consult on this matter?
>=20
>         I actually have not seen changes, or comments, on this. In =
OLSRv2, the WG was making it
>         a strong requirement that it should be possible to use the =
same IP address on different
>         interfaces of a router. It was somewhat tedious to design =
around, but it was worked out, and
>         the conditions under which that was possible were defined and =
documented.
>=20
>         I would like to see the same done for this protocol.
>=20
>         I also note that this is not unrelated to RFC6621-discussions. =
For example, when selecting
>         S-MPRs on a multi-interface and multi-address-per-interface =
router, care must be taken
>         least things won=E2=80=99t work. So, if (and this links back =
to previous mails) RFC6621 is a
>         requirement or desire for this protocol, then there are some =
considerations required here.
>=20
>         I see that the definition of =E2=80=9CRouter Client=E2=80=9D =
has changed to be
>=20
>                 =E2=80=9CAn address or address range=E2=80=A6the =
AODVv2 router=E2=80=99s interface addresses
>                  are also configured as router clients=E2=80=9D
>=20
>         Better than before, but still missing the target. The term =
=E2=80=9CRouter Client=E2=80=9D is, as I indicated
>         numerous times before, odd.
>=20
>         But the second part of the sentence, does that mean (what it =
says) that the interfaces
>         must be configured specially, so as to be able to be =E2=80=9Cro=
uter clients=E2=80=9D? That can=E2=80=99t be true.
>=20
>         What you likely mean is:
>=20
>                 =E2=80=9CAn AODVv2 router is configured so as to =
consider its own interfaces as part of
>                  the locally attached network set=E2=80=9D ?
>=20
>         You configure the router, right? No special =E2=80=9Cinterface =
configuration properties=E2=80=9D are required
>         for an interface to be announcable by  an AODVv2 router?
>         (And, getting rid of node would actually make the definition =
shorter and nicer)
>=20
>         Now, snipping out from the applicability statement:
>=20
>                 "Multi-homing of an IP address is not supported by =
AODVv2, and therefore a
>                   Router Client, i.e. an IP Address,  =E2=80=A6 "
>=20
>         =E2=80=A6evidence to there being some redundant terminology =
here to weed away.
>=20
>         The below is a little bit of a meta-comment, I am not quite =
sure what I think here.
>         The definitions for Target Node and such were confusing =
before. They still are, somewhat.
>=20
>         I think that it may be because the definitions now used are =
simply copy-pasted out from the
>         tables in the previous version, for example:
>=20
>                 An AODVv2 Data Element containing the destination =
address of the
>                 IP packet triggering route discovery.
>=20
>         OK, I can trace back and see that a Data Element is something =
that exists inside a
>         protocol message. To me, however, that=E2=80=99s not really =
general terminology as such, but
>         part of the specification of a packet format - or rather, it =
is the notation that you use
>         when describing an algorithm. By the way, why are some =
notations in CamelCase
>         whereas others have a space in them, e.g. =E2=80=9CTarget =
Node=E2=80=9D and =E2=80=9CTargMetric=E2=80=9D, both of which
>         are Data Elements? Would be good with a consistent approach =
here.
>=20
>         I *think* that it would be better to take all those =E2=80=9CDat=
a Element=E2=80=9D bits and move to a separate
>         section (or subsection) to the terminology, and then keep all =
the =E2=80=9Cother stuff=E2=80=9D (Neighbor, =E2=80=A6)
>         in its own section.
>=20
>         I=E2=80=99m a great fan of calling this section =E2=80=9CTermino=
logy and Notation=E2=80=9D and then having two
>         subsections, one which is =E2=80=9CTerminology=E2=80=9D and =
one which is =E2=80=9CNotation=E2=80=9D, with the
>         TargMetric and Target Node being firmly in the latter.
>=20
>         I made a comment:
>                 "Second, should =E2=80=9Cvalid route=E2=80=9D not be =
qualified by =E2=80=9Cto a specific address=E2=80=9D?=E2=80=9D
>=20
>         Which was not addressed.
>=20
>         I also made a comment on "Unreachable Address=E2=80=9D - I am =
glad I did, because I apparently
>         had a different understanding than what was intended. I now =
see that an Unreachable Address
>         by definition is an address listed in a RERR message, and not =
the same as an address to
>         which no route has yet  been discovered? If yes, then please =
use a different term, such as
>         =E2=80=9CFormerlyReachableAddress=E2=80=9D or something of the =
sort?
>=20
> Applicability statement
>=20
>         First, I would like to recognize the efforts made to improve =
this since last review. Thanks
>=20
>         Second, the document states:
>=20
>                 "AODVv2 supports routers with multiple interfaces, as =
long as each
>                    interface configured for AODVv2 has a unicast IP =
address.  A router
>                    may use the same IP address on multiple interfaces. =
 Address
>                    assignment procedures are out of scope for =
AODVv2.=E2=80=9D
>=20
>         Is that true? Granted, I have not worked this through in =
detail, but I can present a counter-example:
>         the use of RFC6621 means that there certainly are some =
constraints that must be respected least
>         various flooding optimizations may not work.
>=20
>         Secondly, if the multiple-interfaces-with-same-address are on =
the same L2, and this is what I
>         have not worked through, are there any situations that will =
not work?
>=20
>         The immediately previous version of this specification read:
>=20
>                 "AODVv2 supports routers with multiple interfaces, as =
long as each
>                    interface configured for AODVv2 has its own unicast =
routable IP address"
>=20
>         So what changed that means that each interface no longer needs =
its *own* unicast address?
>=20
>         I pointed out to the Applicability Statement:
>=20
>                 I think that appendix B needs to be removed. =
Essentially, it makes claims that it is
>                 possible to do multi-homing =E2=80=94 but neither =
specifies how it is done, nor gives
>                 pointers to documents that justify the claim.
>=20
>                 AODVv2 does not support multi-homing =E2=80=94 =
that=E2=80=99s clear, and it is fine that it is
>                 called out here. Thank you for that.
>=20
>                 Now, with that being said, I am torn between being =
satisfied that it is called out on
>                 one hand, and wanting to have =E2=80=9Cmulti homing=E2=80=
=9D on the other hand. RFC7181 supports
>                 multi-homing, FWIW.
>=20
>                 I believe that this also would merit some explicit =
discussion by the WG, in order to
>                 understand if this design decision is acceptable?
>=20
>         I see that Appendix B still is in the document, and I do not =
recall having seen this discussed
>         on the mailing list. Simply removing the reference from the =
Applicability Statement to Appendix B
>         does not address the issue that I raised in my previous =
review.
>=20
> To 4.1, I made the following comment:
>=20
>         "Is this a should, or a SHOULD? If the latter, should it be a =
MUST?
>=20
>           In general, there are a lot of such =E2=80=9Cmaybe normative =
language=E2=80=9D through the
>          document, and I would much like to see an editorial pass =E2=80=
=94 essentially all
>          may/should/ must and friends carefully evaluated as if they =
should become
>          2119-terms, and ... more importantly (it has been called out =
before, fwiw)
>          quite a bit of should/SHOULD which ought to be transformed =
into MUST.
>=20
>         Generally, aiming for a very a low number of SHOULD is a good =
design metric for a document=E2=80=9D
>=20
> Aside from the general comment on 2119-language, why is this a SHOULD?
>=20
> To 4.2, I made the following comment:
>=20
>         As indicated earlier, I believe that the term =E2=80=9CRouter =
Client=E2=80=9D is ill chosen.
>         I believe that it is more appropriately an =E2=80=9CAttached =
Network Set=E2=80=9D since =E2=80=94
>         as indicated previously =E2=80=94 the term =E2=80=9CRouter =
Client=E2=80=9D is ambiguous. I am pleased
>         to see, though, that this =E2=80=9CRouter Client List=E2=80=9D =
in reality is an =E2=80=9CAttached Network Set=E2=80=9D
>         and so that change should be (relatively) easy.
>=20
> The above comment still is applicable to this revision,
>=20
> To 4.2, I made the following comment:
>=20
>         Also, I recommend to not say =E2=80=9Csubnet=E2=80=9D =E2=80=94 =
how about rephrasing to =E2=80=9CIf a prefix
>         is included in the attached network set of an AODVv2 router, =
then that AODVv2
>         router MUST provide connectivity for, i.e. answer to RREQs and =
maintain
>         sequence numbers for, all addresses from within that =
prefix.=E2=80=9D
>=20
> I note that while the term has been removed from section 4, there=E2=80=99=
re 4 lingering instances of this term in the document, that could easily =
be removed.
>=20
> I Also made a comment about Appendix B in my previous review, which is =
referenced here. That comment still applies.
>=20
> To Section 4.3, I noticed:
>=20
>         Does section 6.2 describe how to monitor an established =
adjacency
>         only, or how to discover neighbouring AODVv2 routers? Looking =
in 6.2, I see
>=20
>                 =E2=80=9CNot every pair of neighboring routers will =
necessarily form an adjacency,=E2=80=9D =E2=80=94
>                  so it likely isn=E2=80=99t 6.2 that tells me how to =
maintain this table?
>=20
>         In short, =E2=80=9CA neighbour table MUST be maintained=E2=80=9D=
 =E2=80=94 where can I find information on how to do this?
>=20
>         Section 6.2 states:
>=20
>                 =E2=80=9CThe default approach for monitoring =
bidirectional connectivity to the next hop toward
>                  OrigAddr is to request acknowledgement of Route Reply =
messages.=E2=80=9D
>=20
>                 That certainly will tell me if a link over which an =
RREP is sent is bi-directional,
>                 but will not maintain a =E2=80=9Cneighbor table=E2=80=9D=
.
>=20
>         So how is this done? Or, is the =E2=80=9CNeighbor Table=E2=80=9D=
 not supposed to contain the
>         complete set of neighbours? What information =E2=80=9C...MUST =
be maintained=E2=80=9D then, in this table?
>=20
>         This is very unclear, I would not know how to implement a =
mechanism that populates this
>         =E2=80=9CNeighbor Table=E2=80=9D with the needed information =
here.
>=20
> I see no (relevant) changes to 6.2 nor to 4.3 so I assume that this =
comment has not been addressed
>=20
> I am throwing this in here, as I am sure that I commented on that in =
the previous review, but I do not see that addressed: is Appendix C =
normative, or not? It represents =E2=80=9C a second specification of the =
protocol, in a different language=E2=80=9D from the main part of the =
specification. I have not walked through and made 200% sure that both =
are perfectly aligned and that there are no ambiguities, but having two =
different specifications of a protocol is a recipe for disaster.  Please =
either make 2000% sure that they are specifying the same thing without =
ambiguities, or remove one.
>=20
> To section 4.4, I wrote:
>=20
>         "would like to nit-pick that: the router can maintain this =
sequence number in whatever
>          format it pleases =E2=80=94 but, when it includes it in =
control messages, it must be
>          representable in a specified format, respecting certain =
rules.=E2=80=9D
>=20
> I see that there were no changes following this comment.
>=20
> To section 4.4 I asked for clarification as to if sequence numbers =
were per interface or per router, as the specification was unclear on =
that. The words has changed, but it still is unclear: how many sequence =
numbers does a router maintain? One? One per interface?
>=20
> In my previous review, I expressed that it would be preferential to =
use =E2=80=9Ca notation of Sets=E2=80=9D rather than tables. I see that =
this has not changed.
>=20
> I made a comment on node and address, let me pick this up again. The =
following:
>=20
>         RteMsg.OrigAddr
>               An IP address of the node which requires the route, =
i.e., the
>               source address of the IP packet triggering the route =
request.
>=20
> would be more compact and clear if getting rid of the term =E2=80=9Cnode=
=E2=80=9D and said:
>=20
> RteMsg.OrigAddr
>         The source address of the IP packet triggering the route =
request.
>=20
>=20
> To section 4.6, and I (and others) have commented on this before:
>=20
>    All AODVv2 routers MUST maintain a route table.  The route table
>    entry is a conceptual data structure.  Implementations MAY use any
>    internal representation but MUST contain the following information:
>=20
> In order to avoid confusion, rename this to =E2=80=9CRouting =
Information Base=E2=80=9D or =E2=80=9CRouting Set=E2=80=9D =E2=80=94 a =
Routing Table is an operating system construct, whereon operations =
directly influence packet forwarding. What you are defining here is a =
RIB/an RS.
>=20
> The confusion that I pointed out in my previous review on =E2=80=9CIP =
address=E2=80=9D and =E2=80=9CAddress=E2=80=9D being used a bit =
haphazardly persists, fwiw. It makes me think, can a router send an RREQ =
for a prefix?
>=20
> I also called this out in my previous review as incorrect, and despite =
wordsmithing it still is:
>=20
>         Route.NextHop
>               The source IP address of the message advertising the =
route to
>               Route.Address, i.e. an IP address of the AODVv2 router =
used for
>               the next hop on the path toward Route.Address.
>=20
> If that =E2=80=9Cmessage=E2=80=9D is an RFC5444 entity, then it does =
to have a =E2=80=9Csource IP Address=E2=80=9D =E2=80=94 the =
encapsulating IP datagram containing the packet containing the message =
does. And the message MAY have an Originator Address
>=20
>=20
> As I indicated, I am walking through my previous review and retaining =
those comments that I still think need attention =E2=80=94 and this is =
=E2=80=9Ccrossing off from part 1 of my previous review=E2=80=9D only. =
More to follow.
>=20
> Thomas
>=20
> _______________________________________________
> manet mailing list
> manet@ietf.org <mailto:manet@ietf.org>
> https://www.ietf.org/mailman/listinfo/manet =
<https://www.ietf.org/mailman/listinfo/manet>
>=20


--Apple-Mail=_ABC69C7A-63FD-4886-ADE1-DE7AE81ED1C2
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D"">Dear Victoria,<div class=3D""><br class=3D""><div><blockquote =
type=3D"cite" class=3D""><div class=3D"">On Dec 2, 2015, at 15:24, =
Victoria Mercieca &lt;<a href=3D"mailto:vmercieca0@gmail.com" =
class=3D"">vmercieca0@gmail.com</a>&gt; wrote:</div><br =
class=3D"Apple-interchange-newline"><div class=3D""><div dir=3D"ltr" =
class=3D""><div class=3D""><div class=3D""><div class=3D""><div =
class=3D"">Hello Thomas,<br class=3D""><br class=3D""></div>Thank you =
again for your time spent reviewing AODVv2. I apologise that we did not =
give a "point by point" response to your comments on draft 11 - I felt =
that since most of the comments were around a few major topics, it made =
sense to address the topic across the whole draft, rather than respond =
to every single comment in order. I did also try to start a discussion =
on the MANET list based on your comments from draft 11, but did not see =
any responses. <br class=3D""><br =
class=3D""></div></div></div></div></div></blockquote><div><br =
class=3D""></div>I saw the mail, but it seemed more of a =E2=80=9Csummary =
of my comments=E2=80=9D, which was a fine initiative =E2=80=94 but, I =
did not really have anything to contribute beyond my initial =
review.</div><div><br class=3D""></div><div>Best,</div><div><br =
class=3D""></div><div>Thomas</div><div><br class=3D""><blockquote =
type=3D"cite" class=3D""><div class=3D""><div dir=3D"ltr" class=3D""><div =
class=3D""><div class=3D"">Thank you again, we will discuss and intend =
to respond soon.</div></div></div></div></blockquote><blockquote =
type=3D"cite" class=3D""><div class=3D""><div dir=3D"ltr" class=3D""><div =
class=3D""><div class=3D""><br class=3D""></div>Kind regards,<br =
class=3D""></div>Victoria.<br class=3D""><div class=3D""><div =
class=3D""><br class=3D""><br class=3D""></div></div></div><div =
class=3D"gmail_extra"><br class=3D""><div class=3D"gmail_quote">On Tue, =
Dec 1, 2015 at 7:21 PM,  <span dir=3D"ltr" class=3D"">&lt;<a =
href=3D"mailto:ietf@thomasclausen.org" target=3D"_blank" =
class=3D"">ietf@thomasclausen.org</a>&gt;</span> wrote:<br =
class=3D""><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 =
.8ex;border-left:1px #ccc solid;padding-left:1ex">All,<br class=3D"">
<br class=3D"">
I am working through the revised I-D to see what comments that I made =
previously have been addressed, and which still do apply.<br class=3D"">
<br class=3D"">
As I sent my original review piecemeal, I=E2=80=99ll send my refresher =
in matching pieces (in part, in recognition that it is hard to get time =
to sit down and review the whole document in one go, and I do want to =
reply to the authors as quickly as possible)<br class=3D"">
<br class=3D"">
In doing so, I am noticing additional things (notably, but not =
exclusively, to section 7 and beyond, which I didn=E2=80=99t get through =
reviewing last time around) which needs attention. I=E2=80=99ll gather =
that in separate emails a bit later, once I=E2=80=99ve worked through =
the complete, updated spec.<br class=3D"">
<br class=3D"">
So onwards...<br class=3D"">
<br class=3D"">
Abstract:<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; I made the following comment, which still =
applies:<br class=3D"">
<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =E2=80=9CThis is =
a little over-stating the applicability: these statements may<br =
class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;be true in =
some scenarios (for example, when there are few<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;concurrent =
traffic flows, and therefore few routes to repair, and<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;therefore =
few flooding operations to contend for channel access).<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;As a =
general statement, this last sentence is incorrect=E2=80=9D=E2=80=9D<br =
class=3D"">
<br class=3D"">
Overview (and elsewhere):<br class=3D"">
<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; I made a comment previously that =E2=80=9CRout=
er client=E2=80=9D is a poorly chosen<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; term, and have proposed alternatives. I=E2=80=99=
ve seen some attempts on the list<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; at rather than change the term, explain it =
=E2=80=94 some of which is in this document.<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; The =E2=80=9COverview=E2=80=9D still talks =
about =E2=80=9Ca router=E2=80=A6one of its clients=E2=80=9D - which is =
no less<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; confusing than last time Iw went through =
it.<br class=3D"">
<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; I reiterate, why not use =E2=80=9CLocal =
Attached Network Set=E2=80=9D, which is the term used<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; by other documents from this WG?<br =
class=3D"">
<br class=3D"">
Overview:<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; The term =E2=80=9Cconfirming adjacency=E2=80=9D=
 is gone, and is now replaced by<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; =E2=80=9Cconfirming bidirectionality=E2=80=9D =
- which, alas, still sounds like there is some active<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; monitoring (HELLO message exchange) going =
on. Unless that is the case,<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; then please be more specific here.<br =
class=3D"">
<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; I note that the term adjacency is used =
through and through the document, btw.<br class=3D"">
<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; I suggested in my last review:<br class=3D"">
<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; The overview =
must also include a paragraph on the intersections<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; between this =
protocol and the forwarding plane =E2=80=94 this, as it is<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; different (and =
more invasive) from that which is typically seen in<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; routing =
protocols.<br class=3D"">
<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Specifically, as =
a reactive protocol, it is required (at least) that the<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; forwarding plane =
is modified :<br class=3D"">
<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 1) A =E2=80=9Cmiss=
=E2=80=9D when looking up a next hop for a data packet to be<br =
class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;forwarded, is signalled to the AODVv2 process so as to permit<br =
class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; that =
route discovery be launched;<br class=3D"">
<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2) A =E2=80=9Cmiss=
=E2=80=9D when attempting to deliver a data packet to a next hop,<br =
class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;which was recorded in the routing table, is signalled to the =
AODVv2<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;process so as to permit that a route repair be initiated and/or a =
Route<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;Error be generated.<br class=3D"">
<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 3) A =E2=80=9Chit=E2=
=80=9D when looking up a next hop for a data packet to be forwarded<br =
class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; to =
a destination is signalled to the AODVv2 process so as to permit<br =
class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
maintenance of =E2=80=9Cactive route=E2=80=9D Route State, timers and =
such.<br class=3D"">
<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Note that these =
things are necessary to call out in the =E2=80=9Coverview=E2=80=9D and =
in<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; the =
=E2=80=9Capplicability statement=E2=80=9D, both: it is not that they are =
negatives per se,<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; but that they =
are important factors governing the applicability of this protocol:<br =
class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; will a given =
platform permit such access to the forwarding plane, for example?<br =
class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Important to =
understand if for that platform this protocol is apple<br class=3D"">
<br class=3D"">
<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; I see that this was not addressed in the =
overview, nor in the applicability other than<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; by a forward reference to section 6.4. While =
it is positive that there is a section 6.4,<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; this does not exonerate the overview and the =
applicability statement for being<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; honest about the requirements (notably to =
the platform/os) that this protocol has<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; for being applicable<br class=3D"">
<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; I suggested in my last review:<br class=3D"">
<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =E2=80=9CIt is =
important to do more than this: 7182 does only provide =
=E2=80=9Ccontainers=E2=80=9D<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;for ICVs =
and timestamps, and does not specify how to use them to obtain<br =
class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;specific =
security properties. RFC7182 may be a tool that can be used, but<br =
class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;*how* that =
tool is used is what determines the security properties.<br class=3D"">
<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Therefore, =
saying that =E2=80=9Csecurity is dealt with by using RFC7182=E2=80=9D is =
either an<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; incomplete =
statement, or is indicative of insufficient security =
considerations.=E2=80=9D<br class=3D"">
<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; The actual sentence in the I-D has been =
changed, now it explicitly names the<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; two TLVs from 7182 that it uses. That is, =
alas, still not sufficient.<br class=3D"">
<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; Making the aside that was discussed recently =
on the list, that (i) control messages<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; are not forwarded, and that (ii) they are =
modified in transit, the security/trust model<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; is somewhat different from that of 7181 and =
consequently for what 7182 was initially<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; written for. I think that&nbsp; calling out =
the trust model, and how 7182 actually is used here,<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; might be what is called for.<br class=3D"">
<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; Continuing with the aside, this *especially* =
as the applicability statement says:<br class=3D"">
<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; "Providing =
security for a reactive routing protocol can be difficult=E2=80=9D<br =
class=3D"">
<br class=3D"">
<br class=3D"">
Terminology:<br class=3D"">
<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; My last review suggested:<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =E2=80=9CThis =
has been brought up on the list several times in the past, without =
having<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;been =
addressed.<br class=3D"">
<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; There are =
=E2=80=9Chosts=E2=80=9D and there are =E2=80=9Crouters=E2=80=9D =E2=80=94 =
whose roles are well defined.<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =E2=80=9CNode=E2=80=
=9D not so much =E2=80=94 which is clear from looking at the definition =
here: =E2=80=9Ceither<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; AODVv2 routers =
or router clients=E2=80=9D (with =E2=80=9Crouter clients=E2=80=9D being =
defined as =E2=80=9Can<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; AODVv2 router is =
also its own router client=E2=80=9D).<br class=3D"">
<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; This is very =
much related to the use of =E2=80=9CRouter Client=E2=80=9D, and both =
that term,<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; and =E2=80=9Cnode=E2=
=80=9D indicative that some clarity is needed here.<br class=3D"">
<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; All a router =
cares about is =E2=80=9Can address=E2=80=9D. If that address is of a =
network, or<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; a router, or an =
interface (and, if said interface is installed in a router or a host)<br =
class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; doesn=E2=80=99t =
matter.<br class=3D"">
<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; So, =E2=80=9Can =
address=E2=80=9D is something that the routing protocol should care =
about<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; finding paths =
to. Which means that each address that should be made<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; reachable by the =
routing protocol should be advertised by (at least) one router<br =
class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; in the =
network.<br class=3D"">
<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; One way of doing =
that would be to simply talk about =E2=80=9CAttached Networks=E2=80=9D =
as<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; is done in =
RFC7181, wherein an address included in the =E2=80=9CAttached Network =
Set=E2=80=9D<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; is advertised by =
an OLSRv2 router....in this case, the equivalent would be =E2=80=9Cfor =
each<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; address in the =
Attached Network Set of an AODVv2 router the router MUST<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; respond =
authoritatively to a RREQ, and MUST maintain the corresponding sequence =
number=E2=80=9D.<br class=3D"">
<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; The text, as it =
currently is, is really hard to read, and a re-edit along these lines =
would go a long way.=E2=80=9D<br class=3D"">
<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; I note that the terms =E2=80=9CNode=E2=80=9D =
and =E2=80=9CRouter Client=E2=80=9D are still used, in their original =
form,<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; and that other than some slight wordsmithing =
this comment has not been addressed in the document.<br class=3D"">
<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; I reiterate that the need to use router, =
host, node, and router client in and by itself should<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; be an indicator that tightening up of =
terminology is required.<br class=3D"">
<br class=3D"">
<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; I made the following comment to Routable =
Unicast IP Address:<br class=3D"">
<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =E2=80=9CAre =
there any technical reason why not simply *any* address could be<br =
class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;considered =
by the routing protocol?<br class=3D"">
<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;My =
understanding, but correct me if I am wrong, is that all that is =
required is<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;that all =
interfaces in a given AODVv2 routing domain has an unique address.<br =
class=3D"">
<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;That some =
of these addresses (by an IP addressing architecture document)<br =
class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;has =
special semantics associated (such as are link locals, or are for =
private<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;use, or =
are for example use only, or are for multicast) is out of scope here?<br =
class=3D"">
<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; I see nothing has changed on the above, so =
let me be more explicit: the routing protocol itself<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; (probably) should not care about what kind =
of addresses are filled into it. Is an 192.16./16 address<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; appropriate? Not across the internet, but it =
may be in somebody=E2=80=99s private deployments. Should<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; the routing protocol be =E2=80=9Caddress =
police=E2=80=9D and is implementation of a =E2=80=9CI refuse to route =
these addresses=E2=80=A6=E2=80=9D<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; a requirement for claiming conformance? =
Suggest simply stating what the requirements are under<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; which the routing protocol will work =E2=80=94=
 and leave =E2=80=9Caddress assignment politics=E2=80=9D aside.<br =
class=3D"">
<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; I also continued:<br class=3D"">
<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Now, with =
that being said also, the WG wanted that RFC7181 supports not<br =
class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;just =
multiple interfaces, but also the same address used on multiple =
interfaces<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;of the =
same router. There were good reasons for that, and while it was not =
trivial<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;to =
implement, it turned out to be the right thing to support. If there are =
technical<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;reasons =
why this is not supported in AODVv2 (for example, if this cannot be<br =
class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;made work =
because of &lt;reason&gt;) then that should be called out in the<br =
class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;applicability statement also?<br class=3D"">
<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Conversely, if =
it is possible in AODVv2, then I do not believe that it is clearly<br =
class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; specified how =
(at least, in the =E2=80=9Cnaive=E2=80=9D on paper examples I drew up, =
something<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; ended up not =
working). So either the protocol as-is does not support it (but<br =
class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; could be made =
to?) or it is supported (but just need to be spelled out), or is<br =
class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; not possible =
(and need to be disclaimed in the applicability statement).<br class=3D"">=

<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Stan Ratliff was =
a driving force in holding the WG=E2=80=99s collective feet to the =
fire<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; in getting this =
support included in RFC7181, and would likely be the right<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; person to =
consult on this matter?<br class=3D"">
<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; I actually have not seen changes, or =
comments, on this. In OLSRv2, the WG was making it<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; a strong requirement that it should be =
possible to use the same IP address on different<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; interfaces of a router. It was somewhat =
tedious to design around, but it was worked out, and<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; the conditions under which that was possible =
were defined and documented.<br class=3D"">
<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; I would like to see the same done for this =
protocol.<br class=3D"">
<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; I also note that this is not unrelated to =
RFC6621-discussions. For example, when selecting<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; S-MPRs on a multi-interface and =
multi-address-per-interface router, care must be taken<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; least things won=E2=80=99t work. So, if (and =
this links back to previous mails) RFC6621 is a<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; requirement or desire for this protocol, =
then there are some considerations required here.<br class=3D"">
<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; I see that the definition of =E2=80=9CRouter =
Client=E2=80=9D has changed to be<br class=3D"">
<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =E2=80=9CAn =
address or address range=E2=80=A6the AODVv2 router=E2=80=99s interface =
addresses<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;are also =
configured as router clients=E2=80=9D<br class=3D"">
<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; Better than before, but still missing the =
target. The term =E2=80=9CRouter Client=E2=80=9D is, as I indicated<br =
class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; numerous times before, odd.<br class=3D"">
<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; But the second part of the sentence, does =
that mean (what it says) that the interfaces<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; must be configured specially, so as to be =
able to be =E2=80=9Crouter clients=E2=80=9D? That can=E2=80=99t be =
true.<br class=3D"">
<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; What you likely mean is:<br class=3D"">
<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =E2=80=9CAn =
AODVv2 router is configured so as to consider its own interfaces as part =
of<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;the =
locally attached network set=E2=80=9D ?<br class=3D"">
<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; You configure the router, right? No special =
=E2=80=9Cinterface configuration properties=E2=80=9D are required<br =
class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; for an interface to be announcable by&nbsp; =
an AODVv2 router?<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; (And, getting rid of node would actually =
make the definition shorter and nicer)<br class=3D"">
<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; Now, snipping out from the applicability =
statement:<br class=3D"">
<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; "Multi-homing of =
an IP address is not supported by AODVv2, and therefore a<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Router =
Client, i.e. an IP Address,&nbsp; =E2=80=A6 "<br class=3D"">
<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; =E2=80=A6evidence to there being some =
redundant terminology here to weed away.<br class=3D"">
<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; The below is a little bit of a meta-comment, =
I am not quite sure what I think here.<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; The definitions for Target Node and such =
were confusing before. They still are, somewhat.<br class=3D"">
<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; I think that it may be because the =
definitions now used are simply copy-pasted out from the<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; tables in the previous version, for =
example:<br class=3D"">
<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; An AODVv2 Data =
Element containing the destination address of the<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; IP packet =
triggering route discovery.<br class=3D"">
<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; OK, I can trace back and see that a Data =
Element is something that exists inside a<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; protocol message. To me, however, that=E2=80=99=
s not really general terminology as such, but<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; part of the specification of a packet format =
- or rather, it is the notation that you use<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; when describing an algorithm. By the way, =
why are some notations in CamelCase<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; whereas others have a space in them, e.g. =
=E2=80=9CTarget Node=E2=80=9D and =E2=80=9CTargMetric=E2=80=9D, both of =
which<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; are Data Elements? Would be good with a =
consistent approach here.<br class=3D"">
<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; I *think* that it would be better to take =
all those =E2=80=9CData Element=E2=80=9D bits and move to a separate<br =
class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; section (or subsection) to the terminology, =
and then keep all the =E2=80=9Cother stuff=E2=80=9D (Neighbor, =E2=80=A6)<=
br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; in its own section.<br class=3D"">
<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; I=E2=80=99m a great fan of calling this =
section =E2=80=9CTerminology and Notation=E2=80=9D and then having =
two<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; subsections, one which is =E2=80=9CTerminology=
=E2=80=9D and one which is =E2=80=9CNotation=E2=80=9D, with the<br =
class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; TargMetric and Target Node being firmly in =
the latter.<br class=3D"">
<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; I made a comment:<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; "Second, should =
=E2=80=9Cvalid route=E2=80=9D not be qualified by =E2=80=9Cto a specific =
address=E2=80=9D?=E2=80=9D<br class=3D"">
<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; Which was not addressed.<br class=3D"">
<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; I also made a comment on "Unreachable =
Address=E2=80=9D - I am glad I did, because I apparently<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; had a different understanding than what was =
intended. I now see that an Unreachable Address<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; by definition is an address listed in a RERR =
message, and not the same as an address to<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; which no route has yet&nbsp; been =
discovered? If yes, then please use a different term, such as<br =
class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; =E2=80=9CFormerlyReachableAddress=E2=80=9D =
or something of the sort?<br class=3D"">
<br class=3D"">
Applicability statement<br class=3D"">
<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; First, I would like to recognize the efforts =
made to improve this since last review. Thanks<br class=3D"">
<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; Second, the document states:<br class=3D"">
<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; "AODVv2 supports =
routers with multiple interfaces, as long as each<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;interface configured for AODVv2 has a unicast IP address.&nbsp; A =
router<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;may =
use the same IP address on multiple interfaces.&nbsp; Address<br =
class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;assignment procedures are out of scope for AODVv2.=E2=80=9D<br =
class=3D"">
<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; Is that true? Granted, I have not worked =
this through in detail, but I can present a counter-example:<br =
class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; the use of RFC6621 means that there =
certainly are some constraints that must be respected least<br class=3D"">=

&nbsp; &nbsp; &nbsp; &nbsp; various flooding optimizations may not =
work.<br class=3D"">
<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; Secondly, if the =
multiple-interfaces-with-same-address are on the same L2, and this is =
what I<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; have not worked through, are there any =
situations that will not work?<br class=3D"">
<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; The immediately previous version of this =
specification read:<br class=3D"">
<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; "AODVv2 supports =
routers with multiple interfaces, as long as each<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;interface configured for AODVv2 has its own unicast routable IP =
address"<br class=3D"">
<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; So what changed that means that each =
interface no longer needs its *own* unicast address?<br class=3D"">
<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; I pointed out to the Applicability =
Statement:<br class=3D"">
<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; I think that =
appendix B needs to be removed. Essentially, it makes claims that it =
is<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; possible to do =
multi-homing =E2=80=94 but neither specifies how it is done, nor =
gives<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; pointers to =
documents that justify the claim.<br class=3D"">
<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; AODVv2 does not =
support multi-homing =E2=80=94 that=E2=80=99s clear, and it is fine that =
it is<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; called out here. =
Thank you for that.<br class=3D"">
<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Now, with that =
being said, I am torn between being satisfied that it is called out =
on<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; one hand, and =
wanting to have =E2=80=9Cmulti homing=E2=80=9D on the other hand. =
RFC7181 supports<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; multi-homing, =
FWIW.<br class=3D"">
<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; I believe that =
this also would merit some explicit discussion by the WG, in order to<br =
class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; understand if =
this design decision is acceptable?<br class=3D"">
<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; I see that Appendix B still is in the =
document, and I do not recall having seen this discussed<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; on the mailing list. Simply removing the =
reference from the Applicability Statement to Appendix B<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; does not address the issue that I raised in =
my previous review.<br class=3D"">
<br class=3D"">
To 4.1, I made the following comment:<br class=3D"">
<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; "Is this a should, or a SHOULD? If the =
latter, should it be a MUST?<br class=3D"">
<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; In general, there are a lot of such =
=E2=80=9Cmaybe normative language=E2=80=9D through the<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;document, and I would much like to see =
an editorial pass =E2=80=94 essentially all<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;may/should/ must and friends carefully =
evaluated as if they should become<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;2119-terms, and ... more importantly =
(it has been called out before, fwiw)<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;quite a bit of should/SHOULD which =
ought to be transformed into MUST.<br class=3D"">
<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; Generally, aiming for a very a low number of =
SHOULD is a good design metric for a document=E2=80=9D<br class=3D"">
<br class=3D"">
Aside from the general comment on 2119-language, why is this a =
SHOULD?<br class=3D"">
<br class=3D"">
To 4.2, I made the following comment:<br class=3D"">
<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; As indicated earlier, I believe that the =
term =E2=80=9CRouter Client=E2=80=9D is ill chosen.<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; I believe that it is more appropriately an =
=E2=80=9CAttached Network Set=E2=80=9D since =E2=80=94<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; as indicated previously =E2=80=94 the term =
=E2=80=9CRouter Client=E2=80=9D is ambiguous. I am pleased<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; to see, though, that this =E2=80=9CRouter =
Client List=E2=80=9D in reality is an =E2=80=9CAttached Network =
Set=E2=80=9D<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; and so that change should be (relatively) =
easy.<br class=3D"">
<br class=3D"">
The above comment still is applicable to this revision,<br class=3D"">
<br class=3D"">
To 4.2, I made the following comment:<br class=3D"">
<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; Also, I recommend to not say =E2=80=9Csubnet=E2=
=80=9D =E2=80=94 how about rephrasing to =E2=80=9CIf a prefix<br =
class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; is included in the attached network set of =
an AODVv2 router, then that AODVv2<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; router MUST provide connectivity for, i.e. =
answer to RREQs and maintain<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; sequence numbers for, all addresses from =
within that prefix.=E2=80=9D<br class=3D"">
<br class=3D"">
I note that while the term has been removed from section 4, there=E2=80=99=
re 4 lingering instances of this term in the document, that could easily =
be removed.<br class=3D"">
<br class=3D"">
I Also made a comment about Appendix B in my previous review, which is =
referenced here. That comment still applies.<br class=3D"">
<br class=3D"">
To Section 4.3, I noticed:<br class=3D"">
<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; Does section 6.2 describe how to monitor an =
established adjacency<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; only, or how to discover neighbouring AODVv2 =
routers? Looking in 6.2, I see<br class=3D"">
<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =E2=80=9CNot =
every pair of neighboring routers will necessarily form an adjacency,=E2=80=
=9D =E2=80=94<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;so it =
likely isn=E2=80=99t 6.2 that tells me how to maintain this table?<br =
class=3D"">
<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; In short, =E2=80=9CA neighbour table MUST be =
maintained=E2=80=9D =E2=80=94 where can I find information on how to do =
this?<br class=3D"">
<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; Section 6.2 states:<br class=3D"">
<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =E2=80=9CThe =
default approach for monitoring bidirectional connectivity to the next =
hop toward<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;OrigAddr =
is to request acknowledgement of Route Reply messages.=E2=80=9D<br =
class=3D"">
<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; That certainly =
will tell me if a link over which an RREP is sent is bi-directional,<br =
class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; but will not =
maintain a =E2=80=9Cneighbor table=E2=80=9D.<br class=3D"">
<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; So how is this done? Or, is the =E2=80=9CNeigh=
bor Table=E2=80=9D not supposed to contain the<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; complete set of neighbours? What information =
=E2=80=9C...MUST be maintained=E2=80=9D then, in this table?<br =
class=3D"">
<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; This is very unclear, I would not know how =
to implement a mechanism that populates this<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; =E2=80=9CNeighbor Table=E2=80=9D with the =
needed information here.<br class=3D"">
<br class=3D"">
I see no (relevant) changes to 6.2 nor to 4.3 so I assume that this =
comment has not been addressed<br class=3D"">
<br class=3D"">
I am throwing this in here, as I am sure that I commented on that in the =
previous review, but I do not see that addressed: is Appendix C =
normative, or not? It represents =E2=80=9C a second specification of the =
protocol, in a different language=E2=80=9D from the main part of the =
specification. I have not walked through and made 200% sure that both =
are perfectly aligned and that there are no ambiguities, but having two =
different specifications of a protocol is a recipe for disaster.&nbsp; =
Please either make 2000% sure that they are specifying the same thing =
without ambiguities, or remove one.<br class=3D"">
<br class=3D"">
To section 4.4, I wrote:<br class=3D"">
<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; "would like to nit-pick that: the router can =
maintain this sequence number in whatever<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;format it pleases =E2=80=94 but, when =
it includes it in control messages, it must be<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;representable in a specified format, =
respecting certain rules.=E2=80=9D<br class=3D"">
<br class=3D"">
I see that there were no changes following this comment.<br class=3D"">
<br class=3D"">
To section 4.4 I asked for clarification as to if sequence numbers were =
per interface or per router, as the specification was unclear on that. =
The words has changed, but it still is unclear: how many sequence =
numbers does a router maintain? One? One per interface?<br class=3D"">
<br class=3D"">
In my previous review, I expressed that it would be preferential to use =
=E2=80=9Ca notation of Sets=E2=80=9D rather than tables. I see that this =
has not changed.<br class=3D"">
<br class=3D"">
I made a comment on node and address, let me pick this up again. The =
following:<br class=3D"">
<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; RteMsg.OrigAddr<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; An IP address of the =
node which requires the route, i.e., the<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; source address of the =
IP packet triggering the route request.<br class=3D"">
<br class=3D"">
would be more compact and clear if getting rid of the term =E2=80=9Cnode=E2=
=80=9D and said:<br class=3D"">
<br class=3D"">
RteMsg.OrigAddr<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; The source address of the IP packet =
triggering the route request.<br class=3D"">
<br class=3D"">
<br class=3D"">
To section 4.6, and I (and others) have commented on this before:<br =
class=3D"">
<br class=3D"">
&nbsp; &nbsp;All AODVv2 routers MUST maintain a route table.&nbsp; The =
route table<br class=3D"">
&nbsp; &nbsp;entry is a conceptual data structure.&nbsp; Implementations =
MAY use any<br class=3D"">
&nbsp; &nbsp;internal representation but MUST contain the following =
information:<br class=3D"">
<br class=3D"">
In order to avoid confusion, rename this to =E2=80=9CRouting Information =
Base=E2=80=9D or =E2=80=9CRouting Set=E2=80=9D =E2=80=94 a Routing Table =
is an operating system construct, whereon operations directly influence =
packet forwarding. What you are defining here is a RIB/an RS.<br =
class=3D"">
<br class=3D"">
The confusion that I pointed out in my previous review on =E2=80=9CIP =
address=E2=80=9D and =E2=80=9CAddress=E2=80=9D being used a bit =
haphazardly persists, fwiw. It makes me think, can a router send an RREQ =
for a prefix?<br class=3D"">
<br class=3D"">
I also called this out in my previous review as incorrect, and despite =
wordsmithing it still is:<br class=3D"">
<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; Route.NextHop<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; The source IP address =
of the message advertising the route to<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Route.Address, i.e. an =
IP address of the AODVv2 router used for<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; the next hop on the =
path toward Route.Address.<br class=3D"">
<br class=3D"">
If that =E2=80=9Cmessage=E2=80=9D is an RFC5444 entity, then it does to =
have a =E2=80=9Csource IP Address=E2=80=9D =E2=80=94 the encapsulating =
IP datagram containing the packet containing the message does. And the =
message MAY have an Originator Address<br class=3D"">
<br class=3D"">
<br class=3D"">
As I indicated, I am walking through my previous review and retaining =
those comments that I still think need attention =E2=80=94 and this is =
=E2=80=9Ccrossing off from part 1 of my previous review=E2=80=9D only. =
More to follow.<br class=3D"">
<br class=3D"">
Thomas<br class=3D"">
<br class=3D"">
_______________________________________________<br class=3D"">
manet mailing list<br class=3D"">
<a href=3D"mailto:manet@ietf.org" class=3D"">manet@ietf.org</a><br =
class=3D"">
<a href=3D"https://www.ietf.org/mailman/listinfo/manet" rel=3D"noreferrer"=
 target=3D"_blank" =
class=3D"">https://www.ietf.org/mailman/listinfo/manet</a><br class=3D"">
</blockquote></div><br class=3D""></div>
</div></blockquote></div><br class=3D""></div></body></html>=

--Apple-Mail=_ABC69C7A-63FD-4886-ADE1-DE7AE81ED1C2--


From nobody Thu Dec  3 08:18:12 2015
Return-Path: <chris.dearlove@baesystems.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 16B571A9094 for <manet@ietfa.amsl.com>; Thu,  3 Dec 2015 08:18:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.102
X-Spam-Level: 
X-Spam-Status: No, score=-4.102 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RDNS_NONE=0.793] 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 2T7Xxs9GKF1t for <manet@ietfa.amsl.com>; Thu,  3 Dec 2015 08:18:08 -0800 (PST)
Received: from ukmta1.baesystems.com (unknown [20.133.0.55]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5B1901A9031 for <manet@ietf.org>; Thu,  3 Dec 2015 08:18:08 -0800 (PST)
X-IronPort-AV: E=Sophos; i="5.20,378,1444690800"; d="scan'208,217"; a="31869540"
Received: from unknown (HELO baemasmds017.greenlnk.net) ([10.15.207.104]) by ukmta1.baesystems.com with ESMTP; 03 Dec 2015 16:18:06 +0000
X-IronPort-AV: E=Sophos;i="5.20,378,1444690800";  d="scan'208,217";a="122783877"
Received: from glkxh0001v.greenlnk.net ([10.109.2.32]) by baemasmds017.greenlnk.net with ESMTP; 03 Dec 2015 16:18:06 +0000
Received: from GLKXM0002V.GREENLNK.net ([169.254.5.2]) by GLKXH0001V.GREENLNK.net ([10.109.2.32]) with mapi id 14.03.0248.002; Thu, 3 Dec 2015 16:18:06 +0000
From: "Dearlove, Christopher (UK)" <chris.dearlove@baesystems.com>
To: "manet@ietf.org" <manet@ietf.org>
Thread-Topic: DLEP-17 comments, part 3
Thread-Index: AdEt5S6kvYFfEAo4TCyYiw0ItRsEwQ==
Date: Thu, 3 Dec 2015 16:18:06 +0000
Message-ID: <B31EEDDDB8ED7E4A93FDF12A4EECD30D7D76D2A4@GLKXM0002V.GREENLNK.net>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.109.62.6]
Content-Type: multipart/alternative; boundary="_000_B31EEDDDB8ED7E4A93FDF12A4EECD30D7D76D2A4GLKXM0002VGREEN_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/MdhY1YX5APcNk3IIMKI7rCKW0Z0>
Subject: [manet] DLEP-17 comments, part 3
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: <https://mailarchive.ietf.org/arch/browse/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: Thu, 03 Dec 2015 16:18:11 -0000

--_000_B31EEDDDB8ED7E4A93FDF12A4EECD30D7D76D2A4GLKXM0002VGREEN_
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable

A quick one, just sections 6 and 7.

Section 6, first line. I wouldn't write this (WG etc.) but that's a style i=
ssue.

Section 6, first paragraph, additional rules of behaviour. Those are tricky=
. New rules because of new messages, OK. But new rules in existing situatio=
ns, that's a compatibility issue. I would suggest making it clear that's no=
t intended. (You can't actually ban it, because an update could remove the =
ban ...)

Section 6, third paragraph. Not Reserved, that has a different meaning. See=
 RFC 5226. All uses of Reserved in the document need review accordingly.

Section 7, line one. The specificity of thousands makes me want to ask for =
details.

Section 7, line 4, is this an RFC 2119 RECOMMENDED?

Section 7. This one paragraph covers two topics, which should be different =
paragraphs. The first is having lots of destinations. The second is managin=
g each destination so as to not produce excessive data. (Actually, there's =
really a third, flapping isn't a DLEP problem, it's a use by the router of =
the data problem.) Only the first of these is scalability, the second is a =
different efficiency issue.
********************************************************************
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.
********************************************************************

--_000_B31EEDDDB8ED7E4A93FDF12A4EECD30D7D76D2A4GLKXM0002VGREEN_
Content-Type: text/html; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii">
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-GB" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">A quick one, just sections 6 and 7.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Section 6, first line. I wouldn&#8217;t write this (=
WG etc.) but that&#8217;s a style issue.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Section 6, first paragraph, additional rules of beha=
viour. Those are tricky. New rules because of new messages, OK. But new rul=
es in existing situations, that&#8217;s a compatibility issue. I would sugg=
est making it clear that&#8217;s not intended.
 (You can&#8217;t actually ban it, because an update could remove the ban &=
#8230;)<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Section 6, third paragraph. Not Reserved, that has a=
 different meaning. See RFC 5226. All uses of Reserved in the document need=
 review accordingly.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Section 7, line one. The specificity of thousands ma=
kes me want to ask for details.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Section 7, line 4, is this an RFC 2119 RECOMMENDED?<=
o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Section 7. This one paragraph covers two topics, whi=
ch should be different paragraphs. The first is having lots of destinations=
. The second is managing each destination so as to not produce excessive da=
ta. (Actually, there&#8217;s really a third,
 flapping isn&#8217;t a DLEP problem, it&#8217;s a use by the router of the=
 data problem.) Only the first of these is scalability, the second is a dif=
ferent efficiency issue.<o:p></o:p></p>
</div>
<p>********************************************************************<br>
This email and any attachments are confidential to the intended<br>
recipient and may also be privileged. If you are not the intended<br>
recipient please delete it from your system and notify the sender.<br>
You should not copy it or use it for any purpose nor disclose or<br>
distribute its contents to any other person.<br>
********************************************************************</p></b=
ody>
</html>

--_000_B31EEDDDB8ED7E4A93FDF12A4EECD30D7D76D2A4GLKXM0002VGREEN_--


From nobody Thu Dec  3 08:37:41 2015
Return-Path: <chris.dearlove@baesystems.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 523FE1A9067 for <manet@ietfa.amsl.com>; Thu,  3 Dec 2015 08:37:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.102
X-Spam-Level: 
X-Spam-Status: No, score=-4.102 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RDNS_NONE=0.793] 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 vlrtl7bN98EW for <manet@ietfa.amsl.com>; Thu,  3 Dec 2015 08:37:37 -0800 (PST)
Received: from ukmta2.baesystems.com (unknown [20.133.0.56]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EAFA41A905C for <manet@ietf.org>; Thu,  3 Dec 2015 08:37:36 -0800 (PST)
X-IronPort-AV: E=Sophos; i="5.20,378,1444690800"; d="scan'208,217"; a="21695027"
Received: from unknown (HELO baemasmds017.greenlnk.net) ([10.15.207.104]) by ukmta2.baesystems.com with ESMTP; 03 Dec 2015 16:37:36 +0000
X-IronPort-AV: E=Sophos;i="5.20,378,1444690800";  d="scan'208,217";a="122787338"
Received: from glkxh0001v.greenlnk.net ([10.109.2.32]) by baemasmds017.greenlnk.net with ESMTP; 03 Dec 2015 16:37:35 +0000
Received: from GLKXM0002V.GREENLNK.net ([169.254.5.2]) by GLKXH0001V.GREENLNK.net ([10.109.2.32]) with mapi id 14.03.0248.002; Thu, 3 Dec 2015 16:37:35 +0000
From: "Dearlove, Christopher (UK)" <chris.dearlove@baesystems.com>
To: "manet@ietf.org" <manet@ietf.org>
Thread-Topic: DLEP-17 review, part 4
Thread-Index: AdEt6OcnixMPXGRpRiWusaacgRpzAA==
Date: Thu, 3 Dec 2015 16:37:34 +0000
Message-ID: <B31EEDDDB8ED7E4A93FDF12A4EECD30D7D76D2BD@GLKXM0002V.GREENLNK.net>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.109.62.6]
Content-Type: multipart/alternative; boundary="_000_B31EEDDDB8ED7E4A93FDF12A4EECD30D7D76D2BDGLKXM0002VGREEN_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/a3rYAAxmR_u8HS2CCjVNyGzZORk>
Subject: [manet] DLEP-17 review, part 4
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: <https://mailarchive.ietf.org/arch/browse/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: Thu, 03 Dec 2015 16:37:40 -0000

--_000_B31EEDDDB8ED7E4A93FDF12A4EECD30D7D76D2BDGLKXM0002VGREEN_
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable

I'm now going to be non-sequential. I will get back to sections 8 to 10, bu=
t here will consider Sections 11, 12 and references.

Section 11. The main issue is that using TLS only helps with the TCP messag=
es, it doesn't help with the UDP ones. If I read correctly, an unauthentica=
ted UDP message could send a modem off to the wrong address and port, so it=
 ignores the correct one.

The denial of service mitigation creates its own denial of service opportun=
ity. If you maintain a database of peers that fail initialisation, then cre=
ate fake traffic apparently from the real peer in order to get the real pee=
r on the blacklist.

There's no discussion of confidentiality. Yes, TLS can manage that, but tha=
t still needs to be said. And still the UDP problem. (Does confidentiality =
matter? I can think of cases it might.)

There's no discussion of key management. Again that's down to TLS (but what=
 about UDP as usual?) but probably needs saying. Are you expecting to pre-s=
hare keys or negotiate? If latter do we consider MitM as an issue?

That security is only considered for multi-hop still leaves possibilities o=
f injection of false messages (if, say, that one hop is an Ethernet bus) an=
d confidentiality. These you may think are acceptable, but need to say so.

(In short, I'm expecting this section not to pass. I may be wrong, but that=
's my guess.)

Section 12

Biggest problem here is that this is not self-contained. That's not the fir=
st time I've said that. I've had IANA unhappy with things significantly mor=
e picky than that Table 1 is off elsewhere. Again, I can only base on my ex=
perience, but I believe you need a fully self-contained section. References=
 from outside into it, OK. So tables need moving here or duplicating. And R=
eserved is misused in this section (see previous part, and I think I've sai=
d this before).

Because of this, I'm not going to attempt to review details in this section=
, that will have to be in another draft. You will need policies for adding =
new entries.

References

I think I forgot to say this in my last part, but I'm still in favour of ma=
king [CREDIT] non-normative and not coupling the fate/delay of this documen=
t to that.

You will probably need RFC 5226 once the IANA section is revised.

It's possible (see comments on part 1) that other informative references mi=
ght help.
********************************************************************
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.
********************************************************************

--_000_B31EEDDDB8ED7E4A93FDF12A4EECD30D7D76D2BDGLKXM0002VGREEN_
Content-Type: text/html; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii">
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-GB" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">I&#8217;m now going to be non-sequential. I will get=
 back to sections 8 to 10, but here will consider Sections 11, 12 and refer=
ences.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Section 11. The main issue is that using TLS only he=
lps with the TCP messages, it doesn&#8217;t help with the UDP ones. If I re=
ad correctly, an unauthenticated UDP message could send a modem off to the =
wrong address and port, so it ignores the
 correct one.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">The denial of service mitigation creates its own den=
ial of service opportunity. If you maintain a database of peers that fail i=
nitialisation, then create fake traffic apparently from the real peer in or=
der to get the real peer on the blacklist.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">There&#8217;s no discussion of confidentiality. Yes,=
 TLS can manage that, but that still needs to be said. And still the UDP pr=
oblem. (Does confidentiality matter? I can think of cases it might.)<o:p></=
o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">There&#8217;s no discussion of key management. Again=
 that&#8217;s down to TLS (but what about UDP as usual?) but probably needs=
 saying. Are you expecting to pre-share keys or negotiate? If latter do we =
consider MitM as an issue?<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">That security is only considered for multi-hop still=
 leaves possibilities of injection of false messages (if, say, that one hop=
 is an Ethernet bus) and confidentiality. These you may think are acceptabl=
e, but need to say so.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">(In short, I&#8217;m expecting this section not to p=
ass. I may be wrong, but that&#8217;s my guess.)<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Section 12<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Biggest problem here is that this is not self-contai=
ned. That&#8217;s not the first time I&#8217;ve said that. I&#8217;ve had I=
ANA unhappy with things significantly more picky than that Table 1 is off e=
lsewhere. Again, I can only base on my experience, but
 I believe you need a fully self-contained section. References from outside=
 into it, OK. So tables need moving here or duplicating. And Reserved is mi=
sused in this section (see previous part, and I think I&#8217;ve said this =
before).<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Because of this, I&#8217;m not going to attempt to r=
eview details in this section, that will have to be in another draft. You w=
ill need policies for adding new entries.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">References<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">I think I forgot to say this in my last part, but I&=
#8217;m still in favour of making [CREDIT] non-normative and not coupling t=
he fate/delay of this document to that.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">You will probably need RFC 5226 once the IANA sectio=
n is revised.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">It&#8217;s possible (see comments on part 1) that ot=
her informative references might help.<o:p></o:p></p>
</div>
<p>********************************************************************<br>
This email and any attachments are confidential to the intended<br>
recipient and may also be privileged. If you are not the intended<br>
recipient please delete it from your system and notify the sender.<br>
You should not copy it or use it for any purpose nor disclose or<br>
distribute its contents to any other person.<br>
********************************************************************</p></b=
ody>
</html>

--_000_B31EEDDDB8ED7E4A93FDF12A4EECD30D7D76D2BDGLKXM0002VGREEN_--


From nobody Thu Dec  3 11:28:36 2015
Return-Path: <ratliffstan@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 494B91A00F5 for <manet@ietfa.amsl.com>; Thu,  3 Dec 2015 11:28:35 -0800 (PST)
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 nAr9FXjhmcxI for <manet@ietfa.amsl.com>; Thu,  3 Dec 2015 11:28:33 -0800 (PST)
Received: from mail-lb0-x232.google.com (mail-lb0-x232.google.com [IPv6:2a00:1450:4010:c04::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EC9751A0093 for <manet@ietf.org>; Thu,  3 Dec 2015 11:28:32 -0800 (PST)
Received: by lbcdv4 with SMTP id dv4so7843411lbc.2 for <manet@ietf.org>; Thu, 03 Dec 2015 11:28:31 -0800 (PST)
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=O3ovLSLNSh5kQuLLitEHkSPyogq0xi3NKxLoq14ccQ8=; b=0QaCeUp8CX4RY31ddl8xgYdYZ99LGv9bEIuQ00bTAlmxOtgTN41dmTz9IQRPk68xJ/ 63UoTN75bD5dOyL0qRJJvqBW71jZTMi0llIChhGOtGME/a1OAHxiAIDSOIm+nuw7S3oB 57mFPqAdex/VfZiC6Wbfuugd/PbG/Mu0OeixErFnwLIsPRZjQJv3oRz3WV8oApWdaeTL W4+4/LwircSi+xKNWCgWTiAQZKHoyC6OtxU5GkJUC7OMHVvQVkozSK0tl24HbBwrAbn7 OgfZCq484c5smRA4oiItcoSIt1y7PyGCtsnJiGVik4Q5i1EAylps0LmNvjovkx0wQTUY fOsA==
MIME-Version: 1.0
X-Received: by 10.112.159.202 with SMTP id xe10mr6408364lbb.122.1449170911145;  Thu, 03 Dec 2015 11:28:31 -0800 (PST)
Received: by 10.25.209.71 with HTTP; Thu, 3 Dec 2015 11:28:31 -0800 (PST)
In-Reply-To: <B31EEDDDB8ED7E4A93FDF12A4EECD30D7D76D2A4@GLKXM0002V.GREENLNK.net>
References: <B31EEDDDB8ED7E4A93FDF12A4EECD30D7D76D2A4@GLKXM0002V.GREENLNK.net>
Date: Thu, 3 Dec 2015 14:28:31 -0500
Message-ID: <CALtoyomsB815HodR4KyQVRhkmZquyy2OZqXFJSiDQWda8KZLZA@mail.gmail.com>
From: Stan Ratliff <ratliffstan@gmail.com>
To: "Dearlove, Christopher (UK)" <chris.dearlove@baesystems.com>
Content-Type: multipart/alternative; boundary=001a11c398f260b9c805260365ab
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/pIg20U7rv4aHNsX8C_jEjOiOgAM>
Cc: "manet@ietf.org" <manet@ietf.org>
Subject: Re: [manet] DLEP-17 comments, part 3
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: <https://mailarchive.ietf.org/arch/browse/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: Thu, 03 Dec 2015 19:28:35 -0000

--001a11c398f260b9c805260365ab
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Chris,

One item, inline:

On Thu, Dec 3, 2015 at 11:18 AM, Dearlove, Christopher (UK) <
chris.dearlove@baesystems.com> wrote:

> A quick one, just sections 6 and 7.
>
>
>
> Section 6, first line. I wouldn=E2=80=99t write this (WG etc.) but that=
=E2=80=99s a style
> issue.
>
>
>
> Section 6, first paragraph, additional rules of behaviour. Those are
> tricky. New rules because of new messages, OK. But new rules in existing
> situations, that=E2=80=99s a compatibility issue. I would suggest making =
it clear
> that=E2=80=99s not intended. (You can=E2=80=99t actually ban it, because =
an update could
> remove the ban =E2=80=A6)
>
>
>
> Section 6, third paragraph. Not Reserved, that has a different meaning.
> See RFC 5226. All uses of Reserved in the document need review accordingl=
y.
>
>
>
> Section 7, line one. The specificity of thousands makes me want to ask fo=
r
> details.
>
>
>
> Section 7, line 4, is this an RFC 2119 RECOMMENDED?
>
>
>
> Section 7. This one paragraph covers two topics, which should be differen=
t
> paragraphs. The first is having lots of destinations. The second is
> managing each destination so as to not produce excessive data. (Actually,
> there=E2=80=99s really a third, flapping isn=E2=80=99t a DLEP problem, it=
=E2=80=99s a use by the
> router of the data problem.) Only the first of these is scalability, the
> second is a different efficiency issue.
>

I think the flapping actually is a DLEP problem - a flapping station on the
far-end of an RF connection could well produce a storm of corresponding
'Destination Up/Destination Down' messages. The text is intended to say
that those types of issues need to be considered.

Regards,
Stan



> ********************************************************************
> 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.
> ********************************************************************
>
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www.ietf.org/mailman/listinfo/manet
>
>

--001a11c398f260b9c805260365ab
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Chris,=C2=A0<div><br></div><div>One item, inline:=C2=A0</d=
iv><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Thu, Dec 3,=
 2015 at 11:18 AM, Dearlove, Christopher (UK) <span dir=3D"ltr">&lt;<a href=
=3D"mailto:chris.dearlove@baesystems.com" target=3D"_blank">chris.dearlove@=
baesystems.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" s=
tyle=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">





<div lang=3D"EN-GB" link=3D"blue" vlink=3D"purple">
<div>
<p class=3D"MsoNormal">A quick one, just sections 6 and 7.<u></u><u></u></p=
>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">Section 6, first line. I wouldn=E2=80=99t write this=
 (WG etc.) but that=E2=80=99s a style issue.<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">Section 6, first paragraph, additional rules of beha=
viour. Those are tricky. New rules because of new messages, OK. But new rul=
es in existing situations, that=E2=80=99s a compatibility issue. I would su=
ggest making it clear that=E2=80=99s not intended.
 (You can=E2=80=99t actually ban it, because an update could remove the ban=
 =E2=80=A6)<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">Section 6, third paragraph. Not Reserved, that has a=
 different meaning. See RFC 5226. All uses of Reserved in the document need=
 review accordingly.<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">Section 7, line one. The specificity of thousands ma=
kes me want to ask for details.<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">Section 7, line 4, is this an RFC 2119 RECOMMENDED?<=
u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">Section 7. This one paragraph covers two topics, whi=
ch should be different paragraphs. The first is having lots of destinations=
. The second is managing each destination so as to not produce excessive da=
ta. (Actually, there=E2=80=99s really a third,
 flapping isn=E2=80=99t a DLEP problem, it=E2=80=99s a use by the router of=
 the data problem.) Only the first of these is scalability, the second is a=
 different efficiency issue.</p></div></div></blockquote><div><br></div><di=
v>I think the flapping actually is a DLEP problem - a flapping station on t=
he far-end of an RF connection could well produce a storm of corresponding =
&#39;Destination Up/Destination Down&#39; messages. The text is intended to=
 say that those types of issues need to be considered.=C2=A0</div><div><br>=
</div><div>Regards,<br>Stan</div><div><br></div><div>=C2=A0</div><blockquot=
e class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc sol=
id;padding-left:1ex"><div lang=3D"EN-GB" link=3D"blue" vlink=3D"purple"><di=
v><p class=3D"MsoNormal"><u></u><u></u></p>
</div>
<p>********************************************************************<br>
This email and any attachments are confidential to the intended<br>
recipient and may also be privileged. If you are not the intended<br>
recipient please delete it from your system and notify the sender.<br>
You should not copy it or use it for any purpose nor disclose or<br>
distribute its contents to any other person.<br>
********************************************************************</p></d=
iv>

<br>_______________________________________________<br>
manet mailing list<br>
<a href=3D"mailto:manet@ietf.org">manet@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/manet" rel=3D"noreferrer" =
target=3D"_blank">https://www.ietf.org/mailman/listinfo/manet</a><br>
<br></blockquote></div><br></div></div>

--001a11c398f260b9c805260365ab--


From nobody Thu Dec  3 12:33:26 2015
Return-Path: <christopher.dearlove@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 38FD21A92ED for <manet@ietfa.amsl.com>; Thu,  3 Dec 2015 12:33:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level: 
X-Spam-Status: No, score=-1.998 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, MIME_QP_LONG_LINE=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 ijkjKnbbyD02 for <manet@ietfa.amsl.com>; Thu,  3 Dec 2015 12:33:21 -0800 (PST)
Received: from mail-wm0-x235.google.com (mail-wm0-x235.google.com [IPv6:2a00:1450:400c:c09::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B7AAC1A92EA for <manet@ietf.org>; Thu,  3 Dec 2015 12:33:20 -0800 (PST)
Received: by wmec201 with SMTP id c201so45263229wme.0 for <manet@ietf.org>; Thu, 03 Dec 2015 12:33:19 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=references:mime-version:in-reply-to:content-type :content-transfer-encoding:message-id:cc:from:subject:date:to; bh=lf8QsjlzbtfbzsOtiFqqp4DciW4Ygtz4cj/JlMCNIws=; b=zzBKWzqW2GjLP6HeVOSSlR77YbSaq8ZVRnj2TlHvA7WHzTXbXr7nDT/6tZRKxOoOzT UOd7hG2XO9YeH07CVTLGUgnsiyhh3dQCg8ChaqG0rWOGk2H1qZTW7O0FNqmYbDAvXxiV ITyGvKi6tgua+gj6OQdXZeqoZv+ocJAHCESXLVcAUGRquIsKGTZwO9iyHf+sqRLaEaCi OSNZMcBeNsMon8NaDBFw+Sb4z2Kcc7V89p90xOLsV1TJH+V+hFcis51DPn03qVz7D40h 4WSFtBv/CdxHFNl1B66hoY7bfK4qRChyPB8UJw+C5+p8M/BI3vhsbIDzOA6TQA12ZBYv B/YQ==
X-Received: by 10.28.46.206 with SMTP id u197mr612404wmu.86.1449174799340; Thu, 03 Dec 2015 12:33:19 -0800 (PST)
Received: from [10.4.237.225] (dab-ell1-h-32-10.dab.02.net. [82.132.239.197]) by smtp.gmail.com with ESMTPSA id vr10sm9194856wjc.38.2015.12.03.12.33.17 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 03 Dec 2015 12:33:18 -0800 (PST)
References: <B31EEDDDB8ED7E4A93FDF12A4EECD30D7D76D2A4@GLKXM0002V.GREENLNK.net> <CALtoyomsB815HodR4KyQVRhkmZquyy2OZqXFJSiDQWda8KZLZA@mail.gmail.com>
Mime-Version: 1.0 (1.0)
In-Reply-To: <CALtoyomsB815HodR4KyQVRhkmZquyy2OZqXFJSiDQWda8KZLZA@mail.gmail.com>
Content-Type: multipart/alternative; boundary=Apple-Mail-63D0842B-2851-4E36-8E7F-37FCE790C802
Content-Transfer-Encoding: 7bit
Message-Id: <D088D82A-837C-4035-837D-AA544DABE1B5@gmail.com>
X-Mailer: iPhone Mail (13B143)
From: Christopher Dearlove <christopher.dearlove@gmail.com>
Date: Thu, 3 Dec 2015 20:33:15 +0000
To: Stan Ratliff <ratliffstan@gmail.com>
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/YZS_s9ZfrflbxMTUk17BL8QNkHM>
Cc: "Dearlove, Christopher \(UK\)" <chris.dearlove@baesystems.com>, "manet@ietf.org" <manet@ietf.org>
Subject: Re: [manet] DLEP-17 comments, part 3
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: <https://mailarchive.ietf.org/arch/browse/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: Thu, 03 Dec 2015 20:33:24 -0000

--Apple-Mail-63D0842B-2851-4E36-8E7F-37FCE790C802
Content-Type: text/plain;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable

Fair point. I was considering the flapping as inducing routing algorithm ins=
tability. That's a worse problem in term in that a linear increase in number=
 of changes may do much worse than that to the routing. That isn't a DLEP pr=
oblem, as the router in turn can smooth and/or use hysteresis. But just simp=
ly that putting every change on the wire is, as you say, a DLEP issue.

(There are solutions that aren't exactly smoothing or hysteresis, but that's=
 up to the modem, not DLEP.)

I don't have DLEP in front of me to re-read and consider if/how I'd suggest a=
 change in wording. But that I didn't pick that up says something, though wh=
ether about DLEP or my reading I don't know.

(I'm hoping to finish looking at the draft tomorrow, but no guarantees.)

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

> On 3 Dec 2015, at 19:28, Stan Ratliff <ratliffstan@gmail.com> wrote:
>=20
> Chris,=20
>=20
> One item, inline:=20
>=20
>> On Thu, Dec 3, 2015 at 11:18 AM, Dearlove, Christopher (UK) <chris.dearlo=
ve@baesystems.com> wrote:
>> A quick one, just sections 6 and 7.
>>=20
>> =20
>>=20
>> Section 6, first line. I wouldn=E2=80=99t write this (WG etc.) but that=E2=
=80=99s a style issue.
>>=20
>> =20
>>=20
>> Section 6, first paragraph, additional rules of behaviour. Those are tric=
ky. New rules because of new messages, OK. But new rules in existing situati=
ons, that=E2=80=99s a compatibility issue. I would suggest making it clear t=
hat=E2=80=99s not intended. (You can=E2=80=99t actually ban it, because an u=
pdate could remove the ban =E2=80=A6)
>>=20
>> =20
>>=20
>> Section 6, third paragraph. Not Reserved, that has a different meaning. S=
ee RFC 5226. All uses of Reserved in the document need review accordingly.
>>=20
>> =20
>>=20
>> Section 7, line one. The specificity of thousands makes me want to ask fo=
r details.
>>=20
>> =20
>>=20
>> Section 7, line 4, is this an RFC 2119 RECOMMENDED?
>>=20
>> =20
>>=20
>> Section 7. This one paragraph covers two topics, which should be differen=
t paragraphs. The first is having lots of destinations. The second is managi=
ng each destination so as to not produce excessive data. (Actually, there=E2=
=80=99s really a third, flapping isn=E2=80=99t a DLEP problem, it=E2=80=99s a=
 use by the router of the data problem.) Only the first of these is scalabil=
ity, the second is a different efficiency issue.
>>=20
>=20
> I think the flapping actually is a DLEP problem - a flapping station on th=
e far-end of an RF connection could well produce a storm of corresponding 'D=
estination Up/Destination Down' messages. The text is intended to say that t=
hose types of issues need to be considered.=20
>=20
> Regards,
> Stan
>=20
> =20
>> ********************************************************************
>> 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.
>> ********************************************************************
>>=20
>>=20
>> _______________________________________________
>> manet mailing list
>> manet@ietf.org
>> https://www.ietf.org/mailman/listinfo/manet
>=20
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www.ietf.org/mailman/listinfo/manet

--Apple-Mail-63D0842B-2851-4E36-8E7F-37FCE790C802
Content-Type: text/html;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable

<html><head><meta http-equiv=3D"content-type" content=3D"text/html; charset=3D=
utf-8"></head><body dir=3D"auto"><div>Fair point. I was considering the flap=
ping as inducing routing algorithm instability. That's a worse problem in te=
rm in that a linear increase in number of changes may do much worse than tha=
t to the routing. That isn't a DLEP problem, as the router in turn can smoot=
h and/or use hysteresis. But just simply that putting every change on the wi=
re is, as you say, a DLEP issue.</div><div><br></div><div>(There are solutio=
ns that aren't exactly smoothing or hysteresis, but that's up to the modem, n=
ot DLEP.)</div><div><br></div><div>I don't have DLEP in front of me to re-re=
ad and consider if/how I'd suggest a change in wording. But that I didn't pi=
ck that up says something, though whether about DLEP or my reading I don't k=
now.</div><div><br></div><div>(I'm hoping to finish looking at the draft tom=
orrow, but no guarantees.)<br><br><div>-- &nbsp;<div>Christopher Dearlove</d=
iv><div><a href=3D"mailto:christopher.dearlove@gmail.com">christopher.dearlo=
ve@gmail.com</a> (iPhone)</div><div><a href=3D"mailto:chris@mnemosyne.demon.=
co.uk">chris@mnemosyne.demon.co.uk</a> (home)</div></div></div><div><br>On 3=
 Dec 2015, at 19:28, Stan Ratliff &lt;<a href=3D"mailto:ratliffstan@gmail.co=
m">ratliffstan@gmail.com</a>&gt; wrote:<br><br></div><blockquote type=3D"cit=
e"><div><meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dut=
f-8"><div dir=3D"ltr">Chris,&nbsp;<div><br></div><div>One item, inline:&nbsp=
;</div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Thu, Dec=
 3, 2015 at 11:18 AM, Dearlove, Christopher (UK) <span dir=3D"ltr">&lt;<a hr=
ef=3D"mailto:chris.dearlove@baesystems.com" target=3D"_blank">chris.dearlove=
@baesystems.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" s=
tyle=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">





<div lang=3D"EN-GB" link=3D"blue" vlink=3D"purple">
<div>
<p class=3D"MsoNormal">A quick one, just sections 6 and 7.<u></u><u></u></p>=

<p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p>
<p class=3D"MsoNormal">Section 6, first line. I wouldn=E2=80=99t write this (=
WG etc.) but that=E2=80=99s a style issue.<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p>
<p class=3D"MsoNormal">Section 6, first paragraph, additional rules of behav=
iour. Those are tricky. New rules because of new messages, OK. But new rules=
 in existing situations, that=E2=80=99s a compatibility issue. I would sugge=
st making it clear that=E2=80=99s not intended.
 (You can=E2=80=99t actually ban it, because an update could remove the ban =E2=
=80=A6)<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p>
<p class=3D"MsoNormal">Section 6, third paragraph. Not Reserved, that has a d=
ifferent meaning. See RFC 5226. All uses of Reserved in the document need re=
view accordingly.<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p>
<p class=3D"MsoNormal">Section 7, line one. The specificity of thousands mak=
es me want to ask for details.<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p>
<p class=3D"MsoNormal">Section 7, line 4, is this an RFC 2119 RECOMMENDED?<u=
></u><u></u></p>
<p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p>
<p class=3D"MsoNormal">Section 7. This one paragraph covers two topics, whic=
h should be different paragraphs. The first is having lots of destinations. T=
he second is managing each destination so as to not produce excessive data. (=
Actually, there=E2=80=99s really a third,
 flapping isn=E2=80=99t a DLEP problem, it=E2=80=99s a use by the router of t=
he data problem.) Only the first of these is scalability, the second is a di=
fferent efficiency issue.</p></div></div></blockquote><div><br></div><div>I t=
hink the flapping actually is a DLEP problem - a flapping station on the far=
-end of an RF connection could well produce a storm of corresponding 'Destin=
ation Up/Destination Down' messages. The text is intended to say that those t=
ypes of issues need to be considered.&nbsp;</div><div><br></div><div>Regards=
,<br>Stan</div><div><br></div><div>&nbsp;</div><blockquote class=3D"gmail_qu=
ote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"=
><div lang=3D"EN-GB" link=3D"blue" vlink=3D"purple"><div><p class=3D"MsoNorm=
al"><u></u><u></u></p>
</div>
<p>********************************************************************<br>
This email and any attachments are confidential to the intended<br>
recipient and may also be privileged. If you are not the intended<br>
recipient please delete it from your system and notify the sender.<br>
You should not copy it or use it for any purpose nor disclose or<br>
distribute its contents to any other person.<br>
********************************************************************</p></di=
v>

<br>_______________________________________________<br>
manet mailing list<br>
<a href=3D"mailto:manet@ietf.org">manet@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/manet" rel=3D"noreferrer" t=
arget=3D"_blank">https://www.ietf.org/mailman/listinfo/manet</a><br>
<br></blockquote></div><br></div></div>
</div></blockquote><blockquote type=3D"cite"><div><span>____________________=
___________________________</span><br><span>manet mailing list</span><br><sp=
an><a href=3D"mailto:manet@ietf.org">manet@ietf.org</a></span><br><span><a h=
ref=3D"https://www.ietf.org/mailman/listinfo/manet">https://www.ietf.org/mai=
lman/listinfo/manet</a></span><br></div></blockquote></body></html>=

--Apple-Mail-63D0842B-2851-4E36-8E7F-37FCE790C802--


From nobody Thu Dec  3 13:00:03 2015
Return-Path: <jch@pps.univ-paris-diderot.fr>
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 0432D1AC44D for <manet@ietfa.amsl.com>; Thu,  3 Dec 2015 13:00:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.55
X-Spam-Level: 
X-Spam-Status: No, score=-1.55 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_FR=0.35] autolearn=no
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 oMtJpoeZyY24 for <manet@ietfa.amsl.com>; Thu,  3 Dec 2015 13:00:00 -0800 (PST)
Received: from korolev.univ-paris7.fr (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2AFA01AC7E8 for <manet@ietf.org>; Thu,  3 Dec 2015 12:59:47 -0800 (PST)
Received: from mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [81.194.30.253]) by korolev.univ-paris7.fr (8.14.4/8.14.4/relay1/56228) with ESMTP id tB3Kxjg7019833; Thu, 3 Dec 2015 21:59:45 +0100
Received: from mailhub.math.univ-paris-diderot.fr (localhost [127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTP id 4A54A61FB8; Thu,  3 Dec 2015 21:59:45 +0100 (CET)
X-Virus-Scanned: amavisd-new at math.univ-paris-diderot.fr
Received: from mailhub.math.univ-paris-diderot.fr ([127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [127.0.0.1]) (amavisd-new, port 10023) with ESMTP id 1eAlPVouuWC7; Thu,  3 Dec 2015 21:59:43 +0100 (CET)
Received: from trurl.pps.univ-paris-diderot.fr (col75-1-78-194-40-74.fbxo.proxad.net [78.194.40.74]) (Authenticated sender: jch) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTPSA id C9DF661FAB; Thu,  3 Dec 2015 21:59:43 +0100 (CET)
Date: Thu, 03 Dec 2015 21:59:44 +0100
Message-ID: <87a8prqmdb.wl-jch@pps.univ-paris-diderot.fr>
From: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
To: Christopher Dearlove <christopher.dearlove@gmail.com>
In-Reply-To: <D088D82A-837C-4035-837D-AA544DABE1B5@gmail.com>
References: <B31EEDDDB8ED7E4A93FDF12A4EECD30D7D76D2A4@GLKXM0002V.GREENLNK.net> <CALtoyomsB815HodR4KyQVRhkmZquyy2OZqXFJSiDQWda8KZLZA@mail.gmail.com> <D088D82A-837C-4035-837D-AA544DABE1B5@gmail.com>
User-Agent: Wanderlust/2.15.9
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (korolev.univ-paris7.fr [194.254.61.138]); Thu, 03 Dec 2015 21:59:45 +0100 (CET)
X-Miltered: at korolev with ID 5660AD41.000 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 5660AD41.000 from mailhub.math.univ-paris-diderot.fr/mailhub.math.univ-paris-diderot.fr/null/mailhub.math.univ-paris-diderot.fr/<jch@pps.univ-paris-diderot.fr>
X-j-chkmail-Score: MSGID : 5660AD41.000 on korolev.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Status: Ham
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/BvZS0tYXQ44v-5rSjwww65Qm9BU>
Cc: "manet@ietf.org" <manet@ietf.org>
Subject: Re: [manet] DLEP-17 comments, part 3
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: <https://mailarchive.ietf.org/arch/browse/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: Thu, 03 Dec 2015 21:00:02 -0000

> (There are solutions that aren't exactly smoothing or hysteresis, but
> that's up to the modem, not DLEP.)

Could you please explain?

-- Juliusz


From nobody Thu Dec  3 13:03:58 2015
Return-Path: <hrogge@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 811591ACCC7 for <manet@ietfa.amsl.com>; Thu,  3 Dec 2015 13:03:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 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, 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 9w9dgT0p1yrb for <manet@ietfa.amsl.com>; Thu,  3 Dec 2015 13:03:56 -0800 (PST)
Received: from mail-wm0-x229.google.com (mail-wm0-x229.google.com [IPv6:2a00:1450:400c:c09::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 28EF11ACCE1 for <manet@ietf.org>; Thu,  3 Dec 2015 13:03:56 -0800 (PST)
Received: by wmvv187 with SMTP id v187so46562357wmv.1 for <manet@ietf.org>; Thu, 03 Dec 2015 13:03:54 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=pxNT/73gc+ntSp2/bGlsgVftQug7QVSPr4hjHnCUiTc=; b=w/k+a2Cmxfkk3xO8945Lo3w0BgZsYl9D4e1NCFRh+1AqUds5aIal/gDD0lvvY3DynC DkahJlxPTHIatHxSjC7ywdAQqU30kHfzm0Bkjm9gwl8mdj5zYN3egfiPu4Fi7BuEF628 eVXnf6W8crbc1omzjpr9Ok1SKWuTyjoaXtzZ6WgCGr7oQAFvyr8wqKrbXeXW4sbQ4M3i jf3vlR3qAYy/2sm16J+cKF0V0lm9g2Uv63Cjz9xZ8OMnhdLWn/GYmp3dGQn9yuPBUEAn STeyt4pGQ9/WRfZj2UlBxv+nCL41Uny3LQih/0Yx1WlZd41WDCvUS5njcCWc8xY3UJj/ zlpA==
X-Received: by 10.194.2.193 with SMTP id 1mr13630850wjw.26.1449176634806; Thu, 03 Dec 2015 13:03:54 -0800 (PST)
MIME-Version: 1.0
Received: by 10.27.94.70 with HTTP; Thu, 3 Dec 2015 13:03:25 -0800 (PST)
In-Reply-To: <87a8prqmdb.wl-jch@pps.univ-paris-diderot.fr>
References: <B31EEDDDB8ED7E4A93FDF12A4EECD30D7D76D2A4@GLKXM0002V.GREENLNK.net> <CALtoyomsB815HodR4KyQVRhkmZquyy2OZqXFJSiDQWda8KZLZA@mail.gmail.com> <D088D82A-837C-4035-837D-AA544DABE1B5@gmail.com> <87a8prqmdb.wl-jch@pps.univ-paris-diderot.fr>
From: Henning Rogge <hrogge@gmail.com>
Date: Thu, 3 Dec 2015 22:03:25 +0100
Message-ID: <CAGnRvuraN2Ldu8dK_-kK0H762bHMJO0XZ6ATzHdd2OZKWYsy=w@mail.gmail.com>
To: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/fW86qLYMThiJwnQ10j7okEtBkRg>
Cc: Christopher Dearlove <christopher.dearlove@gmail.com>, "manet@ietf.org" <manet@ietf.org>
Subject: Re: [manet] DLEP-17 comments, part 3
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: <https://mailarchive.ietf.org/arch/browse/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: Thu, 03 Dec 2015 21:03:57 -0000

On Thu, Dec 3, 2015 at 9:59 PM, Juliusz Chroboczek
<jch@pps.univ-paris-diderot.fr> wrote:
>> (There are solutions that aren't exactly smoothing or hysteresis, but
>> that's up to the modem, not DLEP.)
>
> Could you please explain?

Rate limitation maybe?

Only allow a certain number of up/down events per neighbor per "time interval"?

Henning Rogge


From nobody Thu Dec  3 13:04:52 2015
Return-Path: <christopher.dearlove@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 015661ACCF6 for <manet@ietfa.amsl.com>; Thu,  3 Dec 2015 13:04:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 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, 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 uZzjncYy5Ab4 for <manet@ietfa.amsl.com>; Thu,  3 Dec 2015 13:04:50 -0800 (PST)
Received: from mail-wm0-x229.google.com (mail-wm0-x229.google.com [IPv6:2a00:1450:400c:c09::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9C0441ACCF4 for <manet@ietf.org>; Thu,  3 Dec 2015 13:04:49 -0800 (PST)
Received: by wmww144 with SMTP id w144so37971179wmw.1 for <manet@ietf.org>; Thu, 03 Dec 2015 13:04:48 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=references:mime-version:in-reply-to:content-type :content-transfer-encoding:message-id:cc:from:subject:date:to; bh=hG7AmKqc48B1Dtf9rn/GUrNLtb/ivJ2yM6SAEVQlSrw=; b=f3ZglbZX+qTjYOaKsYDxZhoHQxoUFmswRAGDJ9LndDeVQ2pQlBKFU9G8S9XaROlBgR D+kiKQnrrT0R+YRfZ4cKpBLLD5Cwbruhccumr4IJOfpBetNDJpi3lj0eWS7dOaBTtHn1 Ebw9CBc2dQz2VPh+a6KGktSVl15reG5QjVOo/yxMOJ/4catczM712OO5owJeCmKHJiaV dLKc71JvUnfA/Rm4FWVgZ8LddlbP4kTOarnPU+rW9RjVy8ek+/5irH+7aUx4rt8hZ9ZG 5TJxroA/2aAdNx3WJcCfXScPd8RkkMaA2u2LWd6rt/tnMzsVwirpuGBhAnwLuMp6sWI9 MZ2A==
X-Received: by 10.194.95.65 with SMTP id di1mr12886234wjb.134.1449176688255; Thu, 03 Dec 2015 13:04:48 -0800 (PST)
Received: from [10.4.237.225] (dab-ell1-h-12-4.dab.02.net. [82.132.237.155]) by smtp.gmail.com with ESMTPSA id a63sm633724wmc.5.2015.12.03.13.04.47 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 03 Dec 2015 13:04:47 -0800 (PST)
References: <B31EEDDDB8ED7E4A93FDF12A4EECD30D7D76D2A4@GLKXM0002V.GREENLNK.net> <CALtoyomsB815HodR4KyQVRhkmZquyy2OZqXFJSiDQWda8KZLZA@mail.gmail.com> <D088D82A-837C-4035-837D-AA544DABE1B5@gmail.com> <87a8prqmdb.wl-jch@pps.univ-paris-diderot.fr>
Mime-Version: 1.0 (1.0)
In-Reply-To: <87a8prqmdb.wl-jch@pps.univ-paris-diderot.fr>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Message-Id: <F2E1DDE2-F980-4DFB-8D05-16EF3164CA48@gmail.com>
X-Mailer: iPhone Mail (13B143)
From: Christopher Dearlove <christopher.dearlove@gmail.com>
Date: Thu, 3 Dec 2015 21:04:43 +0000
To: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/foCtq8gxJLu2A8fsomiV_LC8f-U>
Cc: "manet@ietf.org" <manet@ietf.org>
Subject: Re: [manet] DLEP-17 comments, part 3
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: <https://mailarchive.ietf.org/arch/browse/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: Thu, 03 Dec 2015 21:04:51 -0000

Off the top of my head, you can for example set a minimum change that you al=
low, suppressing values that are within that margin of the last value. Or yo=
u can set a maximum rate of updates. I'm sure other strategies can be devise=
d.

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

On 3 Dec 2015, at 20:59, Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr> w=
rote:

>> (There are solutions that aren't exactly smoothing or hysteresis, but
>> that's up to the modem, not DLEP.)
>=20
> Could you please explain?
>=20
> -- Juliusz


From nobody Thu Dec  3 13:25:10 2015
Return-Path: <sratliff@idirect.net>
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 971A11ACCF6 for <manet@ietfa.amsl.com>; Thu,  3 Dec 2015 13:25:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.911
X-Spam-Level: 
X-Spam-Status: No, score=-1.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 GQY5p5fHg5qj for <manet@ietfa.amsl.com>; Thu,  3 Dec 2015 13:25:04 -0800 (PST)
Received: from smtp1.idirect.net (smtp1.idirect.net [198.180.159.61]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 214821A883E for <manet@ietf.org>; Thu,  3 Dec 2015 13:25:02 -0800 (PST)
IronPort-PHdr: 9a23:6dUxnB0OZRcrV+i8smDT+DRfVm0co7zxezQtwd8ZsekUL/ad9pjvdHbS+e9qxAeQG96LtbQc06L/iOPJZy8p2d65qncMcZhBBVcuqP49uEgeOvODElDxN/XwbiY3T4xoXV5h+GynYwAOQJ6tL2PbrnD61zMOABK3bVMzfbSrXNaKx+2MlMmMuLTrKz1SgzS8Zb4gZD6Xli728vcsvI15N6wqwQHIqHYbM85fxGdvOE7B102kvpT41NdZ/i9Ro/Ms8dJbGeW/JvxgDO8QMDNzE20z4sztulH5SgSA6zNIUn8RnRVFKwfA5RD+GJz2t32+/shg3CiHJt++ZrAuXj6l5LVmS1e8iiwHHyYh6yfKjM1uybpSuhO64hB+z4POZ53TOuAoLY3HetZPD1BIQsJQWSIFSrigZo0LAvtLdbJDtYDho1oAozO/CQi2CejzjDlFmimljuUBz+09HFSej0QbFNUUvSGR9Y2tOQ==
X-IronPort-AV: E=Sophos;i="5.20,378,1444708800";  d="scan'208";a="1012181"
X-IPAS-Result: A2DMAQAdsWBW/8n6+gpeGQEBAQEPAQEBAYNdbga9OwENgWQKFwyFawKCBhQBAQEBAQEBAYEJgi2CBwEBAQEDAQEBNzQLDAQCAQgOAwQBAQEeCQchBgsUCQgBAQQBDQUIE4d/Ax+9Kw2ETwEBAQEBAQEBAQEBAQEBAQEBAQEBARiGVoR7glOCOoQuBZZhAYUshhiBcIFiSYN6jnaHWR8BAYRGcgGEZ4EHAQEB
From: "Ratliff, Stanley" <sratliff@idirect.net>
To: Henning Rogge <hrogge@gmail.com>, Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
Thread-Topic: [manet] DLEP-17 comments, part 3
Thread-Index: AdEt5S6kvYFfEAo4TCyYiw0ItRsEwQARYUiAAAJCw4AAAOzHAAAAIO+AAAnVZrA=
Date: Thu, 3 Dec 2015 21:22:58 +0000
Message-ID: <3746483422e1407eae6e17a2c016e3d1@VAUSDITCHM2.idirect.net>
References: <B31EEDDDB8ED7E4A93FDF12A4EECD30D7D76D2A4@GLKXM0002V.GREENLNK.net> <CALtoyomsB815HodR4KyQVRhkmZquyy2OZqXFJSiDQWda8KZLZA@mail.gmail.com> <D088D82A-837C-4035-837D-AA544DABE1B5@gmail.com> <87a8prqmdb.wl-jch@pps.univ-paris-diderot.fr> <CAGnRvuraN2Ldu8dK_-kK0H762bHMJO0XZ6ATzHdd2OZKWYsy=w@mail.gmail.com>
In-Reply-To: <CAGnRvuraN2Ldu8dK_-kK0H762bHMJO0XZ6ATzHdd2OZKWYsy=w@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.250.250.20]
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/rcBBOLSjPWB05GRR8IOfgW5HZr0>
Cc: Christopher Dearlove <christopher.dearlove@gmail.com>, "manet@ietf.org" <manet@ietf.org>
Subject: Re: [manet] DLEP-17 comments, part 3
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: <https://mailarchive.ietf.org/arch/browse/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: Thu, 03 Dec 2015 21:25:07 -0000

Yeah.  Here's an example of event dampening from Cisco: http://www.cisco.co=
m/c/en/us/td/docs/ios/12_0s/feature/guide/s_ipevdp.html =


Regards,
Stan

> -----Original Message-----
> From: manet [mailto:manet-bounces@ietf.org] On Behalf Of Henning Rogge
> Sent: Thursday, December 03, 2015 4:03 PM
> To: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
> Cc: Christopher Dearlove <christopher.dearlove@gmail.com>;
> manet@ietf.org
> Subject: Re: [manet] DLEP-17 comments, part 3
> =

> On Thu, Dec 3, 2015 at 9:59 PM, Juliusz Chroboczek <jch@pps.univ-paris-
> diderot.fr> wrote:
> >> (There are solutions that aren't exactly smoothing or hysteresis, but
> >> that's up to the modem, not DLEP.)
> >
> > Could you please explain?
> =

> Rate limitation maybe?
> =

> Only allow a certain number of up/down events per neighbor per "time
> interval"?
> =

> Henning Rogge
> =

> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www.ietf.org/mailman/listinfo/manet


_____________________________________________________
This electronic message and any files transmitted with it contains
information from iDirect, which may be privileged, proprietary
and/or confidential. It is intended solely for the use of the individual
or entity to whom they are addressed. If you are not the original
recipient or the person responsible for delivering the email to the
intended recipient, be advised that you have received this email
in error, and that any use, dissemination, forwarding, printing, or
copying of this email is strictly prohibited. If you received this email
in error, please delete it and immediately notify the sender.
_____________________________________________________


From nobody Thu Dec  3 13:42:53 2015
Return-Path: <yi.jiazi@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 BE98D1ACE03 for <manet@ietfa.amsl.com>; Thu,  3 Dec 2015 13:42:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.077
X-Spam-Level: 
X-Spam-Status: No, score=-0.077 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, J_CHICKENPOX_35=0.6, J_CHICKENPOX_52=0.6, SPF_PASS=-0.001] autolearn=no
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 eg9yWTn-7aMh for <manet@ietfa.amsl.com>; Thu,  3 Dec 2015 13:42:46 -0800 (PST)
Received: from mail-wm0-x230.google.com (mail-wm0-x230.google.com [IPv6:2a00:1450:400c:c09::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 635CA1ACE00 for <manet@ietf.org>; Thu,  3 Dec 2015 13:42:45 -0800 (PST)
Received: by wmec201 with SMTP id c201so40728966wme.1 for <manet@ietf.org>; Thu, 03 Dec 2015 13:42:44 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=1W0LEYASikW20ohnF/dC5C/6YopUWx40AJcBe6uhR/E=; b=Wct67fhfYUo3QUS+QFrJX/O55UOd3faRBi+RnxziB9nWIDMgBlOfJWaUYolKCLpQeu 2CBVzi853MtOSflxq+tBjx3Cj7RTSE6QCBOSuqLjPuYVk7SKGxt65i+ivP8ZwLccgKi7 xxvMI61oyduQHbBubdWSurdrltdmFD7uVWtJabIYLNn2jqM5RkWsN7LkQo7pxnsIPyfc RfTaPIwZwq6qgM8ePD70pRucgnZpEMjbVFjWQR2QEWNrW2CGdMZ+HHmrOQKHTBLSpFNV 1b9HeVyS/NKATZuY6IczYiAZkDzbc3nFIVc+UZZ4E6Re55lHeextwlL1Y4Wzf5qMw9Of I9KQ==
MIME-Version: 1.0
X-Received: by 10.194.111.199 with SMTP id ik7mr13685684wjb.167.1449178963932;  Thu, 03 Dec 2015 13:42:43 -0800 (PST)
Sender: yi.jiazi@gmail.com
Received: by 10.194.26.3 with HTTP; Thu, 3 Dec 2015 13:42:43 -0800 (PST)
In-Reply-To: <D2925838-C6F4-4E13-85F8-499651983056@thomasclausen.org>
References: <241ccb422cb941bda2617d7be275c649@VAUSDITCHM2.idirect.net> <9948DF10-0B9B-404E-BA09-C90CDE209756@thomasclausen.org> <DCC7ED56-7ED9-4610-91A0-3D70620B9823@gmail.com> <CAAePS4DtpBrWtgBbnWjLZN07mcyH=hmK0pzPvCrjwwLiTuXc2Q@mail.gmail.com> <CAAePS4AtbPekzU=m7aut08yHwZPmk-TiCdG4vvfNZtSWPowx=Q@mail.gmail.com> <8228CBB8-BCB5-4ED9-9E0C-F76CD63D2DFC@thomasclausen.org> <B31EEDDDB8ED7E4A93FDF12A4EECD30D7D76C1DB@GLKXM0002V.GREENLNK.net> <D2925838-C6F4-4E13-85F8-499651983056@thomasclausen.org>
Date: Thu, 3 Dec 2015 22:42:43 +0100
X-Google-Sender-Auth: 4LJStWnkvpvEBSQKsQFuTamU4Gs
Message-ID: <CAN1bDFwtKOkA2-MWCk0gPHVJ9_eki2P2Rb5Gu4s65pKV1mKehA@mail.gmail.com>
From: Jiazi YI <ietf@jiaziyi.com>
To: Thomas Heide Clausen <ietf@thomasclausen.org>
Content-Type: multipart/alternative; boundary=001a1130d0ea5c7f5d05260545aa
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/v0bmwa5PlYoHzNTkHzwjqxZcvTc>
Cc: "Dearlove, Christopher \(UK\)" <chris.dearlove@baesystems.com>, manet <manet@ietf.org>, Victoria Mercieca <vmercieca0@gmail.com>
Subject: Re: [manet] draft-ietf-manet-aodvv2-12 and draft-ietf-manet-dlep-17
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: <https://mailarchive.ietf.org/arch/browse/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: Thu, 03 Dec 2015 21:42:51 -0000

--001a1130d0ea5c7f5d05260545aa
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

I agree with Chris and Thomas on their concerns on the hop-by-hop security
issue.

This is very different from classical DV protocol, in which the vector
information is designed to be exchanged between neighbours.
In AODVv2, the RREQ/RREP/RERR are to be forwarded through multiple hops. A
router can sign a message that isn't actually initialised by itself -- this
is, at least, against intuition.

This can be an issue if we have compromised routers in the network. Of
course, a compromised router is a problem for every protocol, like OLSRv2.
But in OLSRv2, a compromised router can only speak on behalf of itself --
however, in AODVv2, a compromised/mis-configured router can pretend to be
any other router (for example, generate RREQ messages using another address
as OrigAddr).  The consequence will be much more serious if that happens.

best

Jiazi


On Thu, Dec 3, 2015 at 2:53 PM, Thomas Heide Clausen <ietf@thomasclausen.or=
g
> wrote:

> That is exactly the thing -  the trust model assumed (& the protocol
> mechanics) need to be understood before designing the necessary MTI
> security, and before deciding which bits (if any) from 7182 to use...
>
> Thomas
>
> On 3 d=C3=A9c. 2015, at 14:26, Dearlove, Christopher (UK) <
> chris.dearlove@baesystems.com> wrote:
>
> If you go down this route of assuming transitive trust, then you might as
> well use 7182=E2=80=99s packet ICV and timestamp rather than message ICV =
and
> timestamp.
>
>
>
> There is a complication (mostly one of presentation) that the 5444
> multiplexer (rather than AODVv2) needs to do this, at least for packets
> containing AODVv2 messages (but at which point, probably all 5444 packets=
).
> So you either, depending on your point of view, need to request it to do
> that, or (administratively) decline to operate except over a 5444
> multiplexer that is doing this.
>
>
>
> The advantage is one of saved space and time when packets contain more
> than one message. Plus slightly better protection (hop count and limit ar=
e
> covered) but which probably doesn=E2=80=99t matter here.
>
>
>
> If messages are changed/replaced on a one-to-one basis as forwarded, then
> the only solutions I can see are hop by hop transitive trust (packets or
> messages per hop), or something complicated involving aggregation and
> knowledge of changes. But the latter would be a research task to develop,
> so let=E2=80=99s not try that.
>
>
>
>
>
> *From:* manet [mailto:manet-bounces@ietf.org <manet-bounces@ietf.org>] *O=
n
> Behalf Of *ietf@thomasclausen.org
> *Sent:* 03 December 2015 12:22
> *To:* Victoria Mercieca
> *Cc:* manet
> *Subject:* Re: [manet] draft-ietf-manet-aodvv2-12 and
> draft-ietf-manet-dlep-17
>
>
>
> Dear Victoria,
>
>
>
> Responding twice to this email, intentionally as I want to address two
> different aspects independently=E2=80=A6.
>
>
>
> On Nov 19, 2015, at 17:09, Victoria Mercieca <vmercieca0@gmail.com> wrote=
:
>
>
>
>
>
> Hi Thomas and Christopher,
>
> Thank you for your comments.  If I may address just one point for starter=
s
> - regeneration vs forwarding. We use the term regeneration since forwardi=
ng
> seems inappropriate when the message content changes at each hop.
>
> The changes we make to the message content are:
>
> 1) We change the metric so that each router along the path learns a route
> from the message, with the metric associated with the path up to that poi=
nt
> 2) AckReq only applies between hops, so needs to be removed at each hop,
> and a new AckReq element may need to be added for the next hop.
> 3) ValidityTime could potentially be added by any intermediate router tha=
t
> wishes to limit the time it will forward packets on the route.
> 4) Stripping out Unreachable Addresses from RERR which did not affect our
> route set.
>
> Can we really use the term "forwarding" if we are changing the metric
> value, adding a validity time, adding/removing AckReq or removing address=
es
> and their associated TLVs?
>
> OK, so assume that I understand regeneration as per my previous email, as
> meaning =E2=80=9Cgenerate a new message and send to my neighbors, based o=
n what I
> learned when processing a received message=E2=80=9D =E2=80=94 just like a=
ny distance vector
> protocol does.
>
>
>
> In that model, what you write makes sense: each originator of a control
> message (i.e., whoever generates or regenerates it) is free to include th=
e
> information it desires, such as the 4 points you list above. No issues wi=
th
> that.
>
>
>
> However, and this joins what I pointed out in a previous email, you write
> in the applicability statement:
>
>
>
>    Providing security for a reactive routing protocol can be difficult.
>
>
> While we can discuss if the nature of =E2=80=9Creactive routing protocol=
=E2=80=9D generates particular difficulties, we certainly can agree that th=
is protocol has the same =E2=80=9Cdifficulties=E2=80=9D as a distance vecto=
r protocol: routing topology information (by definition) not being exchange=
d end-to-end, but between neighbors (who do calculations and generate their=
 own announcements =E2=80=94 regeneration, as you call it).
>
>
> This means that a specific security model of transitive trust must be ass=
umed, no? I trust Victoria, therefore when Victoria says =E2=80=9CStan told=
 me=E2=80=9D then I trust that she actually verified that "it was indeed St=
an who told her =E2=80=A6=E2=80=9D =E2=80=94 and either way, I have no way =
of verifying?
>
>
> I did not see the trust model / trust assumption discussed in the specifi=
cation (specifically not in applicability and in section 13, both of where =
it should be called out), but I think that this is actually a crucial point=
 to get right, in order to approach developing the MTI security mechanisms.
>
>
> Anyways, that observation actually contrasts strongly with what the appli=
cability statement then goes on to say, namely:
>
>
>
>    AODVv2 provides for message integrity and security against replay
>
>    attacks by using integrity check values, timestamps and sequence
>
>    numbers, as described in Section 13 <https://tools.ietf.org/html/draft=
-ietf-manet-aodvv2-12#section-13>.
>
>
> This is true only in as much as messages are indeed exchanged between nei=
ghbors: when you =E2=80=9Cregenerate=E2=80=9D a message, i.e., generate a n=
ew message in response to receipt of a message, you generate brand new payl=
oad (but possibly including some of the data from the received message, of =
course): thus, any ICVs =E2=80=9Cfrom farther away than the neighbor=E2=80=
=9D will be useless (or, if you zero out the parts that you change, these p=
arts will not be protected).
>
>
> The above sentence, quoted from the applicability statement, and that whi=
ch transpires from section 13, seems - certainly, absent the trust model as=
sumed - to suggest that end-to-end protection/validation is provided. But, =
this is *not* the case.
>
>
> Finally to the applicability statement, a question:
>
>
>    If security associations can be
>
>    established, encryption can be used for AODVv2 messages to ensure
>
>    that only trusted routers participate in routing operations.
>
>
>
> What you want to say here is that =E2=80=9Cif all trusted routers have a =
shared
> secret, then we=E2=80=99re able to use that shared secret to ignore non-t=
rusted
> routers=E2=80=9D, right?
>
> While =E2=80=9Csecurity associations=E2=80=9D that do not pass through a =
shared secret
> probably can be thought up, it=E2=80=99s not trivial and I did not find a=
ny
> discussion of that in the document?
>
>
>
> Having, on the topic of security, re-read Section 13, which starts:
>
>
>
>    This section describes various security considerations and potential
>
>    avenues to secure AODVv2 routing.
>
>
>
> While this is an honest description of what follows, I remain convinced
> that this is not sufficient. So let me ask as precisely as I can:
>
>
>
>             o          what is the MTI security mechanism that a
> conformant implementation must provide?
>
>                         Specifically:
>
>                                     -           which are the processing
> steps (for example in section 7.2.1
>
>                                                 and section 7.2.2 for
> RREP - and similarly for the other message
>
>                                                 types) that define that
> security mechanism
>
>
>
>             o          what protection is offered by that MTI security
> mechanism? And what remains
>
>                         vulnerable.
>
>
>
> If this specification targets std.track, then it should include
> (reasonably solid, but definitely well specified) MTI security.
>
>
>
> Best
>
>
>
> Thomas
>
>
>
> Further, in reply to the comment about use of the msg-hop-count and
> msg-hop-limit fields, I think it does not matter that a message only
> travels one hop in that particular form, with that exact set of informati=
on
> enclosed. Hop limit and hop count are part of the message and used by the
> routing protocol, and so they refer to the multi-hop path that the AODVv2
> message will follow, indicating when not to regenerate any further. So
> AODVv2 uses these fields as suggested in RFC5444 Appendix B, to limit the
> number of hops across which it will regenerate a packet so as to "prevent
> messages from endlessly circulating in a MANET".
>
> Kind regards,
> Victoria.
>
>
>
> On Wed, Nov 18, 2015 at 8:49 AM, Christopher Dearlove <
> christopher.dearlove@gmail.com> wrote:
>
> I've not had time to look at either yet, though I hope to review DLEP ver=
y
> soon.
>
>
>
> But this has made me think about the RFC 6621 reference in AODVv2. It's
> always been clear this has been rather a throwaway comment that needed
> thought, but until now I hadn't really given it any.
>
>
>
> And it doesn't work. RFC 6621 is fundamentally unusable here. Let's
> consider each on turn.
>
>
>
> AODVv2 is in the RFC 5444 structure. As has been noted on many occasions,
> AOVDVv2 gets to use messages, but packets are not in its competence.
>
>
>
> RFC 6621 is about packets. But not even RFC 5444 packets but IP packets.
> It's about whether or not to forward them. But RFC 5444 packets aren't ju=
st
> not forwarded in unchanged IP packets, they aren't even forwarded at all.
> They are each a single hop construct, and if a message is forwarded (whic=
h
> is by the routing protocol, as far as RFC 5444 is concerned, it's a new
> message) it will be in a new packet, with possibly new companions.
>
>
>
> If AODVv2 wants to use a more efficient flooding process, it needs one at
> the message level. Now an example of that exists - the mechanism on RFC
> 7181. Unfortunately we didn't break that out as a separate draft (we woul=
d
> have liked to, but there were reasons we didn't).
>
>
>
> And even if (by reference or other means) it were used - or some related
> mechanism such as a CDS - that processing/forwarding mechanism assumes yo=
u
> have defined MPRs (or similarly, that you have defined a CDS). And that
> needs a local exchange of information, such as NHDP's HELLO messages (and
> the rest of NHDP) augmented with RFC 7181's MPR TLV (though only the
> flooding bit is needed).
>
>
>
> In other words, taking some real work to define. And also raising a
> question for the WG - why do we want a reactive protocol? The main
> attraction as I see it is the "if you're not doing anything, you're not
> transmitting" property. Which adding this voids. Of course maybe the WG
> doesn't value that. Or it is acceptable as an option. But if so it needs =
to
> be an option that all routers use, or none. And if all, compatibly. (MPR
> flooding allows different MPR selection algorithms - but only as long as
> they satisfy the fundamental MPR algorithm properties.)
>
>
>
> In short, RFC 6621 must go. The alternative is nothing, or significant
> work.
>
> --
>
> Christopher Dearlove
>
> christopher.dearlove@gmail.com (iPhone)
>
> chris@mnemosyne.demon.co.uk (home)
>
>
> On 18 Nov 2015, at 01:35, Thomas Clausen <ietf@thomasclausen.org> wrote:
>
> Dear all,
>
>
>
> I have started looking through the recently
> updated draft-ietf-manet-aodvv2-12. A lot has changed, and I regret not t=
o
> have had a blow-by-bow comeback to the previous review comments  - would
> have made it a somewhat easier task to check if all have been addressed o=
r
> not.
>
>
>
> But, I will work through it and produce a detailed review - but from my
> first quick read-through there're a couple of issue that jumped at me as
> worth bringing forward on a more global level already.
>
>
>
> The first relates to  how RREQs are forwarded -- or, more generally, are
> not.
>
>
>
> The protocol currently talks about "message is regenerated" rather than
> "forwarded". I have understood that this means that a RREQ is actually no=
t
> an "end to end" entity, but is a "hop by hop" entity.
>
>
>
> First, that is a curious design choice, is there any reason why this is s=
o
> considered?
>
>
>
> Second, if a RREQ message is hop-by-hop only, then I do not think that th=
e
> use of the RFC5444 hop-limit/hop-count fields is appropriate.
>
>
>
> Third, the statement in section 6.5 on the use of RFC6621 is incorrect in
> two ways: RFC6621 does specify how messages are *forwarded* (but, as
> discussed above, you are not forwarding messages).
>
>
>
> More seriously, this paragraph is incorrect:
>
>
>
> "Implementations MAY choose to employ techniques to reduce the number of =
multicast messages sent. Use of [RFC6621 <https://tools.ietf.org/html/rfc66=
21>] in deployments is recommended. Employing [RFC6621 <https://tools.ietf.=
org/html/rfc6621>] in a subset of the operational AODVv2 routers in a netwo=
rk, or configuring different algorithms on different routers, will not caus=
e interoperability issues, but will reduce the effectiveness of the multica=
st reduction scheme."
>
>
>
> Different routers using different relay selection algorithms in the same
> network will not *just* cause loss of efficiency, but *will* cause
> interoperability issues.
>
>
>
> For example if "router A" decides to suppress its message relaying becaus=
e
> it estimates that "router B" provides sufficient coverage - and conversel=
y
> "router B" suppresses relaying for the same reason: neither A nor B would
> relay, and so any routers reachable only via A and B would not be covered=
.
>
>
>
> This is not a far-sought example: it can be as simple as A and B simply
> using self-selecting relay algorithms with different tie-breakers.
>
>
>
> In short: I think that the whole message flooding/regeneration part
> requires serious work.
>
>
>
> The second issue is that I also suspect that there is some issue with
> buffering, or rather with how it is specified; starting in section 6.6, I
> am not sure that leaving that as "a matter of policy at each router" is
> entirely right.
>
>
>
> Also on buffering, I am wondering if the "start delivering buffered
> packets" conditions (penultimate paragraph in 6.6, and of course through
> the processing sections) is sufficient; I suspect that the condition "Whe=
n
> a valid route is installed" is not sufficient - that there are situations
> where a routing table entry is installed, but the complete route is not
> available or is not bidirectional?This obviously is related to RREP_Ack
> being hop-by-hop and not end-to-end....
>
>
>
> Either way, the parts of the specification that relate to buffering
> contain a mixture of normative and non-normative verbiage (a lot of "can"
> but also a lot of MUST/SHOULD) which I think could do with a tightening u=
p.
>
>
>
> But....is buffering even something that should be specified by this
> document? It does not impact interoperability and it interferes
> substantially with transport and congestion control, and I am not sure th=
at
> we understand the consequences (I am not convinced that the claims in the
> document on benefits to TCP are substantiated or even true).
>
>
>
> As I indicated, a complete review will follow, but I thought that these
> was a global enough topics to call out and get engineered right.
>
>
>
> Thomas
>
>
>
> PS: I remain convinced that the security considerations section is
> insufficient ; I will try to articulate my thoughts on why that is, but f=
or
> starters looking at the recently raised (by somebody else, the Chris
> replied) AODV security questions would probably be helpful
>
>
> On 10 Nov 2015, at 02:10, Ratliff, Stanley <sratliff@idirect.net> wrote:
>
> Hello WG participants =E2=80=93
>
>
>
> The above referenced drafts were posted Oct. 13 (for AODVv2), and Oct. 16
> (DLEP). The co-authors and the chairs ask that you please take some time =
to
> review and comment on the new submissions.
>
>
>
> Regards,
>
> Stan
>
>
>
>
>
>
> _____________________________________________________
> This electronic message and any files transmitted with it contains
> information from iDirect, which may be privileged, proprietary
> and/or confidential. It is intended solely for the use of the individual
> or entity to whom they are addressed. If you are not the original
> recipient or the person responsible for delivering the email to the
> intended recipient, be advised that you have received this email
> in error, and that any use, dissemination, forwarding, printing, or
> copying of this email is strictly prohibited. If you received this email
> in error, please delete it and immediately notify the sender.
> _____________________________________________________
>
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www.ietf.org/mailman/listinfo/manet
>
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www.ietf.org/mailman/listinfo/manet
>
>
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www.ietf.org/mailman/listinfo/manet
>
>
>
>
>
> _______________________________________________
> 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.
> ********************************************************************
>
>
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www.ietf.org/mailman/listinfo/manet
>
>

--001a1130d0ea5c7f5d05260545aa
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">I agree with Chris and Thomas on their concerns on the hop=
-by-hop security issue.=C2=A0<div><br></div><div>This is very different fro=
m classical DV protocol, in which the vector information is designed to be =
exchanged between neighbours.=C2=A0</div><div>In AODVv2, the RREQ/RREP/RERR=
 are to be forwarded through multiple hops. A router can sign a message tha=
t isn&#39;t actually initialised by itself -- this is, at least, against in=
tuition.=C2=A0</div><div><br></div><div>This can be an issue if we have com=
promised routers in the network. Of course, a compromised router is a probl=
em for every protocol, like OLSRv2. But in OLSRv2, a compromised router can=
 only speak on behalf of itself -- however, in AODVv2, a compromised/mis-co=
nfigured router can pretend to be any other router (for example, generate R=
REQ messages using another address as OrigAddr).=C2=A0 The consequence will=
 be much more serious if that happens.=C2=A0</div><div><br></div><div>best<=
/div><div><br></div><div>Jiazi</div><div><br></div></div><div class=3D"gmai=
l_extra"><br><div class=3D"gmail_quote">On Thu, Dec 3, 2015 at 2:53 PM, Tho=
mas Heide Clausen <span dir=3D"ltr">&lt;<a href=3D"mailto:ietf@thomasclause=
n.org" target=3D"_blank">ietf@thomasclausen.org</a>&gt;</span> wrote:<br><b=
lockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px =
#ccc solid;padding-left:1ex"><div dir=3D"auto"><div>That is exactly the thi=
ng - =C2=A0the trust model assumed (&amp; the protocol mechanics) need to b=
e understood before designing the necessary MTI security, and before decidi=
ng which bits (if any) from 7182 to use...<span class=3D"HOEnZb"><font colo=
r=3D"#888888"><br><br></font></span></div><span class=3D"HOEnZb"><font colo=
r=3D"#888888"><div>Thomas</div></font></span><div><div class=3D"h5"><div><b=
r>On 3 d=C3=A9c. 2015, at 14:26, Dearlove, Christopher (UK) &lt;<a href=3D"=
mailto:chris.dearlove@baesystems.com" target=3D"_blank">chris.dearlove@baes=
ystems.com</a>&gt; wrote:<br><br></div><blockquote type=3D"cite"><div>






<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">If you go down this route=
 of assuming transitive trust, then you might as well use 7182=E2=80=99s pa=
cket ICV and timestamp rather than message ICV and timestamp.<u></u><u></u>=
</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=C2=A0<u></u></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">There is a complication (=
mostly one of presentation) that the 5444 multiplexer (rather than AODVv2) =
needs to do this, at least for packets containing AODVv2
 messages (but at which point, probably all 5444 packets). So you either, d=
epending on your point of view, need to request it to do that, or (administ=
ratively) decline to operate except over a 5444 multiplexer that is doing t=
his.<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=C2=A0<u></u></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">The advantage is one of s=
aved space and time when packets contain more than one message. Plus slight=
ly better protection (hop count and limit are covered) but
 which probably doesn=E2=80=99t matter here.<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=C2=A0<u></u></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">If messages are changed/r=
eplaced on a one-to-one basis as forwarded, then the only solutions I can s=
ee are hop by hop transitive trust (packets or messages
 per hop), or something complicated involving aggregation and knowledge of =
changes. But the latter would be a research task to develop, so let=E2=80=
=99s not try that.<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=C2=A0<u></u></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=C2=A0<u></u></spa=
n></p>
<div>
<div style=3D"border:none;border-top:solid #b5c4df 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal"><b><span lang=3D"EN-US" style=3D"font-size:10.0pt;fo=
nt-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span =
lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&qu=
ot;sans-serif&quot;"> manet [<a href=3D"mailto:manet-bounces@ietf.org" targ=
et=3D"_blank">mailto:manet-bounces@ietf.org</a>]
<b>On Behalf Of </b><a href=3D"mailto:ietf@thomasclausen.org" target=3D"_bl=
ank">ietf@thomasclausen.org</a><br>
<b>Sent:</b> 03 December 2015 12:22<br>
<b>To:</b> Victoria Mercieca<br>
<b>Cc:</b> manet<br>
<b>Subject:</b> Re: [manet] draft-ietf-manet-aodvv2-12 and draft-ietf-manet=
-dlep-17<u></u><u></u></span></p>
</div>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<p class=3D"MsoNormal">Dear Victoria,<u></u><u></u></p>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Responding twice to this email, intentionally as I w=
ant to address two different aspects independently=E2=80=A6.<u></u><u></u><=
/p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<div>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class=3D"MsoNormal">On Nov 19, 2015, at 17:09, Victoria Mercieca &lt;<a =
href=3D"mailto:vmercieca0@gmail.com" target=3D"_blank">vmercieca0@gmail.com=
</a>&gt; wrote:<u></u><u></u></p>
</div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<div>
<div>
<p class=3D"MsoNormal">Hi Thomas and Christopher,<u></u><u></u></p>
<p class=3D"MsoNormal">Thank you for your comments.=C2=A0 If I may address =
just one point for starters - regeneration vs forwarding. We use the term r=
egeneration since forwarding seems inappropriate when the
 message content changes at each hop.<u></u><u></u></p>
<p class=3D"MsoNormal">The changes we make to the message content are:<u></=
u><u></u></p>
<p class=3D"MsoNormal">1) We change the metric so that each router along th=
e path learns a route from the message, with the metric associated with the=
 path up to that point<br>
2) AckReq only applies between hops, so needs to be removed at each hop, an=
d a new AckReq element may need to be added for the next hop.<br>
3) ValidityTime could potentially be added by any intermediate router that =
wishes to limit the time it will forward packets on the route.<br>
4) Stripping out Unreachable Addresses from RERR which did not affect our r=
oute set.<u></u><u></u></p>
<p class=3D"MsoNormal">Can we really use the term &quot;forwarding&quot; if=
 we are changing the metric value, adding a validity time, adding/removing =
AckReq or removing addresses and their associated TLVs?<u></u><u></u></p>
</div>
</div>
</div>
</div>
</blockquote>
<p class=3D"MsoNormal">OK, so assume that I understand regeneration as per =
my previous email, as meaning =E2=80=9Cgenerate a new message and send to m=
y neighbors, based on what I learned when processing a received message=E2=
=80=9D =E2=80=94 just like any distance vector protocol does.<u></u><u></u>=
</p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">In that model, what you write makes sense: each orig=
inator of a control message (i.e., whoever generates or regenerates it) is =
free to include the information it desires, such as the 4 points you list a=
bove. No issues with that.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">However, and this joins what I pointed out in a prev=
ious email, you write in the applicability statement:<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<pre>=C2=A0=C2=A0 Providing security for a reactive routing protocol can be=
 difficult.<u></u><u></u></pre>
<span style=3D"font-size:9.0pt;font-family:&quot;Helvetica&quot;,&quot;sans=
-serif&quot;"><br clear=3D"all">
</span>
<pre><span style=3D"font-family:&quot;Helvetica&quot;,&quot;sans-serif&quot=
;">While we can discuss if the nature of=C2=A0=E2=80=9Creactive routing pro=
tocol=E2=80=9D generates particular difficulties, we certainly can agree th=
at this protocol has the same=C2=A0=E2=80=9Cdifficulties=E2=80=9D as a dist=
ance vector protocol: routing=C2=A0topology information (by definition) not=
 being exchanged end-to-end, but between neighbors (who do=C2=A0calculation=
s and generate their own announcements=C2=A0=E2=80=94 regeneration, as you =
call it).=C2=A0</span><u></u><u></u></pre>
<span style=3D"font-size:10.0pt;font-family:&quot;Helvetica&quot;,&quot;san=
s-serif&quot;"><br clear=3D"all">
</span>
<pre><span style=3D"font-family:&quot;Helvetica&quot;,&quot;sans-serif&quot=
;">This means that a specific security model of transitive trust must be as=
sumed, no? I trust Victoria,=C2=A0therefore when Victoria says=C2=A0=E2=80=
=9CStan told me=E2=80=9D=C2=A0then I trust that she=C2=A0actually verified =
that &quot;it was indeed Stan who told her=C2=A0=E2=80=A6=E2=80=9D=C2=A0=E2=
=80=94 and either way, I have no way of verifying?</span><u></u><u></u></pr=
e>
<span style=3D"font-size:10.0pt;font-family:&quot;Helvetica&quot;,&quot;san=
s-serif&quot;"><br clear=3D"all">
</span>
<pre><span style=3D"font-family:&quot;Helvetica&quot;,&quot;sans-serif&quot=
;">I did not see the trust model / trust assumption discussed in the specif=
ication (specifically not in applicability and in section 13, both of where=
 it should be called out), but I think that this is actually a crucial poin=
t to get right, in order to approach developing the MTI security mechanisms=
.</span><u></u><u></u></pre>
<span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;"><br cl=
ear=3D"all">
</span>
<pre><span style=3D"font-family:&quot;Helvetica&quot;,&quot;sans-serif&quot=
;">Anyways, that observation actually contrasts strongly with what the appl=
icability statement then goes on to say, namely:</span><u></u><u></u></pre>
<pre><u></u>=C2=A0<u></u></pre>
<pre>=C2=A0=C2=A0 AODVv2 provides for message integrity and security agains=
t replay<u></u><u></u></pre>
<pre>=C2=A0=C2=A0 attacks by using integrity check values, timestamps and s=
equence<u></u><u></u></pre>
<pre>=C2=A0=C2=A0 numbers, as described in <a href=3D"https://tools.ietf.or=
g/html/draft-ietf-manet-aodvv2-12#section-13" target=3D"_blank">Section 13<=
/a><span style=3D"font-size:12.0pt">.</span><u></u><u></u></pre>
<span style=3D"font-size:12.0pt;font-family:&quot;Courier New&quot;"><br cl=
ear=3D"all">
</span>
<pre><span style=3D"font-family:&quot;Helvetica&quot;,&quot;sans-serif&quot=
;">This is true only in as much as messages are indeed exchanged between ne=
ighbors: when you=C2=A0=E2=80=9Cregenerate=E2=80=9D a message, i.e., genera=
te a new=C2=A0message in response to receipt of a message, you generate bra=
nd new payload (but possibly including some of=C2=A0the data from the recei=
ved message, of course): thus, any ICVs=C2=A0=E2=80=9Cfrom farther away tha=
n the neighbor=E2=80=9D=C2=A0will be useless (or, if you zero out the parts=
 that you change, these parts will not be protected).</span><u></u><u></u><=
/pre>
<span style=3D"font-size:10.0pt;font-family:&quot;Helvetica&quot;,&quot;san=
s-serif&quot;"><br clear=3D"all">
</span>
<pre><span style=3D"font-family:&quot;Helvetica&quot;,&quot;sans-serif&quot=
;">The above sentence, quoted from the applicability statement, and that wh=
ich transpires from section 13, seems - certainly, absent the trust model a=
ssumed - to suggest that end-to-end protection/validation is provided. But,=
 this is <b><u>not</u></b> the case.</span><u></u><u></u></pre>
<span style=3D"font-size:10.0pt;font-family:&quot;Helvetica&quot;,&quot;san=
s-serif&quot;"><br clear=3D"all">
</span>
<pre><span style=3D"font-family:&quot;Helvetica&quot;,&quot;sans-serif&quot=
;">Finally to the applicability statement, a question:</span><u></u><u></u>=
</pre>
<span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;"><br cl=
ear=3D"all">
</span>
<pre><span style=3D"font-size:12.0pt">=C2=A0=C2=A0 If security associations=
 can be<u></u><u></u></span></pre>
<pre><span style=3D"font-size:12.0pt">=C2=A0=C2=A0 established, encryption =
can be used for AODVv2 messages to ensure<u></u><u></u></span></pre>
<pre><span style=3D"font-size:12.0pt">=C2=A0 =C2=A0that only trusted router=
s participate in routing operations.</span><u></u><u></u></pre>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
</div>
<div>
<p class=3D"MsoNormal">What you want to say here is that =E2=80=9Cif all tr=
usted routers have a shared secret, then we=E2=80=99re able to use that sha=
red secret to ignore non-trusted routers=E2=80=9D, right?=C2=A0<u></u><u></=
u></p>
</div>
<div>
<p class=3D"MsoNormal">While =E2=80=9Csecurity associations=E2=80=9D that d=
o not pass through a shared secret probably can be thought up, it=E2=80=99s=
 not trivial and I did not find any discussion of that in the document?<u><=
/u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Having, on the topic of security, re-read Section 13=
, which starts:<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<pre>=C2=A0=C2=A0 This section describes various security considerations an=
d potential<u></u><u></u></pre>
<pre>=C2=A0=C2=A0 avenues to secure AODVv2 routing.=C2=A0 <u></u><u></u></p=
re>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
</div>
<div>
<p class=3D"MsoNormal">While this is an honest description of what follows,=
 I remain convinced that this is not sufficient. So let me ask as precisely=
 as I can:<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><span>=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0 </span>o<span>=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0
</span>what is the MTI security mechanism that a conformant implementation =
must provide?=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><span>=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0 </span>
Specifically:<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><span>=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0
</span>-<span>=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 =
</span>which are the processing steps (for example in section 7.2.1=C2=A0<u=
></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><span>=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0
</span>and section 7.2.2 for RREP - and similarly for the other message=C2=
=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><span>=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0
</span>types) that define that security mechanism<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><span>=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0 </span>o<span>=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0
</span>what protection is offered by that MTI security mechanism? And what =
remains<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><span>=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0 </span>
vulnerable.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">If this specification targets std.track, then it sho=
uld include (reasonably solid, but definitely well specified) MTI security.=
<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Best<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Thomas<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<div>
<div>
<div>
<p class=3D"MsoNormal">Further, in reply to the comment about use of the ms=
g-hop-count and msg-hop-limit fields, I think it does not matter that a mes=
sage only travels one hop in that particular form,
 with that exact set of information enclosed. Hop limit and hop count are p=
art of the message and used by the routing protocol, and so they refer to t=
he multi-hop path that the AODVv2 message will follow, indicating when not =
to regenerate any further. So AODVv2
 uses these fields as suggested in RFC5444 Appendix B, to limit the number =
of hops across which it will regenerate a packet so as to &quot;prevent mes=
sages from endlessly circulating in a MANET&quot;.
<u></u><u></u></p>
<p class=3D"MsoNormal">Kind regards,<br>
Victoria.<u></u><u></u></p>
</div>
<div>
<div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<div>
<p class=3D"MsoNormal">On Wed, Nov 18, 2015 at 8:49 AM, Christopher Dearlov=
e &lt;<a href=3D"mailto:christopher.dearlove@gmail.com" target=3D"_blank">c=
hristopher.dearlove@gmail.com</a>&gt; wrote:<u></u><u></u></p>
<div>
<div>
<p class=3D"MsoNormal">I&#39;ve not had time to look at either yet, though =
I hope to review DLEP very soon.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">But this has made me think about the RFC 6621 refere=
nce in AODVv2. It&#39;s always been clear this has been rather a throwaway =
comment that needed thought, but until now I hadn&#39;t really given it any=
.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">And it doesn&#39;t work. RFC 6621 is fundamentally u=
nusable here. Let&#39;s consider each on turn.=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">AODVv2 is in the RFC 5444 structure. As has been not=
ed on many occasions, AOVDVv2 gets to use messages, but packets are not in =
its competence.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">RFC 6621 is about packets. But not even RFC 5444 pac=
kets but IP packets. It&#39;s about whether or not to forward them. But RFC=
 5444 packets aren&#39;t just not forwarded in unchanged IP packets, they a=
ren&#39;t even forwarded at all. They are each
 a single hop construct, and if a message is forwarded (which is by the rou=
ting protocol, as far as RFC 5444 is concerned, it&#39;s a new message) it =
will be in a new packet, with possibly new companions.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">If AODVv2 wants to use a more efficient flooding pro=
cess, it needs one at the message level. Now an example of that exists - th=
e mechanism on RFC 7181. Unfortunately we didn&#39;t break that out as a se=
parate draft (we would have liked to,
 but there were reasons we didn&#39;t).<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">And even if (by reference or other means) it were us=
ed - or some related mechanism such as a CDS - that processing/forwarding m=
echanism assumes you have defined MPRs (or similarly, that you have defined=
 a CDS). And that needs a local exchange
 of information, such as NHDP&#39;s HELLO messages (and the rest of NHDP) a=
ugmented with RFC 7181&#39;s MPR TLV (though only the flooding bit is neede=
d).<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">In other words, taking some real work to define. And=
 also raising a question for the WG - why do we want a reactive protocol? T=
he main attraction as I see it is the &quot;if you&#39;re not doing anythin=
g, you&#39;re not transmitting&quot; property. Which
 adding this voids. Of course maybe the WG doesn&#39;t value that. Or it is=
 acceptable as an option. But if so it needs to be an option that all route=
rs use, or none. And if all, compatibly. (MPR flooding allows different MPR=
 selection algorithms - but only as
 long as they satisfy the fundamental MPR algorithm properties.)<u></u><u><=
/u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">In short, RFC 6621 mu=
st go. The alternative is nothing, or significant work.<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">-- =C2=A0<span style=3D"color:#888888"><u></u><u></u=
></span></p>
<div>
<p class=3D"MsoNormal"><span style=3D"color:#888888">Christopher Dearlove<u=
></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"color:#888888"><a href=3D"mailto:chri=
stopher.dearlove@gmail.com" target=3D"_blank">christopher.dearlove@gmail.co=
m</a> (iPhone)<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"color:#888888"><a href=3D"mailto:chri=
s@mnemosyne.demon.co.uk" target=3D"_blank">chris@mnemosyne.demon.co.uk</a> =
(home)<u></u><u></u></span></p>
</div>
</div>
</div>
<div>
<div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><br>
On 18 Nov 2015, at 01:35, Thomas Clausen &lt;<a href=3D"mailto:ietf@thomasc=
lausen.org" target=3D"_blank">ietf@thomasclausen.org</a>&gt; wrote:<u></u><=
u></u></p>
</div>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<div>
<p class=3D"MsoNormal">Dear all,<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">I have started looking through the recently updated=
=C2=A0draft-ietf-manet-aodvv2-12. A lot has changed, and I regret not to ha=
ve had a blow-by-bow comeback to the previous review comments =C2=A0- would=
 have made it a somewhat easier task to check
 if all have been addressed or not.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">But, I will work through it and produce a detailed r=
eview - but from my first quick read-through there&#39;re a couple of issue=
 that jumped at me as worth bringing forward on a more global level already=
.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">The first relates to =C2=A0how RREQs are forwarded -=
- or, more generally, are not.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">The protocol currently talks about &quot;message is =
regenerated&quot; rather than &quot;forwarded&quot;. I have understood that=
 this means that a RREQ is actually not an &quot;end to end&quot; entity, b=
ut is a &quot;hop by hop&quot; entity.=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">First, that is a curious design choice, is there any=
 reason why this is so considered?<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Second, if a RREQ message is hop-by-hop only, then I=
 do not think that the use of the RFC5444 hop-limit/hop-count fields is app=
ropriate.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Third, the statement in section 6.5 on the use of RF=
C6621 is incorrect in two ways: RFC6621 does specify how messages are *forw=
arded* (but, as discussed above, you are not forwarding messages).<u></u><u=
></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">More seriously, this paragraph is incorrect:<u></u><=
u></u></p>
</div>
<div>
<pre><span style=3D"font-family:&quot;UICTFontTextStyleTallBody&quot;,&quot=
;serif&quot;"><br><br></span><u></u><u></u></pre>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<pre><span style=3D"font-family:&quot;UICTFontTextStyleTallBody&quot;,&quot=
;serif&quot;">&quot;Implementations MAY choose to employ techniques to redu=
ce the number of multicast messages sent. Use of [<a href=3D"https://tools.=
ietf.org/html/rfc6621" title=3D"&quot;Simplified Multicast Forwarding&quot;=
" target=3D"_blank">RFC6621</a>] in deployments is recommended. Employing [=
<a href=3D"https://tools.ietf.org/html/rfc6621" title=3D"&quot;Simplified M=
ulticast Forwarding&quot;" target=3D"_blank">RFC6621</a>] in a subset of th=
e operational AODVv2 routers in a network, or configuring different algorit=
hms on different routers, will not cause interoperability issues, but will =
reduce the effectiveness of the multicast reduction scheme.&quot;</span><sp=
an style=3D"font-size:14.5pt"><u></u><u></u></span></pre>
</blockquote>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Different routers using different relay selection al=
gorithms in the same network will not *just* cause loss of efficiency, but =
*will* cause interoperability issues.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">For example if &quot;router A&quot; decides to suppr=
ess its message relaying because it estimates that &quot;router B&quot; pro=
vides sufficient coverage - and conversely &quot;router B&quot; suppresses =
relaying for the same reason: neither A nor B would relay, and so
 any routers reachable only via A and B would not be covered.<u></u><u></u>=
</p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">This is not a far-sought example: it can be as simpl=
e as A and B simply using self-selecting relay algorithms with different ti=
e-breakers.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">In short: I think that the whole message flooding/re=
generation part requires serious work.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<div>
<p class=3D"MsoNormal">The second issue is that I also suspect that there i=
s some issue with buffering, or rather with how it is specified; starting i=
n section 6.6, I am not sure that leaving that as &quot;a matter of policy =
at each router&quot; is entirely right.=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><br>
<br>
<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Also on buffering, I am wondering if the &quot;start=
 delivering buffered packets&quot; conditions (penultimate paragraph in 6.6=
, and of course through the processing sections) is sufficient; I suspect t=
hat the condition &quot;When a valid route is installed&quot;
 is not sufficient - that there are situations where a routing table entry =
is installed, but the complete route is not available or is not bidirection=
al?This obviously is related to RREP_Ack being hop-by-hop and not end-to-en=
d....<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><br>
<br>
<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Either way, the parts of the specification that rela=
te to buffering contain a mixture of normative and non-normative verbiage (=
a lot of &quot;can&quot; but also a lot of MUST/SHOULD) which I think could=
 do with a tightening up.=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><br>
<br>
<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">But....is buffering even something that should be sp=
ecified by this document? It does not impact interoperability and it interf=
eres substantially with transport and congestion control, and I am not sure=
 that we understand the consequences
 (I am not convinced that the claims in the document on benefits to TCP are=
 substantiated or even true).<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><br>
<br>
<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">As I indicated, a complete review will follow, but I=
 thought that these was a global enough topics to call out and get engineer=
ed right.<u></u><u></u></p>
</div>
</div>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Thomas<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">PS: I remain convinced that the security considerati=
ons section is insufficient ; I will try to articulate my thoughts on why t=
hat is, but for starters looking at the recently raised (by somebody else, =
the Chris replied) AODV security questions
 would probably be helpful<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><br>
On 10 Nov 2015, at 02:10, Ratliff, Stanley &lt;<a href=3D"mailto:sratliff@i=
direct.net" target=3D"_blank">sratliff@idirect.net</a>&gt; wrote:<u></u><u>=
</u></p>
</div>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<div>
<p class=3D"MsoNormal">Hello WG participants =E2=80=93
<u></u><u></u></p>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"text-autospace:none">
The above referenced drafts were posted Oct. 13 (for AODVv2), and Oct. 16 (=
DLEP). The co-authors and the chairs ask that you please take some time to =
review and comment on the new submissions.
<u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"text-autospace:none">
=C2=A0<u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"text-autospace:none">
Regards,<u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"text-autospace:none">
Stan<u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"text-autospace:none">
=C2=A0<u></u><u></u></p>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
</div>
<p class=3D"MsoNormal"><br>
<span style=3D"font-size:8.0pt;font-family:&quot;Arial&quot;,&quot;sans-ser=
if&quot;;color:#003366">___________________________________________________=
__<br>
This electronic message and any files transmitted with it contains<br>
information from iDirect, which may be privileged, proprietary<br>
and/or confidential. It is intended solely for the use of the individual<br=
>
or entity to whom they are addressed. If you are not the original<br>
recipient or the person responsible for delivering the email to the<br>
intended recipient, be advised that you have received this email<br>
in error, and that any use, dissemination, forwarding, printing, or<br>
copying of this email is strictly prohibited. If you received this email<br=
>
in error, please delete it and immediately notify the sender.<br>
_____________________________________________________</span> <u></u><u></u>=
</p>
</div>
</blockquote>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class=3D"MsoNormal">_______________________________________________<br>
manet mailing list<br>
<a href=3D"mailto:manet@ietf.org" target=3D"_blank">manet@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/manet" target=3D"_blank">h=
ttps://www.ietf.org/mailman/listinfo/manet</a><u></u><u></u></p>
</div>
</blockquote>
</div>
</blockquote>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class=3D"MsoNormal">_______________________________________________<br>
manet mailing list<br>
<a href=3D"mailto:manet@ietf.org" target=3D"_blank">manet@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/manet" target=3D"_blank">h=
ttps://www.ietf.org/mailman/listinfo/manet</a><u></u><u></u></p>
</div>
</blockquote>
</div>
</div>
</div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><br>
_______________________________________________<br>
manet mailing list<br>
<a href=3D"mailto:manet@ietf.org" target=3D"_blank">manet@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/manet" target=3D"_blank">h=
ttps://www.ietf.org/mailman/listinfo/manet</a><u></u><u></u></p>
</div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
</div>
</div>
</div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<p class=3D"MsoNormal">_______________________________________________<br>
manet mailing list<br>
<a href=3D"mailto:manet@ietf.org" target=3D"_blank">manet@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/manet" target=3D"_blank">h=
ttps://www.ietf.org/mailman/listinfo/manet</a><u></u><u></u></p>
</div>
</blockquote>
</div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
</div>
<p>********************************************************************<br>
This email and any attachments are confidential to the intended<br>
recipient and may also be privileged. If you are not the intended<br>
recipient please delete it from your system and notify the sender.<br>
You should not copy it or use it for any purpose nor disclose or<br>
distribute its contents to any other person.<br>
********************************************************************</p>

</div></blockquote></div></div></div><br>__________________________________=
_____________<br>
manet mailing list<br>
<a href=3D"mailto:manet@ietf.org">manet@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/manet" rel=3D"noreferrer" =
target=3D"_blank">https://www.ietf.org/mailman/listinfo/manet</a><br>
<br></blockquote></div><br></div>

--001a1130d0ea5c7f5d05260545aa--


From nobody Thu Dec  3 13:46:39 2015
Return-Path: <ben@nostrum.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 0F03E1ACE1B; Thu,  3 Dec 2015 13:46:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] 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 SIKX02q-XO7f; Thu,  3 Dec 2015 13:46:29 -0800 (PST)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D2F741ACE1A; Thu,  3 Dec 2015 13:46:28 -0800 (PST)
Received: from [10.0.1.10] (cpe-70-119-203-4.tx.res.rr.com [70.119.203.4]) (authenticated bits=0) by nostrum.com (8.15.2/8.14.9) with ESMTPSA id tB3LkOPH021897 (version=TLSv1 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Thu, 3 Dec 2015 15:46:25 -0600 (CST) (envelope-from ben@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host cpe-70-119-203-4.tx.res.rr.com [70.119.203.4] claimed to be [10.0.1.10]
From: "Ben Campbell" <ben@nostrum.com>
To: "Henning Rogge" <hrogge@gmail.com>
Date: Thu, 03 Dec 2015 15:46:24 -0600
Message-ID: <B1C7927F-7313-4334-9563-463195C4320F@nostrum.com>
In-Reply-To: <CAGnRvurhqzAoNK_PQo6d3nVe9T0Buo3YFgSUfL0ibSP9+GB7MQ@mail.gmail.com>
References: <20151202221712.3505.78561.idtracker@ietfa.amsl.com> <CAGnRvurhqzAoNK_PQo6d3nVe9T0Buo3YFgSUfL0ibSP9+GB7MQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; format=flowed
X-Mailer: MailMate (1.9.3r5187)
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/pmJdQF1gcmRsDY3ZNa_ljuPAXmg>
Cc: draft-ietf-manet-olsrv2-dat-metric@ietf.org, MANET IETF <manet@ietf.org>, The IESG <iesg@ietf.org>, manet-chairs@ietf.org
Subject: Re: [manet] Ben Campbell's No Objection on draft-ietf-manet-olsrv2-dat-metric-10: (with COMMENT)
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: <https://mailarchive.ietf.org/arch/browse/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: Thu, 03 Dec 2015 21:46:31 -0000

On 3 Dec 2015, at 3:34, Henning Rogge wrote:

> On Wed, Dec 2, 2015 at 11:17 PM, Ben Campbell <ben@nostrum.com> wrote:
>> Ben Campbell has entered the following ballot position for
>> draft-ietf-manet-olsrv2-dat-metric-10: No Objection
>>
>> ----------------------------------------------------------------------
>> COMMENT:
>> ----------------------------------------------------------------------
>>
>> - section 1, last paragraph:
>> The first part of this paragraph sounds like justification for making
>> this standards track. It would be useful to discuss why this is
>> experimental.  Is there an expectation some version of this may be
>> republished in the standards track in the future? Is there a need for
>> deployment experience prior to standardization?
>
> While I think the metric should work well, I think it should get more
> testing by other parties in different scenarios and mesh topologies.
> This is the first metric published in the Manet WG, I don't feel
> comfortable to push it to standard track without more data.
>
> There is also the possibility that someone will come up with a better
> idea to calculate the packet loss over time than the "queue of
> counters" in the DAT metric. Something that detects a "relevant"
> metric change would be great and would allow the metric to change its
> value faster without producing more noise.

Those are perfectly good reasons for experimental. It might be worth 
adding a sentence to the draft to that effect.

Thanks!

Ben.


From nobody Thu Dec  3 13:54:20 2015
Return-Path: <christopher.dearlove@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 A520E1ACE3D for <manet@ietfa.amsl.com>; Thu,  3 Dec 2015 13:54:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.798
X-Spam-Level: 
X-Spam-Status: No, score=-0.798 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, J_CHICKENPOX_35=0.6, J_CHICKENPOX_52=0.6, MIME_QP_LONG_LINE=0.001, SPF_PASS=-0.001] autolearn=no
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 lDsLr1WUhREQ for <manet@ietfa.amsl.com>; Thu,  3 Dec 2015 13:54:11 -0800 (PST)
Received: from mail-wm0-x232.google.com (mail-wm0-x232.google.com [IPv6:2a00:1450:400c:c09::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 589D41ACE42 for <manet@ietf.org>; Thu,  3 Dec 2015 13:54:00 -0800 (PST)
Received: by wmww144 with SMTP id w144so39349375wmw.1 for <manet@ietf.org>; Thu, 03 Dec 2015 13:53:59 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=references:mime-version:in-reply-to:content-type :content-transfer-encoding:message-id:cc:from:subject:date:to; bh=Wqsss6YIrn63cp7WptZQ94rj2oQzwZKlk2nmmWxtoSg=; b=YRPHoueZw4/OV2qoJrdoYaJy2bfOMloO+qMXd6rREQOZ8+eFbC7/OekGVFgc3QKStX pKOLQ7aCU0zsj3oMdJyw+odvqgg7EJUB3FMoRq3fjuWhhT8HPes+g49sjQS7R3zdQnQG +F/JFYgNb8VLHi7trKwnvVS2s+sjfd4i4yn4muwbcU+i99FjlC1xeQpsPDLzwGaSescZ vNcg4dNCi6CPWX5ERvt/gMJEEeur1vrFEIji/kt4oaniX+/TchnZ9FvvDa/qGB1Grrlk m7BSl5TFLpCY7gF09UYajKVje/giGohLZi1icL99bUNDimPqKbKCYEa/cod2RYL5XHq4 rTEg==
X-Received: by 10.28.143.11 with SMTP id r11mr993619wmd.28.1449179638972; Thu, 03 Dec 2015 13:53:58 -0800 (PST)
Received: from [10.4.237.225] (dab-ell1-h-32-10.dab.02.net. [82.132.239.197]) by smtp.gmail.com with ESMTPSA id qm9sm9309030wjc.39.2015.12.03.13.53.57 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 03 Dec 2015 13:53:57 -0800 (PST)
References: <241ccb422cb941bda2617d7be275c649@VAUSDITCHM2.idirect.net> <9948DF10-0B9B-404E-BA09-C90CDE209756@thomasclausen.org> <DCC7ED56-7ED9-4610-91A0-3D70620B9823@gmail.com> <CAAePS4DtpBrWtgBbnWjLZN07mcyH=hmK0pzPvCrjwwLiTuXc2Q@mail.gmail.com> <CAAePS4AtbPekzU=m7aut08yHwZPmk-TiCdG4vvfNZtSWPowx=Q@mail.gmail.com> <8228CBB8-BCB5-4ED9-9E0C-F76CD63D2DFC@thomasclausen.org> <B31EEDDDB8ED7E4A93FDF12A4EECD30D7D76C1DB@GLKXM0002V.GREENLNK.net> <D2925838-C6F4-4E13-85F8-499651983056@thomasclausen.org> <CAN1bDFwtKOkA2-MWCk0gPHVJ9_eki2P2Rb5Gu4s65pKV1mKehA@mail.gmail.com>
Mime-Version: 1.0 (1.0)
In-Reply-To: <CAN1bDFwtKOkA2-MWCk0gPHVJ9_eki2P2Rb5Gu4s65pKV1mKehA@mail.gmail.com>
Content-Type: multipart/alternative; boundary=Apple-Mail-9C59CABF-82CB-4EE4-B752-471F22A5F9E5
Content-Transfer-Encoding: 7bit
Message-Id: <0E81A665-85F2-4358-A5E9-1151CCAB0E61@gmail.com>
X-Mailer: iPhone Mail (13B143)
From: Christopher Dearlove <christopher.dearlove@gmail.com>
Date: Thu, 3 Dec 2015 21:53:53 +0000
To: Jiazi YI <ietf@jiaziyi.com>
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/1xsww9mWQQgioLzHxUv7KharMto>
Cc: "Dearlove, Christopher \(UK\)" <chris.dearlove@baesystems.com>, manet <manet@ietf.org>, Victoria Mercieca <vmercieca0@gmail.com>
Subject: Re: [manet] draft-ietf-manet-aodvv2-12 and draft-ietf-manet-dlep-17
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: <https://mailarchive.ietf.org/arch/browse/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: Thu, 03 Dec 2015 21:54:17 -0000

--Apple-Mail-9C59CABF-82CB-4EE4-B752-471F22A5F9E5
Content-Type: text/plain;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable

In OLSRv2 a compromised router can only speak for itself if ICVs are linked t=
o specific routers. Use a shared secret key (as RFC 7183) then a compromised=
 router can impersonate any router. draft-ietf-manet-ibs is however an examp=
le where it can't.

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

> On 3 Dec 2015, at 21:42, Jiazi YI <ietf@jiaziyi.com> wrote:
>=20
> I agree with Chris and Thomas on their concerns on the hop-by-hop security=
 issue.=20
>=20
> This is very different from classical DV protocol, in which the vector inf=
ormation is designed to be exchanged between neighbours.=20
> In AODVv2, the RREQ/RREP/RERR are to be forwarded through multiple hops. A=
 router can sign a message that isn't actually initialised by itself -- this=
 is, at least, against intuition.=20
>=20
> This can be an issue if we have compromised routers in the network. Of cou=
rse, a compromised router is a problem for every protocol, like OLSRv2. But i=
n OLSRv2, a compromised router can only speak on behalf of itself -- however=
, in AODVv2, a compromised/mis-configured router can pretend to be any other=
 router (for example, generate RREQ messages using another address as OrigAd=
dr).  The consequence will be much more serious if that happens.=20
>=20
> best
>=20
> Jiazi
>=20
>=20
>> On Thu, Dec 3, 2015 at 2:53 PM, Thomas Heide Clausen <ietf@thomasclausen.=
org> wrote:
>> That is exactly the thing -  the trust model assumed (& the protocol mech=
anics) need to be understood before designing the necessary MTI security, an=
d before deciding which bits (if any) from 7182 to use...
>>=20
>> Thomas
>>=20
>>> On 3 d=C3=A9c. 2015, at 14:26, Dearlove, Christopher (UK) <chris.dearlov=
e@baesystems.com> wrote:
>>>=20
>>> If you go down this route of assuming transitive trust, then you might a=
s well use 7182=E2=80=99s packet ICV and timestamp rather than message ICV a=
nd timestamp.
>>>=20
>>> =20
>>>=20
>>> There is a complication (mostly one of presentation) that the 5444 multi=
plexer (rather than AODVv2) needs to do this, at least for packets containin=
g AODVv2 messages (but at which point, probably all 5444 packets). So you ei=
ther, depending on your point of view, need to request it to do that, or (ad=
ministratively) decline to operate except over a 5444 multiplexer that is do=
ing this.
>>>=20
>>> =20
>>>=20
>>> The advantage is one of saved space and time when packets contain more t=
han one message. Plus slightly better protection (hop count and limit are co=
vered) but which probably doesn=E2=80=99t matter here.
>>>=20
>>> =20
>>>=20
>>> If messages are changed/replaced on a one-to-one basis as forwarded, the=
n the only solutions I can see are hop by hop transitive trust (packets or m=
essages per hop), or something complicated involving aggregation and knowled=
ge of changes. But the latter would be a research task to develop, so let=E2=
=80=99s not try that.
>>>=20
>>> =20
>>>=20
>>> =20
>>>=20
>>> From: manet [mailto:manet-bounces@ietf.org] On Behalf Of ietf@thomasclau=
sen.org
>>> Sent: 03 December 2015 12:22
>>> To: Victoria Mercieca
>>> Cc: manet
>>> Subject: Re: [manet] draft-ietf-manet-aodvv2-12 and draft-ietf-manet-dle=
p-17
>>>=20
>>> =20
>>>=20
>>> Dear Victoria,
>>>=20
>>> =20
>>>=20
>>> Responding twice to this email, intentionally as I want to address two d=
ifferent aspects independently=E2=80=A6.
>>>=20
>>> =20
>>>=20
>>> On Nov 19, 2015, at 17:09, Victoria Mercieca <vmercieca0@gmail.com> wrot=
e:
>>>=20
>>> =20
>>>=20
>>> =20
>>>=20
>>> Hi Thomas and Christopher,
>>>=20
>>> Thank you for your comments.  If I may address just one point for starte=
rs - regeneration vs forwarding. We use the term regeneration since forwardi=
ng seems inappropriate when the message content changes at each hop.
>>>=20
>>> The changes we make to the message content are:
>>>=20
>>> 1) We change the metric so that each router along the path learns a rout=
e from the message, with the metric associated with the path up to that poin=
t
>>> 2) AckReq only applies between hops, so needs to be removed at each hop,=
 and a new AckReq element may need to be added for the next hop.
>>> 3) ValidityTime could potentially be added by any intermediate router th=
at wishes to limit the time it will forward packets on the route.
>>> 4) Stripping out Unreachable Addresses from RERR which did not affect ou=
r route set.
>>>=20
>>> Can we really use the term "forwarding" if we are changing the metric va=
lue, adding a validity time, adding/removing AckReq or removing addresses an=
d their associated TLVs?
>>>=20
>>> OK, so assume that I understand regeneration as per my previous email, a=
s meaning =E2=80=9Cgenerate a new message and send to my neighbors, based on=
 what I learned when processing a received message=E2=80=9D =E2=80=94 just l=
ike any distance vector protocol does.
>>>=20
>>> =20
>>>=20
>>> In that model, what you write makes sense: each originator of a control m=
essage (i.e., whoever generates or regenerates it) is free to include the in=
formation it desires, such as the 4 points you list above. No issues with th=
at.
>>>=20
>>> =20
>>>=20
>>> However, and this joins what I pointed out in a previous email, you writ=
e in the applicability statement:
>>>=20
>>> =20
>>>=20
>>>    Providing security for a reactive routing protocol can be difficult.
>>>=20
>>>  While we can discuss if the nature of =E2=80=9Creactive routing protoco=
l=E2=80=9D generates particular difficulties, we certainly can agree that th=
is protocol has the same =E2=80=9Cdifficulties=E2=80=9D as a distance vector=
 protocol: routing topology information (by definition) not being exchanged e=
nd-to-end, but between neighbors (who do calculations and generate their own=
 announcements =E2=80=94 regeneration, as you call it).=20
>>>=20
>>>  This means that a specific security model of transitive trust must be a=
ssumed, no? I trust Victoria, therefore when Victoria says =E2=80=9CStan tol=
d me=E2=80=9D then I trust that she actually verified that "it was indeed St=
an who told her =E2=80=A6=E2=80=9D =E2=80=94 and either way, I have no way o=
f verifying?
>>>=20
>>>  I did not see the trust model / trust assumption discussed in the speci=
fication (specifically not in applicability and in section 13, both of where=
 it should be called out), but I think that this is actually a crucial point=
 to get right, in order to approach developing the MTI security mechanisms.
>>>=20
>>>  Anyways, that observation actually contrasts strongly with what the app=
licability statement then goes on to say, namely:
>>> =20
>>>    AODVv2 provides for message integrity and security against replay
>>>    attacks by using integrity check values, timestamps and sequence
>>>    numbers, as described in Section 13.
>>>=20
>>>  This is true only in as much as messages are indeed exchanged between n=
eighbors: when you =E2=80=9Cregenerate=E2=80=9D a message, i.e., generate a n=
ew message in response to receipt of a message, you generate brand new paylo=
ad (but possibly including some of the data from the received message, of co=
urse): thus, any ICVs =E2=80=9Cfrom farther away than the neighbor=E2=80=9D w=
ill be useless (or, if you zero out the parts that you change, these parts w=
ill not be protected).
>>>=20
>>>  The above sentence, quoted from the applicability statement, and that w=
hich transpires from section 13, seems - certainly, absent the trust model a=
ssumed - to suggest that end-to-end protection/validation is provided. But, t=
his is not the case.
>>>=20
>>>  Finally to the applicability statement, a question:
>>>=20
>>>     If security associations can be
>>>    established, encryption can be used for AODVv2 messages to ensure
>>>    that only trusted routers participate in routing operations.
>>> =20
>>>=20
>>> What you want to say here is that =E2=80=9Cif all trusted routers have a=
 shared secret, then we=E2=80=99re able to use that shared secret to ignore n=
on-trusted routers=E2=80=9D, right?=20
>>>=20
>>> While =E2=80=9Csecurity associations=E2=80=9D that do not pass through a=
 shared secret probably can be thought up, it=E2=80=99s not trivial and I di=
d not find any discussion of that in the document?
>>>=20
>>> =20
>>>=20
>>> Having, on the topic of security, re-read Section 13, which starts:
>>>=20
>>> =20
>>>=20
>>>    This section describes various security considerations and potential
>>>    avenues to secure AODVv2 routing. =20
>>> =20
>>>=20
>>> While this is an honest description of what follows, I remain convinced t=
hat this is not sufficient. So let me ask as precisely as I can:
>>>=20
>>> =20
>>>=20
>>>             o          what is the MTI security mechanism that a conform=
ant implementation must provide?=20
>>>=20
>>>                         Specifically:
>>>=20
>>>                                     -           which are the processing=
 steps (for example in section 7.2.1=20
>>>=20
>>>                                                 and section 7.2.2 for RR=
EP - and similarly for the other message=20
>>>=20
>>>                                                 types) that define that s=
ecurity mechanism
>>>=20
>>> =20
>>>=20
>>>             o          what protection is offered by that MTI security m=
echanism? And what remains
>>>=20
>>>                         vulnerable.
>>>=20
>>> =20
>>>=20
>>> If this specification targets std.track, then it should include (reasona=
bly solid, but definitely well specified) MTI security.
>>>=20
>>> =20
>>>=20
>>> Best
>>>=20
>>> =20
>>>=20
>>> Thomas
>>>=20
>>> =20
>>>=20
>>> Further, in reply to the comment about use of the msg-hop-count and msg-=
hop-limit fields, I think it does not matter that a message only travels one=
 hop in that particular form, with that exact set of information enclosed. H=
op limit and hop count are part of the message and used by the routing proto=
col, and so they refer to the multi-hop path that the AODVv2 message will fo=
llow, indicating when not to regenerate any further. So AODVv2 uses these fi=
elds as suggested in RFC5444 Appendix B, to limit the number of hops across w=
hich it will regenerate a packet so as to "prevent messages from endlessly c=
irculating in a MANET".
>>>=20
>>> Kind regards,
>>> Victoria.
>>>=20
>>> =20
>>>=20
>>> On Wed, Nov 18, 2015 at 8:49 AM, Christopher Dearlove <christopher.dearl=
ove@gmail.com> wrote:
>>>=20
>>> I've not had time to look at either yet, though I hope to review DLEP ve=
ry soon.
>>>=20
>>> =20
>>>=20
>>> But this has made me think about the RFC 6621 reference in AODVv2. It's a=
lways been clear this has been rather a throwaway comment that needed though=
t, but until now I hadn't really given it any.
>>>=20
>>> =20
>>>=20
>>> And it doesn't work. RFC 6621 is fundamentally unusable here. Let's cons=
ider each on turn.=20
>>>=20
>>> =20
>>>=20
>>> AODVv2 is in the RFC 5444 structure. As has been noted on many occasions=
, AOVDVv2 gets to use messages, but packets are not in its competence.
>>>=20
>>> =20
>>>=20
>>> RFC 6621 is about packets. But not even RFC 5444 packets but IP packets.=
 It's about whether or not to forward them. But RFC 5444 packets aren't just=
 not forwarded in unchanged IP packets, they aren't even forwarded at all. T=
hey are each a single hop construct, and if a message is forwarded (which is=
 by the routing protocol, as far as RFC 5444 is concerned, it's a new messag=
e) it will be in a new packet, with possibly new companions.
>>>=20
>>> =20
>>>=20
>>> If AODVv2 wants to use a more efficient flooding process, it needs one a=
t the message level. Now an example of that exists - the mechanism on RFC 71=
81. Unfortunately we didn't break that out as a separate draft (we would hav=
e liked to, but there were reasons we didn't).
>>>=20
>>> =20
>>>=20
>>> And even if (by reference or other means) it were used - or some related=
 mechanism such as a CDS - that processing/forwarding mechanism assumes you h=
ave defined MPRs (or similarly, that you have defined a CDS). And that needs=
 a local exchange of information, such as NHDP's HELLO messages (and the res=
t of NHDP) augmented with RFC 7181's MPR TLV (though only the flooding bit i=
s needed).
>>>=20
>>> =20
>>>=20
>>> In other words, taking some real work to define. And also raising a ques=
tion for the WG - why do we want a reactive protocol? The main attraction as=
 I see it is the "if you're not doing anything, you're not transmitting" pro=
perty. Which adding this voids. Of course maybe the WG doesn't value that. O=
r it is acceptable as an option. But if so it needs to be an option that all=
 routers use, or none. And if all, compatibly. (MPR flooding allows differen=
t MPR selection algorithms - but only as long as they satisfy the fundamenta=
l MPR algorithm properties.)
>>>=20
>>> =20
>>>=20
>>> In short, RFC 6621 must go. The alternative is nothing, or significant w=
ork.
>>>=20
>>> -- =20
>>>=20
>>> Christopher Dearlove
>>>=20
>>> christopher.dearlove@gmail.com (iPhone)
>>>=20
>>> chris@mnemosyne.demon.co.uk (home)
>>>=20
>>>=20
>>> On 18 Nov 2015, at 01:35, Thomas Clausen <ietf@thomasclausen.org> wrote:=

>>>=20
>>> Dear all,
>>>=20
>>> =20
>>>=20
>>> I have started looking through the recently updated draft-ietf-manet-aod=
vv2-12. A lot has changed, and I regret not to have had a blow-by-bow comeba=
ck to the previous review comments  - would have made it a somewhat easier t=
ask to check if all have been addressed or not.
>>>=20
>>> =20
>>>=20
>>> But, I will work through it and produce a detailed review - but from my f=
irst quick read-through there're a couple of issue that jumped at me as wort=
h bringing forward on a more global level already.
>>>=20
>>> =20
>>>=20
>>> The first relates to  how RREQs are forwarded -- or, more generally, are=
 not.
>>>=20
>>> =20
>>>=20
>>> The protocol currently talks about "message is regenerated" rather than "=
forwarded". I have understood that this means that a RREQ is actually not an=
 "end to end" entity, but is a "hop by hop" entity.=20
>>>=20
>>> =20
>>>=20
>>> First, that is a curious design choice, is there any reason why this is s=
o considered?
>>>=20
>>> =20
>>>=20
>>> Second, if a RREQ message is hop-by-hop only, then I do not think that t=
he use of the RFC5444 hop-limit/hop-count fields is appropriate.
>>>=20
>>> =20
>>>=20
>>> Third, the statement in section 6.5 on the use of RFC6621 is incorrect i=
n two ways: RFC6621 does specify how messages are *forwarded* (but, as discu=
ssed above, you are not forwarding messages).
>>>=20
>>> =20
>>>=20
>>> More seriously, this paragraph is incorrect:
>>>=20
>>>=20
>>>=20
>>> "Implementations MAY choose to employ techniques to reduce the number of=
 multicast messages sent. Use of [RFC6621] in deployments is recommended. Em=
ploying [RFC6621] in a subset of the operational AODVv2 routers in a network=
, or configuring different algorithms on different routers, will not cause i=
nteroperability issues, but will reduce the effectiveness of the multicast r=
eduction scheme."
>>> =20
>>>=20
>>> Different routers using different relay selection algorithms in the same=
 network will not *just* cause loss of efficiency, but *will* cause interope=
rability issues.
>>>=20
>>> =20
>>>=20
>>> For example if "router A" decides to suppress its message relaying becau=
se it estimates that "router B" provides sufficient coverage - and conversel=
y "router B" suppresses relaying for the same reason: neither A nor B would r=
elay, and so any routers reachable only via A and B would not be covered.
>>>=20
>>> =20
>>>=20
>>> This is not a far-sought example: it can be as simple as A and B simply u=
sing self-selecting relay algorithms with different tie-breakers.
>>>=20
>>> =20
>>>=20
>>> In short: I think that the whole message flooding/regeneration part requ=
ires serious work.
>>>=20
>>> =20
>>>=20
>>> The second issue is that I also suspect that there is some issue with bu=
ffering, or rather with how it is specified; starting in section 6.6, I am n=
ot sure that leaving that as "a matter of policy at each router" is entirely=
 right.=20
>>>=20
>>>=20
>>>=20
>>>=20
>>> Also on buffering, I am wondering if the "start delivering buffered pack=
ets" conditions (penultimate paragraph in 6.6, and of course through the pro=
cessing sections) is sufficient; I suspect that the condition "When a valid r=
oute is installed" is not sufficient - that there are situations where a rou=
ting table entry is installed, but the complete route is not available or is=
 not bidirectional?This obviously is related to RREP_Ack being hop-by-hop an=
d not end-to-end....
>>>=20
>>>=20
>>>=20
>>>=20
>>> Either way, the parts of the specification that relate to buffering cont=
ain a mixture of normative and non-normative verbiage (a lot of "can" but al=
so a lot of MUST/SHOULD) which I think could do with a tightening up.=20
>>>=20
>>>=20
>>>=20
>>>=20
>>> But....is buffering even something that should be specified by this docu=
ment? It does not impact interoperability and it interferes substantially wi=
th transport and congestion control, and I am not sure that we understand th=
e consequences (I am not convinced that the claims in the document on benefi=
ts to TCP are substantiated or even true).
>>>=20
>>>=20
>>>=20
>>>=20
>>> As I indicated, a complete review will follow, but I thought that these w=
as a global enough topics to call out and get engineered right.
>>>=20
>>> =20
>>>=20
>>> Thomas
>>>=20
>>> =20
>>>=20
>>> PS: I remain convinced that the security considerations section is insuf=
ficient ; I will try to articulate my thoughts on why that is, but for start=
ers looking at the recently raised (by somebody else, the Chris replied) AOD=
V security questions would probably be helpful
>>>=20
>>>=20
>>> On 10 Nov 2015, at 02:10, Ratliff, Stanley <sratliff@idirect.net> wrote:=

>>>=20
>>> Hello WG participants =E2=80=93
>>>=20
>>> =20
>>>=20
>>> The above referenced drafts were posted Oct. 13 (for AODVv2), and Oct. 1=
6 (DLEP). The co-authors and the chairs ask that you please take some time t=
o review and comment on the new submissions.
>>>=20
>>> =20
>>>=20
>>> Regards,
>>>=20
>>> Stan
>>>=20
>>> =20
>>>=20
>>> =20
>>>=20
>>>=20
>>> _____________________________________________________
>>> This electronic message and any files transmitted with it contains
>>> information from iDirect, which may be privileged, proprietary
>>> and/or confidential. It is intended solely for the use of the individual=

>>> or entity to whom they are addressed. If you are not the original
>>> recipient or the person responsible for delivering the email to the
>>> intended recipient, be advised that you have received this email
>>> in error, and that any use, dissemination, forwarding, printing, or
>>> copying of this email is strictly prohibited. If you received this email=

>>> in error, please delete it and immediately notify the sender.
>>> _____________________________________________________
>>>=20
>>> _______________________________________________
>>> manet mailing list
>>> manet@ietf.org
>>> https://www.ietf.org/mailman/listinfo/manet
>>>=20
>>> _______________________________________________
>>> manet mailing list
>>> manet@ietf.org
>>> https://www.ietf.org/mailman/listinfo/manet
>>>=20
>>>=20
>>> _______________________________________________
>>> manet mailing list
>>> manet@ietf.org
>>> https://www.ietf.org/mailman/listinfo/manet
>>>=20
>>> =20
>>>=20
>>> =20
>>>=20
>>> _______________________________________________
>>> manet mailing list
>>> manet@ietf.org
>>> https://www.ietf.org/mailman/listinfo/manet
>>>=20
>>> =20
>>>=20
>>> ********************************************************************
>>> 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.
>>> ********************************************************************
>>>=20
>>=20
>> _______________________________________________
>> manet mailing list
>> manet@ietf.org
>> https://www.ietf.org/mailman/listinfo/manet
>=20
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www.ietf.org/mailman/listinfo/manet

--Apple-Mail-9C59CABF-82CB-4EE4-B752-471F22A5F9E5
Content-Type: text/html;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable

<html><head><meta http-equiv=3D"content-type" content=3D"text/html; charset=3D=
utf-8"></head><body dir=3D"auto"><div>In OLSRv2 a compromised router can onl=
y speak for itself if ICVs are linked to specific routers. Use a shared secr=
et key (as RFC 7183) then a compromised router can impersonate any router. d=
raft-ietf-manet-ibs is however an example where it can't.<br><br>-- &nbsp;<d=
iv>Christopher Dearlove</div><div><a href=3D"mailto:christopher.dearlove@gma=
il.com">christopher.dearlove@gmail.com</a> (iPhone)</div><div><a href=3D"mai=
lto:chris@mnemosyne.demon.co.uk">chris@mnemosyne.demon.co.uk</a> (home)</div=
></div><div><br>On 3 Dec 2015, at 21:42, Jiazi YI &lt;<a href=3D"mailto:ietf=
@jiaziyi.com">ietf@jiaziyi.com</a>&gt; wrote:<br><br></div><blockquote type=3D=
"cite"><div><meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3D=
utf-8"><div dir=3D"ltr">I agree with Chris and Thomas on their concerns on t=
he hop-by-hop security issue.&nbsp;<div><br></div><div>This is very differen=
t from classical DV protocol, in which the vector information is designed to=
 be exchanged between neighbours.&nbsp;</div><div>In AODVv2, the RREQ/RREP/R=
ERR are to be forwarded through multiple hops. A router can sign a message t=
hat isn't actually initialised by itself -- this is, at least, against intui=
tion.&nbsp;</div><div><br></div><div>This can be an issue if we have comprom=
ised routers in the network. Of course, a compromised router is a problem fo=
r every protocol, like OLSRv2. But in OLSRv2, a compromised router can only s=
peak on behalf of itself -- however, in AODVv2, a compromised/mis-configured=
 router can pretend to be any other router (for example, generate RREQ messa=
ges using another address as OrigAddr).&nbsp; The consequence will be much m=
ore serious if that happens.&nbsp;</div><div><br></div><div>best</div><div><=
br></div><div>Jiazi</div><div><br></div></div><div class=3D"gmail_extra"><br=
><div class=3D"gmail_quote">On Thu, Dec 3, 2015 at 2:53 PM, Thomas Heide Cla=
usen <span dir=3D"ltr">&lt;<a href=3D"mailto:ietf@thomasclausen.org" target=3D=
"_blank">ietf@thomasclausen.org</a>&gt;</span> wrote:<br><blockquote class=3D=
"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-=
left:1ex"><div dir=3D"auto"><div>That is exactly the thing - &nbsp;the trust=
 model assumed (&amp; the protocol mechanics) need to be understood before d=
esigning the necessary MTI security, and before deciding which bits (if any)=
 from 7182 to use...<span class=3D"HOEnZb"><font color=3D"#888888"><br><br><=
/font></span></div><span class=3D"HOEnZb"><font color=3D"#888888"><div>Thoma=
s</div></font></span><div><div class=3D"h5"><div><br>On 3 d=C3=A9c. 2015, at=
 14:26, Dearlove, Christopher (UK) &lt;<a href=3D"mailto:chris.dearlove@baes=
ystems.com" target=3D"_blank">chris.dearlove@baesystems.com</a>&gt; wrote:<b=
r><br></div><blockquote type=3D"cite"><div>






<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Cal=
ibri&quot;,&quot;sans-serif&quot;;color:#1f497d">If you go down this route o=
f assuming transitive trust, then you might as well use 7182=E2=80=99s packe=
t ICV and timestamp rather than message ICV and timestamp.<u></u><u></u></sp=
an></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Cal=
ibri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>&nbsp;<u></u></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Cal=
ibri&quot;,&quot;sans-serif&quot;;color:#1f497d">There is a complication (mo=
stly one of presentation) that the 5444 multiplexer (rather than AODVv2) nee=
ds to do this, at least for packets containing AODVv2
 messages (but at which point, probably all 5444 packets). So you either, de=
pending on your point of view, need to request it to do that, or (administra=
tively) decline to operate except over a 5444 multiplexer that is doing this=
.<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Cal=
ibri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>&nbsp;<u></u></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Cal=
ibri&quot;,&quot;sans-serif&quot;;color:#1f497d">The advantage is one of sav=
ed space and time when packets contain more than one message. Plus slightly b=
etter protection (hop count and limit are covered) but
 which probably doesn=E2=80=99t matter here.<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Cal=
ibri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>&nbsp;<u></u></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Cal=
ibri&quot;,&quot;sans-serif&quot;;color:#1f497d">If messages are changed/rep=
laced on a one-to-one basis as forwarded, then the only solutions I can see a=
re hop by hop transitive trust (packets or messages
 per hop), or something complicated involving aggregation and knowledge of c=
hanges. But the latter would be a research task to develop, so let=E2=80=99s=
 not try that.<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Cal=
ibri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>&nbsp;<u></u></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Cal=
ibri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>&nbsp;<u></u></span>=
</p>
<div>
<div style=3D"border:none;border-top:solid #b5c4df 1.0pt;padding:3.0pt 0cm 0=
cm 0cm">
<p class=3D"MsoNormal"><b><span lang=3D"EN-US" style=3D"font-size:10.0pt;fon=
t-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span la=
ng=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;=
sans-serif&quot;"> manet [<a href=3D"mailto:manet-bounces@ietf.org" target=3D=
"_blank">mailto:manet-bounces@ietf.org</a>]
<b>On Behalf Of </b><a href=3D"mailto:ietf@thomasclausen.org" target=3D"_bla=
nk">ietf@thomasclausen.org</a><br>
<b>Sent:</b> 03 December 2015 12:22<br>
<b>To:</b> Victoria Mercieca<br>
<b>Cc:</b> manet<br>
<b>Subject:</b> Re: [manet] draft-ietf-manet-aodvv2-12 and draft-ietf-manet-=
dlep-17<u></u><u></u></span></p>
</div>
</div>
<div>
<p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p>
</div>
<p class=3D"MsoNormal">Dear Victoria,<u></u><u></u></p>
<div>
<p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Responding twice to this email, intentionally as I wa=
nt to address two different aspects independently=E2=80=A6.<u></u><u></u></p=
>
</div>
<div>
<p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p>
</div>
<div>
<div>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class=3D"MsoNormal">On Nov 19, 2015, at 17:09, Victoria Mercieca &lt;<a h=
ref=3D"mailto:vmercieca0@gmail.com" target=3D"_blank">vmercieca0@gmail.com</=
a>&gt; wrote:<u></u><u></u></p>
</div>
<p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p>
<div>
<div>
<p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p>
<div>
<div>
<p class=3D"MsoNormal">Hi Thomas and Christopher,<u></u><u></u></p>
<p class=3D"MsoNormal">Thank you for your comments.&nbsp; If I may address j=
ust one point for starters - regeneration vs forwarding. We use the term reg=
eneration since forwarding seems inappropriate when the
 message content changes at each hop.<u></u><u></u></p>
<p class=3D"MsoNormal">The changes we make to the message content are:<u></u=
><u></u></p>
<p class=3D"MsoNormal">1) We change the metric so that each router along the=
 path learns a route from the message, with the metric associated with the p=
ath up to that point<br>
2) AckReq only applies between hops, so needs to be removed at each hop, and=
 a new AckReq element may need to be added for the next hop.<br>
3) ValidityTime could potentially be added by any intermediate router that w=
ishes to limit the time it will forward packets on the route.<br>
4) Stripping out Unreachable Addresses from RERR which did not affect our ro=
ute set.<u></u><u></u></p>
<p class=3D"MsoNormal">Can we really use the term "forwarding" if we are cha=
nging the metric value, adding a validity time, adding/removing AckReq or re=
moving addresses and their associated TLVs?<u></u><u></u></p>
</div>
</div>
</div>
</div>
</blockquote>
<p class=3D"MsoNormal">OK, so assume that I understand regeneration as per m=
y previous email, as meaning =E2=80=9Cgenerate a new message and send to my n=
eighbors, based on what I learned when processing a received message=E2=80=9D=
 =E2=80=94 just like any distance vector protocol does.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">In that model, what you write makes sense: each origi=
nator of a control message (i.e., whoever generates or regenerates it) is fr=
ee to include the information it desires, such as the 4 points you list abov=
e. No issues with that.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">However, and this joins what I pointed out in a previ=
ous email, you write in the applicability statement:<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p>
</div>
<div>
<pre>&nbsp;&nbsp; Providing security for a reactive routing protocol can be d=
ifficult.<u></u><u></u></pre>
<span style=3D"font-size:9.0pt;font-family:&quot;Helvetica&quot;,&quot;sans-=
serif&quot;"><br clear=3D"all">
</span>
<pre><span style=3D"font-family:&quot;Helvetica&quot;,&quot;sans-serif&quot;=
">While we can discuss if the nature of&nbsp;=E2=80=9Creactive routing proto=
col=E2=80=9D generates particular difficulties, we certainly can agree that t=
his protocol has the same&nbsp;=E2=80=9Cdifficulties=E2=80=9D as a distance v=
ector protocol: routing&nbsp;topology information (by definition) not being e=
xchanged end-to-end, but between neighbors (who do&nbsp;calculations and gen=
erate their own announcements&nbsp;=E2=80=94 regeneration, as you call it).&=
nbsp;</span><u></u><u></u></pre>
<span style=3D"font-size:10.0pt;font-family:&quot;Helvetica&quot;,&quot;sans=
-serif&quot;"><br clear=3D"all">
</span>
<pre><span style=3D"font-family:&quot;Helvetica&quot;,&quot;sans-serif&quot;=
">This means that a specific security model of transitive trust must be assu=
med, no? I trust Victoria,&nbsp;therefore when Victoria says&nbsp;=E2=80=9CS=
tan told me=E2=80=9D&nbsp;then I trust that she&nbsp;actually verified that "=
it was indeed Stan who told her&nbsp;=E2=80=A6=E2=80=9D&nbsp;=E2=80=94 and e=
ither way, I have no way of verifying?</span><u></u><u></u></pre>
<span style=3D"font-size:10.0pt;font-family:&quot;Helvetica&quot;,&quot;sans=
-serif&quot;"><br clear=3D"all">
</span>
<pre><span style=3D"font-family:&quot;Helvetica&quot;,&quot;sans-serif&quot;=
">I did not see the trust model / trust assumption discussed in the specific=
ation (specifically not in applicability and in section 13, both of where it=
 should be called out), but I think that this is actually a crucial point to=
 get right, in order to approach developing the MTI security mechanisms.</sp=
an><u></u><u></u></pre>
<span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;"><br cle=
ar=3D"all">
</span>
<pre><span style=3D"font-family:&quot;Helvetica&quot;,&quot;sans-serif&quot;=
">Anyways, that observation actually contrasts strongly with what the applic=
ability statement then goes on to say, namely:</span><u></u><u></u></pre>
<pre><u></u>&nbsp;<u></u></pre>
<pre>&nbsp;&nbsp; AODVv2 provides for message integrity and security against=
 replay<u></u><u></u></pre>
<pre>&nbsp;&nbsp; attacks by using integrity check values, timestamps and se=
quence<u></u><u></u></pre>
<pre>&nbsp;&nbsp; numbers, as described in <a href=3D"https://tools.ietf.org=
/html/draft-ietf-manet-aodvv2-12#section-13" target=3D"_blank">Section 13</a=
><span style=3D"font-size:12.0pt">.</span><u></u><u></u></pre>
<span style=3D"font-size:12.0pt;font-family:&quot;Courier New&quot;"><br cle=
ar=3D"all">
</span>
<pre><span style=3D"font-family:&quot;Helvetica&quot;,&quot;sans-serif&quot;=
">This is true only in as much as messages are indeed exchanged between neig=
hbors: when you&nbsp;=E2=80=9Cregenerate=E2=80=9D a message, i.e., generate a=
 new&nbsp;message in response to receipt of a message, you generate brand ne=
w payload (but possibly including some of&nbsp;the data from the received me=
ssage, of course): thus, any ICVs&nbsp;=E2=80=9Cfrom farther away than the n=
eighbor=E2=80=9D&nbsp;will be useless (or, if you zero out the parts that yo=
u change, these parts will not be protected).</span><u></u><u></u></pre>
<span style=3D"font-size:10.0pt;font-family:&quot;Helvetica&quot;,&quot;sans=
-serif&quot;"><br clear=3D"all">
</span>
<pre><span style=3D"font-family:&quot;Helvetica&quot;,&quot;sans-serif&quot;=
">The above sentence, quoted from the applicability statement, and that whic=
h transpires from section 13, seems - certainly, absent the trust model assu=
med - to suggest that end-to-end protection/validation is provided. But, thi=
s is <b><u>not</u></b> the case.</span><u></u><u></u></pre>
<span style=3D"font-size:10.0pt;font-family:&quot;Helvetica&quot;,&quot;sans=
-serif&quot;"><br clear=3D"all">
</span>
<pre><span style=3D"font-family:&quot;Helvetica&quot;,&quot;sans-serif&quot;=
">Finally to the applicability statement, a question:</span><u></u><u></u></=
pre>
<span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;"><br cle=
ar=3D"all">
</span>
<pre><span style=3D"font-size:12.0pt">&nbsp;&nbsp; If security associations c=
an be<u></u><u></u></span></pre>
<pre><span style=3D"font-size:12.0pt">&nbsp;&nbsp; established, encryption c=
an be used for AODVv2 messages to ensure<u></u><u></u></span></pre>
<pre><span style=3D"font-size:12.0pt">&nbsp; &nbsp;that only trusted routers=
 participate in routing operations.</span><u></u><u></u></pre>
<div>
<p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p>
</div>
</div>
<div>
<p class=3D"MsoNormal">What you want to say here is that =E2=80=9Cif all tru=
sted routers have a shared secret, then we=E2=80=99re able to use that share=
d secret to ignore non-trusted routers=E2=80=9D, right?&nbsp;<u></u><u></u><=
/p>
</div>
<div>
<p class=3D"MsoNormal">While =E2=80=9Csecurity associations=E2=80=9D that do=
 not pass through a shared secret probably can be thought up, it=E2=80=99s n=
ot trivial and I did not find any discussion of that in the document?<u></u>=
<u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Having, on the topic of security, re-read Section 13,=
 which starts:<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p>
</div>
<div>
<pre>&nbsp;&nbsp; This section describes various security considerations and=
 potential<u></u><u></u></pre>
<pre>&nbsp;&nbsp; avenues to secure AODVv2 routing.&nbsp; <u></u><u></u></pr=
e>
<div>
<p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p>
</div>
</div>
<div>
<p class=3D"MsoNormal">While this is an honest description of what follows, I=
 remain convinced that this is not sufficient. So let me ask as precisely as=
 I can:<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp; </span>o<span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;
</span>what is the MTI security mechanism that a conformant implementation m=
ust provide?&nbsp;<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp; </span>
Specifically:<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;
</span>-<span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <=
/span>which are the processing steps (for example in section 7.2.1&nbsp;<u><=
/u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;
</span>and section 7.2.2 for RREP - and similarly for the other message&nbsp=
;<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;
</span>types) that define that security mechanism<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp; </span>o<span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;
</span>what protection is offered by that MTI security mechanism? And what r=
emains<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp; </span>
vulnerable.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">If this specification targets std.track, then it shou=
ld include (reasonably solid, but definitely well specified) MTI security.<u=
></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Best<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Thomas<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p>
</div>
<div>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<div>
<div>
<div>
<p class=3D"MsoNormal">Further, in reply to the comment about use of the msg=
-hop-count and msg-hop-limit fields, I think it does not matter that a messa=
ge only travels one hop in that particular form,
 with that exact set of information enclosed. Hop limit and hop count are pa=
rt of the message and used by the routing protocol, and so they refer to the=
 multi-hop path that the AODVv2 message will follow, indicating when not to r=
egenerate any further. So AODVv2
 uses these fields as suggested in RFC5444 Appendix B, to limit the number o=
f hops across which it will regenerate a packet so as to "prevent messages f=
rom endlessly circulating in a MANET".
<u></u><u></u></p>
<p class=3D"MsoNormal">Kind regards,<br>
Victoria.<u></u><u></u></p>
</div>
<div>
<div>
<div>
<p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p>
<div>
<p class=3D"MsoNormal">On Wed, Nov 18, 2015 at 8:49 AM, Christopher Dearlove=
 &lt;<a href=3D"mailto:christopher.dearlove@gmail.com" target=3D"_blank">chr=
istopher.dearlove@gmail.com</a>&gt; wrote:<u></u><u></u></p>
<div>
<div>
<p class=3D"MsoNormal">I've not had time to look at either yet, though I hop=
e to review DLEP very soon.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">But this has made me think about the RFC 6621 referen=
ce in AODVv2. It's always been clear this has been rather a throwaway commen=
t that needed thought, but until now I hadn't really given it any.<u></u><u>=
</u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">And it doesn't work. RFC 6621 is fundamentally unusab=
le here. Let's consider each on turn.&nbsp;<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">AODVv2 is in the RFC 5444 structure. As has been note=
d on many occasions, AOVDVv2 gets to use messages, but packets are not in it=
s competence.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">RFC 6621 is about packets. But not even RFC 5444 pack=
ets but IP packets. It's about whether or not to forward them. But RFC 5444 p=
ackets aren't just not forwarded in unchanged IP packets, they aren't even f=
orwarded at all. They are each
 a single hop construct, and if a message is forwarded (which is by the rout=
ing protocol, as far as RFC 5444 is concerned, it's a new message) it will b=
e in a new packet, with possibly new companions.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">If AODVv2 wants to use a more efficient flooding proc=
ess, it needs one at the message level. Now an example of that exists - the m=
echanism on RFC 7181. Unfortunately we didn't break that out as a separate d=
raft (we would have liked to,
 but there were reasons we didn't).<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">And even if (by reference or other means) it were use=
d - or some related mechanism such as a CDS - that processing/forwarding mec=
hanism assumes you have defined MPRs (or similarly, that you have defined a C=
DS). And that needs a local exchange
 of information, such as NHDP's HELLO messages (and the rest of NHDP) augmen=
ted with RFC 7181's MPR TLV (though only the flooding bit is needed).<u></u>=
<u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">In other words, taking some real work to define. And a=
lso raising a question for the WG - why do we want a reactive protocol? The m=
ain attraction as I see it is the "if you're not doing anything, you're not t=
ransmitting" property. Which
 adding this voids. Of course maybe the WG doesn't value that. Or it is acce=
ptable as an option. But if so it needs to be an option that all routers use=
, or none. And if all, compatibly. (MPR flooding allows different MPR select=
ion algorithms - but only as
 long as they satisfy the fundamental MPR algorithm properties.)<u></u><u></=
u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">In short, RFC 6621 mus=
t go. The alternative is nothing, or significant work.<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">-- &nbsp;<span style=3D"color:#888888"><u></u><u></u>=
</span></p>
<div>
<p class=3D"MsoNormal"><span style=3D"color:#888888">Christopher Dearlove<u>=
</u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"color:#888888"><a href=3D"mailto:chris=
topher.dearlove@gmail.com" target=3D"_blank">christopher.dearlove@gmail.com<=
/a> (iPhone)<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"color:#888888"><a href=3D"mailto:chris=
@mnemosyne.demon.co.uk" target=3D"_blank">chris@mnemosyne.demon.co.uk</a> (h=
ome)<u></u><u></u></span></p>
</div>
</div>
</div>
<div>
<div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><br>
On 18 Nov 2015, at 01:35, Thomas Clausen &lt;<a href=3D"mailto:ietf@thomascl=
ausen.org" target=3D"_blank">ietf@thomasclausen.org</a>&gt; wrote:<u></u><u>=
</u></p>
</div>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<div>
<p class=3D"MsoNormal">Dear all,<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">I have started looking through the recently updated&n=
bsp;draft-ietf-manet-aodvv2-12. A lot has changed, and I regret not to have h=
ad a blow-by-bow comeback to the previous review comments &nbsp;- would have=
 made it a somewhat easier task to check
 if all have been addressed or not.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">But, I will work through it and produce a detailed re=
view - but from my first quick read-through there're a couple of issue that j=
umped at me as worth bringing forward on a more global level already.<u></u>=
<u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">The first relates to &nbsp;how RREQs are forwarded --=
 or, more generally, are not.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">The protocol currently talks about "message is regene=
rated" rather than "forwarded". I have understood that this means that a RRE=
Q is actually not an "end to end" entity, but is a "hop by hop" entity.&nbsp=
;<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">First, that is a curious design choice, is there any r=
eason why this is so considered?<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Second, if a RREQ message is hop-by-hop only, then I d=
o not think that the use of the RFC5444 hop-limit/hop-count fields is approp=
riate.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Third, the statement in section 6.5 on the use of RFC=
6621 is incorrect in two ways: RFC6621 does specify how messages are *forwar=
ded* (but, as discussed above, you are not forwarding messages).<u></u><u></=
u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">More seriously, this paragraph is incorrect:<u></u><u=
></u></p>
</div>
<div>
<pre><span style=3D"font-family:&quot;UICTFontTextStyleTallBody&quot;,&quot;=
serif&quot;"><br><br></span><u></u><u></u></pre>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<pre><span style=3D"font-family:&quot;UICTFontTextStyleTallBody&quot;,&quot;=
serif&quot;">"Implementations MAY choose to employ techniques to reduce the n=
umber of multicast messages sent. Use of [<a href=3D"https://tools.ietf.org/=
html/rfc6621" title=3D"&quot;Simplified Multicast Forwarding&quot;" target=3D=
"_blank">RFC6621</a>] in deployments is recommended. Employing [<a href=3D"h=
ttps://tools.ietf.org/html/rfc6621" title=3D"&quot;Simplified Multicast Forw=
arding&quot;" target=3D"_blank">RFC6621</a>] in a subset of the operational A=
ODVv2 routers in a network, or configuring different algorithms on different=
 routers, will not cause interoperability issues, but will reduce the effect=
iveness of the multicast reduction scheme."</span><span style=3D"font-size:1=
4.5pt"><u></u><u></u></span></pre>
</blockquote>
</div>
<div>
<p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Different routers using different relay selection alg=
orithms in the same network will not *just* cause loss of efficiency, but *w=
ill* cause interoperability issues.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">For example if "router A" decides to suppress its mes=
sage relaying because it estimates that "router B" provides sufficient cover=
age - and conversely "router B" suppresses relaying for the same reason: nei=
ther A nor B would relay, and so
 any routers reachable only via A and B would not be covered.<u></u><u></u><=
/p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">This is not a far-sought example: it can be as simple=
 as A and B simply using self-selecting relay algorithms with different tie-=
breakers.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">In short: I think that the whole message flooding/reg=
eneration part requires serious work.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p>
</div>
<div>
<div>
<p class=3D"MsoNormal">The second issue is that I also suspect that there is=
 some issue with buffering, or rather with how it is specified; starting in s=
ection 6.6, I am not sure that leaving that as "a matter of policy at each r=
outer" is entirely right.&nbsp;<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><br>
<br>
<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Also on buffering, I am wondering if the "start deliv=
ering buffered packets" conditions (penultimate paragraph in 6.6, and of cou=
rse through the processing sections) is sufficient; I suspect that the condi=
tion "When a valid route is installed"
 is not sufficient - that there are situations where a routing table entry i=
s installed, but the complete route is not available or is not bidirectional=
?This obviously is related to RREP_Ack being hop-by-hop and not end-to-end..=
..<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><br>
<br>
<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Either way, the parts of the specification that relat=
e to buffering contain a mixture of normative and non-normative verbiage (a l=
ot of "can" but also a lot of MUST/SHOULD) which I think could do with a tig=
htening up.&nbsp;<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><br>
<br>
<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">But....is buffering even something that should be spe=
cified by this document? It does not impact interoperability and it interfer=
es substantially with transport and congestion control, and I am not sure th=
at we understand the consequences
 (I am not convinced that the claims in the document on benefits to TCP are s=
ubstantiated or even true).<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><br>
<br>
<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">As I indicated, a complete review will follow, but I t=
hought that these was a global enough topics to call out and get engineered r=
ight.<u></u><u></u></p>
</div>
</div>
</div>
<div>
<p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Thomas<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">PS: I remain convinced that the security consideratio=
ns section is insufficient ; I will try to articulate my thoughts on why tha=
t is, but for starters looking at the recently raised (by somebody else, the=
 Chris replied) AODV security questions
 would probably be helpful<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><br>
On 10 Nov 2015, at 02:10, Ratliff, Stanley &lt;<a href=3D"mailto:sratliff@id=
irect.net" target=3D"_blank">sratliff@idirect.net</a>&gt; wrote:<u></u><u></=
u></p>
</div>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<div>
<p class=3D"MsoNormal">Hello WG participants =E2=80=93
<u></u><u></u></p>
<p class=3D"MsoNormal">&nbsp;<u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"text-autospace:none">
The above referenced drafts were posted Oct. 13 (for AODVv2), and Oct. 16 (D=
LEP). The co-authors and the chairs ask that you please take some time to re=
view and comment on the new submissions.
<u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"text-autospace:none">
&nbsp;<u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"text-autospace:none">
Regards,<u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"text-autospace:none">
Stan<u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"text-autospace:none">
&nbsp;<u></u><u></u></p>
<p class=3D"MsoNormal">&nbsp;<u></u><u></u></p>
</div>
<p class=3D"MsoNormal"><br>
<span style=3D"font-size:8.0pt;font-family:&quot;Arial&quot;,&quot;sans-seri=
f&quot;;color:#003366">_____________________________________________________=
<br>
This electronic message and any files transmitted with it contains<br>
information from iDirect, which may be privileged, proprietary<br>
and/or confidential. It is intended solely for the use of the individual<br>=

or entity to whom they are addressed. If you are not the original<br>
recipient or the person responsible for delivering the email to the<br>
intended recipient, be advised that you have received this email<br>
in error, and that any use, dissemination, forwarding, printing, or<br>
copying of this email is strictly prohibited. If you received this email<br>=

in error, please delete it and immediately notify the sender.<br>
_____________________________________________________</span> <u></u><u></u><=
/p>
</div>
</blockquote>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class=3D"MsoNormal">_______________________________________________<br>
manet mailing list<br>
<a href=3D"mailto:manet@ietf.org" target=3D"_blank">manet@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/manet" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/manet</a><u></u><u></u></p>
</div>
</blockquote>
</div>
</blockquote>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class=3D"MsoNormal">_______________________________________________<br>
manet mailing list<br>
<a href=3D"mailto:manet@ietf.org" target=3D"_blank">manet@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/manet" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/manet</a><u></u><u></u></p>
</div>
</blockquote>
</div>
</div>
</div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><br>
_______________________________________________<br>
manet mailing list<br>
<a href=3D"mailto:manet@ietf.org" target=3D"_blank">manet@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/manet" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/manet</a><u></u><u></u></p>
</div>
<p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p>
</div>
</div>
</div>
</div>
<p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p>
</div>
<p class=3D"MsoNormal">_______________________________________________<br>
manet mailing list<br>
<a href=3D"mailto:manet@ietf.org" target=3D"_blank">manet@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/manet" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/manet</a><u></u><u></u></p>
</div>
</blockquote>
</div>
<p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p>
</div>
</div>
<p>********************************************************************<br>
This email and any attachments are confidential to the intended<br>
recipient and may also be privileged. If you are not the intended<br>
recipient please delete it from your system and notify the sender.<br>
You should not copy it or use it for any purpose nor disclose or<br>
distribute its contents to any other person.<br>
********************************************************************</p>

</div></blockquote></div></div></div><br>___________________________________=
____________<br>
manet mailing list<br>
<a href=3D"mailto:manet@ietf.org">manet@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/manet" rel=3D"noreferrer" t=
arget=3D"_blank">https://www.ietf.org/mailman/listinfo/manet</a><br>
<br></blockquote></div><br></div>
</div></blockquote><blockquote type=3D"cite"><div><span>____________________=
___________________________</span><br><span>manet mailing list</span><br><sp=
an><a href=3D"mailto:manet@ietf.org">manet@ietf.org</a></span><br><span><a h=
ref=3D"https://www.ietf.org/mailman/listinfo/manet">https://www.ietf.org/mai=
lman/listinfo/manet</a></span><br></div></blockquote></body></html>=

--Apple-Mail-9C59CABF-82CB-4EE4-B752-471F22A5F9E5--


From nobody Thu Dec  3 14:10:50 2015
Return-Path: <yi.jiazi@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 255AF1ACE92 for <manet@ietfa.amsl.com>; Thu,  3 Dec 2015 14:10:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.077
X-Spam-Level: 
X-Spam-Status: No, score=-0.077 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, J_CHICKENPOX_35=0.6, J_CHICKENPOX_52=0.6, SPF_PASS=-0.001] autolearn=no
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 GCMewacSBXgo for <manet@ietfa.amsl.com>; Thu,  3 Dec 2015 14:10:42 -0800 (PST)
Received: from mail-wm0-x233.google.com (mail-wm0-x233.google.com [IPv6:2a00:1450:400c:c09::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 66AAC1ACE90 for <manet@ietf.org>; Thu,  3 Dec 2015 14:10:41 -0800 (PST)
Received: by wmec201 with SMTP id c201so48459454wme.0 for <manet@ietf.org>; Thu, 03 Dec 2015 14:10:39 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=yGZ5nbWeDWFb/bHgQw67BaGoB4GJEEzII67q7Nv8o04=; b=BliurH9bVov0N6ZXeUTdPyR2WXGOvNF9/tRcznllpb86KBgtTtVo+VA4jDkYjVf4eH 1ZdMpQqZAyYu3S7Lw+eWvPHMr6ItF5zQpbekw6jOq/ZQzfefbzYfbhdIxUXAxe2402Jk YzON2GgH+Rarmy8PKTuZI3+NqEAa1mmySdQbi6B34e1fOJX+FCYfXh6XSy2VOZvahETe 6aI1RIfVHeu55+nboPEyQMr8ohyNbmSu5+alE8x1DkDD+fJ3TyuIes21gx3I3o5YBB6m J2/IFe96WH/B+dGwfPiaUQmzcgqIBcfUNeYexiTrhOR3JJU0yjlNRyjoJnSVRHfFUmEU tj3w==
MIME-Version: 1.0
X-Received: by 10.194.111.199 with SMTP id ik7mr13773026wjb.167.1449180639803;  Thu, 03 Dec 2015 14:10:39 -0800 (PST)
Sender: yi.jiazi@gmail.com
Received: by 10.194.26.3 with HTTP; Thu, 3 Dec 2015 14:10:39 -0800 (PST)
In-Reply-To: <0E81A665-85F2-4358-A5E9-1151CCAB0E61@gmail.com>
References: <241ccb422cb941bda2617d7be275c649@VAUSDITCHM2.idirect.net> <9948DF10-0B9B-404E-BA09-C90CDE209756@thomasclausen.org> <DCC7ED56-7ED9-4610-91A0-3D70620B9823@gmail.com> <CAAePS4DtpBrWtgBbnWjLZN07mcyH=hmK0pzPvCrjwwLiTuXc2Q@mail.gmail.com> <CAAePS4AtbPekzU=m7aut08yHwZPmk-TiCdG4vvfNZtSWPowx=Q@mail.gmail.com> <8228CBB8-BCB5-4ED9-9E0C-F76CD63D2DFC@thomasclausen.org> <B31EEDDDB8ED7E4A93FDF12A4EECD30D7D76C1DB@GLKXM0002V.GREENLNK.net> <D2925838-C6F4-4E13-85F8-499651983056@thomasclausen.org> <CAN1bDFwtKOkA2-MWCk0gPHVJ9_eki2P2Rb5Gu4s65pKV1mKehA@mail.gmail.com> <0E81A665-85F2-4358-A5E9-1151CCAB0E61@gmail.com>
Date: Thu, 3 Dec 2015 23:10:39 +0100
X-Google-Sender-Auth: 7jywRE8LQNb7eGlO_GJVVZsr9wY
Message-ID: <CAN1bDFyEQkGr-vt+ngXt6V+21K6qiMv56FQu1boL=Ju+PQpqZQ@mail.gmail.com>
From: Jiazi YI <ietf@jiaziyi.com>
To: Christopher Dearlove <christopher.dearlove@gmail.com>
Content-Type: multipart/alternative; boundary=001a1130d0ea404083052605a96e
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/zXVqWPbunmEuCMOam1_76mywbNk>
Cc: "Dearlove, Christopher \(UK\)" <chris.dearlove@baesystems.com>, manet <manet@ietf.org>, Victoria Mercieca <vmercieca0@gmail.com>
Subject: Re: [manet] draft-ietf-manet-aodvv2-12 and draft-ietf-manet-dlep-17
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: <https://mailarchive.ietf.org/arch/browse/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: Thu, 03 Dec 2015 22:10:48 -0000

--001a1130d0ea404083052605a96e
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Sure. thanks for making it more precise :)

Jiazi



On Thu, Dec 3, 2015 at 10:53 PM, Christopher Dearlove <
christopher.dearlove@gmail.com> wrote:

> In OLSRv2 a compromised router can only speak for itself if ICVs are
> linked to specific routers. Use a shared secret key (as RFC 7183) then a
> compromised router can impersonate any router. draft-ietf-manet-ibs is
> however an example where it can't.
>
> --
> Christopher Dearlove
> christopher.dearlove@gmail.com (iPhone)
> chris@mnemosyne.demon.co.uk (home)
>
> On 3 Dec 2015, at 21:42, Jiazi YI <ietf@jiaziyi.com> wrote:
>
> I agree with Chris and Thomas on their concerns on the hop-by-hop securit=
y
> issue.
>
> This is very different from classical DV protocol, in which the vector
> information is designed to be exchanged between neighbours.
> In AODVv2, the RREQ/RREP/RERR are to be forwarded through multiple hops. =
A
> router can sign a message that isn't actually initialised by itself -- th=
is
> is, at least, against intuition.
>
> This can be an issue if we have compromised routers in the network. Of
> course, a compromised router is a problem for every protocol, like OLSRv2=
.
> But in OLSRv2, a compromised router can only speak on behalf of itself --
> however, in AODVv2, a compromised/mis-configured router can pretend to be
> any other router (for example, generate RREQ messages using another addre=
ss
> as OrigAddr).  The consequence will be much more serious if that happens.
>
> best
>
> Jiazi
>
>
> On Thu, Dec 3, 2015 at 2:53 PM, Thomas Heide Clausen <
> ietf@thomasclausen.org> wrote:
>
>> That is exactly the thing -  the trust model assumed (& the protocol
>> mechanics) need to be understood before designing the necessary MTI
>> security, and before deciding which bits (if any) from 7182 to use...
>>
>> Thomas
>>
>> On 3 d=C3=A9c. 2015, at 14:26, Dearlove, Christopher (UK) <
>> chris.dearlove@baesystems.com> wrote:
>>
>> If you go down this route of assuming transitive trust, then you might a=
s
>> well use 7182=E2=80=99s packet ICV and timestamp rather than message ICV=
 and
>> timestamp.
>>
>>
>>
>> There is a complication (mostly one of presentation) that the 5444
>> multiplexer (rather than AODVv2) needs to do this, at least for packets
>> containing AODVv2 messages (but at which point, probably all 5444 packet=
s).
>> So you either, depending on your point of view, need to request it to do
>> that, or (administratively) decline to operate except over a 5444
>> multiplexer that is doing this.
>>
>>
>>
>> The advantage is one of saved space and time when packets contain more
>> than one message. Plus slightly better protection (hop count and limit a=
re
>> covered) but which probably doesn=E2=80=99t matter here.
>>
>>
>>
>> If messages are changed/replaced on a one-to-one basis as forwarded, the=
n
>> the only solutions I can see are hop by hop transitive trust (packets or
>> messages per hop), or something complicated involving aggregation and
>> knowledge of changes. But the latter would be a research task to develop=
,
>> so let=E2=80=99s not try that.
>>
>>
>>
>>
>>
>> *From:* manet [mailto:manet-bounces@ietf.org <manet-bounces@ietf.org>] *=
On
>> Behalf Of *ietf@thomasclausen.org
>> *Sent:* 03 December 2015 12:22
>> *To:* Victoria Mercieca
>> *Cc:* manet
>> *Subject:* Re: [manet] draft-ietf-manet-aodvv2-12 and
>> draft-ietf-manet-dlep-17
>>
>>
>>
>> Dear Victoria,
>>
>>
>>
>> Responding twice to this email, intentionally as I want to address two
>> different aspects independently=E2=80=A6.
>>
>>
>>
>> On Nov 19, 2015, at 17:09, Victoria Mercieca <vmercieca0@gmail.com>
>> wrote:
>>
>>
>>
>>
>>
>> Hi Thomas and Christopher,
>>
>> Thank you for your comments.  If I may address just one point for
>> starters - regeneration vs forwarding. We use the term regeneration sinc=
e
>> forwarding seems inappropriate when the message content changes at each =
hop.
>>
>> The changes we make to the message content are:
>>
>> 1) We change the metric so that each router along the path learns a rout=
e
>> from the message, with the metric associated with the path up to that po=
int
>> 2) AckReq only applies between hops, so needs to be removed at each hop,
>> and a new AckReq element may need to be added for the next hop.
>> 3) ValidityTime could potentially be added by any intermediate router
>> that wishes to limit the time it will forward packets on the route.
>> 4) Stripping out Unreachable Addresses from RERR which did not affect ou=
r
>> route set.
>>
>> Can we really use the term "forwarding" if we are changing the metric
>> value, adding a validity time, adding/removing AckReq or removing addres=
ses
>> and their associated TLVs?
>>
>> OK, so assume that I understand regeneration as per my previous email, a=
s
>> meaning =E2=80=9Cgenerate a new message and send to my neighbors, based =
on what I
>> learned when processing a received message=E2=80=9D =E2=80=94 just like =
any distance vector
>> protocol does.
>>
>>
>>
>> In that model, what you write makes sense: each originator of a control
>> message (i.e., whoever generates or regenerates it) is free to include t=
he
>> information it desires, such as the 4 points you list above. No issues w=
ith
>> that.
>>
>>
>>
>> However, and this joins what I pointed out in a previous email, you writ=
e
>> in the applicability statement:
>>
>>
>>
>>    Providing security for a reactive routing protocol can be difficult.
>>
>>
>> While we can discuss if the nature of =E2=80=9Creactive routing protocol=
=E2=80=9D generates particular difficulties, we certainly can agree that th=
is protocol has the same =E2=80=9Cdifficulties=E2=80=9D as a distance vecto=
r protocol: routing topology information (by definition) not being exchange=
d end-to-end, but between neighbors (who do calculations and generate their=
 own announcements =E2=80=94 regeneration, as you call it).
>>
>>
>> This means that a specific security model of transitive trust must be as=
sumed, no? I trust Victoria, therefore when Victoria says =E2=80=9CStan tol=
d me=E2=80=9D then I trust that she actually verified that "it was indeed S=
tan who told her =E2=80=A6=E2=80=9D =E2=80=94 and either way, I have no way=
 of verifying?
>>
>>
>> I did not see the trust model / trust assumption discussed in the specif=
ication (specifically not in applicability and in section 13, both of where=
 it should be called out), but I think that this is actually a crucial poin=
t to get right, in order to approach developing the MTI security mechanisms=
.
>>
>>
>> Anyways, that observation actually contrasts strongly with what the appl=
icability statement then goes on to say, namely:
>>
>>
>>
>>    AODVv2 provides for message integrity and security against replay
>>
>>    attacks by using integrity check values, timestamps and sequence
>>
>>    numbers, as described in Section 13 <https://tools.ietf.org/html/draf=
t-ietf-manet-aodvv2-12#section-13>.
>>
>>
>> This is true only in as much as messages are indeed exchanged between ne=
ighbors: when you =E2=80=9Cregenerate=E2=80=9D a message, i.e., generate a =
new message in response to receipt of a message, you generate brand new pay=
load (but possibly including some of the data from the received message, of=
 course): thus, any ICVs =E2=80=9Cfrom farther away than the neighbor=E2=80=
=9D will be useless (or, if you zero out the parts that you change, these p=
arts will not be protected).
>>
>>
>> The above sentence, quoted from the applicability statement, and that wh=
ich transpires from section 13, seems - certainly, absent the trust model a=
ssumed - to suggest that end-to-end protection/validation is provided. But,=
 this is *not* the case.
>>
>>
>> Finally to the applicability statement, a question:
>>
>>
>>    If security associations can be
>>
>>    established, encryption can be used for AODVv2 messages to ensure
>>
>>    that only trusted routers participate in routing operations.
>>
>>
>>
>> What you want to say here is that =E2=80=9Cif all trusted routers have a=
 shared
>> secret, then we=E2=80=99re able to use that shared secret to ignore non-=
trusted
>> routers=E2=80=9D, right?
>>
>> While =E2=80=9Csecurity associations=E2=80=9D that do not pass through a=
 shared secret
>> probably can be thought up, it=E2=80=99s not trivial and I did not find =
any
>> discussion of that in the document?
>>
>>
>>
>> Having, on the topic of security, re-read Section 13, which starts:
>>
>>
>>
>>    This section describes various security considerations and potential
>>
>>    avenues to secure AODVv2 routing.
>>
>>
>>
>> While this is an honest description of what follows, I remain convinced
>> that this is not sufficient. So let me ask as precisely as I can:
>>
>>
>>
>>             o          what is the MTI security mechanism that a
>> conformant implementation must provide?
>>
>>                         Specifically:
>>
>>                                     -           which are the processing
>> steps (for example in section 7.2.1
>>
>>                                                 and section 7.2.2 for
>> RREP - and similarly for the other message
>>
>>                                                 types) that define that
>> security mechanism
>>
>>
>>
>>             o          what protection is offered by that MTI security
>> mechanism? And what remains
>>
>>                         vulnerable.
>>
>>
>>
>> If this specification targets std.track, then it should include
>> (reasonably solid, but definitely well specified) MTI security.
>>
>>
>>
>> Best
>>
>>
>>
>> Thomas
>>
>>
>>
>> Further, in reply to the comment about use of the msg-hop-count and
>> msg-hop-limit fields, I think it does not matter that a message only
>> travels one hop in that particular form, with that exact set of informat=
ion
>> enclosed. Hop limit and hop count are part of the message and used by th=
e
>> routing protocol, and so they refer to the multi-hop path that the AODVv=
2
>> message will follow, indicating when not to regenerate any further. So
>> AODVv2 uses these fields as suggested in RFC5444 Appendix B, to limit th=
e
>> number of hops across which it will regenerate a packet so as to "preven=
t
>> messages from endlessly circulating in a MANET".
>>
>> Kind regards,
>> Victoria.
>>
>>
>>
>> On Wed, Nov 18, 2015 at 8:49 AM, Christopher Dearlove <
>> christopher.dearlove@gmail.com> wrote:
>>
>> I've not had time to look at either yet, though I hope to review DLEP
>> very soon.
>>
>>
>>
>> But this has made me think about the RFC 6621 reference in AODVv2. It's
>> always been clear this has been rather a throwaway comment that needed
>> thought, but until now I hadn't really given it any.
>>
>>
>>
>> And it doesn't work. RFC 6621 is fundamentally unusable here. Let's
>> consider each on turn.
>>
>>
>>
>> AODVv2 is in the RFC 5444 structure. As has been noted on many occasions=
,
>> AOVDVv2 gets to use messages, but packets are not in its competence.
>>
>>
>>
>> RFC 6621 is about packets. But not even RFC 5444 packets but IP packets.
>> It's about whether or not to forward them. But RFC 5444 packets aren't j=
ust
>> not forwarded in unchanged IP packets, they aren't even forwarded at all=
.
>> They are each a single hop construct, and if a message is forwarded (whi=
ch
>> is by the routing protocol, as far as RFC 5444 is concerned, it's a new
>> message) it will be in a new packet, with possibly new companions.
>>
>>
>>
>> If AODVv2 wants to use a more efficient flooding process, it needs one a=
t
>> the message level. Now an example of that exists - the mechanism on RFC
>> 7181. Unfortunately we didn't break that out as a separate draft (we wou=
ld
>> have liked to, but there were reasons we didn't).
>>
>>
>>
>> And even if (by reference or other means) it were used - or some related
>> mechanism such as a CDS - that processing/forwarding mechanism assumes y=
ou
>> have defined MPRs (or similarly, that you have defined a CDS). And that
>> needs a local exchange of information, such as NHDP's HELLO messages (an=
d
>> the rest of NHDP) augmented with RFC 7181's MPR TLV (though only the
>> flooding bit is needed).
>>
>>
>>
>> In other words, taking some real work to define. And also raising a
>> question for the WG - why do we want a reactive protocol? The main
>> attraction as I see it is the "if you're not doing anything, you're not
>> transmitting" property. Which adding this voids. Of course maybe the WG
>> doesn't value that. Or it is acceptable as an option. But if so it needs=
 to
>> be an option that all routers use, or none. And if all, compatibly. (MPR
>> flooding allows different MPR selection algorithms - but only as long as
>> they satisfy the fundamental MPR algorithm properties.)
>>
>>
>>
>> In short, RFC 6621 must go. The alternative is nothing, or significant
>> work.
>>
>> --
>>
>> Christopher Dearlove
>>
>> christopher.dearlove@gmail.com (iPhone)
>>
>> chris@mnemosyne.demon.co.uk (home)
>>
>>
>> On 18 Nov 2015, at 01:35, Thomas Clausen <ietf@thomasclausen.org> wrote:
>>
>> Dear all,
>>
>>
>>
>> I have started looking through the recently
>> updated draft-ietf-manet-aodvv2-12. A lot has changed, and I regret not =
to
>> have had a blow-by-bow comeback to the previous review comments  - would
>> have made it a somewhat easier task to check if all have been addressed =
or
>> not.
>>
>>
>>
>> But, I will work through it and produce a detailed review - but from my
>> first quick read-through there're a couple of issue that jumped at me as
>> worth bringing forward on a more global level already.
>>
>>
>>
>> The first relates to  how RREQs are forwarded -- or, more generally, are
>> not.
>>
>>
>>
>> The protocol currently talks about "message is regenerated" rather than
>> "forwarded". I have understood that this means that a RREQ is actually n=
ot
>> an "end to end" entity, but is a "hop by hop" entity.
>>
>>
>>
>> First, that is a curious design choice, is there any reason why this is
>> so considered?
>>
>>
>>
>> Second, if a RREQ message is hop-by-hop only, then I do not think that
>> the use of the RFC5444 hop-limit/hop-count fields is appropriate.
>>
>>
>>
>> Third, the statement in section 6.5 on the use of RFC6621 is incorrect i=
n
>> two ways: RFC6621 does specify how messages are *forwarded* (but, as
>> discussed above, you are not forwarding messages).
>>
>>
>>
>> More seriously, this paragraph is incorrect:
>>
>>
>>
>> "Implementations MAY choose to employ techniques to reduce the number of=
 multicast messages sent. Use of [RFC6621 <https://tools.ietf.org/html/rfc6=
621>] in deployments is recommended. Employing [RFC6621 <https://tools.ietf=
.org/html/rfc6621>] in a subset of the operational AODVv2 routers in a netw=
ork, or configuring different algorithms on different routers, will not cau=
se interoperability issues, but will reduce the effectiveness of the multic=
ast reduction scheme."
>>
>>
>>
>> Different routers using different relay selection algorithms in the same
>> network will not *just* cause loss of efficiency, but *will* cause
>> interoperability issues.
>>
>>
>>
>> For example if "router A" decides to suppress its message relaying
>> because it estimates that "router B" provides sufficient coverage - and
>> conversely "router B" suppresses relaying for the same reason: neither A
>> nor B would relay, and so any routers reachable only via A and B would n=
ot
>> be covered.
>>
>>
>>
>> This is not a far-sought example: it can be as simple as A and B simply
>> using self-selecting relay algorithms with different tie-breakers.
>>
>>
>>
>> In short: I think that the whole message flooding/regeneration part
>> requires serious work.
>>
>>
>>
>> The second issue is that I also suspect that there is some issue with
>> buffering, or rather with how it is specified; starting in section 6.6, =
I
>> am not sure that leaving that as "a matter of policy at each router" is
>> entirely right.
>>
>>
>>
>> Also on buffering, I am wondering if the "start delivering buffered
>> packets" conditions (penultimate paragraph in 6.6, and of course through
>> the processing sections) is sufficient; I suspect that the condition "Wh=
en
>> a valid route is installed" is not sufficient - that there are situation=
s
>> where a routing table entry is installed, but the complete route is not
>> available or is not bidirectional?This obviously is related to RREP_Ack
>> being hop-by-hop and not end-to-end....
>>
>>
>>
>> Either way, the parts of the specification that relate to buffering
>> contain a mixture of normative and non-normative verbiage (a lot of "can=
"
>> but also a lot of MUST/SHOULD) which I think could do with a tightening =
up.
>>
>>
>>
>> But....is buffering even something that should be specified by this
>> document? It does not impact interoperability and it interferes
>> substantially with transport and congestion control, and I am not sure t=
hat
>> we understand the consequences (I am not convinced that the claims in th=
e
>> document on benefits to TCP are substantiated or even true).
>>
>>
>>
>> As I indicated, a complete review will follow, but I thought that these
>> was a global enough topics to call out and get engineered right.
>>
>>
>>
>> Thomas
>>
>>
>>
>> PS: I remain convinced that the security considerations section is
>> insufficient ; I will try to articulate my thoughts on why that is, but =
for
>> starters looking at the recently raised (by somebody else, the Chris
>> replied) AODV security questions would probably be helpful
>>
>>
>> On 10 Nov 2015, at 02:10, Ratliff, Stanley <sratliff@idirect.net> wrote:
>>
>> Hello WG participants =E2=80=93
>>
>>
>>
>> The above referenced drafts were posted Oct. 13 (for AODVv2), and Oct. 1=
6
>> (DLEP). The co-authors and the chairs ask that you please take some time=
 to
>> review and comment on the new submissions.
>>
>>
>>
>> Regards,
>>
>> Stan
>>
>>
>>
>>
>>
>>
>> _____________________________________________________
>> This electronic message and any files transmitted with it contains
>> information from iDirect, which may be privileged, proprietary
>> and/or confidential. It is intended solely for the use of the individual
>> or entity to whom they are addressed. If you are not the original
>> recipient or the person responsible for delivering the email to the
>> intended recipient, be advised that you have received this email
>> in error, and that any use, dissemination, forwarding, printing, or
>> copying of this email is strictly prohibited. If you received this email
>> in error, please delete it and immediately notify the sender.
>> _____________________________________________________
>>
>> _______________________________________________
>> manet mailing list
>> manet@ietf.org
>> https://www.ietf.org/mailman/listinfo/manet
>>
>> _______________________________________________
>> manet mailing list
>> manet@ietf.org
>> https://www.ietf.org/mailman/listinfo/manet
>>
>>
>> _______________________________________________
>> manet mailing list
>> manet@ietf.org
>> https://www.ietf.org/mailman/listinfo/manet
>>
>>
>>
>>
>>
>> _______________________________________________
>> 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.
>> ********************************************************************
>>
>>
>> _______________________________________________
>> manet mailing list
>> manet@ietf.org
>> https://www.ietf.org/mailman/listinfo/manet
>>
>>
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www.ietf.org/mailman/listinfo/manet
>
>

--001a1130d0ea404083052605a96e
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Sure. thanks for making it more precise :)</div><div>=
<br></div><div>Jiazi</div><div><div><br></div><div><br></div></div></div><d=
iv class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Thu, Dec 3, 2015=
 at 10:53 PM, Christopher Dearlove <span dir=3D"ltr">&lt;<a href=3D"mailto:=
christopher.dearlove@gmail.com" target=3D"_blank">christopher.dearlove@gmai=
l.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"m=
argin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir=3D"a=
uto"><div>In OLSRv2 a compromised router can only speak for itself if ICVs =
are linked to specific routers. Use a shared secret key (as RFC 7183) then =
a compromised router can impersonate any router. draft-ietf-manet-ibs is ho=
wever an example where it can&#39;t.<span class=3D""><br><br>-- =C2=A0<div>=
Christopher Dearlove</div><div><a href=3D"mailto:christopher.dearlove@gmail=
.com" target=3D"_blank">christopher.dearlove@gmail.com</a> (iPhone)</div><d=
iv><a href=3D"mailto:chris@mnemosyne.demon.co.uk" target=3D"_blank">chris@m=
nemosyne.demon.co.uk</a> (home)</div></span></div><div><div class=3D"h5"><d=
iv><br>On 3 Dec 2015, at 21:42, Jiazi YI &lt;<a href=3D"mailto:ietf@jiaziyi=
.com" target=3D"_blank">ietf@jiaziyi.com</a>&gt; wrote:<br><br></div><block=
quote type=3D"cite"><div><div dir=3D"ltr">I agree with Chris and Thomas on =
their concerns on the hop-by-hop security issue.=C2=A0<div><br></div><div>T=
his is very different from classical DV protocol, in which the vector infor=
mation is designed to be exchanged between neighbours.=C2=A0</div><div>In A=
ODVv2, the RREQ/RREP/RERR are to be forwarded through multiple hops. A rout=
er can sign a message that isn&#39;t actually initialised by itself -- this=
 is, at least, against intuition.=C2=A0</div><div><br></div><div>This can b=
e an issue if we have compromised routers in the network. Of course, a comp=
romised router is a problem for every protocol, like OLSRv2. But in OLSRv2,=
 a compromised router can only speak on behalf of itself -- however, in AOD=
Vv2, a compromised/mis-configured router can pretend to be any other router=
 (for example, generate RREQ messages using another address as OrigAddr).=
=C2=A0 The consequence will be much more serious if that happens.=C2=A0</di=
v><div><br></div><div>best</div><div><br></div><div>Jiazi</div><div><br></d=
iv></div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Thu, =
Dec 3, 2015 at 2:53 PM, Thomas Heide Clausen <span dir=3D"ltr">&lt;<a href=
=3D"mailto:ietf@thomasclausen.org" target=3D"_blank">ietf@thomasclausen.org=
</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin=
:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir=3D"auto">=
<div>That is exactly the thing - =C2=A0the trust model assumed (&amp; the p=
rotocol mechanics) need to be understood before designing the necessary MTI=
 security, and before deciding which bits (if any) from 7182 to use...<span=
><font color=3D"#888888"><br><br></font></span></div><span><font color=3D"#=
888888"><div>Thomas</div></font></span><div><div><div><br>On 3 d=C3=A9c. 20=
15, at 14:26, Dearlove, Christopher (UK) &lt;<a href=3D"mailto:chris.dearlo=
ve@baesystems.com" target=3D"_blank">chris.dearlove@baesystems.com</a>&gt; =
wrote:<br><br></div><blockquote type=3D"cite"><div>






<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">If you go down this route=
 of assuming transitive trust, then you might as well use 7182=E2=80=99s pa=
cket ICV and timestamp rather than message ICV and timestamp.<u></u><u></u>=
</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=C2=A0<u></u></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">There is a complication (=
mostly one of presentation) that the 5444 multiplexer (rather than AODVv2) =
needs to do this, at least for packets containing AODVv2
 messages (but at which point, probably all 5444 packets). So you either, d=
epending on your point of view, need to request it to do that, or (administ=
ratively) decline to operate except over a 5444 multiplexer that is doing t=
his.<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=C2=A0<u></u></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">The advantage is one of s=
aved space and time when packets contain more than one message. Plus slight=
ly better protection (hop count and limit are covered) but
 which probably doesn=E2=80=99t matter here.<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=C2=A0<u></u></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">If messages are changed/r=
eplaced on a one-to-one basis as forwarded, then the only solutions I can s=
ee are hop by hop transitive trust (packets or messages
 per hop), or something complicated involving aggregation and knowledge of =
changes. But the latter would be a research task to develop, so let=E2=80=
=99s not try that.<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=C2=A0<u></u></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=C2=A0<u></u></spa=
n></p>
<div>
<div style=3D"border:none;border-top:solid #b5c4df 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal"><b><span lang=3D"EN-US" style=3D"font-size:10.0pt;fo=
nt-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span =
lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&qu=
ot;sans-serif&quot;"> manet [<a href=3D"mailto:manet-bounces@ietf.org" targ=
et=3D"_blank">mailto:manet-bounces@ietf.org</a>]
<b>On Behalf Of </b><a href=3D"mailto:ietf@thomasclausen.org" target=3D"_bl=
ank">ietf@thomasclausen.org</a><br>
<b>Sent:</b> 03 December 2015 12:22<br>
<b>To:</b> Victoria Mercieca<br>
<b>Cc:</b> manet<br>
<b>Subject:</b> Re: [manet] draft-ietf-manet-aodvv2-12 and draft-ietf-manet=
-dlep-17<u></u><u></u></span></p>
</div>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<p class=3D"MsoNormal">Dear Victoria,<u></u><u></u></p>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Responding twice to this email, intentionally as I w=
ant to address two different aspects independently=E2=80=A6.<u></u><u></u><=
/p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<div>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class=3D"MsoNormal">On Nov 19, 2015, at 17:09, Victoria Mercieca &lt;<a =
href=3D"mailto:vmercieca0@gmail.com" target=3D"_blank">vmercieca0@gmail.com=
</a>&gt; wrote:<u></u><u></u></p>
</div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<div>
<div>
<p class=3D"MsoNormal">Hi Thomas and Christopher,<u></u><u></u></p>
<p class=3D"MsoNormal">Thank you for your comments.=C2=A0 If I may address =
just one point for starters - regeneration vs forwarding. We use the term r=
egeneration since forwarding seems inappropriate when the
 message content changes at each hop.<u></u><u></u></p>
<p class=3D"MsoNormal">The changes we make to the message content are:<u></=
u><u></u></p>
<p class=3D"MsoNormal">1) We change the metric so that each router along th=
e path learns a route from the message, with the metric associated with the=
 path up to that point<br>
2) AckReq only applies between hops, so needs to be removed at each hop, an=
d a new AckReq element may need to be added for the next hop.<br>
3) ValidityTime could potentially be added by any intermediate router that =
wishes to limit the time it will forward packets on the route.<br>
4) Stripping out Unreachable Addresses from RERR which did not affect our r=
oute set.<u></u><u></u></p>
<p class=3D"MsoNormal">Can we really use the term &quot;forwarding&quot; if=
 we are changing the metric value, adding a validity time, adding/removing =
AckReq or removing addresses and their associated TLVs?<u></u><u></u></p>
</div>
</div>
</div>
</div>
</blockquote>
<p class=3D"MsoNormal">OK, so assume that I understand regeneration as per =
my previous email, as meaning =E2=80=9Cgenerate a new message and send to m=
y neighbors, based on what I learned when processing a received message=E2=
=80=9D =E2=80=94 just like any distance vector protocol does.<u></u><u></u>=
</p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">In that model, what you write makes sense: each orig=
inator of a control message (i.e., whoever generates or regenerates it) is =
free to include the information it desires, such as the 4 points you list a=
bove. No issues with that.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">However, and this joins what I pointed out in a prev=
ious email, you write in the applicability statement:<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<pre>=C2=A0=C2=A0 Providing security for a reactive routing protocol can be=
 difficult.<u></u><u></u></pre>
<span style=3D"font-size:9.0pt;font-family:&quot;Helvetica&quot;,&quot;sans=
-serif&quot;"><br clear=3D"all">
</span>
<pre><span style=3D"font-family:&quot;Helvetica&quot;,&quot;sans-serif&quot=
;">While we can discuss if the nature of=C2=A0=E2=80=9Creactive routing pro=
tocol=E2=80=9D generates particular difficulties, we certainly can agree th=
at this protocol has the same=C2=A0=E2=80=9Cdifficulties=E2=80=9D as a dist=
ance vector protocol: routing=C2=A0topology information (by definition) not=
 being exchanged end-to-end, but between neighbors (who do=C2=A0calculation=
s and generate their own announcements=C2=A0=E2=80=94 regeneration, as you =
call it).=C2=A0</span><u></u><u></u></pre>
<span style=3D"font-size:10.0pt;font-family:&quot;Helvetica&quot;,&quot;san=
s-serif&quot;"><br clear=3D"all">
</span>
<pre><span style=3D"font-family:&quot;Helvetica&quot;,&quot;sans-serif&quot=
;">This means that a specific security model of transitive trust must be as=
sumed, no? I trust Victoria,=C2=A0therefore when Victoria says=C2=A0=E2=80=
=9CStan told me=E2=80=9D=C2=A0then I trust that she=C2=A0actually verified =
that &quot;it was indeed Stan who told her=C2=A0=E2=80=A6=E2=80=9D=C2=A0=E2=
=80=94 and either way, I have no way of verifying?</span><u></u><u></u></pr=
e>
<span style=3D"font-size:10.0pt;font-family:&quot;Helvetica&quot;,&quot;san=
s-serif&quot;"><br clear=3D"all">
</span>
<pre><span style=3D"font-family:&quot;Helvetica&quot;,&quot;sans-serif&quot=
;">I did not see the trust model / trust assumption discussed in the specif=
ication (specifically not in applicability and in section 13, both of where=
 it should be called out), but I think that this is actually a crucial poin=
t to get right, in order to approach developing the MTI security mechanisms=
.</span><u></u><u></u></pre>
<span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;"><br cl=
ear=3D"all">
</span>
<pre><span style=3D"font-family:&quot;Helvetica&quot;,&quot;sans-serif&quot=
;">Anyways, that observation actually contrasts strongly with what the appl=
icability statement then goes on to say, namely:</span><u></u><u></u></pre>
<pre><u></u>=C2=A0<u></u></pre>
<pre>=C2=A0=C2=A0 AODVv2 provides for message integrity and security agains=
t replay<u></u><u></u></pre>
<pre>=C2=A0=C2=A0 attacks by using integrity check values, timestamps and s=
equence<u></u><u></u></pre>
<pre>=C2=A0=C2=A0 numbers, as described in <a href=3D"https://tools.ietf.or=
g/html/draft-ietf-manet-aodvv2-12#section-13" target=3D"_blank">Section 13<=
/a><span style=3D"font-size:12.0pt">.</span><u></u><u></u></pre>
<span style=3D"font-size:12.0pt;font-family:&quot;Courier New&quot;"><br cl=
ear=3D"all">
</span>
<pre><span style=3D"font-family:&quot;Helvetica&quot;,&quot;sans-serif&quot=
;">This is true only in as much as messages are indeed exchanged between ne=
ighbors: when you=C2=A0=E2=80=9Cregenerate=E2=80=9D a message, i.e., genera=
te a new=C2=A0message in response to receipt of a message, you generate bra=
nd new payload (but possibly including some of=C2=A0the data from the recei=
ved message, of course): thus, any ICVs=C2=A0=E2=80=9Cfrom farther away tha=
n the neighbor=E2=80=9D=C2=A0will be useless (or, if you zero out the parts=
 that you change, these parts will not be protected).</span><u></u><u></u><=
/pre>
<span style=3D"font-size:10.0pt;font-family:&quot;Helvetica&quot;,&quot;san=
s-serif&quot;"><br clear=3D"all">
</span>
<pre><span style=3D"font-family:&quot;Helvetica&quot;,&quot;sans-serif&quot=
;">The above sentence, quoted from the applicability statement, and that wh=
ich transpires from section 13, seems - certainly, absent the trust model a=
ssumed - to suggest that end-to-end protection/validation is provided. But,=
 this is <b><u>not</u></b> the case.</span><u></u><u></u></pre>
<span style=3D"font-size:10.0pt;font-family:&quot;Helvetica&quot;,&quot;san=
s-serif&quot;"><br clear=3D"all">
</span>
<pre><span style=3D"font-family:&quot;Helvetica&quot;,&quot;sans-serif&quot=
;">Finally to the applicability statement, a question:</span><u></u><u></u>=
</pre>
<span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;"><br cl=
ear=3D"all">
</span>
<pre><span style=3D"font-size:12.0pt">=C2=A0=C2=A0 If security associations=
 can be<u></u><u></u></span></pre>
<pre><span style=3D"font-size:12.0pt">=C2=A0=C2=A0 established, encryption =
can be used for AODVv2 messages to ensure<u></u><u></u></span></pre>
<pre><span style=3D"font-size:12.0pt">=C2=A0 =C2=A0that only trusted router=
s participate in routing operations.</span><u></u><u></u></pre>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
</div>
<div>
<p class=3D"MsoNormal">What you want to say here is that =E2=80=9Cif all tr=
usted routers have a shared secret, then we=E2=80=99re able to use that sha=
red secret to ignore non-trusted routers=E2=80=9D, right?=C2=A0<u></u><u></=
u></p>
</div>
<div>
<p class=3D"MsoNormal">While =E2=80=9Csecurity associations=E2=80=9D that d=
o not pass through a shared secret probably can be thought up, it=E2=80=99s=
 not trivial and I did not find any discussion of that in the document?<u><=
/u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Having, on the topic of security, re-read Section 13=
, which starts:<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<pre>=C2=A0=C2=A0 This section describes various security considerations an=
d potential<u></u><u></u></pre>
<pre>=C2=A0=C2=A0 avenues to secure AODVv2 routing.=C2=A0 <u></u><u></u></p=
re>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
</div>
<div>
<p class=3D"MsoNormal">While this is an honest description of what follows,=
 I remain convinced that this is not sufficient. So let me ask as precisely=
 as I can:<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><span>=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0 </span>o<span>=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0
</span>what is the MTI security mechanism that a conformant implementation =
must provide?=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><span>=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0 </span>
Specifically:<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><span>=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0
</span>-<span>=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 =
</span>which are the processing steps (for example in section 7.2.1=C2=A0<u=
></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><span>=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0
</span>and section 7.2.2 for RREP - and similarly for the other message=C2=
=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><span>=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0
</span>types) that define that security mechanism<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><span>=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0 </span>o<span>=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0
</span>what protection is offered by that MTI security mechanism? And what =
remains<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><span>=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0 </span>
vulnerable.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">If this specification targets std.track, then it sho=
uld include (reasonably solid, but definitely well specified) MTI security.=
<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Best<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Thomas<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<div>
<div>
<div>
<p class=3D"MsoNormal">Further, in reply to the comment about use of the ms=
g-hop-count and msg-hop-limit fields, I think it does not matter that a mes=
sage only travels one hop in that particular form,
 with that exact set of information enclosed. Hop limit and hop count are p=
art of the message and used by the routing protocol, and so they refer to t=
he multi-hop path that the AODVv2 message will follow, indicating when not =
to regenerate any further. So AODVv2
 uses these fields as suggested in RFC5444 Appendix B, to limit the number =
of hops across which it will regenerate a packet so as to &quot;prevent mes=
sages from endlessly circulating in a MANET&quot;.
<u></u><u></u></p>
<p class=3D"MsoNormal">Kind regards,<br>
Victoria.<u></u><u></u></p>
</div>
<div>
<div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<div>
<p class=3D"MsoNormal">On Wed, Nov 18, 2015 at 8:49 AM, Christopher Dearlov=
e &lt;<a href=3D"mailto:christopher.dearlove@gmail.com" target=3D"_blank">c=
hristopher.dearlove@gmail.com</a>&gt; wrote:<u></u><u></u></p>
<div>
<div>
<p class=3D"MsoNormal">I&#39;ve not had time to look at either yet, though =
I hope to review DLEP very soon.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">But this has made me think about the RFC 6621 refere=
nce in AODVv2. It&#39;s always been clear this has been rather a throwaway =
comment that needed thought, but until now I hadn&#39;t really given it any=
.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">And it doesn&#39;t work. RFC 6621 is fundamentally u=
nusable here. Let&#39;s consider each on turn.=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">AODVv2 is in the RFC 5444 structure. As has been not=
ed on many occasions, AOVDVv2 gets to use messages, but packets are not in =
its competence.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">RFC 6621 is about packets. But not even RFC 5444 pac=
kets but IP packets. It&#39;s about whether or not to forward them. But RFC=
 5444 packets aren&#39;t just not forwarded in unchanged IP packets, they a=
ren&#39;t even forwarded at all. They are each
 a single hop construct, and if a message is forwarded (which is by the rou=
ting protocol, as far as RFC 5444 is concerned, it&#39;s a new message) it =
will be in a new packet, with possibly new companions.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">If AODVv2 wants to use a more efficient flooding pro=
cess, it needs one at the message level. Now an example of that exists - th=
e mechanism on RFC 7181. Unfortunately we didn&#39;t break that out as a se=
parate draft (we would have liked to,
 but there were reasons we didn&#39;t).<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">And even if (by reference or other means) it were us=
ed - or some related mechanism such as a CDS - that processing/forwarding m=
echanism assumes you have defined MPRs (or similarly, that you have defined=
 a CDS). And that needs a local exchange
 of information, such as NHDP&#39;s HELLO messages (and the rest of NHDP) a=
ugmented with RFC 7181&#39;s MPR TLV (though only the flooding bit is neede=
d).<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">In other words, taking some real work to define. And=
 also raising a question for the WG - why do we want a reactive protocol? T=
he main attraction as I see it is the &quot;if you&#39;re not doing anythin=
g, you&#39;re not transmitting&quot; property. Which
 adding this voids. Of course maybe the WG doesn&#39;t value that. Or it is=
 acceptable as an option. But if so it needs to be an option that all route=
rs use, or none. And if all, compatibly. (MPR flooding allows different MPR=
 selection algorithms - but only as
 long as they satisfy the fundamental MPR algorithm properties.)<u></u><u><=
/u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">In short, RFC 6621 mu=
st go. The alternative is nothing, or significant work.<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">-- =C2=A0<span style=3D"color:#888888"><u></u><u></u=
></span></p>
<div>
<p class=3D"MsoNormal"><span style=3D"color:#888888">Christopher Dearlove<u=
></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"color:#888888"><a href=3D"mailto:chri=
stopher.dearlove@gmail.com" target=3D"_blank">christopher.dearlove@gmail.co=
m</a> (iPhone)<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"color:#888888"><a href=3D"mailto:chri=
s@mnemosyne.demon.co.uk" target=3D"_blank">chris@mnemosyne.demon.co.uk</a> =
(home)<u></u><u></u></span></p>
</div>
</div>
</div>
<div>
<div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><br>
On 18 Nov 2015, at 01:35, Thomas Clausen &lt;<a href=3D"mailto:ietf@thomasc=
lausen.org" target=3D"_blank">ietf@thomasclausen.org</a>&gt; wrote:<u></u><=
u></u></p>
</div>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<div>
<p class=3D"MsoNormal">Dear all,<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">I have started looking through the recently updated=
=C2=A0draft-ietf-manet-aodvv2-12. A lot has changed, and I regret not to ha=
ve had a blow-by-bow comeback to the previous review comments =C2=A0- would=
 have made it a somewhat easier task to check
 if all have been addressed or not.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">But, I will work through it and produce a detailed r=
eview - but from my first quick read-through there&#39;re a couple of issue=
 that jumped at me as worth bringing forward on a more global level already=
.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">The first relates to =C2=A0how RREQs are forwarded -=
- or, more generally, are not.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">The protocol currently talks about &quot;message is =
regenerated&quot; rather than &quot;forwarded&quot;. I have understood that=
 this means that a RREQ is actually not an &quot;end to end&quot; entity, b=
ut is a &quot;hop by hop&quot; entity.=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">First, that is a curious design choice, is there any=
 reason why this is so considered?<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Second, if a RREQ message is hop-by-hop only, then I=
 do not think that the use of the RFC5444 hop-limit/hop-count fields is app=
ropriate.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Third, the statement in section 6.5 on the use of RF=
C6621 is incorrect in two ways: RFC6621 does specify how messages are *forw=
arded* (but, as discussed above, you are not forwarding messages).<u></u><u=
></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">More seriously, this paragraph is incorrect:<u></u><=
u></u></p>
</div>
<div>
<pre><span style=3D"font-family:&quot;UICTFontTextStyleTallBody&quot;,&quot=
;serif&quot;"><br><br></span><u></u><u></u></pre>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<pre><span style=3D"font-family:&quot;UICTFontTextStyleTallBody&quot;,&quot=
;serif&quot;">&quot;Implementations MAY choose to employ techniques to redu=
ce the number of multicast messages sent. Use of [<a href=3D"https://tools.=
ietf.org/html/rfc6621" title=3D"&quot;Simplified Multicast Forwarding&quot;=
" target=3D"_blank">RFC6621</a>] in deployments is recommended. Employing [=
<a href=3D"https://tools.ietf.org/html/rfc6621" title=3D"&quot;Simplified M=
ulticast Forwarding&quot;" target=3D"_blank">RFC6621</a>] in a subset of th=
e operational AODVv2 routers in a network, or configuring different algorit=
hms on different routers, will not cause interoperability issues, but will =
reduce the effectiveness of the multicast reduction scheme.&quot;</span><sp=
an style=3D"font-size:14.5pt"><u></u><u></u></span></pre>
</blockquote>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Different routers using different relay selection al=
gorithms in the same network will not *just* cause loss of efficiency, but =
*will* cause interoperability issues.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">For example if &quot;router A&quot; decides to suppr=
ess its message relaying because it estimates that &quot;router B&quot; pro=
vides sufficient coverage - and conversely &quot;router B&quot; suppresses =
relaying for the same reason: neither A nor B would relay, and so
 any routers reachable only via A and B would not be covered.<u></u><u></u>=
</p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">This is not a far-sought example: it can be as simpl=
e as A and B simply using self-selecting relay algorithms with different ti=
e-breakers.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">In short: I think that the whole message flooding/re=
generation part requires serious work.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<div>
<p class=3D"MsoNormal">The second issue is that I also suspect that there i=
s some issue with buffering, or rather with how it is specified; starting i=
n section 6.6, I am not sure that leaving that as &quot;a matter of policy =
at each router&quot; is entirely right.=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><br>
<br>
<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Also on buffering, I am wondering if the &quot;start=
 delivering buffered packets&quot; conditions (penultimate paragraph in 6.6=
, and of course through the processing sections) is sufficient; I suspect t=
hat the condition &quot;When a valid route is installed&quot;
 is not sufficient - that there are situations where a routing table entry =
is installed, but the complete route is not available or is not bidirection=
al?This obviously is related to RREP_Ack being hop-by-hop and not end-to-en=
d....<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><br>
<br>
<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Either way, the parts of the specification that rela=
te to buffering contain a mixture of normative and non-normative verbiage (=
a lot of &quot;can&quot; but also a lot of MUST/SHOULD) which I think could=
 do with a tightening up.=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><br>
<br>
<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">But....is buffering even something that should be sp=
ecified by this document? It does not impact interoperability and it interf=
eres substantially with transport and congestion control, and I am not sure=
 that we understand the consequences
 (I am not convinced that the claims in the document on benefits to TCP are=
 substantiated or even true).<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><br>
<br>
<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">As I indicated, a complete review will follow, but I=
 thought that these was a global enough topics to call out and get engineer=
ed right.<u></u><u></u></p>
</div>
</div>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Thomas<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">PS: I remain convinced that the security considerati=
ons section is insufficient ; I will try to articulate my thoughts on why t=
hat is, but for starters looking at the recently raised (by somebody else, =
the Chris replied) AODV security questions
 would probably be helpful<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><br>
On 10 Nov 2015, at 02:10, Ratliff, Stanley &lt;<a href=3D"mailto:sratliff@i=
direct.net" target=3D"_blank">sratliff@idirect.net</a>&gt; wrote:<u></u><u>=
</u></p>
</div>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<div>
<p class=3D"MsoNormal">Hello WG participants =E2=80=93
<u></u><u></u></p>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"text-autospace:none">
The above referenced drafts were posted Oct. 13 (for AODVv2), and Oct. 16 (=
DLEP). The co-authors and the chairs ask that you please take some time to =
review and comment on the new submissions.
<u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"text-autospace:none">
=C2=A0<u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"text-autospace:none">
Regards,<u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"text-autospace:none">
Stan<u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"text-autospace:none">
=C2=A0<u></u><u></u></p>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
</div>
<p class=3D"MsoNormal"><br>
<span style=3D"font-size:8.0pt;font-family:&quot;Arial&quot;,&quot;sans-ser=
if&quot;;color:#003366">___________________________________________________=
__<br>
This electronic message and any files transmitted with it contains<br>
information from iDirect, which may be privileged, proprietary<br>
and/or confidential. It is intended solely for the use of the individual<br=
>
or entity to whom they are addressed. If you are not the original<br>
recipient or the person responsible for delivering the email to the<br>
intended recipient, be advised that you have received this email<br>
in error, and that any use, dissemination, forwarding, printing, or<br>
copying of this email is strictly prohibited. If you received this email<br=
>
in error, please delete it and immediately notify the sender.<br>
_____________________________________________________</span> <u></u><u></u>=
</p>
</div>
</blockquote>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class=3D"MsoNormal">_______________________________________________<br>
manet mailing list<br>
<a href=3D"mailto:manet@ietf.org" target=3D"_blank">manet@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/manet" target=3D"_blank">h=
ttps://www.ietf.org/mailman/listinfo/manet</a><u></u><u></u></p>
</div>
</blockquote>
</div>
</blockquote>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class=3D"MsoNormal">_______________________________________________<br>
manet mailing list<br>
<a href=3D"mailto:manet@ietf.org" target=3D"_blank">manet@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/manet" target=3D"_blank">h=
ttps://www.ietf.org/mailman/listinfo/manet</a><u></u><u></u></p>
</div>
</blockquote>
</div>
</div>
</div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><br>
_______________________________________________<br>
manet mailing list<br>
<a href=3D"mailto:manet@ietf.org" target=3D"_blank">manet@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/manet" target=3D"_blank">h=
ttps://www.ietf.org/mailman/listinfo/manet</a><u></u><u></u></p>
</div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
</div>
</div>
</div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<p class=3D"MsoNormal">_______________________________________________<br>
manet mailing list<br>
<a href=3D"mailto:manet@ietf.org" target=3D"_blank">manet@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/manet" target=3D"_blank">h=
ttps://www.ietf.org/mailman/listinfo/manet</a><u></u><u></u></p>
</div>
</blockquote>
</div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
</div>
<p>********************************************************************<br>
This email and any attachments are confidential to the intended<br>
recipient and may also be privileged. If you are not the intended<br>
recipient please delete it from your system and notify the sender.<br>
You should not copy it or use it for any purpose nor disclose or<br>
distribute its contents to any other person.<br>
********************************************************************</p>

</div></blockquote></div></div></div><br>__________________________________=
_____________<br>
manet mailing list<br>
<a href=3D"mailto:manet@ietf.org" target=3D"_blank">manet@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/manet" rel=3D"noreferrer" =
target=3D"_blank">https://www.ietf.org/mailman/listinfo/manet</a><br>
<br></blockquote></div><br></div>
</div></blockquote><blockquote type=3D"cite"><div><span>___________________=
____________________________</span><br><span>manet mailing list</span><br><=
span><a href=3D"mailto:manet@ietf.org" target=3D"_blank">manet@ietf.org</a>=
</span><br><span><a href=3D"https://www.ietf.org/mailman/listinfo/manet" ta=
rget=3D"_blank">https://www.ietf.org/mailman/listinfo/manet</a></span><br><=
/div></blockquote></div></div></div></blockquote></div><br></div>

--001a1130d0ea404083052605a96e--


From nobody Thu Dec  3 14:28:30 2015
Return-Path: <lberger@labn.net>
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 3BCE01ACF1C for <manet@ietfa.amsl.com>; Thu,  3 Dec 2015 14:28:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.667
X-Spam-Level: 
X-Spam-Status: No, score=-1.667 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, IP_NOT_FRIENDLY=0.334, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no
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 YoJnKeWGpeDg for <manet@ietfa.amsl.com>; Thu,  3 Dec 2015 14:28:26 -0800 (PST)
Received: from gproxy9-pub.mail.unifiedlayer.com (gproxy9-pub.mail.unifiedlayer.com [69.89.20.122]) by ietfa.amsl.com (Postfix) with SMTP id 047751ACEFB for <manet@ietf.org>; Thu,  3 Dec 2015 14:28:16 -0800 (PST)
Received: (qmail 15374 invoked by uid 0); 3 Dec 2015 22:28:13 -0000
Received: from unknown (HELO CMOut01) (10.0.90.82) by gproxy9.mail.unifiedlayer.com with SMTP; 3 Dec 2015 22:28:13 -0000
Received: from box313.bluehost.com ([69.89.31.113]) by CMOut01 with  id pAU61r00U2SSUrH01AU97a; Thu, 03 Dec 2015 15:28:12 -0700
X-Authority-Analysis: v=2.1 cv=Zc6OaKlA c=1 sm=1 tr=0 a=h1BC+oY+fLhyFmnTBx92Jg==:117 a=wU2YTnxGAAAA:8 a=cNaOj0WVAAAA:8 a=IkcTkHD0fZMA:10 a=-NfooI8aBGcA:10 a=uEJ9t1CZtbIA:10 a=wUQvQvOEmiQA:10 a=N5mEvZXgYaY78W9nbtYA:9 a=QEXdDO2ut3YA:10
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=labn.net; s=default;  h=Content-Transfer-Encoding:Content-Type:In-Reply-To:MIME-Version:Date:Message-ID:From:Cc:References:To:Subject; bh=bDUwcBzJ7JGnkppLw8m8tvrj5IhrDvAwuNl4tpdqAuw=;  b=ytJAFluexopX4q47ft5M9PGsvix0n8eV5nol26Y12tqsHLcI3NlM51+wspOx7HX0f7iQvhI3T4ZckNEHPZpuzi8Kg+71eXBrDP+hkpJ+YG+SWzF6JXZW/QhHDQsU6WPy;
Received: from box313.bluehost.com ([69.89.31.113]:33427 helo=[127.0.0.1]) by box313.bluehost.com with esmtpa (Exim 4.84) (envelope-from <lberger@labn.net>) id 1a4cMB-0000xo-9U; Thu, 03 Dec 2015 15:28:07 -0700
To: Stan Ratliff <ratliffstan@gmail.com>
References: <5575E8A7.6030508@labn.net> <565E2EC4.50504@labn.net> <CALtoyo=2YrNT9CJCoqJ_x1+Cbyu8stfNuwjQXJFvjWfE9h+2Mw@mail.gmail.com> <565E4E8D.8080704@labn.net> <CALtoyokCuQOWAX8QYPK79_W+75cQhuFKvBGqwCf6NSpvD1-r2A@mail.gmail.com>
From: Lou Berger <lberger@labn.net>
Message-ID: <5660C1F3.7010708@labn.net>
Date: Thu, 3 Dec 2015 17:28:03 -0500
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.4.0
MIME-Version: 1.0
In-Reply-To: <CALtoyokCuQOWAX8QYPK79_W+75cQhuFKvBGqwCf6NSpvD1-r2A@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-Identified-User: {1038:box313.bluehost.com:labnmobi:labn.net} {sentby:smtp auth 69.89.31.113 authed with lberger@labn.net}
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/f7mQ1TBAJeAw9OcQz7ii6iIUq4c>
Cc: MANET IETF <manet@ietf.org>, draft-ietf-manet-dlep@ietf.org
Subject: Re: [manet] DLEP-17 and RtgDir review of draft-ietf-manet-dlep-14
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: <https://mailarchive.ietf.org/arch/browse/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: Thu, 03 Dec 2015 22:28:28 -0000

Stan,


On 12/1/2015 10:36 PM, Stan Ratliff wrote:
>
>
> On Tue, Dec 1, 2015 at 8:51 PM, Lou Berger <lberger@labn.net
> <mailto:lberger@labn.net>> wrote:
>
>     Stan,
>
>     On 12/1/2015 8:30 PM, Stan Ratliff wrote:
>     > Lou,
>     >
>     > Thanks for the review. I wanted to respond to a couple of your
>     points
>     > while they're fresh on my mind:
>

any thoughts on the other points?  Some of them a bit more substantive.


>     >
>     > On Tue, Dec 1, 2015 at 6:35 PM, Lou Berger <lberger@labn.net
>     <mailto:lberger@labn.net>
>     > <mailto:lberger@labn.net <mailto:lberger@labn.net>>> wrote:
>     >
>     > [snip]
>     >
>     >
>     >     >     - Sections 8.19 and 8.20 define "Resources" related Data
>     >     Items.  The
>     >     >       definition related to these basically says a
>     resources is "An
>     >     >       8-bit integer percentage, 0-100, representing the
>     amount of
>     >     >       resources allocated to receiving|transmitting
>     data.".  If
>     >     I were
>     >     >       implementing this protocol, I'd have no idea how to
>     produce,
>     >     >       update or use this information.  I think there is
>     some missing
>     >     >       informative and normative (RFC 2119) text related to
>     these
>     >     >       formats.
>     >
>     >     Unless I missed it, no change.
>     >
>     >     The basic point is that the document should state what are
>     >     interoperable
>     >     implementations supposed to do with this parameter.
>     >
>     >     >
>     >     >     - Sections 8.21 and 8.22 (Relative Link Quality) have
>     a similar
>     >     >       problem of being under described, in particular it's
>     >     unclear if
>     >     >       there's a meaningful, non-proprietary definition for
>     link
>     >     quality
>     >     >       that an implementation is to act on or if the passed
>     value
>     >     is just
>     >     >       passed for as monitoring information.  Either way, this
>     >     needs to
>     >     >       be clarified.
>     >     Unless I missed it, no change.
>     >
>     >     The basic point is that the document should state what are
>     >     interoperable
>     >     implementations supposed to do with this parameter.
>     >
>     > [snip]
>     >
>     > The document doesn't mention what an interoperable implementation is
>     > supposed to do with *any* data item. AFAIK, no data item has a "and
>     > here's what you do with it" clause (and if there is one there,
>     please
>     > let me know and I'll delete it). ;-)
>
>     I think the spec is pretty clear what data items 1-16 mean and are
>     to be
>     used and to be meaningful in an interoperable scenario.
>
>     >
>     > What you actually do with the data items is out of scope for this
>     > document - by necessity. If we attempted to document what could (or
>     > should) be done with these data items, the spec is 'deat meat' -
>     we'll
>     > be at this for the next 40 years, since the data (for instance, data
>     > rate) *could* be used in more than one place - the complexity
>     explodes
>     > exponentially, the arguing goes on and on without end. The short
>     > answer is - when received, the data can be a part of your
>     > implementation's information base.
>     >
>
>     for link quality, I think simply saying that the metric can be
>     used (for
>     example) by a router when selecting between alternate available paths.
>
>
> That's true for any metric, including "Resources". I respectfully
> disagree that we should step into the "... , and here's what you would
> do with it..." morass. You said in your response "I think the spec is
> pretty clear what data items 1-16 mean and are to be used", but I note
> again, the spec doesn't specifically say how (or even whether) they
> are supposed to be used. I do not believe we should make an exception
> for the above two.

If I was to implement the router side, I'd know what to do with the
other items, but not resource.  I defer to the WG to come to consensus
on this question (and if the full value range is permissible.)

I look forward to hearing back on the other open topics.

Lou

>
> Regards,
> Stan
>
>
>  
>
>     In which case I'd ask why is this limited to 100 rather than the full
>     range of the field.
>
>     for resources, I actually have no guess as to what it means or
>     what you
>     expect a router to do with this. Without additional information and
>     assuming your next statement is correct, it's for strictly proprietary
>     (and non-interoperable) applications, I'd say drop it from the spec.
>
>     Lou
>
>     > Oh, and as to the 2 above data items - they are implemented with
>     > proprietary algorithms. If words to that effect will clear the issue
>     > up, let me know and I'll attempt to add that.
>     >
>     > Regards,
>     > Stan
>     >
>
>
>



From nobody Thu Dec  3 14:37:32 2015
Return-Path: <hrogge@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 0F1D91AD0CB; Thu,  3 Dec 2015 14:37:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 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, 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 pSbMV9CJOC4T; Thu,  3 Dec 2015 14:37:30 -0800 (PST)
Received: from mail-wm0-x235.google.com (mail-wm0-x235.google.com [IPv6:2a00:1450:400c:c09::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BA0651AD0AC; Thu,  3 Dec 2015 14:37:29 -0800 (PST)
Received: by wmww144 with SMTP id w144so42017302wmw.0; Thu, 03 Dec 2015 14:37:28 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=L/txEhGDc2lchH6kubXDGuNO4ILWCEGL4AIu8EhUmJE=; b=WxJiXg/8l7W5jAHeRS0qHNISpEnLCRW+ml78/fGGCOVa1eW62ZlZCiUmc3UT+adeo1 bt9O+lpW3VVfTzoZk1d6eANpQtOHHWLhIb3lzYlRmrN0xrEbxeU3v99WG2sr9SZiXOBL qpsCw7DnOnlmKU4zZdWnAlJL+6w8NW9E7WGw6G7CMawj0Pq/6I4Hi5qEoX4hPw0nw92t BS0LB1V9drx6j8VJHmHoEsEwFQsrccpOrisMcAaJQKHBZgiya4wHBIyBy9LuZuRR+EAb vnwCA4AVO3zOwuAeCrcMaQ/PpzWw41dPW5ev17589aMbMIhoY7sQ9K83sxvbJS5zjiwm 5uSQ==
X-Received: by 10.28.47.212 with SMTP id v203mr980847wmv.37.1449182248358; Thu, 03 Dec 2015 14:37:28 -0800 (PST)
MIME-Version: 1.0
Received: by 10.27.94.70 with HTTP; Thu, 3 Dec 2015 14:36:58 -0800 (PST)
In-Reply-To: <5660C1F3.7010708@labn.net>
References: <5575E8A7.6030508@labn.net> <565E2EC4.50504@labn.net> <CALtoyo=2YrNT9CJCoqJ_x1+Cbyu8stfNuwjQXJFvjWfE9h+2Mw@mail.gmail.com> <565E4E8D.8080704@labn.net> <CALtoyokCuQOWAX8QYPK79_W+75cQhuFKvBGqwCf6NSpvD1-r2A@mail.gmail.com> <5660C1F3.7010708@labn.net>
From: Henning Rogge <hrogge@gmail.com>
Date: Thu, 3 Dec 2015 23:36:58 +0100
Message-ID: <CAGnRvupZvXK5VT09ug1C9sGw6CefOp9iLdXr=6iwzSA6Y-YTEA@mail.gmail.com>
To: Lou Berger <lberger@labn.net>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/Uvov-9PDwPNSBwZoiBU8LStJiJo>
Cc: MANET IETF <manet@ietf.org>, draft-ietf-manet-dlep@ietf.org
Subject: Re: [manet] DLEP-17 and RtgDir review of draft-ietf-manet-dlep-14
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: <https://mailarchive.ietf.org/arch/browse/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: Thu, 03 Dec 2015 22:37:31 -0000

On Thu, Dec 3, 2015 at 11:28 PM, Lou Berger <lberger@labn.net> wrote:
> On 12/1/2015 10:36 PM, Stan Ratliff wrote:
>> That's true for any metric, including "Resources". I respectfully
>> disagree that we should step into the "... , and here's what you would
>> do with it..." morass. You said in your response "I think the spec is
>> pretty clear what data items 1-16 mean and are to be used", but I note
>> again, the spec doesn't specifically say how (or even whether) they
>> are supposed to be used. I do not believe we should make an exception
>> for the above two.
>
> If I was to implement the router side, I'd know what to do with the
> other items, but not resource.  I defer to the WG to come to consensus
> on this question (and if the full value range is permissible.)

My interpretation was always something like "battery level"... might
make sense if the router is just a virtual software instance running
on the radio hardware but using the standardized DLEP interface to get
its data.

Henning Rogge


From nobody Thu Dec  3 14:41:15 2015
Return-Path: <ratliffstan@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 861D91B2A4E; Thu,  3 Dec 2015 14:41:13 -0800 (PST)
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 ZxybTWwsxa_R; Thu,  3 Dec 2015 14:41:10 -0800 (PST)
Received: from mail-lb0-x234.google.com (mail-lb0-x234.google.com [IPv6:2a00:1450:4010:c04::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0CF6E1B2A40; Thu,  3 Dec 2015 14:41:10 -0800 (PST)
Received: by lbcdv4 with SMTP id dv4so10475145lbc.2; Thu, 03 Dec 2015 14:41:08 -0800 (PST)
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=1GmOj8WrVqbhTokIxiuHxvDGvQspCz97km/A88sLous=; b=ee9eLKlO4TfZvPBrTG+dPxQvPdK4UDOM8YG8T9sYE3/vxZty2kdRvV76tu47f7ngco WQXn2JJcS9y98PD0FcExqNECLyVVSyWr8DSd/k4M23dQaPzXxQvrAjsTRxcPsKnE+xlv nSuJeiWiFxlnW1wv2xLbPPEC9PCbHe5fs+iACyxdWmF4wigJ405SQB4T49jilFz2f8+n rtLNLOwq4dAvw8jQafNKl8j+45H2zFd5xrjUSzJeqetWYPQ46grUzddN/uhXCYuRIz6V VWJwFI4F6z9ljRM/j3WzqxcaF61oHdTyBp2g6LmYa0pfyINycAYPB94hl829UyAX9+K0 cYzg==
MIME-Version: 1.0
X-Received: by 10.112.36.130 with SMTP id q2mr6897929lbj.24.1449182468249; Thu, 03 Dec 2015 14:41:08 -0800 (PST)
Received: by 10.25.209.71 with HTTP; Thu, 3 Dec 2015 14:41:08 -0800 (PST)
In-Reply-To: <5660C1F3.7010708@labn.net>
References: <5575E8A7.6030508@labn.net> <565E2EC4.50504@labn.net> <CALtoyo=2YrNT9CJCoqJ_x1+Cbyu8stfNuwjQXJFvjWfE9h+2Mw@mail.gmail.com> <565E4E8D.8080704@labn.net> <CALtoyokCuQOWAX8QYPK79_W+75cQhuFKvBGqwCf6NSpvD1-r2A@mail.gmail.com> <5660C1F3.7010708@labn.net>
Date: Thu, 3 Dec 2015 17:41:08 -0500
Message-ID: <CALtoyokEWk8CXKxE0ALsPH_GRyg7pcp3B+ucSi+rcFQGN=UzVw@mail.gmail.com>
From: Stan Ratliff <ratliffstan@gmail.com>
To: Lou Berger <lberger@labn.net>
Content-Type: multipart/alternative; boundary=001a113405403c22cb05260616ee
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/SEt8-6hKiJC8m2EjLIMBowhN6hY>
Cc: MANET IETF <manet@ietf.org>, draft-ietf-manet-dlep@ietf.org
Subject: Re: [manet] DLEP-17 and RtgDir review of draft-ietf-manet-dlep-14
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: <https://mailarchive.ietf.org/arch/browse/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: Thu, 03 Dec 2015 22:41:13 -0000

--001a113405403c22cb05260616ee
Content-Type: text/plain; charset=UTF-8

Lou,

With regard to the other points you raise, I'm thinking we (Rick and
myself) need to address them with an update. There are a few I'm frankly
struggling with, and I'd like to reserve the option of coming back & saying
"I don't get it", but...

As long as you're asking, I do have one question - when discussing the
transaction model, you say (in part):
" More significantly, it's unclear how new messages should be handled."

Since we're talking about new messages, and I have no idea what those
messages would involve, it's somewhat hard to fully pin-down how they
should be handled. If the new messages are destination-oriented, they
should fall into the "1 transaction in-flight per destination" rule. If the
new messages are peer-oriented, then they would fall into the "1
transaction in-flight per peer" rule... but in the case where a new message
introduces some sort of new context that I can't currently see? I'm lost
there.

Regards,
Stan



On Thu, Dec 3, 2015 at 5:28 PM, Lou Berger <lberger@labn.net> wrote:

> Stan,
>
>
> On 12/1/2015 10:36 PM, Stan Ratliff wrote:
> >
> >
> > On Tue, Dec 1, 2015 at 8:51 PM, Lou Berger <lberger@labn.net
> > <mailto:lberger@labn.net>> wrote:
> >
> >     Stan,
> >
> >     On 12/1/2015 8:30 PM, Stan Ratliff wrote:
> >     > Lou,
> >     >
> >     > Thanks for the review. I wanted to respond to a couple of your
> >     points
> >     > while they're fresh on my mind:
> >
>
> any thoughts on the other points?  Some of them a bit more substantive.
>
>
> >     >
> >     > On Tue, Dec 1, 2015 at 6:35 PM, Lou Berger <lberger@labn.net
> >     <mailto:lberger@labn.net>
> >     > <mailto:lberger@labn.net <mailto:lberger@labn.net>>> wrote:
> >     >
> >     > [snip]
> >     >
> >     >
> >     >     >     - Sections 8.19 and 8.20 define "Resources" related Data
> >     >     Items.  The
> >     >     >       definition related to these basically says a
> >     resources is "An
> >     >     >       8-bit integer percentage, 0-100, representing the
> >     amount of
> >     >     >       resources allocated to receiving|transmitting
> >     data.".  If
> >     >     I were
> >     >     >       implementing this protocol, I'd have no idea how to
> >     produce,
> >     >     >       update or use this information.  I think there is
> >     some missing
> >     >     >       informative and normative (RFC 2119) text related to
> >     these
> >     >     >       formats.
> >     >
> >     >     Unless I missed it, no change.
> >     >
> >     >     The basic point is that the document should state what are
> >     >     interoperable
> >     >     implementations supposed to do with this parameter.
> >     >
> >     >     >
> >     >     >     - Sections 8.21 and 8.22 (Relative Link Quality) have
> >     a similar
> >     >     >       problem of being under described, in particular it's
> >     >     unclear if
> >     >     >       there's a meaningful, non-proprietary definition for
> >     link
> >     >     quality
> >     >     >       that an implementation is to act on or if the passed
> >     value
> >     >     is just
> >     >     >       passed for as monitoring information.  Either way, this
> >     >     needs to
> >     >     >       be clarified.
> >     >     Unless I missed it, no change.
> >     >
> >     >     The basic point is that the document should state what are
> >     >     interoperable
> >     >     implementations supposed to do with this parameter.
> >     >
> >     > [snip]
> >     >
> >     > The document doesn't mention what an interoperable implementation
> is
> >     > supposed to do with *any* data item. AFAIK, no data item has a "and
> >     > here's what you do with it" clause (and if there is one there,
> >     please
> >     > let me know and I'll delete it). ;-)
> >
> >     I think the spec is pretty clear what data items 1-16 mean and are
> >     to be
> >     used and to be meaningful in an interoperable scenario.
> >
> >     >
> >     > What you actually do with the data items is out of scope for this
> >     > document - by necessity. If we attempted to document what could (or
> >     > should) be done with these data items, the spec is 'deat meat' -
> >     we'll
> >     > be at this for the next 40 years, since the data (for instance,
> data
> >     > rate) *could* be used in more than one place - the complexity
> >     explodes
> >     > exponentially, the arguing goes on and on without end. The short
> >     > answer is - when received, the data can be a part of your
> >     > implementation's information base.
> >     >
> >
> >     for link quality, I think simply saying that the metric can be
> >     used (for
> >     example) by a router when selecting between alternate available
> paths.
> >
> >
> > That's true for any metric, including "Resources". I respectfully
> > disagree that we should step into the "... , and here's what you would
> > do with it..." morass. You said in your response "I think the spec is
> > pretty clear what data items 1-16 mean and are to be used", but I note
> > again, the spec doesn't specifically say how (or even whether) they
> > are supposed to be used. I do not believe we should make an exception
> > for the above two.
>
> If I was to implement the router side, I'd know what to do with the
> other items, but not resource.  I defer to the WG to come to consensus
> on this question (and if the full value range is permissible.)
>
> I look forward to hearing back on the other open topics.
>
> Lou
>
> >
> > Regards,
> > Stan
> >
> >
> >
> >
> >     In which case I'd ask why is this limited to 100 rather than the full
> >     range of the field.
> >
> >     for resources, I actually have no guess as to what it means or
> >     what you
> >     expect a router to do with this. Without additional information and
> >     assuming your next statement is correct, it's for strictly
> proprietary
> >     (and non-interoperable) applications, I'd say drop it from the spec.
> >
> >     Lou
> >
> >     > Oh, and as to the 2 above data items - they are implemented with
> >     > proprietary algorithms. If words to that effect will clear the
> issue
> >     > up, let me know and I'll attempt to add that.
> >     >
> >     > Regards,
> >     > Stan
> >     >
> >
> >
> >
>
>
>

--001a113405403c22cb05260616ee
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Lou,=C2=A0<div><br></div><div>With regard to the other poi=
nts you raise, I&#39;m thinking we (Rick and myself) need to address them w=
ith an update. There are a few I&#39;m frankly struggling with, and I&#39;d=
 like to reserve the option of coming back &amp; saying &quot;I don&#39;t g=
et it&quot;, but...=C2=A0</div><div><br></div><div>As long as you&#39;re as=
king, I do have one question - when discussing the transaction model, you s=
ay (in part):=C2=A0</div><div>&quot;<span style=3D"font-size:12.8px">=C2=A0=
More=C2=A0</span><span style=3D"font-size:12.8px">significantly, it&#39;s u=
nclear how new messages should be handled.&quot;</span></div><div><span sty=
le=3D"font-size:12.8px"><br></span></div><div><span style=3D"font-size:12.8=
px">Since we&#39;re talking about new messages, and I have no idea what tho=
se messages would involve, it&#39;s somewhat hard to fully pin-down how the=
y should be handled. If the new messages are destination-oriented, they sho=
uld fall into the &quot;1 transaction in-flight per destination&quot; rule.=
 If the new messages are peer-oriented, then they would fall into the &quot=
;1 transaction in-flight per peer&quot; rule... but in the case where a new=
 message introduces some sort of new context that I can&#39;t currently see=
? I&#39;m lost there.</span></div><div><span style=3D"font-size:12.8px"><br=
></span></div><div><span style=3D"font-size:12.8px">Regards,<br>Stan</span>=
</div><div><span style=3D"font-size:12.8px"><br></span></div><div><span sty=
le=3D"font-size:12.8px"><br></span><div class=3D"gmail_extra"><br><div clas=
s=3D"gmail_quote">On Thu, Dec 3, 2015 at 5:28 PM, Lou Berger <span dir=3D"l=
tr">&lt;<a href=3D"mailto:lberger@labn.net" target=3D"_blank">lberger@labn.=
net</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"mar=
gin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,2=
04);border-left-style:solid;padding-left:1ex">Stan,<br>
<br>
<br>
On 12/1/2015 10:36 PM, Stan Ratliff wrote:<br>
&gt;<br>
&gt;<br>
&gt; On Tue, Dec 1, 2015 at 8:51 PM, Lou Berger &lt;<a href=3D"mailto:lberg=
er@labn.net">lberger@labn.net</a><br>
&gt; &lt;mailto:<a href=3D"mailto:lberger@labn.net">lberger@labn.net</a>&gt=
;&gt; wrote:<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0Stan,<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0On 12/1/2015 8:30 PM, Stan Ratliff wrote:<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; Lou,<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; Thanks for the review. I wanted to respond to =
a couple of your<br>
&gt;=C2=A0 =C2=A0 =C2=A0points<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; while they&#39;re fresh on my mind:<br>
&gt;<br>
<br>
any thoughts on the other points?=C2=A0 Some of them a bit more substantive=
.<br>
<br>
<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; On Tue, Dec 1, 2015 at 6:35 PM, Lou Berger &lt=
;<a href=3D"mailto:lberger@labn.net">lberger@labn.net</a><br>
&gt;=C2=A0 =C2=A0 =C2=A0&lt;mailto:<a href=3D"mailto:lberger@labn.net">lber=
ger@labn.net</a>&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; &lt;mailto:<a href=3D"mailto:lberger@labn.net"=
>lberger@labn.net</a> &lt;mailto:<a href=3D"mailto:lberger@labn.net">lberge=
r@labn.net</a>&gt;&gt;&gt; wrote:<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; [snip]<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0- S=
ections 8.19 and 8.20 define &quot;Resources&quot; related Data<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0Items.=C2=A0 The<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0 =
=C2=A0definition related to these basically says a<br>
&gt;=C2=A0 =C2=A0 =C2=A0resources is &quot;An<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0 =
=C2=A08-bit integer percentage, 0-100, representing the<br>
&gt;=C2=A0 =C2=A0 =C2=A0amount of<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0 =
=C2=A0resources allocated to receiving|transmitting<br>
&gt;=C2=A0 =C2=A0 =C2=A0data.&quot;.=C2=A0 If<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0I were<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0 =
=C2=A0implementing this protocol, I&#39;d have no idea how to<br>
&gt;=C2=A0 =C2=A0 =C2=A0produce,<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0 =
=C2=A0update or use this information.=C2=A0 I think there is<br>
&gt;=C2=A0 =C2=A0 =C2=A0some missing<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0 =
=C2=A0informative and normative (RFC 2119) text related to<br>
&gt;=C2=A0 =C2=A0 =C2=A0these<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0 =
=C2=A0formats.<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0Unless I missed it, no chan=
ge.<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0The basic point is that the=
 document should state what are<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0interoperable<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0implementations supposed to=
 do with this parameter.<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0- S=
ections 8.21 and 8.22 (Relative Link Quality) have<br>
&gt;=C2=A0 =C2=A0 =C2=A0a similar<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0 =
=C2=A0problem of being under described, in particular it&#39;s<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0unclear if<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0 =
=C2=A0there&#39;s a meaningful, non-proprietary definition for<br>
&gt;=C2=A0 =C2=A0 =C2=A0link<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0quality<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0 =
=C2=A0that an implementation is to act on or if the passed<br>
&gt;=C2=A0 =C2=A0 =C2=A0value<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0is just<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0 =
=C2=A0passed for as monitoring information.=C2=A0 Either way, this<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0needs to<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0 =
=C2=A0be clarified.<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0Unless I missed it, no chan=
ge.<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0The basic point is that the=
 document should state what are<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0interoperable<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0implementations supposed to=
 do with this parameter.<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; [snip]<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; The document doesn&#39;t mention what an inter=
operable implementation is<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; supposed to do with *any* data item. AFAIK, no=
 data item has a &quot;and<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; here&#39;s what you do with it&quot; clause (a=
nd if there is one there,<br>
&gt;=C2=A0 =C2=A0 =C2=A0please<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; let me know and I&#39;ll delete it). ;-)<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0I think the spec is pretty clear what data items 1-=
16 mean and are<br>
&gt;=C2=A0 =C2=A0 =C2=A0to be<br>
&gt;=C2=A0 =C2=A0 =C2=A0used and to be meaningful in an interoperable scena=
rio.<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; What you actually do with the data items is ou=
t of scope for this<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; document - by necessity. If we attempted to do=
cument what could (or<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; should) be done with these data items, the spe=
c is &#39;deat meat&#39; -<br>
&gt;=C2=A0 =C2=A0 =C2=A0we&#39;ll<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; be at this for the next 40 years, since the da=
ta (for instance, data<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; rate) *could* be used in more than one place -=
 the complexity<br>
&gt;=C2=A0 =C2=A0 =C2=A0explodes<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; exponentially, the arguing goes on and on with=
out end. The short<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; answer is - when received, the data can be a p=
art of your<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; implementation&#39;s information base.<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0for link quality, I think simply saying that the me=
tric can be<br>
&gt;=C2=A0 =C2=A0 =C2=A0used (for<br>
&gt;=C2=A0 =C2=A0 =C2=A0example) by a router when selecting between alterna=
te available paths.<br>
&gt;<br>
&gt;<br>
&gt; That&#39;s true for any metric, including &quot;Resources&quot;. I res=
pectfully<br>
&gt; disagree that we should step into the &quot;... , and here&#39;s what =
you would<br>
&gt; do with it...&quot; morass. You said in your response &quot;I think th=
e spec is<br>
&gt; pretty clear what data items 1-16 mean and are to be used&quot;, but I=
 note<br>
&gt; again, the spec doesn&#39;t specifically say how (or even whether) the=
y<br>
&gt; are supposed to be used. I do not believe we should make an exception<=
br>
&gt; for the above two.<br>
<br>
If I was to implement the router side, I&#39;d know what to do with the<br>
other items, but not resource.=C2=A0 I defer to the WG to come to consensus=
<br>
on this question (and if the full value range is permissible.)<br>
<br>
I look forward to hearing back on the other open topics.<br>
<br>
Lou<br>
<br>
&gt;<br>
&gt; Regards,<br>
&gt; Stan<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0In which case I&#39;d ask why is this limited to 10=
0 rather than the full<br>
&gt;=C2=A0 =C2=A0 =C2=A0range of the field.<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0for resources, I actually have no guess as to what =
it means or<br>
&gt;=C2=A0 =C2=A0 =C2=A0what you<br>
&gt;=C2=A0 =C2=A0 =C2=A0expect a router to do with this. Without additional=
 information and<br>
&gt;=C2=A0 =C2=A0 =C2=A0assuming your next statement is correct, it&#39;s f=
or strictly proprietary<br>
&gt;=C2=A0 =C2=A0 =C2=A0(and non-interoperable) applications, I&#39;d say d=
rop it from the spec.<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0Lou<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; Oh, and as to the 2 above data items - they ar=
e implemented with<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; proprietary algorithms. If words to that effec=
t will clear the issue<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; up, let me know and I&#39;ll attempt to add th=
at.<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; Regards,<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; Stan<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
<br>
<br>
</blockquote></div><br></div></div></div>

--001a113405403c22cb05260616ee--


From nobody Thu Dec  3 18:33:07 2015
Return-Path: <Ietf@thomasclausen.org>
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 4CC341B29FE; Thu,  3 Dec 2015 18:33:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.702
X-Spam-Level: 
X-Spam-Status: No, score=-2.702 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-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 cyMn_nTYRYBy; Thu,  3 Dec 2015 18:33:03 -0800 (PST)
Received: from mailb2.tigertech.net (mailb2.tigertech.net [208.80.4.154]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8DF4A1B29F6; Thu,  3 Dec 2015 18:33:03 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mailb2.tigertech.net (Postfix) with ESMTP id 326921C043E; Thu,  3 Dec 2015 18:33:03 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=thomasclausen.org; s=1.tigertech; t=1449196383; bh=kA/1VhGmOMSEquvm59YQ2moYFlZwjPZuiruwcsntw6g=; h=Subject:From:In-Reply-To:Date:Cc:References:To:From; b=h4Qd5Ni45psgGc3iFY/cQo44yYlsnoZ6l922E/vQOFm7JV1pHk8a3Lhu3VTqgnnVi haS73weFMECIXoAOQrOJIbAIvMwt1am0XVJhlVavyOI5dizfWT8VUkTafOcKHA78d/ JFCs/rdD3MGBX5LMu7rALsHJzrrsh9yV8UV2hXJ8=
X-Virus-Scanned: Debian amavisd-new at b2.tigertech.net
Received: from [129.104.75.80] (unknown [129.104.75.80]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailb2.tigertech.net (Postfix) with ESMTPSA id B070D1C038E; Thu,  3 Dec 2015 18:33:01 -0800 (PST)
Mime-Version: 1.0 (Mac OS X Mail 9.1 \(3096.5\))
Content-Type: text/plain; charset=utf-8
From: ietf@thomasclausen.org
In-Reply-To: <20151203141014.13172.85185.idtracker@ietfa.amsl.com>
Date: Fri, 4 Dec 2015 03:33:00 +0100
Content-Transfer-Encoding: quoted-printable
Sendlaterdate: Fri, 4 Dec 2015 03:33:00 +0100
Message-Id: <4C05351D-C18C-446C-B2CB-82FAAC9840B9@thomasclausen.org>
References: <20151203141014.13172.85185.idtracker@ietfa.amsl.com>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
X-Mailer: Apple Mail (2.3096.5)
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/L2zCr_2tTxWy6g-s7CB3dAZoKmw>
Cc: manet-chairs@ietf.org, manet@ietf.org, The IESG <iesg@ietf.org>, draft-ietf-manet-olsrv2-dat-metric@ietf.org
Subject: Re: [manet] Stephen Farrell's No Objection on draft-ietf-manet-olsrv2-dat-metric-10: (with COMMENT)
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: <https://mailarchive.ietf.org/arch/browse/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, 04 Dec 2015 02:33:05 -0000

Stephen,

I was actually one of the people recommending that the authors focus on =
OLSRv2.=20

The reason for that being, simply, that we do not know how this metric =
behaves with other protocols (yet), whereas we have some idea of how it =
behaves with OLSRv2.  I also do not think that we know how it would fit =
into the other protocols in this WG, not to mention in other WGs.=20

You are right, of course, if the experiment that this document enables =
allows figuring that out, it would be interesting.

Yet, I think that the primary goal (and, perhaps, the only real bar for =
progressing eventually to std.track) of this experiment should be =
=E2=80=9Cconfirm if this is a metric worth recommending for OLSRv2=E2=80=9D=
 not =E2=80=9Cset out to boil the ocean and come up with the one metric =
to rule them all=E2=80=9D=E2=80=A6=20

Thomas

> On 03 Dec 2015, at 15:10, Stephen Farrell <stephen.farrell@cs.tcd.ie> =
wrote:
>=20
> Stephen Farrell has entered the following ballot position for
> draft-ietf-manet-olsrv2-dat-metric-10: No Objection
>=20
> When responding, please keep the subject line intact and reply to all
> email addresses included in the To and CC lines. (Feel free to cut =
this
> introductory paragraph, however.)
>=20
>=20
> Please refer to =
https://www.ietf.org/iesg/statement/discuss-criteria.html
> for more information about IESG DISCUSS and COMMENT positions.
>=20
>=20
> The document, along with other ballot positions, can be found here:
> https://datatracker.ietf.org/doc/draft-ietf-manet-olsrv2-dat-metric/
>=20
>=20
>=20
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
>=20
>=20
> - General: This seems mostly to be an abstract metric that could be
> re-used e.g. in ROLL or HOMENET (if it's good:-) but with
> OLSR-specific text and concepts mixed in here and there.  It'd have
> been better were it possible to separate the abstract metric from
> the OLSR-specifics to make the former easier to re-use later. It's
> fine if determining if that would be useful is a part of the
> experiment, but it might be good to mention it here.
>=20
> - Section 6: In particular "fraction of the loss rate" isn't clear
> to me, but maybe that's fine and it's known term of art to folks who
> do metrics.
>=20
> - Section 11: Wrt the MitM comments from other ADs - one possiblity
> here might be to recommend that protocols making use of this metric
> should be cognizant of, and include mitigtions for, MitM attacks of
> this kind. (Just a suggestion, feel free to ignore if you prefer.)=20
>=20
> - Thanks for handling the secdir review [1] - I think that all the
> issues there were resolved, but do say if some still need a bit
> more chatting.
>=20
>   [1] =
https://www.ietf.org/mail-archive/web/secdir/current/msg06185.html
>=20
>=20
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www.ietf.org/mailman/listinfo/manet


From nobody Thu Dec  3 21:53:17 2015
Return-Path: <rick@tropicalstormsoftware.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 5B9FA1A1B5D; Thu,  3 Dec 2015 21:53:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.911
X-Spam-Level: 
X-Spam-Status: No, score=-1.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 3J0qiJ0uxD_m; Thu,  3 Dec 2015 21:53:12 -0800 (PST)
Received: from mail.tropicalstormsoftware.com (mail.tropicalstormsoftware.com [188.94.42.120]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C92661A1B5B; Thu,  3 Dec 2015 21:53:11 -0800 (PST)
Received: from tss-server1.home.tropicalstormsoftware.com ([fe80::753b:fa82:5c0:af0d]) by tss-server1.home.tropicalstormsoftware.com ([fe80::753b:fa82:5c0:af0d%10]) with mapi; Fri, 4 Dec 2015 05:52:45 +0000
From: Rick Taylor <rick@tropicalstormsoftware.com>
To: Stan Ratliff <ratliffstan@gmail.com>, Lou Berger <lberger@labn.net>
Thread-Topic: [manet] DLEP-17 and RtgDir review of draft-ietf-manet-dlep-14
Thread-Index: AQHRLJEIc/FObi/UnECavgTFHNfC+w==
Date: Fri, 4 Dec 2015 05:52:44 +0000
Message-ID: <38A5475DE83986499AEACD2CFAFC3F9801B32FE340@tss-server1.home.tropicalstormsoftware.com>
References: <5575E8A7.6030508@labn.net> <565E2EC4.50504@labn.net> <CALtoyo=2YrNT9CJCoqJ_x1+Cbyu8stfNuwjQXJFvjWfE9h+2Mw@mail.gmail.com> <565E4E8D.8080704@labn.net> <CALtoyokCuQOWAX8QYPK79_W+75cQhuFKvBGqwCf6NSpvD1-r2A@mail.gmail.com> <5660C1F3.7010708@labn.net> <CALtoyokEWk8CXKxE0ALsPH_GRyg7pcp3B+ucSi+rcFQGN=UzVw@mail.gmail.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/r9WdcAguwhwHXUMpctU3iIAinFw>
Cc: MANET IETF <manet@ietf.org>, "draft-ietf-manet-dlep@ietf.org" <draft-ietf-manet-dlep@ietf.org>
Subject: Re: [manet] DLEP-17 and RtgDir review of draft-ietf-manet-dlep-14
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: <https://mailarchive.ietf.org/arch/browse/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, 04 Dec 2015 05:53:15 -0000

Lou, et al.=0A=
=0A=
I'm afraid I'm on vacation until the 14th, so I'm resisting the urge to=0A=
reply to some of the questions rather than leaving Stan out to dry.=0A=
=0A=
As Stan said, I think we will have to address your, and the other (thank=0A=
you all) comments with an update.=0A=
=0A=
We will attempt to get something out ASAP, vacations permitting.=0A=
=0A=
Cheers,=0A=
=0A=
Rick=0A=
=0A=
=0A=
On 03/12/15 22:41, Stan Ratliff wrote:=0A=
> Lou, =0A=
>=0A=
> With regard to the other points you raise, I'm thinking we (Rick and=0A=
> myself) need to address them with an update. There are a few I'm=0A=
> frankly struggling with, and I'd like to reserve the option of coming=0A=
> back & saying "I don't get it", but... =0A=
>=0A=
> As long as you're asking, I do have one question - when discussing the=0A=
> transaction model, you say (in part): =0A=
> " More significantly, it's unclear how new messages should be handled."=
=0A=
>=0A=
> Since we're talking about new messages, and I have no idea what those=0A=
> messages would involve, it's somewhat hard to fully pin-down how they=0A=
> should be handled. If the new messages are destination-oriented, they=0A=
> should fall into the "1 transaction in-flight per destination" rule.=0A=
> If the new messages are peer-oriented, then they would fall into the=0A=
> "1 transaction in-flight per peer" rule... but in the case where a new=0A=
> message introduces some sort of new context that I can't currently=0A=
> see? I'm lost there.=0A=
>=0A=
> Regards,=0A=
> Stan=0A=
>=0A=
>=0A=
>=0A=
> On Thu, Dec 3, 2015 at 5:28 PM, Lou Berger <lberger@labn.net=0A=
> <mailto:lberger@labn.net>> wrote:=0A=
>=0A=
>     Stan,=0A=
>=0A=
>=0A=
>     On 12/1/2015 10:36 PM, Stan Ratliff wrote:=0A=
>     >=0A=
>     >=0A=
>     > On Tue, Dec 1, 2015 at 8:51 PM, Lou Berger <lberger@labn.net=0A=
>     <mailto:lberger@labn.net>=0A=
>     > <mailto:lberger@labn.net <mailto:lberger@labn.net>>> wrote:=0A=
>     >=0A=
>     >     Stan,=0A=
>     >=0A=
>     >     On 12/1/2015 8:30 PM, Stan Ratliff wrote:=0A=
>     >     > Lou,=0A=
>     >     >=0A=
>     >     > Thanks for the review. I wanted to respond to a couple of you=
r=0A=
>     >     points=0A=
>     >     > while they're fresh on my mind:=0A=
>     >=0A=
>=0A=
>     any thoughts on the other points?  Some of them a bit more=0A=
>     substantive.=0A=
>=0A=
>=0A=
>     >     >=0A=
>     >     > On Tue, Dec 1, 2015 at 6:35 PM, Lou Berger=0A=
>     <lberger@labn.net <mailto:lberger@labn.net>=0A=
>     >     <mailto:lberger@labn.net <mailto:lberger@labn.net>>=0A=
>     >     > <mailto:lberger@labn.net <mailto:lberger@labn.net>=0A=
>     <mailto:lberger@labn.net <mailto:lberger@labn.net>>>> wrote:=0A=
>     >     >=0A=
>     >     > [snip]=0A=
>     >     >=0A=
>     >     >=0A=
>     >     >     >     - Sections 8.19 and 8.20 define "Resources"=0A=
>     related Data=0A=
>     >     >     Items.  The=0A=
>     >     >     >       definition related to these basically says a=0A=
>     >     resources is "An=0A=
>     >     >     >       8-bit integer percentage, 0-100, representing the=
=0A=
>     >     amount of=0A=
>     >     >     >       resources allocated to receiving|transmitting=0A=
>     >     data.".  If=0A=
>     >     >     I were=0A=
>     >     >     >       implementing this protocol, I'd have no idea=0A=
>     how to=0A=
>     >     produce,=0A=
>     >     >     >       update or use this information.  I think there is=
=0A=
>     >     some missing=0A=
>     >     >     >       informative and normative (RFC 2119) text=0A=
>     related to=0A=
>     >     these=0A=
>     >     >     >       formats.=0A=
>     >     >=0A=
>     >     >     Unless I missed it, no change.=0A=
>     >     >=0A=
>     >     >     The basic point is that the document should state what ar=
e=0A=
>     >     >     interoperable=0A=
>     >     >     implementations supposed to do with this parameter.=0A=
>     >     >=0A=
>     >     >     >=0A=
>     >     >     >     - Sections 8.21 and 8.22 (Relative Link Quality)=0A=
>     have=0A=
>     >     a similar=0A=
>     >     >     >       problem of being under described, in=0A=
>     particular it's=0A=
>     >     >     unclear if=0A=
>     >     >     >       there's a meaningful, non-proprietary=0A=
>     definition for=0A=
>     >     link=0A=
>     >     >     quality=0A=
>     >     >     >       that an implementation is to act on or if the=0A=
>     passed=0A=
>     >     value=0A=
>     >     >     is just=0A=
>     >     >     >       passed for as monitoring information.  Either=0A=
>     way, this=0A=
>     >     >     needs to=0A=
>     >     >     >       be clarified.=0A=
>     >     >     Unless I missed it, no change.=0A=
>     >     >=0A=
>     >     >     The basic point is that the document should state what ar=
e=0A=
>     >     >     interoperable=0A=
>     >     >     implementations supposed to do with this parameter.=0A=
>     >     >=0A=
>     >     > [snip]=0A=
>     >     >=0A=
>     >     > The document doesn't mention what an interoperable=0A=
>     implementation is=0A=
>     >     > supposed to do with *any* data item. AFAIK, no data item=0A=
>     has a "and=0A=
>     >     > here's what you do with it" clause (and if there is one there=
,=0A=
>     >     please=0A=
>     >     > let me know and I'll delete it). ;-)=0A=
>     >=0A=
>     >     I think the spec is pretty clear what data items 1-16 mean=0A=
>     and are=0A=
>     >     to be=0A=
>     >     used and to be meaningful in an interoperable scenario.=0A=
>     >=0A=
>     >     >=0A=
>     >     > What you actually do with the data items is out of scope=0A=
>     for this=0A=
>     >     > document - by necessity. If we attempted to document what=0A=
>     could (or=0A=
>     >     > should) be done with these data items, the spec is 'deat=0A=
>     meat' -=0A=
>     >     we'll=0A=
>     >     > be at this for the next 40 years, since the data (for=0A=
>     instance, data=0A=
>     >     > rate) *could* be used in more than one place - the complexity=
=0A=
>     >     explodes=0A=
>     >     > exponentially, the arguing goes on and on without end. The=0A=
>     short=0A=
>     >     > answer is - when received, the data can be a part of your=0A=
>     >     > implementation's information base.=0A=
>     >     >=0A=
>     >=0A=
>     >     for link quality, I think simply saying that the metric can be=
=0A=
>     >     used (for=0A=
>     >     example) by a router when selecting between alternate=0A=
>     available paths.=0A=
>     >=0A=
>     >=0A=
>     > That's true for any metric, including "Resources". I respectfully=
=0A=
>     > disagree that we should step into the "... , and here's what you=0A=
>     would=0A=
>     > do with it..." morass. You said in your response "I think the=0A=
>     spec is=0A=
>     > pretty clear what data items 1-16 mean and are to be used", but=0A=
>     I note=0A=
>     > again, the spec doesn't specifically say how (or even whether) they=
=0A=
>     > are supposed to be used. I do not believe we should make an=0A=
>     exception=0A=
>     > for the above two.=0A=
>=0A=
>     If I was to implement the router side, I'd know what to do with the=
=0A=
>     other items, but not resource.  I defer to the WG to come to consensu=
s=0A=
>     on this question (and if the full value range is permissible.)=0A=
>=0A=
>     I look forward to hearing back on the other open topics.=0A=
>=0A=
>     Lou=0A=
>=0A=
>     >=0A=
>     > Regards,=0A=
>     > Stan=0A=
>     >=0A=
>     >=0A=
>     >=0A=
>     >=0A=
>     >     In which case I'd ask why is this limited to 100 rather than=0A=
>     the full=0A=
>     >     range of the field.=0A=
>     >=0A=
>     >     for resources, I actually have no guess as to what it means or=
=0A=
>     >     what you=0A=
>     >     expect a router to do with this. Without additional=0A=
>     information and=0A=
>     >     assuming your next statement is correct, it's for strictly=0A=
>     proprietary=0A=
>     >     (and non-interoperable) applications, I'd say drop it from=0A=
>     the spec.=0A=
>     >=0A=
>     >     Lou=0A=
>     >=0A=
>     >     > Oh, and as to the 2 above data items - they are=0A=
>     implemented with=0A=
>     >     > proprietary algorithms. If words to that effect will clear=0A=
>     the issue=0A=
>     >     > up, let me know and I'll attempt to add that.=0A=
>     >     >=0A=
>     >     > Regards,=0A=
>     >     > Stan=0A=
>     >     >=0A=
>     >=0A=
>     >=0A=
>     >=0A=
>=0A=
>=0A=
>=0A=
=0A=


From nobody Thu Dec  3 23:39:57 2015
Return-Path: <christopher.dearlove@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 6285C1B2EB0; Thu,  3 Dec 2015 23:39:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 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, 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 m0Ay3PlUpaF4; Thu,  3 Dec 2015 23:39:51 -0800 (PST)
Received: from mail-wm0-x233.google.com (mail-wm0-x233.google.com [IPv6:2a00:1450:400c:c09::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5E5211AD0AD; Thu,  3 Dec 2015 23:39:51 -0800 (PST)
Received: by wmww144 with SMTP id w144so50757426wmw.1; Thu, 03 Dec 2015 23:39:50 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=references:mime-version:in-reply-to:content-type :content-transfer-encoding:message-id:cc:from:subject:date:to; bh=xwlYFeAEyRo9khqX9Hjb6J7CRgvbiYU2PKETs8df0lA=; b=PkSynSlUftlFK8NXag/Yp4qZLi135gQqTcK9+//bsYiHPi8ZXHY/+9CXNXt6QzP2/G Mc82floR8KWKLIBxhg8hNLAPsuBT66EesvhNNBW7hEbgy1Qozj19dmIqujymMDZGixpj 5rSA0JD0h7ZnCTmpTWsodZ4AmT2Xd2fjPjCz3P0HZQiDkjJ8CTG0LiYK6e5yHiq62xTX 2TVkKdm64fItqCUwiGqXJ/uoZ3ylsZZEB89rTOfL5DF8A1bkTSCGkucEbiN0W6+ldz1L k1INtNkkAURLH9guWyn99OO12m9xO+W/mp3TFdt70enWvy0U2EpVq7OGZrvuj2ZWf0+1 e2lw==
X-Received: by 10.28.195.138 with SMTP id t132mr3015579wmf.86.1449214790006; Thu, 03 Dec 2015 23:39:50 -0800 (PST)
Received: from [10.4.237.225] (dab-ell1-h-32-10.dab.02.net. [82.132.239.197]) by smtp.gmail.com with ESMTPSA id vr10sm10975366wjc.38.2015.12.03.23.39.49 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 03 Dec 2015 23:39:49 -0800 (PST)
References: <20151203141014.13172.85185.idtracker@ietfa.amsl.com> <4C05351D-C18C-446C-B2CB-82FAAC9840B9@thomasclausen.org>
Mime-Version: 1.0 (1.0)
In-Reply-To: <4C05351D-C18C-446C-B2CB-82FAAC9840B9@thomasclausen.org>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Message-Id: <25B2290A-435F-45FB-AC38-C632A7993DB4@gmail.com>
X-Mailer: iPhone Mail (13B143)
From: Christopher Dearlove <christopher.dearlove@gmail.com>
Date: Fri, 4 Dec 2015 07:39:45 +0000
To: ietf@thomasclausen.org
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/ECVZxzMH-7i9IQiVdCYOz4fQxWg>
Cc: draft-ietf-manet-olsrv2-dat-metric@ietf.org, manet@ietf.org, manet-chairs@ietf.org, The IESG <iesg@ietf.org>, Stephen Farrell <stephen.farrell@cs.tcd.ie>
Subject: Re: [manet] Stephen Farrell's No Objection on draft-ietf-manet-olsrv2-dat-metric-10: (with COMMENT)
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: <https://mailarchive.ietf.org/arch/browse/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, 04 Dec 2015 07:39:53 -0000

Yes, OLSRv2 is the obvious use case. But separation of concerns: the abstrac=
t metric definition from the metric representation from the metric use, is a=
lways good. Though not having the draft in front of me, I'm not sure how muc=
h work that would be.

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

> On 4 Dec 2015, at 02:33, ietf@thomasclausen.org wrote:
>=20
> Stephen,
>=20
> I was actually one of the people recommending that the authors focus on OL=
SRv2.=20
>=20
> The reason for that being, simply, that we do not know how this metric beh=
aves with other protocols (yet), whereas we have some idea of how it behaves=
 with OLSRv2.  I also do not think that we know how it would fit into the ot=
her protocols in this WG, not to mention in other WGs.=20
>=20
> You are right, of course, if the experiment that this document enables all=
ows figuring that out, it would be interesting.
>=20
> Yet, I think that the primary goal (and, perhaps, the only real bar for pr=
ogressing eventually to std.track) of this experiment should be =E2=80=9Ccon=
firm if this is a metric worth recommending for OLSRv2=E2=80=9D not =E2=80=9C=
set out to boil the ocean and come up with the one metric to rule them all=E2=
=80=9D=E2=80=A6=20
>=20
> Thomas
>=20
>> On 03 Dec 2015, at 15:10, Stephen Farrell <stephen.farrell@cs.tcd.ie> wro=
te:
>>=20
>> Stephen Farrell has entered the following ballot position for
>> draft-ietf-manet-olsrv2-dat-metric-10: No Objection
>>=20
>> When responding, please keep the subject line intact and reply to all
>> email addresses included in the To and CC lines. (Feel free to cut this
>> introductory paragraph, however.)
>>=20
>>=20
>> Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html=

>> for more information about IESG DISCUSS and COMMENT positions.
>>=20
>>=20
>> The document, along with other ballot positions, can be found here:
>> https://datatracker.ietf.org/doc/draft-ietf-manet-olsrv2-dat-metric/
>>=20
>>=20
>>=20
>> ----------------------------------------------------------------------
>> COMMENT:
>> ----------------------------------------------------------------------
>>=20
>>=20
>> - General: This seems mostly to be an abstract metric that could be
>> re-used e.g. in ROLL or HOMENET (if it's good:-) but with
>> OLSR-specific text and concepts mixed in here and there.  It'd have
>> been better were it possible to separate the abstract metric from
>> the OLSR-specifics to make the former easier to re-use later. It's
>> fine if determining if that would be useful is a part of the
>> experiment, but it might be good to mention it here.
>>=20
>> - Section 6: In particular "fraction of the loss rate" isn't clear
>> to me, but maybe that's fine and it's known term of art to folks who
>> do metrics.
>>=20
>> - Section 11: Wrt the MitM comments from other ADs - one possiblity
>> here might be to recommend that protocols making use of this metric
>> should be cognizant of, and include mitigtions for, MitM attacks of
>> this kind. (Just a suggestion, feel free to ignore if you prefer.)=20
>>=20
>> - Thanks for handling the secdir review [1] - I think that all the
>> issues there were resolved, but do say if some still need a bit
>> more chatting.
>>=20
>>  [1] https://www.ietf.org/mail-archive/web/secdir/current/msg06185.html
>>=20
>>=20
>> _______________________________________________
>> manet mailing list
>> manet@ietf.org
>> https://www.ietf.org/mailman/listinfo/manet
>=20
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www.ietf.org/mailman/listinfo/manet


From nobody Fri Dec  4 03:44:16 2015
Return-Path: <stephen.farrell@cs.tcd.ie>
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 93FE41B308F; Fri,  4 Dec 2015 03:44:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.311
X-Spam-Level: 
X-Spam-Status: No, score=-4.311 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 TJGzM09dNVp5; Fri,  4 Dec 2015 03:44:12 -0800 (PST)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7A1AC1B3091; Fri,  4 Dec 2015 03:44:12 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 3F7F9BE3E; Fri,  4 Dec 2015 11:44:11 +0000 (GMT)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yoV8tBKqCtBx; Fri,  4 Dec 2015 11:44:09 +0000 (GMT)
Received: from [10.87.48.95] (unknown [86.46.20.32]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 57285BE38; Fri,  4 Dec 2015 11:44:08 +0000 (GMT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; s=mail; t=1449229449; bh=P/ih/cLhSTLvp7nCxrnQqHeYc6lNbfnFg3SfzCGBmh0=; h=Subject:To:References:Cc:From:Date:In-Reply-To:From; b=YPikZZZtN/Hkn67K3OMjASivvsI2xW0kjuY5KCOGLUuZh4xoKgt4PMqXzOj87lxNr TfCwKXC8e3l+RM1xx+iEjJfQtNYHgepnOYRkpMuPBtmn3Ous5aPe2imwthy4FDwSq9 YzeWvK638mMoJBRDEd9CJ0wBMWAJpXVPTMQsqT58=
To: ietf@thomasclausen.org
References: <20151203141014.13172.85185.idtracker@ietfa.amsl.com> <4C05351D-C18C-446C-B2CB-82FAAC9840B9@thomasclausen.org>
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Openpgp: id=D66EA7906F0B897FB2E97D582F3C8736805F8DA2; url=
Message-ID: <56617C88.6010302@cs.tcd.ie>
Date: Fri, 4 Dec 2015 11:44:08 +0000
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0
MIME-Version: 1.0
In-Reply-To: <4C05351D-C18C-446C-B2CB-82FAAC9840B9@thomasclausen.org>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/HJBYOCZ8XeSXWzvmy1vPJent4Ww>
Cc: draft-ietf-manet-olsrv2-dat-metric@ietf.org, manet@ietf.org, The IESG <iesg@ietf.org>, manet-chairs@ietf.org
Subject: Re: [manet] Stephen Farrell's No Objection on draft-ietf-manet-olsrv2-dat-metric-10: (with COMMENT)
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: <https://mailarchive.ietf.org/arch/browse/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, 04 Dec 2015 11:44:14 -0000

On 04/12/15 02:33, ietf@thomasclausen.org wrote:
> Stephen,
> 
> I was actually one of the people recommending that the authors focus
> on OLSRv2.
> 
> The reason for that being, simply, that we do not know how this
> metric behaves with other protocols (yet), whereas we have some idea
> of how it behaves with OLSRv2.  I also do not think that we know how
> it would fit into the other protocols in this WG, not to mention in
> other WGs.
> 
> You are right, of course, if the experiment that this document
> enables allows figuring that out, it would be interesting.
> 
> Yet, I think that the primary goal (and, perhaps, the only real bar
> for progressing eventually to std.track) of this experiment should be
> “confirm if this is a metric worth recommending for OLSRv2” not “set
> out to boil the ocean and come up with the one metric to rule them
> all”…

Understood, and my comment is entirely non-blocking.

However, wondering if the metric might work for ROLL and HOMENET
is hardly ocean-boiling, nor I think is considering re-use in
other pieces of similar ongoing IETF work.

I hope someone does think about this and we don't end up with a
battle of metrics nonsensically based on which protocol I'm using
on the same lower layers in the same conditions.

Cheers,
S.



> 
> Thomas
> 
>> On 03 Dec 2015, at 15:10, Stephen Farrell
>> <stephen.farrell@cs.tcd.ie> wrote:
>> 
>> Stephen Farrell has entered the following ballot position for 
>> draft-ietf-manet-olsrv2-dat-metric-10: No Objection
>> 
>> When responding, please keep the subject line intact and reply to
>> all email addresses included in the To and CC lines. (Feel free to
>> cut this introductory paragraph, however.)
>> 
>> 
>> Please refer to
>> https://www.ietf.org/iesg/statement/discuss-criteria.html for more
>> information about IESG DISCUSS and COMMENT positions.
>> 
>> 
>> The document, along with other ballot positions, can be found
>> here: 
>> https://datatracker.ietf.org/doc/draft-ietf-manet-olsrv2-dat-metric/
>>
>>
>>
>>
>> 
----------------------------------------------------------------------
>> COMMENT: 
>> ----------------------------------------------------------------------
>>
>>
>>
>> 
- General: This seems mostly to be an abstract metric that could be
>> re-used e.g. in ROLL or HOMENET (if it's good:-) but with 
>> OLSR-specific text and concepts mixed in here and there.  It'd
>> have been better were it possible to separate the abstract metric
>> from the OLSR-specifics to make the former easier to re-use later.
>> It's fine if determining if that would be useful is a part of the 
>> experiment, but it might be good to mention it here.
>> 
>> - Section 6: In particular "fraction of the loss rate" isn't clear 
>> to me, but maybe that's fine and it's known term of art to folks
>> who do metrics.
>> 
>> - Section 11: Wrt the MitM comments from other ADs - one
>> possiblity here might be to recommend that protocols making use of
>> this metric should be cognizant of, and include mitigtions for,
>> MitM attacks of this kind. (Just a suggestion, feel free to ignore
>> if you prefer.)
>> 
>> - Thanks for handling the secdir review [1] - I think that all the 
>> issues there were resolved, but do say if some still need a bit 
>> more chatting.
>> 
>> [1]
>> https://www.ietf.org/mail-archive/web/secdir/current/msg06185.html
>> 
>> 
>> _______________________________________________ manet mailing list 
>> manet@ietf.org https://www.ietf.org/mailman/listinfo/manet
> 


From nobody Fri Dec  4 04:03:40 2015
Return-Path: <hrogge@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 22FDD1A6FCB; Fri,  4 Dec 2015 04:03:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 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, 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 23ztvCN2QsXi; Fri,  4 Dec 2015 04:03:37 -0800 (PST)
Received: from mail-wm0-x236.google.com (mail-wm0-x236.google.com [IPv6:2a00:1450:400c:c09::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6C1751A6FCF; Fri,  4 Dec 2015 04:03:37 -0800 (PST)
Received: by wmww144 with SMTP id w144so59104814wmw.1; Fri, 04 Dec 2015 04:03:36 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; bh=MzAuCZ8RmT4a38V19wCVfd2wea8J4VGK2/M/cWG2wnk=; b=ZM4B9sZDae2S9yYMooW+VNb3aVfQLcJCmpInz6Wf2E5r2chQ/mxmbkHbc+/qwDXt6d P/B/BRYsRTv4sFgI/8YG2ly9QUCfgDtZ7IjzjAxjiMZSKV6G2q8oPFwbPWeVxCcUA27i rC2U15kWWz9e6jG2FW3wTfWrgqo5TwBcEToVk51T8fBHpqRvFOlM965pIqrVnCGs4oFT 4IJN5Ozv7SDEqKD/DHQFRt1XrWgiaBiD0AC2MMkLGQkZtiLzq+acWRziqvaxxgEmNOaC ahjZu19eVl74tkIFvyJjeZVCUGwdIC6EMNwfjZu8er6xif/R+lpmrcNi47DXFs0BNOqF gFiA==
X-Received: by 10.194.2.193 with SMTP id 1mr17504788wjw.26.1449230616052; Fri, 04 Dec 2015 04:03:36 -0800 (PST)
MIME-Version: 1.0
Received: by 10.27.94.70 with HTTP; Fri, 4 Dec 2015 04:03:06 -0800 (PST)
In-Reply-To: <56617C88.6010302@cs.tcd.ie>
References: <20151203141014.13172.85185.idtracker@ietfa.amsl.com> <4C05351D-C18C-446C-B2CB-82FAAC9840B9@thomasclausen.org> <56617C88.6010302@cs.tcd.ie>
From: Henning Rogge <hrogge@gmail.com>
Date: Fri, 4 Dec 2015 13:03:06 +0100
Message-ID: <CAGnRvurt5ATgwWmMGSUYfcvfx+rKPrQReQjq4Z6pXOS5HKq4KQ@mail.gmail.com>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/dOkatHJdmzweOkdi5P9JQ39ZcvA>
Cc: The IESG <iesg@ietf.org>, manet-chairs@ietf.org, MANET IETF <manet@ietf.org>, draft-ietf-manet-olsrv2-dat-metric@ietf.org
Subject: Re: [manet] Stephen Farrell's No Objection on draft-ietf-manet-olsrv2-dat-metric-10: (with COMMENT)
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: <https://mailarchive.ietf.org/arch/browse/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, 04 Dec 2015 12:03:39 -0000

On Fri, Dec 4, 2015 at 12:44 PM, Stephen Farrell
<stephen.farrell@cs.tcd.ie> wrote:
>
>
> On 04/12/15 02:33, ietf@thomasclausen.org wrote:
>> Stephen,
>>
>> I was actually one of the people recommending that the authors focus
>> on OLSRv2.
>>
>> The reason for that being, simply, that we do not know how this
>> metric behaves with other protocols (yet), whereas we have some idea
>> of how it behaves with OLSRv2.  I also do not think that we know how
>> it would fit into the other protocols in this WG, not to mention in
>> other WGs.
>>
>> You are right, of course, if the experiment that this document
>> enables allows figuring that out, it would be interesting.
>>
>> Yet, I think that the primary goal (and, perhaps, the only real bar
>> for progressing eventually to std.track) of this experiment should be
>> =E2=80=9Cconfirm if this is a metric worth recommending for OLSRv2=E2=80=
=9D not =E2=80=9Cset
>> out to boil the ocean and come up with the one metric to rule them
>> all=E2=80=9D=E2=80=A6
>
> Understood, and my comment is entirely non-blocking.
>
> However, wondering if the metric might work for ROLL and HOMENET
> is hardly ocean-boiling, nor I think is considering re-use in
> other pieces of similar ongoing IETF work.
>
> I hope someone does think about this and we don't end up with a
> battle of metrics nonsensically based on which protocol I'm using
> on the same lower layers in the same conditions.

Could this take the form of an appendix... one that discuss the
"input" of the DAT metric and how it could be adapted to other
protocols?

Henning Rogge


From nobody Fri Dec  4 04:08:53 2015
Return-Path: <stephen.farrell@cs.tcd.ie>
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 CF4E11A8739; Fri,  4 Dec 2015 04:08:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.311
X-Spam-Level: 
X-Spam-Status: No, score=-4.311 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 fuqxN1Ry0Wdv; Fri,  4 Dec 2015 04:08:46 -0800 (PST)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 783341A870E; Fri,  4 Dec 2015 04:08:46 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 1C2B2BE38; Fri,  4 Dec 2015 12:08:45 +0000 (GMT)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Si8-PHOZHbL8; Fri,  4 Dec 2015 12:08:43 +0000 (GMT)
Received: from [10.87.48.95] (unknown [86.46.20.32]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id D9E58BE3F; Fri,  4 Dec 2015 12:08:42 +0000 (GMT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; s=mail; t=1449230923; bh=6ktJlyn4y7RQpLuzCNvBSYuf8xjZkVyvZdyiM1H4vwM=; h=Subject:To:References:Cc:From:Date:In-Reply-To:From; b=WBbAxD6utLrcy4Mn5C7MojqHvCJirrfc7frW1ffbgoXho/0IMd57x0tQYTgqjZJ4L uHtw0B5n46DfYg/KB/QaOOml3094MhtdpXd/xEUdX7QDzK8H993PM6r8jAkizCAmRs Q/BTJO7oyqr2FjoOshg/T0zd/h3NPLIFP4NLX8uw=
To: Henning Rogge <hrogge@gmail.com>
References: <20151203141014.13172.85185.idtracker@ietfa.amsl.com> <4C05351D-C18C-446C-B2CB-82FAAC9840B9@thomasclausen.org> <56617C88.6010302@cs.tcd.ie> <CAGnRvurt5ATgwWmMGSUYfcvfx+rKPrQReQjq4Z6pXOS5HKq4KQ@mail.gmail.com>
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Openpgp: id=D66EA7906F0B897FB2E97D582F3C8736805F8DA2; url=
Message-ID: <5661824A.1080907@cs.tcd.ie>
Date: Fri, 4 Dec 2015 12:08:42 +0000
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0
MIME-Version: 1.0
In-Reply-To: <CAGnRvurt5ATgwWmMGSUYfcvfx+rKPrQReQjq4Z6pXOS5HKq4KQ@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/7P3PEfazYIZsHG-VlfmmWV3qieY>
Cc: draft-ietf-manet-olsrv2-dat-metric@ietf.org, MANET IETF <manet@ietf.org>, The IESG <iesg@ietf.org>, manet-chairs@ietf.org
Subject: Re: [manet] Stephen Farrell's No Objection on draft-ietf-manet-olsrv2-dat-metric-10: (with COMMENT)
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: <https://mailarchive.ietf.org/arch/browse/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, 04 Dec 2015 12:08:49 -0000

On 04/12/15 12:03, Henning Rogge wrote:
> On Fri, Dec 4, 2015 at 12:44 PM, Stephen Farrell
> <stephen.farrell@cs.tcd.ie> wrote:
>>
>>
>> On 04/12/15 02:33, ietf@thomasclausen.org wrote:
>>> Stephen,
>>>
>>> I was actually one of the people recommending that the authors focus
>>> on OLSRv2.
>>>
>>> The reason for that being, simply, that we do not know how this
>>> metric behaves with other protocols (yet), whereas we have some idea
>>> of how it behaves with OLSRv2.  I also do not think that we know how
>>> it would fit into the other protocols in this WG, not to mention in
>>> other WGs.
>>>
>>> You are right, of course, if the experiment that this document
>>> enables allows figuring that out, it would be interesting.
>>>
>>> Yet, I think that the primary goal (and, perhaps, the only real bar
>>> for progressing eventually to std.track) of this experiment should be
>>> “confirm if this is a metric worth recommending for OLSRv2” not “set
>>> out to boil the ocean and come up with the one metric to rule them
>>> all”…
>>
>> Understood, and my comment is entirely non-blocking.
>>
>> However, wondering if the metric might work for ROLL and HOMENET
>> is hardly ocean-boiling, nor I think is considering re-use in
>> other pieces of similar ongoing IETF work.
>>
>> I hope someone does think about this and we don't end up with a
>> battle of metrics nonsensically based on which protocol I'm using
>> on the same lower layers in the same conditions.
> 
> Could this take the form of an appendix... one that discuss the
> "input" of the DAT metric and how it could be adapted to other
> protocols?

You could do that. But that'd be more than I was asking about
really.

Mostly, what I think might be good is to say something like:
"the outcome of this experiment will include consideration of
whether and, if so, how, this metric could be re-used in other
relevant IETF protocols."

S.


> 
> Henning Rogge
> 


From nobody Fri Dec  4 04:33:28 2015
Return-Path: <chris.dearlove@baesystems.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 822CD1B2BA3 for <manet@ietfa.amsl.com>; Fri,  4 Dec 2015 04:33:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.909
X-Spam-Level: 
X-Spam-Status: No, score=-6.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, T_RP_MATCHES_RCVD=-0.01] 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 GFkSgYWVPhvd for <manet@ietfa.amsl.com>; Fri,  4 Dec 2015 04:33:22 -0800 (PST)
Received: from ukmta3.baesystems.com (ukmta3.baesystems.com [20.133.40.55]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 703A61A870E for <manet@ietf.org>; Fri,  4 Dec 2015 04:31:12 -0800 (PST)
X-IronPort-AV: E=Sophos; i="5.20,380,1444690800"; d="scan'208,217"; a="25385201"
Received: from unknown (HELO baemasodc005.greenlnk.net) ([10.108.52.29]) by ukmta3.baesystems.com with ESMTP; 04 Dec 2015 12:31:11 +0000
X-IronPort-AV: E=Sophos;i="5.20,380,1444690800";  d="scan'208,217";a="126168200"
Received: from glkxh0001v.greenlnk.net ([10.109.2.32]) by baemasodc005.greenlnk.net with ESMTP; 04 Dec 2015 12:31:10 +0000
Received: from GLKXM0002V.GREENLNK.net ([169.254.5.2]) by GLKXH0001V.GREENLNK.net ([10.109.2.32]) with mapi id 14.03.0248.002; Fri, 4 Dec 2015 12:31:10 +0000
From: "Dearlove, Christopher (UK)" <chris.dearlove@baesystems.com>
To: "manet@ietf.org" <manet@ietf.org>
Thread-Topic: DLEP-17 comments, part 5
Thread-Index: AdEuioI1nu3D6DG1QPO5w47r4t/cUA==
Date: Fri, 4 Dec 2015 12:31:09 +0000
Message-ID: <B31EEDDDB8ED7E4A93FDF12A4EECD30D7D76E443@GLKXM0002V.GREENLNK.net>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.109.62.6]
Content-Type: multipart/alternative; boundary="_000_B31EEDDDB8ED7E4A93FDF12A4EECD30D7D76E443GLKXM0002VGREEN_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/1vlMEHJS7EdVVf7iaeu0Ghcf0s0>
Subject: [manet] DLEP-17 comments, part 5
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: <https://mailarchive.ietf.org/arch/browse/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, 04 Dec 2015 12:33:26 -0000

--_000_B31EEDDDB8ED7E4A93FDF12A4EECD30D7D76E443GLKXM0002VGREEN_
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable

This is Sections 8 and 9. Still to go, Section 10 and appendices.

Section 8. At this point I wondered if the signal/message separation (which=
 I haven't respected in all my previous comments) was properly foreshadowed=
. And it isn't. Section 4 uses both in its subject line, but then never des=
cribes the difference. Consider this a comment on section 4 I missed earlie=
r.

Section 8.0 penultimate paragraph, should this be more clearly the acceptab=
ility of duplicate data items?

Section 8.1 I'm not familiar with the U+44 syntax (for UTC-8 I assume). Is =
it well-known to be hex?

Section 8.1 Length. Part of, rather than associated with.

Section 8.1 and elsewhere use SHALL for length restrictions. I know 2119 eq=
uates SHALL and MUST, but everywhere else is MUST, is there a reason for SH=
ALL here?

Section 8.1 (and I think also for messages) says one or more data items. Th=
at must be zero or more, there are several cases where zero is permitted, a=
nd at least one where it is required (heartbeat).

Section 8.1 in the list of reasons to reject, a missing required data item =
isn't listed, and as well as an unrecognised data item, should have not app=
ropriate to this signal. (And the same is probably said again for messages =
- the duplication makes me wonder if the separation loses more than it gain=
s.)

Section 8.2, similar comments to Section 8.1.

Section 8.3, Length. value should probably be Value. And the term header ha=
sn't been defined for a data item.

I would prefer a separation of the signal/message/data item syntax from the=
 behaviour. Admittedly there are a couple of corner cases (how to handle a =
missing Status - though that itself is a bit ugly). But for example section=
 9.5 (probably the worst case) starts with behaviour, has an aside (which I=
'll come back to), then more behaviour, then syntax, then some behaviour ag=
ain.

Yes, that would be significant work to restructure, and it's not my call to=
 say it should be done. But it would (in my opinion) make for a better docu=
ment.

Section 9.0 paragraph 1, last line, is "this header" (singular) correct?

Section 9.0 second paragraph "Following is" is wording I'd make a guess the=
 RFC Editor will change if still there. (Based on the last few RFC Editor r=
esponses I've had, they are changing quite a bit of wordings they don't lik=
e, more than they used to.)

Table 1. Apart from the IANA issue I raised in last part of my comments, wh=
y do signal and message types share a single space?

Table 1, previously noted Reserved is incorrect usage (17+)

Section 9.1 At this point with SHOULD, I'm left asking what if not? That I =
assume is because of the preconfiguration option discussed in an earlier se=
ction. But doesn't say so, and is part of the it would be clearer to separa=
te data from process.

Section 9.1 MAY implement own heuristics. This I think goes all the way to =
MUST, not even SHOULD. OK, possibly the heuristic is "don't bother", but yo=
u still need to decide that and decide it's acceptable.

Section 9.2 . Later lists use an "each of the following data items" even wh=
en singular. I have no idea whether the RFC Editor will accept that. But he=
re before the first list singular is used, and the second list uses "any" r=
ather than "each".

Section 9.2 the discussion of ports in the IP connection (or well-known if =
none) is this consistent with the use of the (not strictly correctly named)=
 unused port in earlier sections? I haven't worked this through.

Section 9.3 last line on page 22 "the" before "Session" (I happened to noti=
ce this one).

Section 9.3 first line on page 23. "should" probably should be SHOULD, exce=
pt I think it actually should be MUST (see above, where it's MAY, so incons=
istent in any case).

Section 9.5. The whole concept of router signalling modem should be brought=
 out earlier in the document. The paragraph starting "Concerning layer 3 ad=
dresses" is a particularly jarring one in the mixture of protocol and data.

Section 9.5 (and elsewhere) information base. I don't think this is discuss=
ed in the introduction. While a mandatory information base format may not b=
e right, a discussion of what data is collected - and what needs to be pers=
istent (such as list of extensions being used) I think would be appropriate.

Section 9.5 (and elsewhere) when indicating IPb4/IPv6 addresses "one or mor=
e of the following" is not clear, suggest "one or more of each of the follo=
wing" (which fits other pattern).

Section 9.7. This is one case of non-success defauilt Status. But here in p=
articular, no reference to where that status is found.

Section 9.14. paragraph three "Great care ... " Is a 2119 MUST appropriate =
here? I'm not sure this sentence helps the implementer. Why? How?

Section 9.15 paragraph 2 "what is" I'd delete the "what". Not sure about ca=
pitalised ONLY. And "partner" is a new term that shouldn't be used.

Section 9.16 Table 3 is here referenced. Apart from the IANA issue, there's=
 also no indication where that is.





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

--_000_B31EEDDDB8ED7E4A93FDF12A4EECD30D7D76E443GLKXM0002VGREEN_
Content-Type: text/html; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii">
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-GB" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">This is Sections 8 and 9. Still to go, Section 10 an=
d appendices.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Section 8. At this point I wondered if the signal/me=
ssage separation (which I haven&#8217;t respected in all my previous commen=
ts) was properly foreshadowed. And it isn&#8217;t. Section 4 uses both in i=
ts subject line, but then never describes the
 difference. Consider this a comment on section 4 I missed earlier.<o:p></o=
:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Section 8.0 penultimate paragraph, should this be mo=
re clearly the acceptability of duplicate data items?<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Section 8.1 I&#8217;m not familiar with the U&#43;44=
 syntax (for UTC-8 I assume). Is it well-known to be hex?<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Section 8.1 Length. Part of, rather than associated =
with.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Section 8.1 and elsewhere use SHALL for length restr=
ictions. I know 2119 equates SHALL and MUST, but everywhere else is MUST, i=
s there a reason for SHALL here?<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Section 8.1 (and I think also for messages) says one=
 or more data items. That must be zero or more, there are several cases whe=
re zero is permitted, and at least one where it is required (heartbeat).<o:=
p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Section 8.1 in the list of reasons to reject, a miss=
ing required data item isn&#8217;t listed, and as well as an unrecognised d=
ata item, should have not appropriate to this signal. (And the same is prob=
ably said again for messages &#8211; the duplication
 makes me wonder if the separation loses more than it gains.)<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Section 8.2, similar comments to Section 8.1.<o:p></=
o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Section 8.3, Length. value should probably be Value.=
 And the term header hasn&#8217;t been defined for a data item.<o:p></o:p><=
/p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">I would prefer a separation of the signal/message/da=
ta item syntax from the behaviour. Admittedly there are a couple of corner =
cases (how to handle a missing Status &#8211; though that itself is a bit u=
gly). But for example section 9.5 (probably
 the worst case) starts with behaviour, has an aside (which I&#8217;ll come=
 back to), then more behaviour, then syntax, then some behaviour again.<o:p=
></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Yes, that would be significant work to restructure, =
and it&#8217;s not my call to say it should be done. But it would (in my op=
inion) make for a better document.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Section 9.0 paragraph 1, last line, is &#8220;this h=
eader&#8221; (singular) correct?<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Section 9.0 second paragraph &#8220;Following is&#82=
21; is wording I&#8217;d make a guess the RFC Editor will change if still t=
here. (Based on the last few RFC Editor responses I&#8217;ve had, they are =
changing quite a bit of wordings they don&#8217;t like, more than
 they used to.)<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Table 1. Apart from the IANA issue I raised in last =
part of my comments, why do signal and message types share a single space?<=
o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Table 1, previously noted Reserved is incorrect usag=
e (17&#43;)<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Section 9.1 At this point with SHOULD, I&#8217;m lef=
t asking what if not? That I assume is because of the preconfiguration opti=
on discussed in an earlier section. But doesn&#8217;t say so, and is part o=
f the it would be clearer to separate data from
 process.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Section 9.1 MAY implement own heuristics. This I thi=
nk goes all the way to MUST, not even SHOULD. OK, possibly the heuristic is=
 &#8220;don&#8217;t bother&#8221;, but you still need to decide that and de=
cide it&#8217;s acceptable.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Section 9.2 . Later lists use an &#8220;each of the =
following data items&#8221; even when singular. I have no idea whether the =
RFC Editor will accept that. But here before the first list singular is use=
d, and the second list uses &#8220;any&#8221; rather than
 &#8220;each&#8221;.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Section 9.2 the discussion of ports in the IP connec=
tion (or well-known if none) is this consistent with the use of the (not st=
rictly correctly named) unused port in earlier sections? I haven&#8217;t wo=
rked this through.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Section 9.3 last line on page 22 &#8220;the&#8221; b=
efore &#8220;Session&#8221; (I happened to notice this one).<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Section 9.3 first line on page 23. &#8220;should&#82=
21; probably should be SHOULD, except I think it actually should be MUST (s=
ee above, where it&#8217;s MAY, so inconsistent in any case).<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Section 9.5. The whole concept of router signalling =
modem should be brought out earlier in the document. The paragraph starting=
 &#8220;Concerning layer 3 addresses&#8221; is a particularly jarring one i=
n the mixture of protocol and data.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Section 9.5 (and elsewhere) information base. I don&=
#8217;t think this is discussed in the introduction. While a mandatory info=
rmation base format may not be right, a discussion of what data is collecte=
d &#8211; and what needs to be persistent (such
 as list of extensions being used) I think would be appropriate.<o:p></o:p>=
</p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Section 9.5 (and elsewhere) when indicating IPb4/IPv=
6 addresses &#8220;one or more of the following&#8221; is not clear, sugges=
t &#8220;one or more of each of the following&#8221; (which fits other patt=
ern).<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Section 9.7. This is one case of non-success defauil=
t Status. But here in particular, no reference to where that status is foun=
d.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Section 9.14. paragraph three &#8220;Great care &#82=
30; &#8220; Is a 2119 MUST appropriate here? I&#8217;m not sure this senten=
ce helps the implementer. Why? How?<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Section 9.15 paragraph 2 &#8220;what is&#8221; I&#82=
17;d delete the &#8220;what&#8221;. Not sure about capitalised ONLY. And &#=
8220;partner&#8221; is a new term that shouldn&#8217;t be used.<o:p></o:p><=
/p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Section 9.16 Table 3 is here referenced. Apart from =
the IANA issue, there&#8217;s also no indication where that is.<o:p></o:p><=
/p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<p>********************************************************************<br>
This email and any attachments are confidential to the intended<br>
recipient and may also be privileged. If you are not the intended<br>
recipient please delete it from your system and notify the sender.<br>
You should not copy it or use it for any purpose nor disclose or<br>
distribute its contents to any other person.<br>
********************************************************************</p></b=
ody>
</html>

--_000_B31EEDDDB8ED7E4A93FDF12A4EECD30D7D76E443GLKXM0002VGREEN_--


From nobody Fri Dec  4 07:15:28 2015
Return-Path: <lberger@labn.net>
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 44DE11A87A0 for <manet@ietfa.amsl.com>; Fri,  4 Dec 2015 07:15:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level: 
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=unavailable
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 ikTkswzZFA-m for <manet@ietfa.amsl.com>; Fri,  4 Dec 2015 07:15:19 -0800 (PST)
Received: from gproxy7-pub.mail.unifiedlayer.com (gproxy7-pub.mail.unifiedlayer.com [70.40.196.235]) by ietfa.amsl.com (Postfix) with SMTP id C0BEF1A8776 for <manet@ietf.org>; Fri,  4 Dec 2015 07:15:18 -0800 (PST)
Received: (qmail 17986 invoked by uid 0); 4 Dec 2015 15:15:17 -0000
Received: from unknown (HELO cmgw2) (10.0.90.83) by gproxy7.mail.unifiedlayer.com with SMTP; 4 Dec 2015 15:15:17 -0000
Received: from box313.bluehost.com ([69.89.31.113]) by cmgw2 with  id pTFB1r00m2SSUrH01TFEht; Fri, 04 Dec 2015 08:15:15 -0700
X-Authority-Analysis: v=2.1 cv=dqRIVTQ4 c=1 sm=1 tr=0 a=h1BC+oY+fLhyFmnTBx92Jg==:117 a=wU2YTnxGAAAA:8 a=cNaOj0WVAAAA:8 a=IkcTkHD0fZMA:10 a=-NfooI8aBGcA:10 a=uEJ9t1CZtbIA:10 a=wUQvQvOEmiQA:10 a=k73-uVdKFN-6WlurXZcA:9 a=CwhSAS8Upv4KEKDO:21 a=_XA1GzmHrkPF-PQd:21 a=QEXdDO2ut3YA:10
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=labn.net; s=default;  h=Content-Transfer-Encoding:Content-Type:In-Reply-To:MIME-Version:Date:Message-ID:Cc:References:To:Subject:From; bh=tTBJ4EaLMouIulasptDJvIONuwTYs0bT6h4Q9Z6PS94=;  b=zcJdvVDd9jl6MBW8WsdwhcdrYW5mSWyAoWqrNb4hEnnlqQDHfJD5nymNBk6gv33dV2a+yqHlMjcV41v8GT7PdQQzqPNQL5PHcFvoOXprDF7MvHi7CfrkVefM5VjL8/J4;
Received: from box313.bluehost.com ([69.89.31.113]:50191 helo=[127.0.0.1]) by box313.bluehost.com with esmtpa (Exim 4.84) (envelope-from <lberger@labn.net>) id 1a4s4n-0006bo-9a; Fri, 04 Dec 2015 08:15:13 -0700
From: Lou Berger <lberger@labn.net>
To: Stan Ratliff <ratliffstan@gmail.com>
References: <5575E8A7.6030508@labn.net> <565E2EC4.50504@labn.net> <CALtoyo=2YrNT9CJCoqJ_x1+Cbyu8stfNuwjQXJFvjWfE9h+2Mw@mail.gmail.com> <565E4E8D.8080704@labn.net> <CALtoyokCuQOWAX8QYPK79_W+75cQhuFKvBGqwCf6NSpvD1-r2A@mail.gmail.com> <5660C1F3.7010708@labn.net> <CALtoyokEWk8CXKxE0ALsPH_GRyg7pcp3B+ucSi+rcFQGN=UzVw@mail.gmail.com>
Message-ID: <5661ADFD.9070505@labn.net>
Date: Fri, 4 Dec 2015 10:15:09 -0500
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.4.0
MIME-Version: 1.0
In-Reply-To: <CALtoyokEWk8CXKxE0ALsPH_GRyg7pcp3B+ucSi+rcFQGN=UzVw@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
X-Identified-User: {1038:box313.bluehost.com:labnmobi:labn.net} {sentby:smtp auth 69.89.31.113 authed with lberger@labn.net}
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/s6oJTvNqUaQ6FHdckcg6V_yj7HY>
Cc: MANET IETF <manet@ietf.org>, draft-ietf-manet-dlep@ietf.org
Subject: Re: [manet] DLEP-17 and RtgDir review of draft-ietf-manet-dlep-14
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: <https://mailarchive.ietf.org/arch/browse/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, 04 Dec 2015 15:15:27 -0000

Stan,


On 12/3/2015 5:41 PM, Stan Ratliff wrote:
> Lou,Â 
>
> With regard to the other points you raise, I'm thinking we (Rick and
> myself) need to address them with an update.

I think the technical issues should be discussed on list before making
changes.Â  Editorial issues can be addressed as you/the editors/the
chairs see fit.

> There are a few I'm frankly struggling with, and I'd like to reserve
> the option of coming back & saying "I don't get it", but...Â 
>
Please do.

> As long as you're asking, I do have one question - when discussing the
> transaction model, you say (in part):Â 
> "Â MoreÂ significantly, it's unclear how new messages should be handled."
>
> Since we're talking about new messages, and I have no idea what those
> messages would involve, it's somewhat hard to fully pin-down how they
> should be handled.
Part of this could be simply saying that if an unknown message is
received it is silently discarded, and may be reported via management
interfaces, e.g., counter increment or logging.Â  Also that any new
message types must identify their transaction class (destination or
session), alternately this can be implicit based on presence of the MAC
address data item...

> If the new messages are destination-oriented, they should fall into
> the "1 transaction in-flight per destination" rule. If the new
> messages are peer-oriented, then they would fall into the "1
> transaction in-flight per peer" rule... but in the case where a new
> message introduces some sort of new context that I can't currently
> see? I'm lost there.

I think the transaction model has come a long way (from no definition),
but it doesn't match my understanding of what was previously discussed
(single transaction. period.) and the model should be flushed out more
fully as well as discussed by the WG  In particular, I think it would be
good to hear from those who have implementations and their
experience/perspective.

Lou

>
> Regards,
> Stan
>
>
>
> On Thu, Dec 3, 2015 at 5:28 PM, Lou Berger <lberger@labn.net
> <mailto:lberger@labn.net>> wrote:
>
>     Stan,
>
>
>     On 12/1/2015 10:36 PM, Stan Ratliff wrote:
>     >
>     >
>     > On Tue, Dec 1, 2015 at 8:51 PM, Lou Berger <lberger@labn.net
>     > <mailto:lberger@labn.net <mailto:lberger@labn.net>>> wrote:
>     >
>     >Â  Â  Â Stan,
>     >
>     >Â  Â  Â On 12/1/2015 8:30 PM, Stan Ratliff wrote:
>     >Â  Â  Â > Lou,
>     >Â  Â  Â >
>     >Â  Â  Â > Thanks for the review. I wanted to respond to a couple
>     of your
>     >Â  Â  Â points
>     >Â  Â  Â > while they're fresh on my mind:
>     >
>
>     any thoughts on the other points?Â  Some of them a bit more
>     substantive.
>
>
>     >Â  Â  Â >
>     >Â  Â  Â > On Tue, Dec 1, 2015 at 6:35 PM, Lou Berger
>     <lberger@labn.net <mailto:lberger@labn.net>
>     >Â  Â  Â <mailto:lberger@labn.net <mailto:lberger@labn.net>>
>     >Â  Â  Â > <mailto:lberger@labn.net <mailto:lberger@labn.net>
>     <mailto:lberger@labn.net <mailto:lberger@labn.net>>>> wrote:
>     >Â  Â  Â >
>     >Â  Â  Â > [snip]
>     >Â  Â  Â >
>     >Â  Â  Â >
>     >Â  Â  Â >Â  Â  Â >Â  Â  Â - Sections 8.19 and 8.20 define
>     "Resources" related Data
>     >Â  Â  Â >Â  Â  Â Items.Â  The
>     >Â  Â  Â >Â  Â  Â >Â  Â  Â  Â definition related to these
>     basically says a
>     >Â  Â  Â resources is "An
>     >Â  Â  Â >Â  Â  Â >Â  Â  Â  Â 8-bit integer percentage, 0-100,
>     representing the
>     >Â  Â  Â amount of
>     >Â  Â  Â >Â  Â  Â >Â  Â  Â  Â resources allocated to
>     receiving|transmitting
>     >Â  Â  Â data.".Â  If
>     >Â  Â  Â >Â  Â  Â I were
>     >Â  Â  Â >Â  Â  Â >Â  Â  Â  Â implementing this protocol, I'd have
>     no idea how to
>     >Â  Â  Â produce,
>     >Â  Â  Â >Â  Â  Â >Â  Â  Â  Â update or use this information.Â  I
>     think there is
>     >Â  Â  Â some missing
>     >Â  Â  Â >Â  Â  Â >Â  Â  Â  Â informative and normative (RFC 2119)
>     text related to
>     >Â  Â  Â these
>     >Â  Â  Â >Â  Â  Â >Â  Â  Â  Â formats.
>     >Â  Â  Â >
>     >Â  Â  Â >Â  Â  Â Unless I missed it, no change.
>     >Â  Â  Â >
>     >Â  Â  Â >Â  Â  Â The basic point is that the document should
>     state what are
>     >Â  Â  Â >Â  Â  Â interoperable
>     >Â  Â  Â >Â  Â  Â implementations supposed to do with this parameter.
>     >Â  Â  Â >
>     >Â  Â  Â >Â  Â  Â >
>     >Â  Â  Â >Â  Â  Â >Â  Â  Â - Sections 8.21 and 8.22 (Relative Link
>     Quality) have
>     >Â  Â  Â a similar
>     >Â  Â  Â >Â  Â  Â >Â  Â  Â  Â problem of being under described, in
>     particular it's
>     >Â  Â  Â >Â  Â  Â unclear if
>     >Â  Â  Â >Â  Â  Â >Â  Â  Â  Â there's a meaningful,
>     non-proprietary definition for
>     >Â  Â  Â link
>     >Â  Â  Â >Â  Â  Â quality
>     >Â  Â  Â >Â  Â  Â >Â  Â  Â  Â that an implementation is to act on
>     or if the passed
>     >Â  Â  Â value
>     >Â  Â  Â >Â  Â  Â is just
>     >Â  Â  Â >Â  Â  Â >Â  Â  Â  Â passed for as monitoring
>     information.Â  Either way, this
>     >Â  Â  Â >Â  Â  Â needs to
>     >Â  Â  Â >Â  Â  Â >Â  Â  Â  Â be clarified.
>     >Â  Â  Â >Â  Â  Â Unless I missed it, no change.
>     >Â  Â  Â >
>     >Â  Â  Â >Â  Â  Â The basic point is that the document should
>     state what are
>     >Â  Â  Â >Â  Â  Â interoperable
>     >Â  Â  Â >Â  Â  Â implementations supposed to do with this parameter.
>     >Â  Â  Â >
>     >Â  Â  Â > [snip]
>     >Â  Â  Â >
>     >Â  Â  Â > The document doesn't mention what an interoperable
>     implementation is
>     >Â  Â  Â > supposed to do with *any* data item. AFAIK, no data
>     item has a "and
>     >Â  Â  Â > here's what you do with it" clause (and if there is one
>     there,
>     >Â  Â  Â please
>     >Â  Â  Â > let me know and I'll delete it). ;-)
>     >
>     >Â  Â  Â I think the spec is pretty clear what data items 1-16
>     mean and are
>     >Â  Â  Â to be
>     >Â  Â  Â used and to be meaningful in an interoperable scenario.
>     >
>     >Â  Â  Â >
>     >Â  Â  Â > What you actually do with the data items is out of
>     scope for this
>     >Â  Â  Â > document - by necessity. If we attempted to document
>     what could (or
>     >Â  Â  Â > should) be done with these data items, the spec is
>     'deat meat' -
>     >Â  Â  Â we'll
>     >Â  Â  Â > be at this for the next 40 years, since the data (for
>     instance, data
>     >Â  Â  Â > rate) *could* be used in more than one place - the
>     complexity
>     >Â  Â  Â explodes
>     >Â  Â  Â > exponentially, the arguing goes on and on without end.
>     The short
>     >Â  Â  Â > answer is - when received, the data can be a part of your
>     >Â  Â  Â > implementation's information base.
>     >Â  Â  Â >
>     >
>     >Â  Â  Â for link quality, I think simply saying that the metric
>     can be
>     >Â  Â  Â used (for
>     >Â  Â  Â example) by a router when selecting between alternate
>     available paths.
>     >
>     >
>     > That's true for any metric, including "Resources". I respectfully
>     > disagree that we should step into the "... , and here's what you
>     would
>     > do with it..." morass. You said in your response "I think the
>     spec is
>     > pretty clear what data items 1-16 mean and are to be used", but
>     I note
>     > again, the spec doesn't specifically say how (or even whether) they
>     > are supposed to be used. I do not believe we should make an
>     exception
>     > for the above two.
>
>     If I was to implement the router side, I'd know what to do with the
>     other items, but not resource.Â  I defer to the WG to come to
>     consensus
>     on this question (and if the full value range is permissible.)
>
>     I look forward to hearing back on the other open topics.
>
>     Lou
>
>     >
>     > Regards,
>     > Stan
>     >
>     >
>     >
>     >
>     >Â  Â  Â In which case I'd ask why is this limited to 100 rather
>     than the full
>     >Â  Â  Â range of the field.
>     >
>     >Â  Â  Â for resources, I actually have no guess as to what it
>     means or
>     >Â  Â  Â what you
>     >Â  Â  Â expect a router to do with this. Without additional
>     information and
>     >Â  Â  Â assuming your next statement is correct, it's for
>     strictly proprietary
>     >Â  Â  Â (and non-interoperable) applications, I'd say drop it
>     from the spec.
>     >
>     >Â  Â  Â Lou
>     >
>     >Â  Â  Â > Oh, and as to the 2 above data items - they are
>     implemented with
>     >Â  Â  Â > proprietary algorithms. If words to that effect will
>     clear the issue
>     >Â  Â  Â > up, let me know and I'll attempt to add that.
>     >Â  Â  Â >
>     >Â  Â  Â > Regards,
>     >Â  Â  Â > Stan
>     >Â  Â  Â >
>     >
>     >
>     >
>
>
>



From nobody Fri Dec  4 07:38:52 2015
Return-Path: <ratliffstan@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 59ABD1A87E1; Fri,  4 Dec 2015 07:38:51 -0800 (PST)
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 bj8cuChsYt9W; Fri,  4 Dec 2015 07:38:49 -0800 (PST)
Received: from mail-lf0-x233.google.com (mail-lf0-x233.google.com [IPv6:2a00:1450:4010:c07::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BA9F51A87F1; Fri,  4 Dec 2015 07:38:48 -0800 (PST)
Received: by lfaz4 with SMTP id z4so114660205lfa.0; Fri, 04 Dec 2015 07:38:47 -0800 (PST)
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=k9XGckJWy9GX2J94Rf1RAxC8/rJcmPCY5pnlh8jCk4c=; b=TX/40Ny0W732IDqvfrLeVxXsP65r810YDvZwKMtGPmFHnSk50ooymJrc6dr26jDDW1 y4rzFpj41zbmZ7fcSspd2BVnleKW/fqqeryvzQbSdlwXZ67iYF7JAwsDDvT/9ZZ9xDdk mvAa+LnQxoTfXmTKop1/naKpJHhN2IQs/9mj1jCeFJBmBRln16NRShBBhqCIsXIhRXDd AW1bECyJ8GIUMqqZUF0Ydsasm9Q196ZmhDhyeYSAjBCqm3QQ7BexFRvUCcvNAYhF6mJD ezRgWrGBvccHMZfsl2P9TINU/Ds8xUvK4jSPff/PeKaBQJuHwjac87x0/HW1MeN2UTl6 UGaQ==
MIME-Version: 1.0
X-Received: by 10.25.43.138 with SMTP id r132mr8311746lfr.103.1449243526923; Fri, 04 Dec 2015 07:38:46 -0800 (PST)
Received: by 10.25.209.71 with HTTP; Fri, 4 Dec 2015 07:38:46 -0800 (PST)
In-Reply-To: <5661ADFD.9070505@labn.net>
References: <5575E8A7.6030508@labn.net> <565E2EC4.50504@labn.net> <CALtoyo=2YrNT9CJCoqJ_x1+Cbyu8stfNuwjQXJFvjWfE9h+2Mw@mail.gmail.com> <565E4E8D.8080704@labn.net> <CALtoyokCuQOWAX8QYPK79_W+75cQhuFKvBGqwCf6NSpvD1-r2A@mail.gmail.com> <5660C1F3.7010708@labn.net> <CALtoyokEWk8CXKxE0ALsPH_GRyg7pcp3B+ucSi+rcFQGN=UzVw@mail.gmail.com> <5661ADFD.9070505@labn.net>
Date: Fri, 4 Dec 2015 10:38:46 -0500
Message-ID: <CALtoyomCk38LdrV33a+Tzeu2CQcojA0sYWxHBq1wS2-FHpXrRw@mail.gmail.com>
From: Stan Ratliff <ratliffstan@gmail.com>
To: Lou Berger <lberger@labn.net>
Content-Type: multipart/alternative; boundary=001a113fadfc9d8f1f0526144dbf
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/rRVsLnn334LWd2QbU7xSKRBQATk>
Cc: MANET IETF <manet@ietf.org>, draft-ietf-manet-dlep@ietf.org
Subject: Re: [manet] DLEP-17 and RtgDir review of draft-ietf-manet-dlep-14
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: <https://mailarchive.ietf.org/arch/browse/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, 04 Dec 2015 15:38:51 -0000

--001a113fadfc9d8f1f0526144dbf
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Lou,


On Fri, Dec 4, 2015 at 10:15 AM, Lou Berger <lberger@labn.net> wrote:

> Stan,
>
>
> On 12/3/2015 5:41 PM, Stan Ratliff wrote:
> > Lou,=C3=82
> >
> > With regard to the other points you raise, I'm thinking we (Rick and
> > myself) need to address them with an update.
>
> I think the technical issues should be discussed on list before making
> changes.=C3=82  Editorial issues can be addressed as you/the editors/the
> chairs see fit.
>

If there are specific technical issues you want discussed, then please let
me know. From an admittedly quick re-read of your last review, it seemed
that the biggest issue was that of IPv6-mandated discovery. We agree that
this should be both IPv4 and IPv6 based, and will change the doc to reflect
that.



>
> > There are a few I'm frankly struggling with, and I'd like to reserve
> > the option of coming back & saying "I don't get it", but...=C3=82
> >
> Please do.
>
> > As long as you're asking, I do have one question - when discussing the
> > transaction model, you say (in part):=C3=82
> > "=C3=82 More=C3=82 significantly, it's unclear how new messages should =
be handled."
> >
> > Since we're talking about new messages, and I have no idea what those
> > messages would involve, it's somewhat hard to fully pin-down how they
> > should be handled.
> Part of this could be simply saying that if an unknown message is
> received it is silently discarded, and may be reported via management
> interfaces, e.g., counter increment or logging.=C3=82  Also that any new
> message types must identify their transaction class (destination or
> session), alternately this can be implicit based on presence of the MAC
> address data item...
>

OK. I can go for some text along the lines of
"Extensions to this draft that contain new messages MUST clearly state
whether a message is a destination message, or a peer message. Those new
messages MUST NOT violate the existing transaction model."   ??



>
> > If the new messages are destination-oriented, they should fall into
> > the "1 transaction in-flight per destination" rule. If the new
> > messages are peer-oriented, then they would fall into the "1
> > transaction in-flight per peer" rule... but in the case where a new
> > message introduces some sort of new context that I can't currently
> > see? I'm lost there.
>
> I think the transaction model has come a long way (from no definition),
> but it doesn't match my understanding of what was previously discussed
> (single transaction. period.) and the model should be flushed out more
> fully as well as discussed by the WG  In particular, I think it would be
> good to hear from those who have implementations and their
> experience/perspective.
>

The documented transaction *is* the viewpoint of at least one
implementer... ;-) It's what I'd done at my previous company. Can you give
me an example of the additional flushing out that needs to be done? I'm
looking for a place to start.


Regards,
Stan


[snip]

--001a113fadfc9d8f1f0526144dbf
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Lou,=C2=A0<div><br><div class=3D"gmail_extra"><br><div cla=
ss=3D"gmail_quote">On Fri, Dec 4, 2015 at 10:15 AM, Lou Berger <span dir=3D=
"ltr">&lt;<a href=3D"mailto:lberger@labn.net" target=3D"_blank">lberger@lab=
n.net</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"m=
argin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Stan,<br>
<br>
<br>
On 12/3/2015 5:41 PM, Stan Ratliff wrote:<br>
&gt; Lou,=C3=82<br>
&gt;<br>
&gt; With regard to the other points you raise, I&#39;m thinking we (Rick a=
nd<br>
&gt; myself) need to address them with an update.<br>
<br>
I think the technical issues should be discussed on list before making<br>
changes.=C3=82=C2=A0 Editorial issues can be addressed as you/the editors/t=
he<br>
chairs see fit.<br></blockquote><div><br></div><div>If there are specific t=
echnical issues you want discussed, then please let me know. From an admitt=
edly quick re-read of your last review, it seemed that the biggest issue wa=
s that of IPv6-mandated discovery. We agree that this should be both IPv4 a=
nd IPv6 based, and will change the doc to reflect that.=C2=A0</div><div><br=
></div><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0=
 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
&gt; There are a few I&#39;m frankly struggling with, and I&#39;d like to r=
eserve<br>
&gt; the option of coming back &amp; saying &quot;I don&#39;t get it&quot;,=
 but...=C3=82<br>
&gt;<br>
Please do.<br>
<br>
&gt; As long as you&#39;re asking, I do have one question - when discussing=
 the<br>
&gt; transaction model, you say (in part):=C3=82<br>
&gt; &quot;=C3=82 More=C3=82 significantly, it&#39;s unclear how new messag=
es should be handled.&quot;<br>
&gt;<br>
&gt; Since we&#39;re talking about new messages, and I have no idea what th=
ose<br>
&gt; messages would involve, it&#39;s somewhat hard to fully pin-down how t=
hey<br>
&gt; should be handled.<br>
Part of this could be simply saying that if an unknown message is<br>
received it is silently discarded, and may be reported via management<br>
interfaces, e.g., counter increment or logging.=C3=82=C2=A0 Also that any n=
ew<br>
message types must identify their transaction class (destination or<br>
session), alternately this can be implicit based on presence of the MAC<br>
address data item...<br></blockquote><div><br></div><div>OK. I can go for s=
ome text along the lines of=C2=A0</div><div>&quot;Extensions to this draft =
that contain new messages MUST clearly state whether a message is a destina=
tion message, or a peer message. Those new messages MUST NOT violate the ex=
isting transaction model.&quot; =C2=A0 ??</div><div><br></div><div>=C2=A0</=
div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-lef=
t:1px #ccc solid;padding-left:1ex">
<br>
&gt; If the new messages are destination-oriented, they should fall into<br=
>
&gt; the &quot;1 transaction in-flight per destination&quot; rule. If the n=
ew<br>
&gt; messages are peer-oriented, then they would fall into the &quot;1<br>
&gt; transaction in-flight per peer&quot; rule... but in the case where a n=
ew<br>
&gt; message introduces some sort of new context that I can&#39;t currently=
<br>
&gt; see? I&#39;m lost there.<br>
<br>
I think the transaction model has come a long way (from no definition),<br>
but it doesn&#39;t match my understanding of what was previously discussed<=
br>
(single transaction. period.) and the model should be flushed out more<br>
fully as well as discussed by the WG=C2=A0 In particular, I think it would =
be<br>
good to hear from those who have implementations and their<br>
experience/perspective.<br></blockquote><div><br></div><div>The documented =
transaction *is* the viewpoint of at least one implementer... ;-) It&#39;s =
what I&#39;d done at my previous company. Can you give me an example of the=
 additional flushing out that needs to be done? I&#39;m looking for a place=
 to start.=C2=A0</div><div><br></div><div><br></div><div>Regards,</div><div=
>Stan</div><div><br></div><div>=C2=A0</div><div>[snip]</div></div></div></d=
iv></div>

--001a113fadfc9d8f1f0526144dbf--


From nobody Fri Dec  4 07:42:44 2015
Return-Path: <jch@pps.univ-paris-diderot.fr>
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 90A901A8864; Fri,  4 Dec 2015 07:42:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.55
X-Spam-Level: 
X-Spam-Status: No, score=-1.55 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_FR=0.35] autolearn=no
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 bZh6rf5IhsKX; Fri,  4 Dec 2015 07:42:38 -0800 (PST)
Received: from korolev.univ-paris7.fr (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AF7D01A8860; Fri,  4 Dec 2015 07:42:37 -0800 (PST)
Received: from potemkin.univ-paris7.fr (potemkin.univ-paris7.fr [IPv6:2001:660:3301:8000::1:1]) by korolev.univ-paris7.fr (8.14.4/8.14.4/relay1/56228) with ESMTP id tB4FgZVv005661 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 4 Dec 2015 16:42:35 +0100
Received: from mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [81.194.30.253]) by potemkin.univ-paris7.fr (8.14.4/8.14.4/relay2/56228) with ESMTP id tB4FgZi0000988; Fri, 4 Dec 2015 16:42:35 +0100
Received: from mailhub.math.univ-paris-diderot.fr (localhost [127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTP id 6E00461F9A; Fri,  4 Dec 2015 16:42:35 +0100 (CET)
X-Virus-Scanned: amavisd-new at math.univ-paris-diderot.fr
Received: from mailhub.math.univ-paris-diderot.fr ([127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [127.0.0.1]) (amavisd-new, port 10023) with ESMTP id q3ssGymWn6hk; Fri,  4 Dec 2015 16:42:34 +0100 (CET)
Received: from lanthane.pps.univ-paris-diderot.fr (unknown [172.23.36.54]) (Authenticated sender: jch) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTPSA id 109A461FAD; Fri,  4 Dec 2015 16:42:33 +0100 (CET)
Received: from localhost ([::1] helo=lanthane.pps.univ-paris-diderot.fr) by lanthane.pps.univ-paris-diderot.fr with esmtp (Exim 4.86) (envelope-from <jch@pps.univ-paris-diderot.fr>) id 1a4sVF-0004oa-NF; Fri, 04 Dec 2015 16:42:33 +0100
Date: Fri, 04 Dec 2015 16:42:33 +0100
Message-ID: <7ivb8ep6dy.wl-jch@pps.univ-paris-diderot.fr>
From: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
To: ietf@thomasclausen.org
In-Reply-To: <4C05351D-C18C-446C-B2CB-82FAAC9840B9@thomasclausen.org>
References: <20151203141014.13172.85185.idtracker@ietfa.amsl.com> <4C05351D-C18C-446C-B2CB-82FAAC9840B9@thomasclausen.org>
User-Agent: Wanderlust/2.15.9
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]); Fri, 04 Dec 2015 16:42:35 +0100 (CET)
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (potemkin.univ-paris7.fr [194.254.61.141]); Fri, 04 Dec 2015 16:42:35 +0100 (CET)
X-Miltered: at korolev with ID 5661B46B.002 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-Miltered: at potemkin with ID 5661B46B.000 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 5661B46B.002 from potemkin.univ-paris7.fr/potemkin.univ-paris7.fr/null/potemkin.univ-paris7.fr/<jch@pps.univ-paris-diderot.fr>
X-j-chkmail-Enveloppe: 5661B46B.000 from mailhub.math.univ-paris-diderot.fr/mailhub.math.univ-paris-diderot.fr/null/mailhub.math.univ-paris-diderot.fr/<jch@pps.univ-paris-diderot.fr>
X-j-chkmail-Score: MSGID : 5661B46B.002 on korolev.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Score: MSGID : 5661B46B.000 on potemkin.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Status: Ham
X-j-chkmail-Status: Ham
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/2BtTyNyfOnvD0UCpuQB6b98HwCQ>
Cc: draft-ietf-manet-olsrv2-dat-metric@ietf.org, manet@ietf.org, The IESG <iesg@ietf.org>, manet-chairs@ietf.org
Subject: Re: [manet] Stephen Farrell's No Objection on draft-ietf-manet-olsrv2-dat-metric-10: (with COMMENT)
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: <https://mailarchive.ietf.org/arch/browse/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, 04 Dec 2015 15:42:39 -0000

> The reason for that being, simply, that we do not know how this metric
> behaves with other protocols (yet),

Uh-huh.

Unlike ETX, ETT and friends, this metric is unidirectional -- it only
considers packet loss in one direction.  Since OLSRv2 already has
a mechanism for pruning unidirectional links, DAT in OLSRv2 will only be
applied to bidirectional links, and therefore yield reasonable results.
This would not be the case in, say, Babel, where the protocol relies on
the metric to detect and prune unidirectional links.

(Of course, there's nothing preventing one from adding an OLSRv2-style
mechanism to Babel, but that doesn't contradict my point, which is that
DAT *as it is defined now* would probably not work well with Babel *as it
is defined now*.)

So I think we're in full agreement -- DAT should not be recommended for
protocols other than OLSRv2 until we have more data.

(I mentioned in Berlin that the point about OLSRv2 using bidirectional
links only should be made explicitly in the document, I don't know if this
comment was taken into account.)

-- Juliusz


From nobody Fri Dec  4 07:45:34 2015
Return-Path: <jch@pps.univ-paris-diderot.fr>
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 DE1A81A885E for <manet@ietfa.amsl.com>; Fri,  4 Dec 2015 07:45:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.55
X-Spam-Level: 
X-Spam-Status: No, score=-1.55 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_FR=0.35] autolearn=no
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 HDeLLhXNT-Oq for <manet@ietfa.amsl.com>; Fri,  4 Dec 2015 07:45:32 -0800 (PST)
Received: from korolev.univ-paris7.fr (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C38191A887E for <manet@ietf.org>; Fri,  4 Dec 2015 07:45:16 -0800 (PST)
Received: from potemkin.univ-paris7.fr (potemkin.univ-paris7.fr [IPv6:2001:660:3301:8000::1:1]) by korolev.univ-paris7.fr (8.14.4/8.14.4/relay1/56228) with ESMTP id tB4FjBwr007118 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 4 Dec 2015 16:45:11 +0100
Received: from mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [81.194.30.253]) by potemkin.univ-paris7.fr (8.14.4/8.14.4/relay2/56228) with ESMTP id tB4FjBeJ002130; Fri, 4 Dec 2015 16:45:11 +0100
Received: from mailhub.math.univ-paris-diderot.fr (localhost [127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTP id 7C5F661FAD; Fri,  4 Dec 2015 16:45:11 +0100 (CET)
X-Virus-Scanned: amavisd-new at math.univ-paris-diderot.fr
Received: from mailhub.math.univ-paris-diderot.fr ([127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [127.0.0.1]) (amavisd-new, port 10023) with ESMTP id 8tqZx-aozCZg; Fri,  4 Dec 2015 16:45:10 +0100 (CET)
Received: from lanthane.pps.univ-paris-diderot.fr (unknown [172.23.36.54]) (Authenticated sender: jch) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTPSA id 33E4061FAB; Fri,  4 Dec 2015 16:45:10 +0100 (CET)
Received: from localhost ([::1] helo=lanthane.pps.univ-paris-diderot.fr) by lanthane.pps.univ-paris-diderot.fr with esmtp (Exim 4.86) (envelope-from <jch@pps.univ-paris-diderot.fr>) id 1a4sXl-0004pE-W8; Fri, 04 Dec 2015 16:45:10 +0100
Date: Fri, 04 Dec 2015 16:45:09 +0100
Message-ID: <7itwnyp69m.wl-jch@pps.univ-paris-diderot.fr>
From: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
To: "Dearlove, Christopher (UK)" <chris.dearlove@baesystems.com>
In-Reply-To: <B31EEDDDB8ED7E4A93FDF12A4EECD30D7D76E443@GLKXM0002V.GREENLNK.net>
References: <B31EEDDDB8ED7E4A93FDF12A4EECD30D7D76E443@GLKXM0002V.GREENLNK.net>
User-Agent: Wanderlust/2.15.9
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]); Fri, 04 Dec 2015 16:45:11 +0100 (CET)
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (potemkin.univ-paris7.fr [194.254.61.141]); Fri, 04 Dec 2015 16:45:11 +0100 (CET)
X-Miltered: at korolev with ID 5661B507.002 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-Miltered: at potemkin with ID 5661B507.002 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 5661B507.002 from potemkin.univ-paris7.fr/potemkin.univ-paris7.fr/null/potemkin.univ-paris7.fr/<jch@pps.univ-paris-diderot.fr>
X-j-chkmail-Enveloppe: 5661B507.002 from mailhub.math.univ-paris-diderot.fr/mailhub.math.univ-paris-diderot.fr/null/mailhub.math.univ-paris-diderot.fr/<jch@pps.univ-paris-diderot.fr>
X-j-chkmail-Score: MSGID : 5661B507.002 on korolev.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Score: MSGID : 5661B507.002 on potemkin.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Status: Ham
X-j-chkmail-Status: Ham
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/mvx9-Kfoy4XR8ZifELK1exqkNq8>
Cc: "manet@ietf.org" <manet@ietf.org>
Subject: Re: [manet] DLEP-17 comments, part 5
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: <https://mailarchive.ietf.org/arch/browse/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, 04 Dec 2015 15:45:33 -0000

> Section 8.1 I’m not familiar with the U+44 syntax (for UTC-8 I assume). Is
> it well-known to be hex?

Yes, but it requires 4 hex digits -- it should say U+0044.

-- Juliusz


From nobody Fri Dec  4 07:46:50 2015
Return-Path: <ratliffstan@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 6B3BE1A8868 for <manet@ietfa.amsl.com>; Fri,  4 Dec 2015 07:46:48 -0800 (PST)
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 3fJckbIkerHp for <manet@ietfa.amsl.com>; Fri,  4 Dec 2015 07:46:46 -0800 (PST)
Received: from mail-lb0-x232.google.com (mail-lb0-x232.google.com [IPv6:2a00:1450:4010:c04::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 721941A8833 for <manet@ietf.org>; Fri,  4 Dec 2015 07:46:46 -0800 (PST)
Received: by lbblt2 with SMTP id lt2so22949777lbb.3 for <manet@ietf.org>; Fri, 04 Dec 2015 07:46:44 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:date:message-id:subject:from:to:content-type; bh=tHL3ZiMahD74ml86XRQF8aeEpwqf0k2/RAjRyINrwWc=; b=e26rGe8kyvi11udkH+ZmNZ9pFxFvFaM42lCU3B+v0iuBA0R6aKiOwaPusHTj0AdrYw XKeTkTaqv0yasqI3mB2ndZJLK/PL66uKb/1890Uj0r3hNgpsR6H2fa5lanHnHKRgyk57 qGydSeLmIRyOz7IWiUzyYQWZG5FT2dlod2D6haIVFxnWEK8PHcuRsqMPcrQCr2W0dtP7 A4Q0fyP5ASWXTjJqbTCK79ZA2Z5z/YCPL+SyN5RcCfhtQD246eUxU3B0nMCzgnFwuZ/d /C3wLHQohv4tj4TW1YzCEWcZMtOqhcKAQmEHJ3ZZX3HpeCkyoM3yhTYJ43fIG9BpeCtb 9uKQ==
MIME-Version: 1.0
X-Received: by 10.112.200.40 with SMTP id jp8mr8251843lbc.104.1449244004601; Fri, 04 Dec 2015 07:46:44 -0800 (PST)
Received: by 10.25.209.71 with HTTP; Fri, 4 Dec 2015 07:46:44 -0800 (PST)
Date: Fri, 4 Dec 2015 10:46:44 -0500
Message-ID: <CALtoyokXY5aNcZLgCV5hs1aDogi+A4f7SBaC7vZoXhTZtKqbXg@mail.gmail.com>
From: Stan Ratliff <ratliffstan@gmail.com>
To: MANET IETF <manet@ietf.org>
Content-Type: multipart/alternative; boundary=001a11c36b2a165a090526146a5c
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/G-ofAtbqnLA2Qmy7YPjW_7vyHiU>
Subject: [manet] DLEP reviews - new info concerning Destination Up
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: <https://mailarchive.ietf.org/arch/browse/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, 04 Dec 2015 15:46:48 -0000

--001a11c36b2a165a090526146a5c
Content-Type: text/plain; charset=UTF-8

Hello WG -

There has been some discussion amongst the authors about the current use of
Destination Up. Specifically, the is concern that allowing Destination Up
to originate from the router (Multicast group creation) towards the modem
is confusing, and is likely to be mis-handled by implementers.

One possible approach is to make the Destination Up message flow *only*
from modem to router, and to introduce a new message that the router would
employ to announce router-discovered (or router-created) destinations - a
"Destination Announce" message, if you will.

The modem action on receipt of this new Destination Announce message would
be to (1) perform any proprietary setup required to flow traffic to the
dest across the RF network, and then to periodically report metrics on the
Announced destination, via 'Destination Update' messages.

Thoughts? Flames? Concerns?

Regards,
Stan

--001a11c36b2a165a090526146a5c
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hello WG -=C2=A0<div><br></div><div>There has been some di=
scussion amongst the authors about the current use of Destination Up. Speci=
fically, the is concern that allowing Destination Up to originate from the =
router (Multicast group creation) towards the modem is confusing, and is li=
kely to be mis-handled by implementers. =C2=A0</div><div><br></div><div>One=
 possible approach is to make the Destination Up message flow *only* from m=
odem to router, and to introduce a new message that the router would employ=
 to announce router-discovered (or router-created) destinations - a &quot;D=
estination Announce&quot; message, if you will.=C2=A0</div><div><br></div><=
div>The modem action on receipt of this new Destination Announce message wo=
uld be to (1) perform any proprietary setup required to flow traffic to the=
 dest across the RF network, and then to periodically report metrics on the=
 Announced destination, via &#39;Destination Update&#39; messages.=C2=A0</d=
iv><div><br></div><div>Thoughts? Flames? Concerns?=C2=A0</div><div><br></di=
v><div>Regards,<br>Stan</div></div>

--001a11c36b2a165a090526146a5c--


From nobody Fri Dec  4 07:55:17 2015
Return-Path: <hrogge@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 C6DB71A88BC for <manet@ietfa.amsl.com>; Fri,  4 Dec 2015 07:55:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 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, 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 05JrlErVrR4O for <manet@ietfa.amsl.com>; Fri,  4 Dec 2015 07:55:14 -0800 (PST)
Received: from mail-wm0-x234.google.com (mail-wm0-x234.google.com [IPv6:2a00:1450:400c:c09::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 795CD1A8897 for <manet@ietf.org>; Fri,  4 Dec 2015 07:55:14 -0800 (PST)
Received: by wmec201 with SMTP id c201so80400198wme.0 for <manet@ietf.org>; Fri, 04 Dec 2015 07:55:13 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=ZOwkvNQJ2UfOp9EfPBcLMkMYKIidjxzMVRJAtClkpg0=; b=tq+LuRM49qEkwPxXnMbVnTv5pJ4knp3tNuznj4emGrkJLrCYPEOoLgMeeQ4yJW7voe Q43ELNSDy8NoHJHjuy89l/W6GTFfKpXgt3X0PzK1cqkt7KxW5I29p7jQAq8Z8AYBcKvJ PDWgAGTdLDwBMgbZ8WcRmv5leVCp4RjhiZo9O7ypxmoOcJthnlfWQsgfTPPaoBdzNzso vFgprGdOa9x4P9pdQvn4olTOHy6E3O9+D1/mC4K07dHwhQcb1KgmuOyxWJqzBxF1+Va8 2u4nH+Opr8I9Z1alp9wFZ+9ToBAWXsLBaVbEYKV4svrX0CUEIL8tn2sZg3r9z6elprMw Y/YQ==
X-Received: by 10.194.2.193 with SMTP id 1mr18812188wjw.26.1449244512953; Fri, 04 Dec 2015 07:55:12 -0800 (PST)
MIME-Version: 1.0
Received: by 10.27.94.70 with HTTP; Fri, 4 Dec 2015 07:54:43 -0800 (PST)
In-Reply-To: <CALtoyokXY5aNcZLgCV5hs1aDogi+A4f7SBaC7vZoXhTZtKqbXg@mail.gmail.com>
References: <CALtoyokXY5aNcZLgCV5hs1aDogi+A4f7SBaC7vZoXhTZtKqbXg@mail.gmail.com>
From: Henning Rogge <hrogge@gmail.com>
Date: Fri, 4 Dec 2015 16:54:43 +0100
Message-ID: <CAGnRvurDfG_nM47gPUKddSZ1sRY9C_J65Jm46CvruCUS_evYLg@mail.gmail.com>
To: Stan Ratliff <ratliffstan@gmail.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/_BxB_iUE2zkmZnEnbzpLO5-13K0>
Cc: MANET IETF <manet@ietf.org>
Subject: Re: [manet] DLEP reviews - new info concerning Destination Up
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: <https://mailarchive.ietf.org/arch/browse/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, 04 Dec 2015 15:55:15 -0000

On Fri, Dec 4, 2015 at 4:46 PM, Stan Ratliff <ratliffstan@gmail.com> wrote:
> Hello WG -
>
> There has been some discussion amongst the authors about the current use of
> Destination Up. Specifically, the is concern that allowing Destination Up to
> originate from the router (Multicast group creation) towards the modem is
> confusing, and is likely to be mis-handled by implementers.
>
> One possible approach is to make the Destination Up message flow *only* from
> modem to router, and to introduce a new message that the router would employ
> to announce router-discovered (or router-created) destinations - a
> "Destination Announce" message, if you will.
>
> The modem action on receipt of this new Destination Announce message would
> be to (1) perform any proprietary setup required to flow traffic to the dest
> across the RF network, and then to periodically report metrics on the
> Announced destination, via 'Destination Update' messages.

So "Destination up" (router to radio) could be (as an example) used
for setting up a multicast address (mac to IP combination) ?

Henning


From nobody Fri Dec  4 07:58:48 2015
Return-Path: <ratliffstan@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 7945D1A88D2 for <manet@ietfa.amsl.com>; Fri,  4 Dec 2015 07:58:47 -0800 (PST)
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 9oIRYvDzogdY for <manet@ietfa.amsl.com>; Fri,  4 Dec 2015 07:58:46 -0800 (PST)
Received: from mail-lf0-x232.google.com (mail-lf0-x232.google.com [IPv6:2a00:1450:4010:c07::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C9DCA1A88D1 for <manet@ietf.org>; Fri,  4 Dec 2015 07:58:45 -0800 (PST)
Received: by lfs39 with SMTP id 39so111501713lfs.3 for <manet@ietf.org>; Fri, 04 Dec 2015 07:58:44 -0800 (PST)
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=mrlUR7CM2hMN9QGE9VQJAE0pPabp4tOMy01MkrvhhEg=; b=jLhsMJtqvPyGeHG2QZCuWWZRM7NZYOStqdg1wnrOra0nUFG3BQV1ZKuFtYyVqjWdcS Sb9SBHvRClfsQyK5YDJ8Hs0ii+5m2zj9aA+KPPlswtLkJmplRTWUrSTlsD3kZY9ZuPeD Mm2KQx8G/Ph4cyGFHRLbvT+Buiu3eDqf7dGUPTA+OGjV3Z6hd0TUjiJPX3zmuFX5DwF4 pKquAHrNJqDe2mLbZvsjXqzAdWPKgvSITANyOE9GmrbnSotSBrAz5HZhiu7Sxuyce9Z6 WmfKGKM9FZRwsJr0XT0qOgxzTDHQ4DWU4SAjI+snr9nGGXKpWcjBlaIV0X4VY8RRc56H 5FDg==
MIME-Version: 1.0
X-Received: by 10.25.83.146 with SMTP id h140mr7740794lfb.52.1449244723903; Fri, 04 Dec 2015 07:58:43 -0800 (PST)
Received: by 10.25.209.71 with HTTP; Fri, 4 Dec 2015 07:58:43 -0800 (PST)
In-Reply-To: <CAGnRvurDfG_nM47gPUKddSZ1sRY9C_J65Jm46CvruCUS_evYLg@mail.gmail.com>
References: <CALtoyokXY5aNcZLgCV5hs1aDogi+A4f7SBaC7vZoXhTZtKqbXg@mail.gmail.com> <CAGnRvurDfG_nM47gPUKddSZ1sRY9C_J65Jm46CvruCUS_evYLg@mail.gmail.com>
Date: Fri, 4 Dec 2015 10:58:43 -0500
Message-ID: <CALtoyon3CjhN+EoyRDfag4ZtgV424Wmd6-L=_cF08_LBrU37tw@mail.gmail.com>
From: Stan Ratliff <ratliffstan@gmail.com>
To: Henning Rogge <hrogge@gmail.com>
Content-Type: multipart/alternative; boundary=001a11419fc0f604230526149440
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/puqvJgjDD6jA17MeEtWI3dNeF34>
Cc: MANET IETF <manet@ietf.org>
Subject: Re: [manet] DLEP reviews - new info concerning Destination Up
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: <https://mailarchive.ietf.org/arch/browse/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, 04 Dec 2015 15:58:47 -0000

--001a11419fc0f604230526149440
Content-Type: text/plain; charset=UTF-8

On Fri, Dec 4, 2015 at 10:54 AM, Henning Rogge <hrogge@gmail.com> wrote:

> On Fri, Dec 4, 2015 at 4:46 PM, Stan Ratliff <ratliffstan@gmail.com>
> wrote:
> > Hello WG -
> >
> > There has been some discussion amongst the authors about the current use
> of
> > Destination Up. Specifically, the is concern that allowing Destination
> Up to
> > originate from the router (Multicast group creation) towards the modem is
> > confusing, and is likely to be mis-handled by implementers.
> >
> > One possible approach is to make the Destination Up message flow *only*
> from
> > modem to router, and to introduce a new message that the router would
> employ
> > to announce router-discovered (or router-created) destinations - a
> > "Destination Announce" message, if you will.
> >
> > The modem action on receipt of this new Destination Announce message
> would
> > be to (1) perform any proprietary setup required to flow traffic to the
> dest
> > across the RF network, and then to periodically report metrics on the
> > Announced destination, via 'Destination Update' messages.
>
> So "Destination up" (router to radio) could be (as an example) used
> for setting up a multicast address (mac to IP combination) ?
>

Yes. In fact, MCAST setup is the only known use case at this point, but I'm
uncomfortable with scoping it down to just MCAST in the document. There may
well be other use-cases.

Regards,
Stan

--001a11419fc0f604230526149440
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><div class=3D"gmail_quo=
te">On Fri, Dec 4, 2015 at 10:54 AM, Henning Rogge <span dir=3D"ltr">&lt;<a=
 href=3D"mailto:hrogge@gmail.com" target=3D"_blank">hrogge@gmail.com</a>&gt=
;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 =
.8ex;border-left:1px #ccc solid;padding-left:1ex">On Fri, Dec 4, 2015 at 4:=
46 PM, Stan Ratliff &lt;<a href=3D"mailto:ratliffstan@gmail.com">ratliffsta=
n@gmail.com</a>&gt; wrote:<br>
&gt; Hello WG -<br>
&gt;<br>
&gt; There has been some discussion amongst the authors about the current u=
se of<br>
&gt; Destination Up. Specifically, the is concern that allowing Destination=
 Up to<br>
&gt; originate from the router (Multicast group creation) towards the modem=
 is<br>
&gt; confusing, and is likely to be mis-handled by implementers.<br>
&gt;<br>
&gt; One possible approach is to make the Destination Up message flow *only=
* from<br>
&gt; modem to router, and to introduce a new message that the router would =
employ<br>
&gt; to announce router-discovered (or router-created) destinations - a<br>
&gt; &quot;Destination Announce&quot; message, if you will.<br>
&gt;<br>
&gt; The modem action on receipt of this new Destination Announce message w=
ould<br>
&gt; be to (1) perform any proprietary setup required to flow traffic to th=
e dest<br>
&gt; across the RF network, and then to periodically report metrics on the<=
br>
&gt; Announced destination, via &#39;Destination Update&#39; messages.<br>
<br>
So &quot;Destination up&quot; (router to radio) could be (as an example) us=
ed<br>
for setting up a multicast address (mac to IP combination) ?<br></blockquot=
e><div><br></div><div>Yes. In fact, MCAST setup is the only known use case =
at this point, but I&#39;m uncomfortable with scoping it down to just MCAST=
 in the document. There may well be other use-cases.=C2=A0</div><div><br></=
div><div>Regards,</div><div>Stan</div><div><br></div><div><br></div></div><=
/div></div>

--001a11419fc0f604230526149440--


From nobody Fri Dec  4 08:14:37 2015
Return-Path: <hrogge@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 9F72A1A8957 for <manet@ietfa.amsl.com>; Fri,  4 Dec 2015 08:14:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 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, 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 z-tkKgzFglr3 for <manet@ietfa.amsl.com>; Fri,  4 Dec 2015 08:14:35 -0800 (PST)
Received: from mail-wm0-x236.google.com (mail-wm0-x236.google.com [IPv6:2a00:1450:400c:c09::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 345D01A8953 for <manet@ietf.org>; Fri,  4 Dec 2015 08:14:35 -0800 (PST)
Received: by wmvv187 with SMTP id v187so81680964wmv.1 for <manet@ietf.org>; Fri, 04 Dec 2015 08:14:33 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=PUJqkbF71M67hhDOyr/Ar3wTaHOZU8ebD/FEsI99nRg=; b=N46p5Bkl5+/sj9sDrhY06wRSOw7+ZzoN5cHsCvLRk6XL7vsVQQwad+7LmADoqvDB3Y bb7bFaMOjMEvNguCzdrU2VtiZQQjtU6M/OniV4APmwkN2hxmdnio77T2y2ymBVB8VFhG acOaRnAW/xN8OejbI32LUNp1dd5HIGuTfgloU9UMdSsJPcYxPAjR7JqzvAgob3mWwnxt 5/Qba9POGrn5vQZmsKuyZpPnEvowTn6j1r9nqrP6psR2oQlqw4t1edlsubu0R9aPf6d0 KRYs5Ls335i3xQww7Z+0Gm6shlJQ6PY4xwvl66r1o/BlSaQ/DjbTjvQsozlW30Mk1c4e Wu5A==
X-Received: by 10.194.2.193 with SMTP id 1mr18922268wjw.26.1449245673803; Fri, 04 Dec 2015 08:14:33 -0800 (PST)
MIME-Version: 1.0
Received: by 10.27.94.70 with HTTP; Fri, 4 Dec 2015 08:14:04 -0800 (PST)
In-Reply-To: <CALtoyon3CjhN+EoyRDfag4ZtgV424Wmd6-L=_cF08_LBrU37tw@mail.gmail.com>
References: <CALtoyokXY5aNcZLgCV5hs1aDogi+A4f7SBaC7vZoXhTZtKqbXg@mail.gmail.com> <CAGnRvurDfG_nM47gPUKddSZ1sRY9C_J65Jm46CvruCUS_evYLg@mail.gmail.com> <CALtoyon3CjhN+EoyRDfag4ZtgV424Wmd6-L=_cF08_LBrU37tw@mail.gmail.com>
From: Henning Rogge <hrogge@gmail.com>
Date: Fri, 4 Dec 2015 17:14:04 +0100
Message-ID: <CAGnRvurZT8OLigxR+pxMtr4GARLYqmQpmeT7+BUKJcxhbKptrA@mail.gmail.com>
To: Stan Ratliff <ratliffstan@gmail.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/ankDRId-LReF0ILWCr5XOcXDgCY>
Cc: MANET IETF <manet@ietf.org>
Subject: Re: [manet] DLEP reviews - new info concerning Destination Up
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: <https://mailarchive.ietf.org/arch/browse/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, 04 Dec 2015 16:14:36 -0000

On Fri, Dec 4, 2015 at 4:58 PM, Stan Ratliff <ratliffstan@gmail.com> wrote:
>> So "Destination up" (router to radio) could be (as an example) used
>> for setting up a multicast address (mac to IP combination) ?
>
>
> Yes. In fact, MCAST setup is the only known use case at this point, but I'm
> uncomfortable with scoping it down to just MCAST in the document. There may
> well be other use-cases.

That reminds me that I still need to check if my implementation
returns an "ack" when the radio receives a Destination Up/Down... it
ignores it of course, but I am not sure about the ack.

Henning


From nobody Fri Dec  4 08:22:28 2015
Return-Path: <ratliffstan@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 351981A8980 for <manet@ietfa.amsl.com>; Fri,  4 Dec 2015 08:22:27 -0800 (PST)
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 kTrGBgPGpp0D for <manet@ietfa.amsl.com>; Fri,  4 Dec 2015 08:22:25 -0800 (PST)
Received: from mail-lb0-x229.google.com (mail-lb0-x229.google.com [IPv6:2a00:1450:4010:c04::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DE19A1A897B for <manet@ietf.org>; Fri,  4 Dec 2015 08:22:24 -0800 (PST)
Received: by lbbkw15 with SMTP id kw15so23429074lbb.0 for <manet@ietf.org>; Fri, 04 Dec 2015 08:22:23 -0800 (PST)
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=evQ76DSi8FcLDCwIqXXCGBEPf9yikI+nshPr74CUgOM=; b=Fe56yd/46/ausIv7JDqxQjsxrx0vsstJljsLIfMMt65EFoopbGF0SPQcX78pS6IPvk uIQfwG8RTWY2SslEtMcMgIsRb5v5Z9xOxZqFc7AU+cElbFp/7XwwA8HfvmO/ZkTCPMv5 +7THo0pJCKlyRjKYCc4euORz+wwLVra8rKAHbxDkL7wMh3fkBoHo276C7zH9og/tERMq atiRLlXrR3E5DRJJ5Jf0I9mukgrRqF71F36YJXz9AUjBaN3zwpQqbqzJVxFCPTZuowf/ +H+gM2m3CXWduNEJ4drWJ6uypZrGffHcGxIzC89pvwpIsRO/jvqsfVOeZWCBkajyFnpw ekJA==
MIME-Version: 1.0
X-Received: by 10.112.202.101 with SMTP id kh5mr8405400lbc.66.1449246143078; Fri, 04 Dec 2015 08:22:23 -0800 (PST)
Received: by 10.25.209.71 with HTTP; Fri, 4 Dec 2015 08:22:22 -0800 (PST)
In-Reply-To: <CAGnRvurZT8OLigxR+pxMtr4GARLYqmQpmeT7+BUKJcxhbKptrA@mail.gmail.com>
References: <CALtoyokXY5aNcZLgCV5hs1aDogi+A4f7SBaC7vZoXhTZtKqbXg@mail.gmail.com> <CAGnRvurDfG_nM47gPUKddSZ1sRY9C_J65Jm46CvruCUS_evYLg@mail.gmail.com> <CALtoyon3CjhN+EoyRDfag4ZtgV424Wmd6-L=_cF08_LBrU37tw@mail.gmail.com> <CAGnRvurZT8OLigxR+pxMtr4GARLYqmQpmeT7+BUKJcxhbKptrA@mail.gmail.com>
Date: Fri, 4 Dec 2015 11:22:22 -0500
Message-ID: <CALtoyo=bbeuR+=zG2dV=uO6ak00YENLo_azg7SR4j1+Z3N=3Jg@mail.gmail.com>
From: Stan Ratliff <ratliffstan@gmail.com>
To: Henning Rogge <hrogge@gmail.com>
Content-Type: multipart/alternative; boundary=001a11c3724c8cec14052614e9e0
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/7ohD1LJ8ZhvfCvwTc0Ugzbrtsho>
Cc: MANET IETF <manet@ietf.org>
Subject: Re: [manet] DLEP reviews - new info concerning Destination Up
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: <https://mailarchive.ietf.org/arch/browse/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, 04 Dec 2015 16:22:27 -0000

--001a11c3724c8cec14052614e9e0
Content-Type: text/plain; charset=UTF-8

On Fri, Dec 4, 2015 at 11:14 AM, Henning Rogge <hrogge@gmail.com> wrote:

> On Fri, Dec 4, 2015 at 4:58 PM, Stan Ratliff <ratliffstan@gmail.com>
> wrote:
> >> So "Destination up" (router to radio) could be (as an example) used
> >> for setting up a multicast address (mac to IP combination) ?
> >
> >
> > Yes. In fact, MCAST setup is the only known use case at this point, but
> I'm
> > uncomfortable with scoping it down to just MCAST in the document. There
> may
> > well be other use-cases.
>
> That reminds me that I still need to check if my implementation
> returns an "ack" when the radio receives a Destination Up/Down... it
> ignores it of course, but I am not sure about the ack.
>

... Hence, the concern that implementations might mis-handle the
Destination Up coming from the router, I guess... ;-)

Any thoughts on a new, 'Destination Announce' message?

Regards,
Stan

--001a11c3724c8cec14052614e9e0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">=
On Fri, Dec 4, 2015 at 11:14 AM, Henning Rogge <span dir=3D"ltr">&lt;<a hre=
f=3D"mailto:hrogge@gmail.com" target=3D"_blank">hrogge@gmail.com</a>&gt;</s=
pan> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0p=
x 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-lef=
t-style:solid;padding-left:1ex">On Fri, Dec 4, 2015 at 4:58 PM, Stan Ratlif=
f &lt;<a href=3D"mailto:ratliffstan@gmail.com">ratliffstan@gmail.com</a>&gt=
; wrote:<br>
&gt;&gt; So &quot;Destination up&quot; (router to radio) could be (as an ex=
ample) used<br>
&gt;&gt; for setting up a multicast address (mac to IP combination) ?<br>
&gt;<br>
&gt;<br>
&gt; Yes. In fact, MCAST setup is the only known use case at this point, bu=
t I&#39;m<br>
&gt; uncomfortable with scoping it down to just MCAST in the document. Ther=
e may<br>
&gt; well be other use-cases.<br>
<br>
That reminds me that I still need to check if my implementation<br>
returns an &quot;ack&quot; when the radio receives a Destination Up/Down...=
 it<br>
ignores it of course, but I am not sure about the ack.<br></blockquote><div=
><br></div>... Hence, the concern that implementations might mis-handle the=
 Destination Up coming from the router, I guess... ;-)=C2=A0<div><br></div>=
<div>Any thoughts on a new, &#39;Destination Announce&#39; message?=C2=A0</=
div><div><br></div><div>Regards,</div><div>Stan=C2=A0</div></div></div></di=
v>

--001a11c3724c8cec14052614e9e0--


From nobody Fri Dec  4 08:31:39 2015
Return-Path: <hrogge@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 47E8F1A8AC1 for <manet@ietfa.amsl.com>; Fri,  4 Dec 2015 08:31:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 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, 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 gM4cRRPK0PBn for <manet@ietfa.amsl.com>; Fri,  4 Dec 2015 08:31:37 -0800 (PST)
Received: from mail-wm0-x229.google.com (mail-wm0-x229.google.com [IPv6:2a00:1450:400c:c09::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ED52A1A8A4E for <manet@ietf.org>; Fri,  4 Dec 2015 08:31:36 -0800 (PST)
Received: by wmec201 with SMTP id c201so81999236wme.0 for <manet@ietf.org>; Fri, 04 Dec 2015 08:31:35 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=HFvPpwHp3p0Y0GGpjHWs1op03eTrjdawSuQLttBMQls=; b=GECnADbBrh1sdXDHPWyS6nA9lAdYdVVtwE5+wLr2fhLzNwH/RIujpC/lgXsaX/Eto+ 2K7NrVKsbnwZAEw+akotmwu9VUxJLYznArOwC+aNieIY2TL7MM1yvvPTqx0XCYrYh/OS ZqI2XsXNxaBouWe5pBV3kA/T9eNmJln7MPZgnJVENa5DZuhWZxr82UIwocyAorezKsk3 A/22qT8Oj5j36UjcbJJmQiCJPTIP8DwdLiG9UoGrOlYhXHxvCE5yfhgzuLMuRQrJf4uB O0mgm1Kjn2tidyk1L0CsaC9siM9Fd5XBxkY4N5r13Z8XD/nKGkadi+nU/T2gPpjtCL2q UmXQ==
X-Received: by 10.28.86.196 with SMTP id k187mr5989755wmb.61.1449246695570; Fri, 04 Dec 2015 08:31:35 -0800 (PST)
MIME-Version: 1.0
Received: by 10.27.94.70 with HTTP; Fri, 4 Dec 2015 08:31:06 -0800 (PST)
In-Reply-To: <CALtoyo=bbeuR+=zG2dV=uO6ak00YENLo_azg7SR4j1+Z3N=3Jg@mail.gmail.com>
References: <CALtoyokXY5aNcZLgCV5hs1aDogi+A4f7SBaC7vZoXhTZtKqbXg@mail.gmail.com> <CAGnRvurDfG_nM47gPUKddSZ1sRY9C_J65Jm46CvruCUS_evYLg@mail.gmail.com> <CALtoyon3CjhN+EoyRDfag4ZtgV424Wmd6-L=_cF08_LBrU37tw@mail.gmail.com> <CAGnRvurZT8OLigxR+pxMtr4GARLYqmQpmeT7+BUKJcxhbKptrA@mail.gmail.com> <CALtoyo=bbeuR+=zG2dV=uO6ak00YENLo_azg7SR4j1+Z3N=3Jg@mail.gmail.com>
From: Henning Rogge <hrogge@gmail.com>
Date: Fri, 4 Dec 2015 17:31:06 +0100
Message-ID: <CAGnRvupwDbrz+RNojq++B0_B37s72C0BhnDSWArEfhOBi=35XA@mail.gmail.com>
To: Stan Ratliff <ratliffstan@gmail.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/9pExyj0-KRHSvPLZTO2593ivm0g>
Cc: MANET IETF <manet@ietf.org>
Subject: Re: [manet] DLEP reviews - new info concerning Destination Up
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: <https://mailarchive.ietf.org/arch/browse/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, 04 Dec 2015 16:31:38 -0000

On Fri, Dec 4, 2015 at 5:22 PM, Stan Ratliff <ratliffstan@gmail.com> wrote:
> ... Hence, the concern that implementations might mis-handle the Destination
> Up coming from the router, I guess... ;-)
>
> Any thoughts on a new, 'Destination Announce' message?

I don't really see a reason to switch away from "Destination Up"...

Henning


From nobody Fri Dec  4 08:45:44 2015
Return-Path: <christopher.dearlove@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 40D631A88EB; Fri,  4 Dec 2015 08:45:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 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, 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 2og1DdU4tvqi; Fri,  4 Dec 2015 08:45:38 -0800 (PST)
Received: from mail-wm0-x22e.google.com (mail-wm0-x22e.google.com [IPv6:2a00:1450:400c:c09::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 636151A88D3; Fri,  4 Dec 2015 08:45:38 -0800 (PST)
Received: by wmec201 with SMTP id c201so82589690wme.0; Fri, 04 Dec 2015 08:45:36 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=references:mime-version:in-reply-to:content-type :content-transfer-encoding:message-id:cc:from:subject:date:to; bh=zEsBUS1aHw9WpcULrcQ/G5X599HSCg3J23PUv2kVJg8=; b=Wwp8afw1XpmhuXhBqG0XH2D/qrwB4bjSp/qF51xy/RT5z88WD8TWhHRlpvbB5l15Cv 8sDVVB7FxAZRLIkaZlKsxd5K/C4BKb3mUPK0iwlwY1HdYWJ6zVOtm2ZTZA18BLl/bVKc WoJY5yWLrFCbwBJautCD9vQ3VoRfVeAspMM7DHwIqU+FqrRALXWAQTlptc4/+NbD7J2C JjSUY9IuFj+NezhK1yp4Muw2sAmlJLolZlNiIBa35xaxNmP9/r8psV/kzVqXqLnRL22e 0nSqvznqgplGBbVz97FJhrH/06/fEL50/2+mFQFIDP+dH5KgS2juEfPy/vvOM0w4y+gX H7rA==
X-Received: by 10.195.13.135 with SMTP id ey7mr18169876wjd.25.1449247536923; Fri, 04 Dec 2015 08:45:36 -0800 (PST)
Received: from [10.1.164.224] (dab-far1-h-1-2.dab.02.net. [82.132.220.222]) by smtp.gmail.com with ESMTPSA id m11sm4261229wma.5.2015.12.04.08.45.36 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 04 Dec 2015 08:45:36 -0800 (PST)
References: <20151203141014.13172.85185.idtracker@ietfa.amsl.com> <4C05351D-C18C-446C-B2CB-82FAAC9840B9@thomasclausen.org> <7ivb8ep6dy.wl-jch@pps.univ-paris-diderot.fr>
Mime-Version: 1.0 (1.0)
In-Reply-To: <7ivb8ep6dy.wl-jch@pps.univ-paris-diderot.fr>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Message-Id: <5B1B4F5F-389B-488C-A6E3-F95FAE680135@gmail.com>
X-Mailer: iPhone Mail (13B143)
From: Christopher Dearlove <christopher.dearlove@gmail.com>
Date: Fri, 4 Dec 2015 16:45:31 +0000
To: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/dDSU3kqgW8sBQ2VnvhBNslzre28>
Cc: The IESG <iesg@ietf.org>, manet-chairs@ietf.org, manet@ietf.org, draft-ietf-manet-olsrv2-dat-metric@ietf.org
Subject: Re: [manet] Stephen Farrell's No Objection on draft-ietf-manet-olsrv2-dat-metric-10: (with COMMENT)
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: <https://mailarchive.ietf.org/arch/browse/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, 04 Dec 2015 16:45:40 -0000

If getting into the details, we want them correct. NHDP records unidirection=
al and bidirectional links. OLSRv2 extends NHDP by assigning metrics to thos=
e links, these metrics being unidirectional. While a link is unidirectional (=
HEARD) it will have a metric in that direction only. Once a link becomes bid=
irectional it will have a metric in each direction, but these are unidirecti=
onal, hence may differ. OLSRv2 (the rest of it) then only uses these bidirec=
tional links, using the appropriate metrics.

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

On 4 Dec 2015, at 15:42, Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr> w=
rote:

>> The reason for that being, simply, that we do not know how this metric
>> behaves with other protocols (yet),
>=20
> Uh-huh.
>=20
> Unlike ETX, ETT and friends, this metric is unidirectional -- it only
> considers packet loss in one direction.  Since OLSRv2 already has
> a mechanism for pruning unidirectional links, DAT in OLSRv2 will only be
> applied to bidirectional links, and therefore yield reasonable results.
> This would not be the case in, say, Babel, where the protocol relies on
> the metric to detect and prune unidirectional links.
>=20
> (Of course, there's nothing preventing one from adding an OLSRv2-style
> mechanism to Babel, but that doesn't contradict my point, which is that
> DAT *as it is defined now* would probably not work well with Babel *as it
> is defined now*.)
>=20
> So I think we're in full agreement -- DAT should not be recommended for
> protocols other than OLSRv2 until we have more data.
>=20
> (I mentioned in Berlin that the point about OLSRv2 using bidirectional
> links only should be made explicitly in the document, I don't know if this=

> comment was taken into account.)
>=20
> -- Juliusz
>=20
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www.ietf.org/mailman/listinfo/manet


From nobody Fri Dec  4 11:20:34 2015
Return-Path: <prvs=9780647f19=david.wiggins@ll.mit.edu>
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 B61691B328B for <manet@ietfa.amsl.com>; Fri,  4 Dec 2015 11:20:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.209
X-Spam-Level: 
X-Spam-Status: No, score=-4.209 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, T_RP_MATCHES_RCVD=-0.01, UNPARSEABLE_RELAY=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 keeImduyh76F for <manet@ietfa.amsl.com>; Fri,  4 Dec 2015 11:20:28 -0800 (PST)
Received: from mx1.ll.mit.edu (MX1.LL.MIT.EDU [129.55.12.45]) by ietfa.amsl.com (Postfix) with ESMTP id 3AF9E1B3289 for <manet@ietf.org>; Fri,  4 Dec 2015 11:20:27 -0800 (PST)
Received: from LLE2K10-HUB02.mitll.ad.local (LLE2K10-HUB02.mitll.ad.local) by mx1.ll.mit.edu (unknown) with ESMTP id tB4JKQYS010790; Fri, 4 Dec 2015 14:20:26 -0500
From: "Wiggins, David - 0665 - MITLL" <David.Wiggins@ll.mit.edu>
To: Henning Rogge <hrogge@gmail.com>, Stan Ratliff <ratliffstan@gmail.com>
Thread-Topic: [manet] DLEP reviews - new info concerning Destination Up
Thread-Index: AQHRLqshkmjWUwhQX02MwJSPON1o3567TqmAgAABH4CAAARJAIAAAlIAgAACcQD//9t7AA==
Date: Fri, 4 Dec 2015 19:20:26 +0000
Message-ID: <D2874FEE.137A%David.Wiggins@ll.mit.edu>
References: <CALtoyokXY5aNcZLgCV5hs1aDogi+A4f7SBaC7vZoXhTZtKqbXg@mail.gmail.com> <CAGnRvurDfG_nM47gPUKddSZ1sRY9C_J65Jm46CvruCUS_evYLg@mail.gmail.com> <CALtoyon3CjhN+EoyRDfag4ZtgV424Wmd6-L=_cF08_LBrU37tw@mail.gmail.com> <CAGnRvurZT8OLigxR+pxMtr4GARLYqmQpmeT7+BUKJcxhbKptrA@mail.gmail.com> <CALtoyo=bbeuR+=zG2dV=uO6ak00YENLo_azg7SR4j1+Z3N=3Jg@mail.gmail.com> <CAGnRvupwDbrz+RNojq++B0_B37s72C0BhnDSWArEfhOBi=35XA@mail.gmail.com>
In-Reply-To: <CAGnRvupwDbrz+RNojq++B0_B37s72C0BhnDSWArEfhOBi=35XA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [172.25.59.174]
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="B_3532083624_131016633"
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.15.21, 1.0.33,  0.0.0000 definitions=2015-12-04_06:2015-12-04,2015-12-04,1970-01-01 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 suspectscore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=7.0.1-1511060000 definitions=main-1512040321
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/PKDUh0kxQ4zEEwKCrqlbdycqD94>
Cc: MANET IETF <manet@ietf.org>
Subject: Re: [manet] DLEP reviews - new info concerning Destination Up
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: <https://mailarchive.ietf.org/arch/browse/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, 04 Dec 2015 19:20:32 -0000

--B_3532083624_131016633
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit

On 12/4/15, 11:31 AM, "manet on behalf of Henning Rogge"
<manet-bounces@ietf.org on behalf of hrogge@gmail.com> wrote:

>On Fri, Dec 4, 2015 at 5:22 PM, Stan Ratliff <ratliffstan@gmail.com>
>wrote:
>> ... Hence, the concern that implementations might mis-handle the
>>Destination
>> Up coming from the router, I guess... ;-)
>>
>> Any thoughts on a new, 'Destination Announce' message?
>
>I don't really see a reason to switch away from "Destination Up"...

Yeah, neither do I.  I admit to being initially puzzled about Destination
Up coming from the router, but now I think it's fine.  I like how almost
all of the messages can be sent by either side; that symmetry allows
almost complete code sharing between the modem and the router.  If there
are different messages depending on which side they're from, that sharing
is going to be reduced.

David

--B_3532083624_131016633
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"

MIIMEgYJKoZIhvcNAQcCoIIMAzCCC/8CAQExCzAJBgUrDgMCGgUAMAsGCSqGSIb3DQEHAaCC
CfUwggT1MIID3aADAgECAgpar+vgAAAAADYOMA0GCSqGSIb3DQEBCwUAMFExCzAJBgNVBAYT
AlVTMR8wHQYDVQQKExZNSVQgTGluY29sbiBMYWJvcmF0b3J5MQwwCgYDVQQLEwNQS0kxEzAR
BgNVBAMTCk1JVExMIENBLTMwHhcNMTUwNDA2MTE1OTM4WhcNMTYwNDA1MTE1OTM4WjBiMQsw
CQYDVQQGEwJVUzEfMB0GA1UEChMWTUlUIExpbmNvbG4gTGFib3JhdG9yeTEPMA0GA1UECxMG
UGVvcGxlMSEwHwYDVQQDExhXaWdnaW5zLkRhdmlkLlAuNTAwMTUyMDcwggEiMA0GCSqGSIb3
DQEBAQUAA4IBDwAwggEKAoIBAQDdVA0BrVjbk6NP8JFi7Lks3SHtN8CxSBqFLPNRVWGjTgLG
W9pDcqqOrij0IHmGpAP404gR4dP9mUEb9KfOhKuDdFQFyZnVICDSRbyT4tGOxiTH7MIsV49d
UwrWhj2P/ms6wf1E5L2QwJqjOTMPZj3IClWAkcZsAix5jHkLvNXI5OilCe2u2TDihM1x2kfB
zgQpRy9tuXpxYtFZpoEb0XbqLIzS9FLkTbqlocSm4jwhPXTFQtFwbd6l4zzD4RVPgnpFxg/8
KpuV35lGkp5lbPvpkskz4+n3P9LoCvpoh1pgj3fS0CvCVRzWRAX+oNR/D7RmP1ug+7Ix+JCg
iAB3vLdFAgMBAAGjggG8MIIBuDAdBgNVHQ4EFgQUofYOKn4e6iCZO59iu2f0FxOad4MwDgYD
VR0PAQH/BAQDAgbAMB8GA1UdIwQYMBaAFNdgZg57SY11TA39z0beyMcSh8q/MDMGA1UdHwQs
MCowKKAmoCSGImh0dHA6Ly9jcmwubGwubWl0LmVkdS9nZXRjcmwvTExDQTMwZgYIKwYBBQUH
AQEEWjBYMC0GCCsGAQUFBzAChiFodHRwOi8vY3JsLmxsLm1pdC5lZHUvZ2V0dG8vTExDQTMw
JwYIKwYBBQUHMAGGG2h0dHA6Ly9vY3NwLmxsLm1pdC5lZHUvb2NzcDA9BgkrBgEEAYI3FQcE
MDAuBiYrBgEEAYI3FQiDg+Udh+ynZoathxWD6vBFhbahHx2Fy94yh/+KcwIBZAIBBTAiBgNV
HSUBAf8EGDAWBggrBgEFBQcDBAYKKwYBBAGCNwoDDDAYBgNVHSAEETAPMA0GCyqGSIb3EgIB
AwEIMCMGA1UdEQQcMBqBGERhdmlkLldpZ2dpbnNAbGwubWl0LmVkdTAnBgkrBgEEAYI3FAIE
Gh4YAEwATABVAHMAZQByAFMAaQBnAC0AUwBXMA0GCSqGSIb3DQEBCwUAA4IBAQCgEybvvRIJ
tAlKEfYZyf5DIlcT+LfePOiebFcPxZatSTQW/hJHv4RX/TN8N3bQrx4Jkxe17eQfsKvJXhOi
R6as3vemCxYEMOFIKSsm5LEIC4D4GcXBRZ1CAJIHCY5ezXfKQUxBSdZAq82/fAoNEEP4KPEv
Y07m7OVwXMWpu7kz3CeBVOqL7xlL53pPvkyxtijQRtZrZ5coE9Qh9tHzATi7DW8UWoUv3Yhj
Qz9SnBn3T30ho0GtlTvMXso7UjGZFWLQI2JyR2QW5FYq8GGEq/5PRz/xslsKA5EoHxmSSeRh
eei3gpFbnUrRS+5JSS6kgA/HVoM7CRFo/O8KYXU5z/ihMIIE+DCCA+CgAwIBAgIKWrCpkwAA
AAA2DzANBgkqhkiG9w0BAQsFADBRMQswCQYDVQQGEwJVUzEfMB0GA1UEChMWTUlUIExpbmNv
bG4gTGFib3JhdG9yeTEMMAoGA1UECxMDUEtJMRMwEQYDVQQDEwpNSVRMTCBDQS0zMB4XDTE1
MDQwNjEyMDAyNloXDTE2MDQwNTEyMDAyNlowYjELMAkGA1UEBhMCVVMxHzAdBgNVBAoTFk1J
VCBMaW5jb2xuIExhYm9yYXRvcnkxDzANBgNVBAsTBlBlb3BsZTEhMB8GA1UEAxMYV2lnZ2lu
cy5EYXZpZC5QLjUwMDE1MjA3MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAlEWD
uIm5kuHghfe7O+eMLVena6sNfAZtHLp2mwXLrNshaHM6wVKmml8zhxeSmJJXTF3Owyn7imKs
vHMWcIJD9EoFQyJoeBaFV5Ll75/fE2WKswtGn9ZSSejplI/Iy99SI/9Lna5B7/BDmPozGn66
jdzgl+JVFptqEUGx5NZlRUEEtVtXYUy+PllIq6SpR/242wFiYVslFqSoHu789mexaDDAl7p7
z3W9cYidPtZUoysjW0omzwZIoYMsIhTbUMnv+TkBuhJErBmaNvAXPf8Y3pNf3pYz8pnR4MyI
ibFv2CS/2KLGxJRE9xt1nrgHT8Wx+E6Ro6IYkYLPSdE6YgYAgwIDAQABo4IBvzCCAbswHQYD
VR0OBBYEFGww5LYEZSoVOkuJ7ZVJS+35ChrUMA4GA1UdDwEB/wQEAwIFIDAfBgNVHSMEGDAW
gBTXYGYOe0mNdUwN/c9G3sjHEofKvzAzBgNVHR8ELDAqMCigJqAkhiJodHRwOi8vY3JsLmxs
Lm1pdC5lZHUvZ2V0Y3JsL0xMQ0EzMGYGCCsGAQUFBwEBBFowWDAtBggrBgEFBQcwAoYhaHR0
cDovL2NybC5sbC5taXQuZWR1L2dldHRvL0xMQ0EzMCcGCCsGAQUFBzABhhtodHRwOi8vb2Nz
cC5sbC5taXQuZWR1L29jc3AwPQYJKwYBBAGCNxUHBDAwLgYmKwYBBAGCNxUIg4PlHYfsp2aG
rYcVg+rwRYW2oR8dhevQcIPr7SACAWQCAQQwJQYDVR0lBB4wHAYEVR0lAAYIKwYBBQUHAwQG
CisGAQQBgjcKAwQwGAYDVR0gBBEwDzANBgsqhkiG9xICAQMBCDAjBgNVHREEHDAagRhEYXZp
ZC5XaWdnaW5zQGxsLm1pdC5lZHUwJwYJKwYBBAGCNxQCBBoeGABMAEwAVQBzAGUAcgBFAG4A
YwAtAFMAVzANBgkqhkiG9w0BAQsFAAOCAQEATCsJT66TKeYNh9hrcC1wxRH08CricKt9JktB
I1WWl48F4CqcYDZlLMpvHuSe6GezZzTUH4oq1y2q3um9Txh1NjLPT7j0k5SSwdr2V7d8upDN
WOrXvCi59Cyz5RvuhleCPIE+6wPyDrQwfBRhte/cv8PVOrsG4tio4VOHi/nXcS+HLgC5qNxk
1/w1UBf8QkkNP8kIgum/uItm4QwVdVAJMuwe3te8dYjtp3M5nC2exfqQfk+Mmw/8fdZFpch0
rSYbpchMMOueBuy2UnWaYBF84uXldBH9fkONRX8AL8EQ3sQEOyzxqpwKQ/d0itjAGaPCCJCI
VgnSYSWYoFiN9idyaTGCAeUwggHhAgEBMF8wUTELMAkGA1UEBhMCVVMxHzAdBgNVBAoTFk1J
VCBMaW5jb2xuIExhYm9yYXRvcnkxDDAKBgNVBAsTA1BLSTETMBEGA1UEAxMKTUlUTEwgQ0Et
MwIKWq/r4AAAAAA2DjAJBgUrDgMCGgUAoF0wIwYJKoZIhvcNAQkEMRYEFERwIHPtQXdFC3Rb
JGFTe3p1SzP8MBgGCSqGSIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTE1
MTIwNDE5MjAyNFowDQYJKoZIhvcNAQEBBQAEggEAZeczIgqoDJEwwynLK72APt9IKKiREPWb
f/T6013lZJ8pC7J0XqtAhdu5lfUJy15OIvVK1O5l97GJNNpURvJopHLX0kIeFg2SpGHhXBee
/FMUu3aXtGOnC99aMKNzVAqyGOOIY+H3HQEhDbj8P/Nf4GL/iM5/78/67/rrAItBnAJKsuhA
1NT75snl3e7foKwD9qZbKuD02LsvoX8nnTERPtBdL9KovYqrppTATc9iwQcgGaDWIua2wNVy
0SuAtGx+MJqZkdpwFW+m5lAvuc7+eAhmpLOZJKTn1o1/ZNohjYl6EXRntePRB8mjjsGpQOfW
hbGn6plWWJ04McPPW6NSow==

--B_3532083624_131016633--


From nobody Fri Dec  4 11:54:22 2015
Return-Path: <ratliffstan@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 195CD1B330E for <manet@ietfa.amsl.com>; Fri,  4 Dec 2015 11:54:21 -0800 (PST)
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 Wbbl_ignS1TV for <manet@ietfa.amsl.com>; Fri,  4 Dec 2015 11:54:19 -0800 (PST)
Received: from mail-lf0-x22f.google.com (mail-lf0-x22f.google.com [IPv6:2a00:1450:4010:c07::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1416E1B330C for <manet@ietf.org>; Fri,  4 Dec 2015 11:54:19 -0800 (PST)
Received: by lfaz4 with SMTP id z4so119263045lfa.0 for <manet@ietf.org>; Fri, 04 Dec 2015 11:54:17 -0800 (PST)
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=3CUrIzMfhcaHMSPSIzNIQ4B+hcRsduCPG1nRvGAkuRQ=; b=hDm0cwGx+J9/zGRz6oxXuUhCQ562DVQs54dsPfW/OejL5yBtuhQw1CIMd/v5WqrpJR +DVKkQHeYeB4pjeZ8i6prhVMmnMyepmF3myciVNWqkKg68idX+uN3KluR6D0Wzksvf23 g/RIk8LBugDMEJkqCUYIFMPHoDU7I1sFfqsbUCuZ7LuIC1AEQLiQ/X0nvMuzR2cbmgff 1pDDeIvFMaCViJkNKSDvZxg2uS3yDLxL0VFXqQplBF4Y33Z7hjaXF1sSn7GnmyQ+lMDE n5XP7NPmU0uee6FXsoiFk6mzbH1tcD9Wk6aX20IYWkvCez3VhDnr9FnFTMD0bBynYjee gIqw==
MIME-Version: 1.0
X-Received: by 10.25.18.93 with SMTP id h90mr8710043lfi.7.1449258857265; Fri, 04 Dec 2015 11:54:17 -0800 (PST)
Received: by 10.25.209.71 with HTTP; Fri, 4 Dec 2015 11:54:17 -0800 (PST)
In-Reply-To: <D2874FEE.137A%David.Wiggins@ll.mit.edu>
References: <CALtoyokXY5aNcZLgCV5hs1aDogi+A4f7SBaC7vZoXhTZtKqbXg@mail.gmail.com> <CAGnRvurDfG_nM47gPUKddSZ1sRY9C_J65Jm46CvruCUS_evYLg@mail.gmail.com> <CALtoyon3CjhN+EoyRDfag4ZtgV424Wmd6-L=_cF08_LBrU37tw@mail.gmail.com> <CAGnRvurZT8OLigxR+pxMtr4GARLYqmQpmeT7+BUKJcxhbKptrA@mail.gmail.com> <CALtoyo=bbeuR+=zG2dV=uO6ak00YENLo_azg7SR4j1+Z3N=3Jg@mail.gmail.com> <CAGnRvupwDbrz+RNojq++B0_B37s72C0BhnDSWArEfhOBi=35XA@mail.gmail.com> <D2874FEE.137A%David.Wiggins@ll.mit.edu>
Date: Fri, 4 Dec 2015 14:54:17 -0500
Message-ID: <CALtoyomZHucM7y38N583POKoXexMBCvLzke0A6oU9Rhzqb+pfw@mail.gmail.com>
From: Stan Ratliff <ratliffstan@gmail.com>
To: "Wiggins, David - 0665 - MITLL" <David.Wiggins@ll.mit.edu>
Content-Type: multipart/alternative; boundary=001a113fb2f060036c052617df4d
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/J9PYOyOoAKaB2UIPhyjjywmB6ss>
Cc: MANET IETF <manet@ietf.org>
Subject: Re: [manet] DLEP reviews - new info concerning Destination Up
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: <https://mailarchive.ietf.org/arch/browse/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, 04 Dec 2015 19:54:21 -0000

--001a113fb2f060036c052617df4d
Content-Type: text/plain; charset=UTF-8

David,

On Fri, Dec 4, 2015 at 2:20 PM, Wiggins, David - 0665 - MITLL <
David.Wiggins@ll.mit.edu> wrote:

> On 12/4/15, 11:31 AM, "manet on behalf of Henning Rogge"
> <manet-bounces@ietf.org on behalf of hrogge@gmail.com> wrote:
>
> >On Fri, Dec 4, 2015 at 5:22 PM, Stan Ratliff <ratliffstan@gmail.com>
> >wrote:
> >> ... Hence, the concern that implementations might mis-handle the
> >>Destination
> >> Up coming from the router, I guess... ;-)
> >>
> >> Any thoughts on a new, 'Destination Announce' message?
> >
> >I don't really see a reason to switch away from "Destination Up"...
>
> Yeah, neither do I.  I admit to being initially puzzled about Destination
> Up coming from the router, but now I think it's fine.  I like how almost
> all of the messages can be sent by either side; that symmetry allows
> almost complete code sharing between the modem and the router.  If there
> are different messages depending on which side they're from, that sharing
> is going to be reduced.
>
>
Thanks for the input. I just want to play "Devil's Advocate" here for a
second -
If we stay with Destination Up, the rules *could* get convoluted - for
example, what do metrics mean on a Destination Up that flows from router to
modem? Should the spec attempt to define that a router-to-modem Destination
Up should not/must not contain metrics? Or, are these metrics some sort of
recommendation (in which case, they overlap with Link Characteristics
Request on the destination)?

To be honest, I'm of the same opinion as you and Henning - I think
Destination Up, flowing from either router or modem, is a good design. But
I can see the potential for some mis-interpretation here.

Your thoughts? Other opinions? Looking for consensus here, WG participants.

Regards,
Stan

--001a113fb2f060036c052617df4d
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">David,=C2=A0<br><div class=3D"gmail_extra"><br><div class=
=3D"gmail_quote">On Fri, Dec 4, 2015 at 2:20 PM, Wiggins, David - 0665 - MI=
TLL <span dir=3D"ltr">&lt;<a href=3D"mailto:David.Wiggins@ll.mit.edu" targe=
t=3D"_blank">David.Wiggins@ll.mit.edu</a>&gt;</span> wrote:<br><blockquote =
class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid=
;padding-left:1ex">On 12/4/15, 11:31 AM, &quot;manet on behalf of Henning R=
ogge&quot;<br>
&lt;<a href=3D"mailto:manet-bounces@ietf.org">manet-bounces@ietf.org</a> on=
 behalf of <a href=3D"mailto:hrogge@gmail.com">hrogge@gmail.com</a>&gt; wro=
te:<br>
<br>
&gt;On Fri, Dec 4, 2015 at 5:22 PM, Stan Ratliff &lt;<a href=3D"mailto:ratl=
iffstan@gmail.com">ratliffstan@gmail.com</a>&gt;<br>
&gt;wrote:<br>
&gt;&gt; ... Hence, the concern that implementations might mis-handle the<b=
r>
&gt;&gt;Destination<br>
&gt;&gt; Up coming from the router, I guess... ;-)<br>
&gt;&gt;<br>
&gt;&gt; Any thoughts on a new, &#39;Destination Announce&#39; message?<br>
&gt;<br>
&gt;I don&#39;t really see a reason to switch away from &quot;Destination U=
p&quot;...<br>
<br>
Yeah, neither do I.=C2=A0 I admit to being initially puzzled about Destinat=
ion<br>
Up coming from the router, but now I think it&#39;s fine.=C2=A0 I like how =
almost<br>
all of the messages can be sent by either side; that symmetry allows<br>
almost complete code sharing between the modem and the router.=C2=A0 If the=
re<br>
are different messages depending on which side they&#39;re from, that shari=
ng<br>
is going to be reduced.<br><span class=3D"HOEnZb"><font color=3D"#888888"><=
br></font></span></blockquote><div><br></div><div>Thanks for the input. I j=
ust want to play &quot;Devil&#39;s Advocate&quot; here for a second -=C2=A0=
</div><div>If we stay with Destination Up, the rules *could* get convoluted=
 - for example, what do metrics mean on a Destination Up that flows from ro=
uter to modem? Should the spec attempt to define that a router-to-modem Des=
tination Up should not/must not contain metrics? Or, are these metrics some=
 sort of recommendation (in which case, they overlap with Link Characterist=
ics Request on the destination)?</div><div><br></div><div>To be honest, I&#=
39;m of the same opinion as you and Henning - I think Destination Up, flowi=
ng from either router or modem, is a good design. But I can see the potenti=
al for some mis-interpretation here.=C2=A0</div><div><br></div><div>Your th=
oughts? Other opinions? Looking for consensus here, WG participants.</div><=
div><br></div><div>Regards,<br>Stan</div><div>=C2=A0=C2=A0</div></div></div=
></div>

--001a113fb2f060036c052617df4d--


From nobody Fri Dec  4 15:10:35 2015
Return-Path: <lberger@labn.net>
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 D39581B2D47 for <manet@ietfa.amsl.com>; Fri,  4 Dec 2015 15:10:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.667
X-Spam-Level: 
X-Spam-Status: No, score=-1.667 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, IP_NOT_FRIENDLY=0.334, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no
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 BL2rO3uDLC7m for <manet@ietfa.amsl.com>; Fri,  4 Dec 2015 15:10:32 -0800 (PST)
Received: from gproxy2-pub.mail.unifiedlayer.com (gproxy2-pub.mail.unifiedlayer.com [69.89.18.3]) by ietfa.amsl.com (Postfix) with SMTP id 13ADB1B2D2B for <manet@ietf.org>; Fri,  4 Dec 2015 15:10:32 -0800 (PST)
Received: (qmail 13289 invoked by uid 0); 4 Dec 2015 23:10:29 -0000
Received: from unknown (HELO cmgw3) (10.0.90.84) by gproxy2.mail.unifiedlayer.com with SMTP; 4 Dec 2015 23:10:29 -0000
Received: from box313.bluehost.com ([69.89.31.113]) by cmgw3 with  id piAQ1r00W2SSUrH01iATp2; Fri, 04 Dec 2015 23:10:27 -0700
X-Authority-Analysis: v=2.1 cv=Caqbutbl c=1 sm=1 tr=0 a=h1BC+oY+fLhyFmnTBx92Jg==:117 a=wU2YTnxGAAAA:8 a=cNaOj0WVAAAA:8 a=IkcTkHD0fZMA:10 a=-NfooI8aBGcA:10 a=uEJ9t1CZtbIA:10 a=wUQvQvOEmiQA:10 a=48vgC7mUAAAA:8 a=k57J53x5Q2Uus6ZrbW0A:9 a=e92K4nx_eKEUQ3gK:21 a=VbON8Pio3kZiBjMJ:21 a=QEXdDO2ut3YA:10
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=labn.net; s=default;  h=Content-Transfer-Encoding:Content-Type:In-Reply-To:MIME-Version:Date:Message-ID:From:Cc:References:To:Subject; bh=emyyYnN0RrD8PkYx1650ulhbEdLH2WLTkwJKGunHSg4=;  b=ihnNl87CsuZ6wHWT5p0QDuCEAQf+6xtcx8mROGulN4dxgZhQL9KCdrooNlBUrcjMD7pNr6SYy+ddy4udGmPjCnw3W3axouXQq5A09aRDSsFZVi9A+DZzS6pniNrOd4Tp;
Received: from box313.bluehost.com ([69.89.31.113]:34634 helo=[127.0.0.1]) by box313.bluehost.com with esmtpa (Exim 4.84) (envelope-from <lberger@labn.net>) id 1a4zUg-0006T6-M6; Fri, 04 Dec 2015 16:10:26 -0700
To: Stan Ratliff <ratliffstan@gmail.com>
References: <5575E8A7.6030508@labn.net> <565E2EC4.50504@labn.net> <CALtoyo=2YrNT9CJCoqJ_x1+Cbyu8stfNuwjQXJFvjWfE9h+2Mw@mail.gmail.com> <565E4E8D.8080704@labn.net> <CALtoyokCuQOWAX8QYPK79_W+75cQhuFKvBGqwCf6NSpvD1-r2A@mail.gmail.com> <5660C1F3.7010708@labn.net> <CALtoyokEWk8CXKxE0ALsPH_GRyg7pcp3B+ucSi+rcFQGN=UzVw@mail.gmail.com> <5661ADFD.9070505@labn.net> <CALtoyomCk38LdrV33a+Tzeu2CQcojA0sYWxHBq1wS2-FHpXrRw@mail.gmail.com>
From: Lou Berger <lberger@labn.net>
X-Enigmail-Draft-Status: N1110
Message-ID: <56621D5E.5080107@labn.net>
Date: Fri, 4 Dec 2015 18:10:22 -0500
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.4.0
MIME-Version: 1.0
In-Reply-To: <CALtoyomCk38LdrV33a+Tzeu2CQcojA0sYWxHBq1wS2-FHpXrRw@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
X-Identified-User: {1038:box313.bluehost.com:labnmobi:labn.net} {sentby:smtp auth 69.89.31.113 authed with lberger@labn.net}
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/8jLW3AfTvj1GBWN5TTqxBYr1-cI>
Cc: MANET IETF <manet@ietf.org>, draft-ietf-manet-dlep@ietf.org
Subject: Re: [manet] DLEP-17 and RtgDir review of draft-ietf-manet-dlep-14
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: <https://mailarchive.ietf.org/arch/browse/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, 04 Dec 2015 23:10:34 -0000

On 12/4/2015 10:38 AM, Stan Ratliff wrote:
> Lou, 
>
>
> On Fri, Dec 4, 2015 at 10:15 AM, Lou Berger <lberger@labn.net
> <mailto:lberger@labn.net>> wrote:
>
>     Stan,
>
>
>     On 12/3/2015 5:41 PM, Stan Ratliff wrote:
>     > Lou,Â
>     >
>     > With regard to the other points you raise, I'm thinking we (Rick and
>     > myself) need to address them with an update.
>
>     I think the technical issues should be discussed on list before making
>     changes.Â  Editorial issues can be addressed as you/the editors/the
>     chairs see fit.
>
>
> If there are specific technical issues you want discussed, then please
> let me know. From an admittedly quick re-read of your last review, it
> seemed that the biggest issue was that of IPv6-mandated discovery. We
> agree that this should be both IPv4 and IPv6 based, and will change
> the doc to reflect that. 
>

from my prior message, the raised open technical issues that I'd expect
to be resolved on list are:
- agreeing on the transaction model (see below)
- documenting handling of TCP close
- handling failures in destination processing (while session processing
continues)
- replacement of 'heuristics' with defined mechanisms
- eliminating duplicate functionality
    1) always require status where currently optional
    2) always require TCP port where currently optional
- Security of UDP messages
- eliminating required range for source ports

The main editorial points, which I think is fine for the
authors/editors/etc, try to address on their own:
- Elimination of duplicate conformance requirements
- General cleanup of conformance language
- Rewrite IANA section to fully align with RFC5226
- (hopefully) addition of ABNF
- Addition clarification / definition of states and transitions (maybe
even state diagrams, again see
https://tools.ietf.org/html/rfc4204#section-11 for a very similar protocol.)
- Fixing the scaling considerations section

>  
>
>
>     > There are a few I'm frankly struggling with, and I'd like to reserve
>     > the option of coming back & saying "I don't get it", but...Â
>     >
>     Please do.
>
>     > As long as you're asking, I do have one question - when
>     discussing the
>     > transaction model, you say (in part):Â
>     > "Â MoreÂ significantly, it's unclear how new messages should be
>     handled."
>     >
>     > Since we're talking about new messages, and I have no idea what
>     those
>     > messages would involve, it's somewhat hard to fully pin-down how
>     they
>     > should be handled.
>     Part of this could be simply saying that if an unknown message is
>     received it is silently discarded, and may be reported via management
>     interfaces, e.g., counter increment or logging.Â  Also that any new
>     message types must identify their transaction class (destination or
>     session), alternately this can be implicit based on presence of
>     the MAC
>     address data item...
>
>
> OK. I can go for some text along the lines of 
> "Extensions to this draft that contain new messages MUST clearly state
> whether a message is a destination message, or a peer message. Those
> new messages MUST NOT violate the existing transaction model."   ??
>
Assuming there are two transaction classes, I'd personally address this
by putting a bit in the message to indicate the message transaction
class.  This would ensure there is no ambiguity now and in perpetuity. 

>  
>
>
>     > If the new messages are destination-oriented, they should fall into
>     > the "1 transaction in-flight per destination" rule. If the new
>     > messages are peer-oriented, then they would fall into the "1
>     > transaction in-flight per peer" rule... but in the case where a new
>     > message introduces some sort of new context that I can't currently
>     > see? I'm lost there.
>
>     I think the transaction model has come a long way (from no
>     definition),
>     but it doesn't match my understanding of what was previously discussed
>     (single transaction. period.) and the model should be flushed out more
>     fully as well as discussed by the WG  In particular, I think it
>     would be
>     good to hear from those who have implementations and their
>     experience/perspective.
>
>
> The documented transaction *is* the viewpoint of at least one
> implementer... ;-)
Fair enough.  I made my comment as the current version didn't match
(perhaps just my memory) of what I had been told was implemented.

> It's what I'd done at my previous company. Can you give me an example
> of the additional flushing out that needs to be done? I'm looking for
> a place to start. 
>
- Explicit identification of message transaction class (the bit
mentioned above)
- Handling of destination transaction failures when there are no session
errors
    - e.g., no response, or destination down or updated during
destination specific transaction
- Handling of TCP closes


Lou
>
> Regards,
> Stan
>
>  
> [snip]



From nobody Fri Dec  4 21:36:05 2015
Return-Path: <rick@tropicalstormsoftware.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 DE9F01A044D for <manet@ietfa.amsl.com>; Fri,  4 Dec 2015 21:36:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.911
X-Spam-Level: 
X-Spam-Status: No, score=-1.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 ufbEjQsyodCo for <manet@ietfa.amsl.com>; Fri,  4 Dec 2015 21:36:02 -0800 (PST)
Received: from mail.tropicalstormsoftware.com (mail.tropicalstormsoftware.com [188.94.42.120]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 87A3A1A0439 for <manet@ietf.org>; Fri,  4 Dec 2015 21:36:01 -0800 (PST)
Received: from tss-server1.home.tropicalstormsoftware.com ([fe80::753b:fa82:5c0:af0d]) by tss-server1.home.tropicalstormsoftware.com ([fe80::753b:fa82:5c0:af0d%10]) with mapi; Sat, 5 Dec 2015 05:35:35 +0000
From: Rick Taylor <rick@tropicalstormsoftware.com>
To: Stan Ratliff <ratliffstan@gmail.com>, "Wiggins, David - 0665 - MITLL" <David.Wiggins@ll.mit.edu>
Thread-Topic: [manet] DLEP reviews - new info concerning Destination Up
Thread-Index: AQHRLqr9rzXjRqERUUWP375DFPGJkg==
Date: Sat, 5 Dec 2015 05:35:33 +0000
Message-ID: <38A5475DE83986499AEACD2CFAFC3F9801B32FFE4D@tss-server1.home.tropicalstormsoftware.com>
References: <CALtoyokXY5aNcZLgCV5hs1aDogi+A4f7SBaC7vZoXhTZtKqbXg@mail.gmail.com> <CAGnRvurDfG_nM47gPUKddSZ1sRY9C_J65Jm46CvruCUS_evYLg@mail.gmail.com> <CALtoyon3CjhN+EoyRDfag4ZtgV424Wmd6-L=_cF08_LBrU37tw@mail.gmail.com> <CAGnRvurZT8OLigxR+pxMtr4GARLYqmQpmeT7+BUKJcxhbKptrA@mail.gmail.com> <CALtoyo=bbeuR+=zG2dV=uO6ak00YENLo_azg7SR4j1+Z3N=3Jg@mail.gmail.com> <CAGnRvupwDbrz+RNojq++B0_B37s72C0BhnDSWArEfhOBi=35XA@mail.gmail.com> <D2874FEE.137A%David.Wiggins@ll.mit.edu> <CALtoyomZHucM7y38N583POKoXexMBCvLzke0A6oU9Rhzqb+pfw@mail.gmail.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/JamEZnTdjQRKwg0DOixDklS5RhQ>
Cc: MANET IETF <manet@ietf.org>
Subject: Re: [manet] DLEP reviews - new info concerning Destination Up
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: <https://mailarchive.ietf.org/arch/browse/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: Sat, 05 Dec 2015 05:36:04 -0000

Sorry for the top post, but I will summarise my side of the discussion=0A=
Stan and I have been having for a week or two.=0A=
=0A=
I have 2 issues with the status-quo of router originated Destination Ups.=
=0A=
=0A=
1) They have been in the document for several years, but until the=0A=
authors pointed them out on the list, no-one had noticed.  This does not=0A=
point to good interoperability (or a good document ;) ).=0A=
=0A=
2) More importantly, a router-originated Destination Up cannot have the=0A=
same data items that a modem originated D/Up, therefore there has to be=0A=
if/else text in the spec covering the two use-cases, and at the point=0A=
one may as well have two messages.=0A=
=0A=
3) The flow of destination messages gets very knotty when some messages=0A=
are unidrectional (Dest_Update) and some are bi-directional (Dest_Up). =0A=
Carefully peeling the two use-cases apart and making them explicitly=0A=
different is clearer.=0A=
=0A=
I have already prototyped the text for a new Destination Interest=0A=
message for a draft-18, and in my opinion it has the following advantages:=
=0A=
=0A=
A) It reads better and is much clearer, and it was not a lot of extra text.=
=0A=
B) It answers Lou's question about how does a router re-acquire a=0A=
destination that the router has previously replied with 'Not=0A=
Interested'.  This is an example of a unicast router-originated=0A=
destination btw.=0A=
C) It helps with Chris' comments about lots of use of the words 'peer'=0A=
and 'participant', the text ends up clearer once one sets the originator=0A=
for each message explicitly.=0A=
=0A=
Hopefully that swings the argument in my favour!=0A=
=0A=
As an exercise for the reader: How many of you have spotted that=0A=
Destination Down can flow in both directions?=0A=
=0A=
Cheers,=0A=
=0A=
Rick=0A=
=0A=
P.S. I am still on vacation so my email latency is high.=0A=
=0A=
=0A=
On 04/12/15 19:54, Stan Ratliff wrote:=0A=
> David, =0A=
>=0A=
> On Fri, Dec 4, 2015 at 2:20 PM, Wiggins, David - 0665 - MITLL=0A=
> <David.Wiggins@ll.mit.edu <mailto:David.Wiggins@ll.mit.edu>> wrote:=0A=
>=0A=
>     On 12/4/15, 11:31 AM, "manet on behalf of Henning Rogge"=0A=
>     <manet-bounces@ietf.org <mailto:manet-bounces@ietf.org> on behalf=0A=
>     of hrogge@gmail.com <mailto:hrogge@gmail.com>> wrote:=0A=
>=0A=
>     >On Fri, Dec 4, 2015 at 5:22 PM, Stan Ratliff=0A=
>     <ratliffstan@gmail.com <mailto:ratliffstan@gmail.com>>=0A=
>     >wrote:=0A=
>     >> ... Hence, the concern that implementations might mis-handle the=
=0A=
>     >>Destination=0A=
>     >> Up coming from the router, I guess... ;-)=0A=
>     >>=0A=
>     >> Any thoughts on a new, 'Destination Announce' message?=0A=
>     >=0A=
>     >I don't really see a reason to switch away from "Destination Up"...=
=0A=
>=0A=
>     Yeah, neither do I.  I admit to being initially puzzled about=0A=
>     Destination=0A=
>     Up coming from the router, but now I think it's fine.  I like how=0A=
>     almost=0A=
>     all of the messages can be sent by either side; that symmetry allows=
=0A=
>     almost complete code sharing between the modem and the router.  If=0A=
>     there=0A=
>     are different messages depending on which side they're from, that=0A=
>     sharing=0A=
>     is going to be reduced.=0A=
>=0A=
>=0A=
> Thanks for the input. I just want to play "Devil's Advocate" here for=0A=
> a second - =0A=
> If we stay with Destination Up, the rules *could* get convoluted - for=0A=
> example, what do metrics mean on a Destination Up that flows from=0A=
> router to modem? Should the spec attempt to define that a=0A=
> router-to-modem Destination Up should not/must not contain metrics?=0A=
> Or, are these metrics some sort of recommendation (in which case, they=0A=
> overlap with Link Characteristics Request on the destination)?=0A=
>=0A=
> To be honest, I'm of the same opinion as you and Henning - I think=0A=
> Destination Up, flowing from either router or modem, is a good design.=0A=
> But I can see the potential for some mis-interpretation here. =0A=
>=0A=
> Your thoughts? Other opinions? Looking for consensus here, WG=0A=
> participants.=0A=
>=0A=
> Regards,=0A=
> Stan=0A=
>   =0A=
=0A=


From nobody Sat Dec  5 00:53:47 2015
Return-Path: <christopher.dearlove@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 BFABB1A1E0E for <manet@ietfa.amsl.com>; Sat,  5 Dec 2015 00:53:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 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, 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 nz6kONjleEGP for <manet@ietfa.amsl.com>; Sat,  5 Dec 2015 00:53:44 -0800 (PST)
Received: from mail-wm0-x235.google.com (mail-wm0-x235.google.com [IPv6:2a00:1450:400c:c09::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 519FA1A1DE1 for <manet@ietf.org>; Sat,  5 Dec 2015 00:53:44 -0800 (PST)
Received: by wmec201 with SMTP id c201so104290038wme.0 for <manet@ietf.org>; Sat, 05 Dec 2015 00:53:42 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=references:mime-version:in-reply-to:content-type :content-transfer-encoding:message-id:cc:from:subject:date:to; bh=iktDSRCh4Dif+fwq0ae/YijdRgxfpaHDHgaHVQ17V74=; b=JUBAEerLeW6QfT1yQo7oFkJrOUF23REq68B52b8Gqgx6f+hQpvT/9pRLv+y7eKCzoN PSV5UOSr1BzhRfi2+7qoJAIwOgV3io1X/+Bj+L3nvwCu68zJMcJQuFByAgZ/gQCwUWn9 WfnqB3jhexyx7AELo/c8947bySFP4/YHYAcsKAdbbX5IRqTuakRG87K2Iv8mm2irDusg fp8vDLMkPjdhmeSEKQ8urQRQzJRIAUI+BTXexzc+ibBOrSyQOWJDVKwsclwPkVM81NcR nppTrB1bgEdQwmsym79lJwRLGLeLsgwVwqwRf2oH7iOjiLMjivitqRK6GsdyFYZFkF6W IcAg==
X-Received: by 10.28.218.75 with SMTP id r72mr9028415wmg.59.1449305622826; Sat, 05 Dec 2015 00:53:42 -0800 (PST)
Received: from [10.6.88.161] (dab-ntm1-h-1-8.dab.02.net. [82.132.230.244]) by smtp.gmail.com with ESMTPSA id t9sm4775582wjx.25.2015.12.05.00.53.41 (version=TLSv1/SSLv3 cipher=OTHER); Sat, 05 Dec 2015 00:53:41 -0800 (PST)
References: <CALtoyokXY5aNcZLgCV5hs1aDogi+A4f7SBaC7vZoXhTZtKqbXg@mail.gmail.com> <CAGnRvurDfG_nM47gPUKddSZ1sRY9C_J65Jm46CvruCUS_evYLg@mail.gmail.com> <CALtoyon3CjhN+EoyRDfag4ZtgV424Wmd6-L=_cF08_LBrU37tw@mail.gmail.com> <CAGnRvurZT8OLigxR+pxMtr4GARLYqmQpmeT7+BUKJcxhbKptrA@mail.gmail.com> <CALtoyo=bbeuR+=zG2dV=uO6ak00YENLo_azg7SR4j1+Z3N=3Jg@mail.gmail.com> <CAGnRvupwDbrz+RNojq++B0_B37s72C0BhnDSWArEfhOBi=35XA@mail.gmail.com> <D2874FEE.137A%David.Wiggins@ll.mit.edu> <CALtoyomZHucM7y38N583POKoXexMBCvLzke0A6oU9Rhzqb+pfw@mail.gmail.com> <38A5475DE83986499AEACD2CFAFC3F9801B32FFE4D@tss-server1.home.tropicalstormsoftware.com>
Mime-Version: 1.0 (1.0)
In-Reply-To: <38A5475DE83986499AEACD2CFAFC3F9801B32FFE4D@tss-server1.home.tropicalstormsoftware.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Message-Id: <B81D51B8-A631-45E5-96ED-A2484ABCDCB6@gmail.com>
X-Mailer: iPhone Mail (13B143)
From: Christopher Dearlove <christopher.dearlove@gmail.com>
Date: Sat, 5 Dec 2015 08:53:37 +0000
To: Rick Taylor <rick@tropicalstormsoftware.com>
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/1y1C7W9u_cFo6jyidPMOnV8yQOs>
Cc: MANET IETF <manet@ietf.org>
Subject: Re: [manet] DLEP reviews - new info concerning Destination Up
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: <https://mailarchive.ietf.org/arch/browse/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: Sat, 05 Dec 2015 08:53:46 -0000

Can't say that I specifically spotted Destination Down, but I had spotted th=
at some information flowed "backwards". One of my comments has been that thi=
s is not brought out in the introductory material. This rather supports that=
.

--=20
Christopher Dearlove

> On 5 Dec 2015, at 05:35, Rick Taylor <rick@tropicalstormsoftware.com> wrot=
e:
>=20
> Sorry for the top post, but I will summarise my side of the discussion
> Stan and I have been having for a week or two.
>=20
> I have 2 issues with the status-quo of router originated Destination Ups.
>=20
> 1) They have been in the document for several years, but until the
> authors pointed them out on the list, no-one had noticed.  This does not
> point to good interoperability (or a good document ;) ).
>=20
> 2) More importantly, a router-originated Destination Up cannot have the
> same data items that a modem originated D/Up, therefore there has to be
> if/else text in the spec covering the two use-cases, and at the point
> one may as well have two messages.
>=20
> 3) The flow of destination messages gets very knotty when some messages
> are unidrectional (Dest_Update) and some are bi-directional (Dest_Up).=20
> Carefully peeling the two use-cases apart and making them explicitly
> different is clearer.
>=20
> I have already prototyped the text for a new Destination Interest
> message for a draft-18, and in my opinion it has the following advantages:=

>=20
> A) It reads better and is much clearer, and it was not a lot of extra text=
.
> B) It answers Lou's question about how does a router re-acquire a
> destination that the router has previously replied with 'Not
> Interested'.  This is an example of a unicast router-originated
> destination btw.
> C) It helps with Chris' comments about lots of use of the words 'peer'
> and 'participant', the text ends up clearer once one sets the originator
> for each message explicitly.
>=20
> Hopefully that swings the argument in my favour!
>=20
> As an exercise for the reader: How many of you have spotted that
> Destination Down can flow in both directions?
>=20
> Cheers,
>=20
> Rick
>=20
> P.S. I am still on vacation so my email latency is high.
>=20
>=20
>> On 04/12/15 19:54, Stan Ratliff wrote:
>> David,=20
>>=20
>> On Fri, Dec 4, 2015 at 2:20 PM, Wiggins, David - 0665 - MITLL
>> <David.Wiggins@ll.mit.edu <mailto:David.Wiggins@ll.mit.edu>> wrote:
>>=20
>>    On 12/4/15, 11:31 AM, "manet on behalf of Henning Rogge"
>>    <manet-bounces@ietf.org <mailto:manet-bounces@ietf.org> on behalf
>>    of hrogge@gmail.com <mailto:hrogge@gmail.com>> wrote:
>>=20
>>> On Fri, Dec 4, 2015 at 5:22 PM, Stan Ratliff
>>    <ratliffstan@gmail.com <mailto:ratliffstan@gmail.com>>
>>> wrote:
>>>> ... Hence, the concern that implementations might mis-handle the
>>>> Destination
>>>> Up coming from the router, I guess... ;-)
>>>>=20
>>>> Any thoughts on a new, 'Destination Announce' message?
>>>=20
>>> I don't really see a reason to switch away from "Destination Up"...
>>=20
>>    Yeah, neither do I.  I admit to being initially puzzled about
>>    Destination
>>    Up coming from the router, but now I think it's fine.  I like how
>>    almost
>>    all of the messages can be sent by either side; that symmetry allows
>>    almost complete code sharing between the modem and the router.  If
>>    there
>>    are different messages depending on which side they're from, that
>>    sharing
>>    is going to be reduced.
>>=20
>>=20
>> Thanks for the input. I just want to play "Devil's Advocate" here for
>> a second -=20
>> If we stay with Destination Up, the rules *could* get convoluted - for
>> example, what do metrics mean on a Destination Up that flows from
>> router to modem? Should the spec attempt to define that a
>> router-to-modem Destination Up should not/must not contain metrics?
>> Or, are these metrics some sort of recommendation (in which case, they
>> overlap with Link Characteristics Request on the destination)?
>>=20
>> To be honest, I'm of the same opinion as you and Henning - I think
>> Destination Up, flowing from either router or modem, is a good design.
>> But I can see the potential for some mis-interpretation here.=20
>>=20
>> Your thoughts? Other opinions? Looking for consensus here, WG
>> participants.
>>=20
>> Regards,
>> Stan
>=20
>=20
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www.ietf.org/mailman/listinfo/manet


From nobody Mon Dec  7 03:13:49 2015
Return-Path: <hrogge@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 C2FE71A87DE; Mon,  7 Dec 2015 03:13:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 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, 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 A7cLmQgm8fct; Mon,  7 Dec 2015 03:13:46 -0800 (PST)
Received: from mail-wm0-x22a.google.com (mail-wm0-x22a.google.com [IPv6:2a00:1450:400c:c09::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5354C1A8750; Mon,  7 Dec 2015 03:13:46 -0800 (PST)
Received: by wmec201 with SMTP id c201so160124085wme.0; Mon, 07 Dec 2015 03:13:45 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=2tTmjSLNoSZIKsbCWd2pE/1MCRe6h8gBBouAgTfRxmY=; b=gnFKcwc4ZBy6w6IAJfvFTF41xWqKHgXaFZWH2HH5knBdX2LGeO/fEQ7sHMHCe7L3xO pkF+M4CRgeb9YxrCvIBhoD5ecl5fYVVDwlNt7uwgFwjkJ8WDeDJAymiJTFGMPzt6pZ3/ 3NlrIUVcGQquc/VV+xhByowVfoMrMC5GBv9wP/jEdMeEOSq250ZFFcIbGZV9br7T88d4 SnDl5jdR6T16yQ+322vilTGXvMFli8MrhoX4WfZRGTEmH3r65EVRXAYxScnTzOHOQstb 8zkCfhJcCv580KPuZtq3tUDgRYA6ou8BPmubb8usmvx98IAakaASkOiZMOvXIhC9YnUS guBQ==
X-Received: by 10.28.47.212 with SMTP id v203mr19526320wmv.37.1449486824955; Mon, 07 Dec 2015 03:13:44 -0800 (PST)
MIME-Version: 1.0
Received: by 10.27.94.70 with HTTP; Mon, 7 Dec 2015 03:13:15 -0800 (PST)
In-Reply-To: <5661824A.1080907@cs.tcd.ie>
References: <20151203141014.13172.85185.idtracker@ietfa.amsl.com> <4C05351D-C18C-446C-B2CB-82FAAC9840B9@thomasclausen.org> <56617C88.6010302@cs.tcd.ie> <CAGnRvurt5ATgwWmMGSUYfcvfx+rKPrQReQjq4Z6pXOS5HKq4KQ@mail.gmail.com> <5661824A.1080907@cs.tcd.ie>
From: Henning Rogge <hrogge@gmail.com>
Date: Mon, 7 Dec 2015 12:13:15 +0100
Message-ID: <CAGnRvupefkkN3LZq6tThk_7biuC2cw5-J74CD=tWY+2jZCG+Vg@mail.gmail.com>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/pCu2oyv8fHq0xfl0sJQBp72OglQ>
Cc: draft-ietf-manet-olsrv2-dat-metric@ietf.org, MANET IETF <manet@ietf.org>, The IESG <iesg@ietf.org>, manet-chairs@ietf.org
Subject: Re: [manet] Stephen Farrell's No Objection on draft-ietf-manet-olsrv2-dat-metric-10: (with COMMENT)
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: <https://mailarchive.ietf.org/arch/browse/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: Mon, 07 Dec 2015 11:13:47 -0000

On Fri, Dec 4, 2015 at 1:08 PM, Stephen Farrell
<stephen.farrell@cs.tcd.ie> wrote:
>> Could this take the form of an appendix... one that discuss the
>> "input" of the DAT metric and how it could be adapted to other
>> protocols?
>
> You could do that. But that'd be more than I was asking about
> really.
>
> Mostly, what I think might be good is to say something like:
> "the outcome of this experiment will include consideration of
> whether and, if so, how, this metric could be re-used in other
> relevant IETF protocols."

I will add this to a draft 11 version.

Henning Rogge


From nobody Mon Dec  7 04:27:20 2015
Return-Path: <chris.dearlove@baesystems.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 375611B31DD for <manet@ietfa.amsl.com>; Mon,  7 Dec 2015 04:27:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.102
X-Spam-Level: 
X-Spam-Status: No, score=-4.102 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RDNS_NONE=0.793] 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 DyoU-hPUpl-w for <manet@ietfa.amsl.com>; Mon,  7 Dec 2015 04:27:16 -0800 (PST)
Received: from ukmta1.baesystems.com (unknown [20.133.0.55]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 475EB1B31DB for <manet@ietf.org>; Mon,  7 Dec 2015 04:27:14 -0800 (PST)
X-IronPort-AV: E=Sophos; i="5.20,394,1444690800"; d="scan'208,217"; a="32356881"
Received: from unknown (HELO baemasmds017.greenlnk.net) ([10.15.207.104]) by ukmta1.baesystems.com with ESMTP; 07 Dec 2015 12:27:14 +0000
X-IronPort-AV: E=Sophos;i="5.20,394,1444690800";  d="scan'208,217";a="123105133"
Received: from glkxh0005v.greenlnk.net ([10.109.2.36]) by baemasmds017.greenlnk.net with ESMTP; 07 Dec 2015 12:27:09 +0000
Received: from GLKXM0002V.GREENLNK.net ([169.254.5.2]) by GLKXH0005V.GREENLNK.net ([10.109.2.36]) with mapi id 14.03.0248.002; Mon, 7 Dec 2015 12:27:09 +0000
From: "Dearlove, Christopher (UK)" <chris.dearlove@baesystems.com>
To: "manet@ietf.org" <manet@ietf.org>
Thread-Topic: DLEP-17 comments, part 6
Thread-Index: AdEw5yOcVne2onB3R9q05GYRmf/1GQ==
Date: Mon, 7 Dec 2015 12:27:09 +0000
Message-ID: <B31EEDDDB8ED7E4A93FDF12A4EECD30D7D76E893@GLKXM0002V.GREENLNK.net>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.109.62.6]
Content-Type: multipart/alternative; boundary="_000_B31EEDDDB8ED7E4A93FDF12A4EECD30D7D76E893GLKXM0002VGREEN_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/DYhLRKt2NQRvwj9iDVl_6SgVHE0>
Subject: [manet] DLEP-17 comments, part 6
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: <https://mailarchive.ietf.org/arch/browse/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: Mon, 07 Dec 2015 12:27:19 -0000

--_000_B31EEDDDB8ED7E4A93FDF12A4EECD30D7D76E893GLKXM0002VGREEN_
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable

Section 10 (just appendices to go).

Many comments made about a section apply to other sections. I have not atte=
mpted to work out all of these.

Table 2, usual IANA comments, including use of Reserved (not for 0).

Section 10.1, first line. "MAY appear" reads like a non-2119 use of may. Bu=
t some later sections have MUST. So really I think this is "MAY be included=
 in". But leaves unspecified what if included elsewhere.

Section 10.1 first paragraph on page 35, not sure about use of "implementat=
ion". i.e. should be e.g. (line 3).

Text description, should you check for unprintable if receiving but not usi=
ng? And what if there are any unprintable characters? Not assuming NUL term=
inated, I think really this is stronger, it should not be.

Section 10., what if receive a success or continue in response to Session T=
ermination?

Table 3, IANA. Odd use of a decimal range (100+) in a binary field. I'd sug=
gest 128+.

Section 10.2 second paragraph is an example of how this section mixes forma=
t and usage. As I've indicated before, I think it would be clearer separate=
d. (Usage as in malformed is OK, that's part of syntax.)

Section 10.2, MBZ. I'm not sure about reserved here. Strictly that's not ho=
w used in 5226, but on the other hand I think in this kind of case its comm=
on (I think I've done it myself).

Section 10., second paragraph, line 3, delete MAY, that's what zero means, =
not an option. (Any use of MAY needs to be elsewhere, and in any case it's =
overruled by RECOMMENDED i.e. SHOULD two lines down.)

Section 10.6, last line, extensions registry, reference. Note that IANA wil=
l want this specified if it is a registry, even if empty.

Section 10.10 (and 10.11). Prefix range should be 0 to 32 (or 128). The "su=
bnet" 0.0.0.0/0 is sometimes useful (especially in a MANET or other edge ne=
twork) to say "the (rest of) the Internet is over here".

Section 10.12 You can get some really insane values in the maximum data rat=
e (and elsewhere). Of course what's insane on an HF link is rather slow on =
a UHF link, so not suggesting any specific thing. But is it worth saying yo=
u MAY reject if this indicates a figure known to be wrong?

Section 10.14, what if current > maximum?

Section 10.16, latency being implementation dependent without any hint what=
 latency means is hard to compare different radios. Which layers are includ=
ed? Mean or worst case? What about jitter?

Section 10.17. This seems the sort of data item there could be more than on=
e of. (Actually, I've missed any example that's allowed more than one of, t=
hough earlier discussion allows it.) But if so, there would have to be more=
 than one kind of resource (which there could be) with a code - even if all=
 codes are private.

Section 10.17 (and elsewhere). If it can't be calculated it SHOULD NOT be i=
ssued. Seems more like a MUST NOT to me.


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

--_000_B31EEDDDB8ED7E4A93FDF12A4EECD30D7D76E893GLKXM0002VGREEN_
Content-Type: text/html; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii">
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-GB" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">Section 10 (just appendices to go).<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Many comments made about a section apply to other se=
ctions. I have not attempted to work out all of these.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Table 2, usual IANA comments, including use of Reser=
ved (not for 0).<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Section 10.1, first line. &#8220;MAY appear&#8221; r=
eads like a non-2119 use of may. But some later sections have MUST. So real=
ly I think this is &#8220;MAY be included in&#8221;. But leaves unspecified=
 what if included elsewhere.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Section 10.1 first paragraph on page 35, not sure ab=
out use of &#8220;implementation&#8221;. i.e. should be e.g. (line 3).<o:p>=
</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Text description, should you check for unprintable i=
f receiving but not using? And what if there are any unprintable characters=
? Not assuming NUL terminated, I think really this is stronger, it should n=
ot be.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Section 10., what if receive a success or continue i=
n response to Session Termination?<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Table 3, IANA. Odd use of a decimal range (100&#43;)=
 in a binary field. I&#8217;d suggest 128&#43;.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Section 10.2 second paragraph is an example of how t=
his section mixes format and usage. As I&#8217;ve indicated before, I think=
 it would be clearer separated. (Usage as in malformed is OK, that&#8217;s =
part of syntax.)<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Section 10.2, MBZ. I&#8217;m not sure about reserved=
 here. Strictly that&#8217;s not how used in 5226, but on the other hand I =
think in this kind of case its common (I think I&#8217;ve done it myself).<=
o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Section 10., second paragraph, line 3, delete MAY, t=
hat&#8217;s what zero means, not an option. (Any use of MAY needs to be els=
ewhere, and in any case it&#8217;s overruled by RECOMMENDED i.e. SHOULD two=
 lines down.)<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Section 10.6, last line, extensions registry, refere=
nce. Note that IANA will want this specified if it is a registry, even if e=
mpty.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Section 10.10 (and 10.11). Prefix range should be 0 =
to 32 (or 128). The &#8220;subnet&#8221; 0.0.0.0/0 is sometimes useful (esp=
ecially in a MANET or other edge network) to say &#8220;the (rest of) the I=
nternet is over here&#8221;.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Section 10.12 You can get some really insane values =
in the maximum data rate (and elsewhere). Of course what&#8217;s insane on =
an HF link is rather slow on a UHF link, so not suggesting any specific thi=
ng. But is it worth saying you MAY reject
 if this indicates a figure known to be wrong?<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Section 10.14, what if current &gt; maximum?<o:p></o=
:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Section 10.16, latency being implementation dependen=
t without any hint what latency means is hard to compare different radios. =
Which layers are included? Mean or worst case? What about jitter?<o:p></o:p=
></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Section 10.17. This seems the sort of data item ther=
e could be more than one of. (Actually, I&#8217;ve missed any example that&=
#8217;s allowed more than one of, though earlier discussion allows it.) But=
 if so, there would have to be more than one kind
 of resource (which there could be) with a code &#8211; even if all codes a=
re private.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Section 10.17 (and elsewhere). If it can&#8217;t be =
calculated it SHOULD NOT be issued. Seems more like a MUST NOT to me.<o:p><=
/o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<p>********************************************************************<br>
This email and any attachments are confidential to the intended<br>
recipient and may also be privileged. If you are not the intended<br>
recipient please delete it from your system and notify the sender.<br>
You should not copy it or use it for any purpose nor disclose or<br>
distribute its contents to any other person.<br>
********************************************************************</p></b=
ody>
</html>

--_000_B31EEDDDB8ED7E4A93FDF12A4EECD30D7D76E893GLKXM0002VGREEN_--


From nobody Mon Dec  7 06:49:43 2015
Return-Path: <chris.dearlove@baesystems.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 872DB1A0354 for <manet@ietfa.amsl.com>; Mon,  7 Dec 2015 06:49:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.102
X-Spam-Level: 
X-Spam-Status: No, score=-4.102 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RDNS_NONE=0.793] 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 fK7-WPWS2Wcz for <manet@ietfa.amsl.com>; Mon,  7 Dec 2015 06:49:39 -0800 (PST)
Received: from ukmta1.baesystems.com (unknown [20.133.0.55]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EA2D71A0031 for <manet@ietf.org>; Mon,  7 Dec 2015 06:49:38 -0800 (PST)
X-IronPort-AV: E=Sophos; i="5.20,395,1444690800"; d="scan'208,217"; a="32393923"
Received: from unknown (HELO baemasmds017.greenlnk.net) ([10.15.207.104]) by ukmta1.baesystems.com with ESMTP; 07 Dec 2015 14:49:37 +0000
X-IronPort-AV: E=Sophos;i="5.20,395,1444690800";  d="scan'208,217";a="123136824"
Received: from glkxh0001v.greenlnk.net ([10.109.2.32]) by baemasmds017.greenlnk.net with ESMTP; 07 Dec 2015 14:49:37 +0000
Received: from GLKXM0002V.GREENLNK.net ([169.254.5.2]) by GLKXH0001V.GREENLNK.net ([10.109.2.32]) with mapi id 14.03.0248.002; Mon, 7 Dec 2015 14:49:37 +0000
From: "Dearlove, Christopher (UK)" <chris.dearlove@baesystems.com>
To: "manet@ietf.org" <manet@ietf.org>
Thread-Topic: DLEP-17 commants part 7 (and last)
Thread-Index: AdEw/FfoGYQm4iItQviBsn+KBq5Rag==
Date: Mon, 7 Dec 2015 14:49:35 +0000
Message-ID: <B31EEDDDB8ED7E4A93FDF12A4EECD30D7D76E992@GLKXM0002V.GREENLNK.net>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.109.62.6]
Content-Type: multipart/alternative; boundary="_000_B31EEDDDB8ED7E4A93FDF12A4EECD30D7D76E992GLKXM0002VGREEN_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/p3g6D8psw1MUeEDUCbUOVE05Wi4>
Subject: [manet] DLEP-17 commants part 7 (and last)
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: <https://mailarchive.ietf.org/arch/browse/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: Mon, 07 Dec 2015 14:49:41 -0000

--_000_B31EEDDDB8ED7E4A93FDF12A4EECD30D7D76E992GLKXM0002VGREEN_
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable

Appendices

Appendix A. What is the alternative if starting with an assumed address/por=
t?

Appendix A Peer Discovery. I wasn't initially clear on why the first Peer D=
iscovery arrow had a different termination. No explicit comment on right as=
 to PD not received.

Appendix A has the MAY stop in an odd place after Peer Offer received. I ca=
n't see how to produce a really nice flow without three PDs. (First says se=
nt, second says may send again, may give up, but not doing so here, third i=
s received, produces offer. Maybe someone can do better than me.)

Appendix B.1, TCP connect and then what? TCP acknowledgement at least?

Appendix B.2, is TCP close discussed in report? (is it just assumed?)

Appendices B.1/B.2 TCP connect starts at single bar to no bar, TCP close is=
 from double bar to double bar. Notation seems inconsistent. (And elsewhere=
 double bar is used for failure.)

Appendix B.5. Will the modem send a Session Termination Response after rece=
iving a TCP shutdown?

Appendix B.8 (and elsewhere) "as above". Reference.

Appendix C.1 shows we have both Destination Up and Destination Update. Coul=
d be confusing (especially if abbreviating).

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

--_000_B31EEDDDB8ED7E4A93FDF12A4EECD30D7D76E992GLKXM0002VGREEN_
Content-Type: text/html; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii">
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-GB" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">Appendices<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Appendix A. What is the alternative if starting with=
 an assumed address/port?<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Appendix A Peer Discovery. I wasn&#8217;t initially =
clear on why the first Peer Discovery arrow had a different termination. No=
 explicit comment on right as to PD not received.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Appendix A has the MAY stop in an odd place after Pe=
er Offer received. I can&#8217;t see how to produce a really nice flow with=
out three PDs. (First says sent, second says may send again, may give up, b=
ut not doing so here, third is received,
 produces offer. Maybe someone can do better than me.)<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Appendix B.1, TCP connect and then what? TCP acknowl=
edgement at least?<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Appendix B.2, is TCP close discussed in report? (is =
it just assumed?)<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Appendices B.1/B.2 TCP connect starts at single bar =
to no bar, TCP close is from double bar to double bar. Notation seems incon=
sistent. (And elsewhere double bar is used for failure.)<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Appendix B.5. Will the modem send a Session Terminat=
ion Response after receiving a TCP shutdown?<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Appendix B.8 (and elsewhere) &#8220;as above&#8221;.=
 Reference.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Appendix C.1 shows we have both Destination Up and D=
estination Update. Could be confusing (especially if abbreviating).<o:p></o=
:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<p>********************************************************************<br>
This email and any attachments are confidential to the intended<br>
recipient and may also be privileged. If you are not the intended<br>
recipient please delete it from your system and notify the sender.<br>
You should not copy it or use it for any purpose nor disclose or<br>
distribute its contents to any other person.<br>
********************************************************************</p></b=
ody>
</html>

--_000_B31EEDDDB8ED7E4A93FDF12A4EECD30D7D76E992GLKXM0002VGREEN_--


From nobody Mon Dec  7 10:38:32 2015
Return-Path: <prvs=97838a2a1e=david.wiggins@ll.mit.edu>
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 ED79E1B3949 for <manet@ietfa.amsl.com>; Mon,  7 Dec 2015 10:38:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.31
X-Spam-Level: 
X-Spam-Status: No, score=-2.31 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, RCVD_IN_DNSWL_MED=-2.3, T_RP_MATCHES_RCVD=-0.01, UNPARSEABLE_RELAY=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 TwTzNb4fpTtZ for <manet@ietfa.amsl.com>; Mon,  7 Dec 2015 10:38:28 -0800 (PST)
Received: from mx1.ll.mit.edu (MX1.LL.MIT.EDU [129.55.12.45]) by ietfa.amsl.com (Postfix) with ESMTP id AB2F21B3946 for <manet@ietf.org>; Mon,  7 Dec 2015 10:38:27 -0800 (PST)
Received: from LLE2K10-HUB02.mitll.ad.local (LLE2K10-HUB02.mitll.ad.local) by mx1.ll.mit.edu (unknown) with ESMTP id tB7IcOIu011182; Mon, 7 Dec 2015 13:38:25 -0500
From: "Wiggins, David - 0665 - MITLL" <David.Wiggins@ll.mit.edu>
To: Rick Taylor <rick@tropicalstormsoftware.com>, Stan Ratliff <ratliffstan@gmail.com>
Thread-Topic: [manet] DLEP reviews - new info concerning Destination Up
Thread-Index: AQHRLqshkmjWUwhQX02MwJSPON1o356/3FGA
Date: Mon, 7 Dec 2015 18:26:47 +0000
Message-ID: <D28B28CE.138C%David.Wiggins@ll.mit.edu>
References: <CALtoyokXY5aNcZLgCV5hs1aDogi+A4f7SBaC7vZoXhTZtKqbXg@mail.gmail.com> <CAGnRvurDfG_nM47gPUKddSZ1sRY9C_J65Jm46CvruCUS_evYLg@mail.gmail.com> <CALtoyon3CjhN+EoyRDfag4ZtgV424Wmd6-L=_cF08_LBrU37tw@mail.gmail.com> <CAGnRvurZT8OLigxR+pxMtr4GARLYqmQpmeT7+BUKJcxhbKptrA@mail.gmail.com> <CALtoyo=bbeuR+=zG2dV=uO6ak00YENLo_azg7SR4j1+Z3N=3Jg@mail.gmail.com> <CAGnRvupwDbrz+RNojq++B0_B37s72C0BhnDSWArEfhOBi=35XA@mail.gmail.com> <D2874FEE.137A%David.Wiggins@ll.mit.edu> <CALtoyomZHucM7y38N583POKoXexMBCvLzke0A6oU9Rhzqb+pfw@mail.gmail.com> <38A5475DE83986499AEACD2CFAFC3F9801B32FFE4D@tss-server1.home.tropicalstormsoftware.com>
In-Reply-To: <38A5475DE83986499AEACD2CFAFC3F9801B32FFE4D@tss-server1.home.tropicalstormsoftware.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [172.25.59.174]
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="B_3532339605_146316674"
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.15.21, 1.0.33,  0.0.0000 definitions=2015-12-07_11:2015-12-07,2015-12-07,1970-01-01 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 suspectscore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=7.0.1-1511060000 definitions=main-1512070295
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/u0jtYh-1MA1d9jpcuYtTxSYonn4>
Cc: MANET IETF <manet@ietf.org>
Subject: Re: [manet] DLEP reviews - new info concerning Destination Up
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: <https://mailarchive.ietf.org/arch/browse/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: Mon, 07 Dec 2015 18:38:31 -0000

--B_3532339605_146316674
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit

Responses inline...

On 12/5/15, 12:35 AM, "Rick Taylor" <rick@tropicalstormsoftware.com> wrote:

>Sorry for the top post, but I will summarise my side of the discussion
>Stan and I have been having for a week or two.
>
>I have 2 issues with the status-quo of router originated Destination Ups.
>
>1) They have been in the document for several years, but until the
>authors pointed them out on the list, no-one had noticed.  This does not
>point to good interoperability (or a good document ;) ).

I first noticed it a few months after I started with DLEP.

>2) More importantly, a router-originated Destination Up cannot have the
>same data items that a modem originated D/Up, therefore there has to be
>if/else text in the spec covering the two use-cases, and at the point
>one may as well have two messages.

Allowing different data items in different directions would wipe out most
of the symmetry benefits that I see.  It would also cause some heartburn
in our implementation.  (Normally I'd just deal with that quietly, but
there's been some encouragement to discuss implementation issues, so I'll
oblige.)  In our implementation, tables define which data items are
allowed on which signals, and the tables are loaded from configuration.
This makes it easy to adapt to changes in data item/signal mappings.
However, a fairly deep assumption is that the set of data items is not
direction-dependent, because so far that's been true (I think).  We could
change that, but it's not especially easy.  A new message is definitely
easier for us to integrate.  From a pure protocol design standpoint, it's
worth considering whether this new wrinkle, direction-dependent data items
for the same message, is a good idea.  The protocol would need to specify
the allowed direction(s) for each data item on each signal/message.

While we are on the topic of Dest Up from the router, and what data items
it allows... we have been considering having the router send Dest Up to
the modem with the IP addresses/subnets of other hosts and networks that
the router can provide access to.  The modem could then propagate this
over-the-air to remote modems, which could then pass it on (via a regular
Destination Up) to their routers.  This point is to let the routers
communicate what networks they have to each other.  It seemed like this
would be allowed, since there were no stated restrictions that would
prohibit it.  If we restrict Destination Up in a way that prevents this
usage, we'll need some other way of accomplishing the same thing.

>
>3) The flow of destination messages gets very knotty when some messages
>are unidrectional (Dest_Update) and some are bi-directional (Dest_Up).
>Carefully peeling the two use-cases apart and making them explicitly
>different is clearer.

Maybe I should just wait for the new text, but I didn't encounter any
special knotty-ness in this area.

>
>I have already prototyped the text for a new Destination Interest
>message for a draft-18, and in my opinion it has the following advantages:
>
>A) It reads better and is much clearer, and it was not a lot of extra
>text.
>B) It answers Lou's question about how does a router re-acquire a
>destination that the router has previously replied with 'Not
>Interested'.  This is an example of a unicast router-originated
>destination btw.
>C) It helps with Chris' comments about lots of use of the words 'peer'
>and 'participant', the text ends up clearer once one sets the originator
>for each message explicitly.
>
>Hopefully that swings the argument in my favour!
>
>As an exercise for the reader: How many of you have spotted that
>Destination Down can flow in both directions?

Saw that the same time I realized it for Destination Up.

Thanks,

David

--B_3532339605_146316674
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"

MIIMEgYJKoZIhvcNAQcCoIIMAzCCC/8CAQExCzAJBgUrDgMCGgUAMAsGCSqGSIb3DQEHAaCC
CfUwggT1MIID3aADAgECAgpar+vgAAAAADYOMA0GCSqGSIb3DQEBCwUAMFExCzAJBgNVBAYT
AlVTMR8wHQYDVQQKExZNSVQgTGluY29sbiBMYWJvcmF0b3J5MQwwCgYDVQQLEwNQS0kxEzAR
BgNVBAMTCk1JVExMIENBLTMwHhcNMTUwNDA2MTE1OTM4WhcNMTYwNDA1MTE1OTM4WjBiMQsw
CQYDVQQGEwJVUzEfMB0GA1UEChMWTUlUIExpbmNvbG4gTGFib3JhdG9yeTEPMA0GA1UECxMG
UGVvcGxlMSEwHwYDVQQDExhXaWdnaW5zLkRhdmlkLlAuNTAwMTUyMDcwggEiMA0GCSqGSIb3
DQEBAQUAA4IBDwAwggEKAoIBAQDdVA0BrVjbk6NP8JFi7Lks3SHtN8CxSBqFLPNRVWGjTgLG
W9pDcqqOrij0IHmGpAP404gR4dP9mUEb9KfOhKuDdFQFyZnVICDSRbyT4tGOxiTH7MIsV49d
UwrWhj2P/ms6wf1E5L2QwJqjOTMPZj3IClWAkcZsAix5jHkLvNXI5OilCe2u2TDihM1x2kfB
zgQpRy9tuXpxYtFZpoEb0XbqLIzS9FLkTbqlocSm4jwhPXTFQtFwbd6l4zzD4RVPgnpFxg/8
KpuV35lGkp5lbPvpkskz4+n3P9LoCvpoh1pgj3fS0CvCVRzWRAX+oNR/D7RmP1ug+7Ix+JCg
iAB3vLdFAgMBAAGjggG8MIIBuDAdBgNVHQ4EFgQUofYOKn4e6iCZO59iu2f0FxOad4MwDgYD
VR0PAQH/BAQDAgbAMB8GA1UdIwQYMBaAFNdgZg57SY11TA39z0beyMcSh8q/MDMGA1UdHwQs
MCowKKAmoCSGImh0dHA6Ly9jcmwubGwubWl0LmVkdS9nZXRjcmwvTExDQTMwZgYIKwYBBQUH
AQEEWjBYMC0GCCsGAQUFBzAChiFodHRwOi8vY3JsLmxsLm1pdC5lZHUvZ2V0dG8vTExDQTMw
JwYIKwYBBQUHMAGGG2h0dHA6Ly9vY3NwLmxsLm1pdC5lZHUvb2NzcDA9BgkrBgEEAYI3FQcE
MDAuBiYrBgEEAYI3FQiDg+Udh+ynZoathxWD6vBFhbahHx2Fy94yh/+KcwIBZAIBBTAiBgNV
HSUBAf8EGDAWBggrBgEFBQcDBAYKKwYBBAGCNwoDDDAYBgNVHSAEETAPMA0GCyqGSIb3EgIB
AwEIMCMGA1UdEQQcMBqBGERhdmlkLldpZ2dpbnNAbGwubWl0LmVkdTAnBgkrBgEEAYI3FAIE
Gh4YAEwATABVAHMAZQByAFMAaQBnAC0AUwBXMA0GCSqGSIb3DQEBCwUAA4IBAQCgEybvvRIJ
tAlKEfYZyf5DIlcT+LfePOiebFcPxZatSTQW/hJHv4RX/TN8N3bQrx4Jkxe17eQfsKvJXhOi
R6as3vemCxYEMOFIKSsm5LEIC4D4GcXBRZ1CAJIHCY5ezXfKQUxBSdZAq82/fAoNEEP4KPEv
Y07m7OVwXMWpu7kz3CeBVOqL7xlL53pPvkyxtijQRtZrZ5coE9Qh9tHzATi7DW8UWoUv3Yhj
Qz9SnBn3T30ho0GtlTvMXso7UjGZFWLQI2JyR2QW5FYq8GGEq/5PRz/xslsKA5EoHxmSSeRh
eei3gpFbnUrRS+5JSS6kgA/HVoM7CRFo/O8KYXU5z/ihMIIE+DCCA+CgAwIBAgIKWrCpkwAA
AAA2DzANBgkqhkiG9w0BAQsFADBRMQswCQYDVQQGEwJVUzEfMB0GA1UEChMWTUlUIExpbmNv
bG4gTGFib3JhdG9yeTEMMAoGA1UECxMDUEtJMRMwEQYDVQQDEwpNSVRMTCBDQS0zMB4XDTE1
MDQwNjEyMDAyNloXDTE2MDQwNTEyMDAyNlowYjELMAkGA1UEBhMCVVMxHzAdBgNVBAoTFk1J
VCBMaW5jb2xuIExhYm9yYXRvcnkxDzANBgNVBAsTBlBlb3BsZTEhMB8GA1UEAxMYV2lnZ2lu
cy5EYXZpZC5QLjUwMDE1MjA3MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAlEWD
uIm5kuHghfe7O+eMLVena6sNfAZtHLp2mwXLrNshaHM6wVKmml8zhxeSmJJXTF3Owyn7imKs
vHMWcIJD9EoFQyJoeBaFV5Ll75/fE2WKswtGn9ZSSejplI/Iy99SI/9Lna5B7/BDmPozGn66
jdzgl+JVFptqEUGx5NZlRUEEtVtXYUy+PllIq6SpR/242wFiYVslFqSoHu789mexaDDAl7p7
z3W9cYidPtZUoysjW0omzwZIoYMsIhTbUMnv+TkBuhJErBmaNvAXPf8Y3pNf3pYz8pnR4MyI
ibFv2CS/2KLGxJRE9xt1nrgHT8Wx+E6Ro6IYkYLPSdE6YgYAgwIDAQABo4IBvzCCAbswHQYD
VR0OBBYEFGww5LYEZSoVOkuJ7ZVJS+35ChrUMA4GA1UdDwEB/wQEAwIFIDAfBgNVHSMEGDAW
gBTXYGYOe0mNdUwN/c9G3sjHEofKvzAzBgNVHR8ELDAqMCigJqAkhiJodHRwOi8vY3JsLmxs
Lm1pdC5lZHUvZ2V0Y3JsL0xMQ0EzMGYGCCsGAQUFBwEBBFowWDAtBggrBgEFBQcwAoYhaHR0
cDovL2NybC5sbC5taXQuZWR1L2dldHRvL0xMQ0EzMCcGCCsGAQUFBzABhhtodHRwOi8vb2Nz
cC5sbC5taXQuZWR1L29jc3AwPQYJKwYBBAGCNxUHBDAwLgYmKwYBBAGCNxUIg4PlHYfsp2aG
rYcVg+rwRYW2oR8dhevQcIPr7SACAWQCAQQwJQYDVR0lBB4wHAYEVR0lAAYIKwYBBQUHAwQG
CisGAQQBgjcKAwQwGAYDVR0gBBEwDzANBgsqhkiG9xICAQMBCDAjBgNVHREEHDAagRhEYXZp
ZC5XaWdnaW5zQGxsLm1pdC5lZHUwJwYJKwYBBAGCNxQCBBoeGABMAEwAVQBzAGUAcgBFAG4A
YwAtAFMAVzANBgkqhkiG9w0BAQsFAAOCAQEATCsJT66TKeYNh9hrcC1wxRH08CricKt9JktB
I1WWl48F4CqcYDZlLMpvHuSe6GezZzTUH4oq1y2q3um9Txh1NjLPT7j0k5SSwdr2V7d8upDN
WOrXvCi59Cyz5RvuhleCPIE+6wPyDrQwfBRhte/cv8PVOrsG4tio4VOHi/nXcS+HLgC5qNxk
1/w1UBf8QkkNP8kIgum/uItm4QwVdVAJMuwe3te8dYjtp3M5nC2exfqQfk+Mmw/8fdZFpch0
rSYbpchMMOueBuy2UnWaYBF84uXldBH9fkONRX8AL8EQ3sQEOyzxqpwKQ/d0itjAGaPCCJCI
VgnSYSWYoFiN9idyaTGCAeUwggHhAgEBMF8wUTELMAkGA1UEBhMCVVMxHzAdBgNVBAoTFk1J
VCBMaW5jb2xuIExhYm9yYXRvcnkxDDAKBgNVBAsTA1BLSTETMBEGA1UEAxMKTUlUTEwgQ0Et
MwIKWq/r4AAAAAA2DjAJBgUrDgMCGgUAoF0wIwYJKoZIhvcNAQkEMRYEFMWjnfB2cLwxEJNm
KRoF+F+zZArLMBgGCSqGSIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTE1
MTIwNzE4MjY0NVowDQYJKoZIhvcNAQEBBQAEggEAJoh+XfSvHhqE2pw8lCx215Dmnu51qd6w
mEzPrnIB95safwipbIjYUG68ygmcIHO+GwsWyZJDeLJltpsbUAAk0c5YP2SIWlI9+fJa2cKN
Vb/JDUlU0OXVfrewoWfF/QX6e5QVmDDQ8c/U8WIiwa/03FVmM4rOvtygV1D59HHFDi4MEQ82
ukSR/CGZljDcs5VYp5MeLRr9l8JE51t8/KL2ojD5WsnbHI/wulxxDhqMqwfcxq754ew6Nmwu
JVPfbiTYT7SRLtfRYdgHWseu+G7qYLme4wjfHlPNAgaKo/3qpoaEqrFP1y7qMDkXyJ+HB6Ic
0SmWKWMY3etsdl32oN5Drw==

--B_3532339605_146316674--


From nobody Mon Dec  7 10:52:48 2015
Return-Path: <sratliff@idirect.net>
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 467641B398D for <manet@ietfa.amsl.com>; Mon,  7 Dec 2015 10:52:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.911
X-Spam-Level: 
X-Spam-Status: No, score=-1.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 wqEah1XmSXJP for <manet@ietfa.amsl.com>; Mon,  7 Dec 2015 10:52:45 -0800 (PST)
Received: from smtp1.idirect.net (smtp1.idirect.net [198.180.159.61]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 62A0D1B3990 for <manet@ietf.org>; Mon,  7 Dec 2015 10:52:45 -0800 (PST)
IronPort-PHdr: 9a23:tygQuRHjhz3UMw/fUjO/rp1GYnF86YWxBRYc798ds5kLTJ74rs2wAkXT6L1XgUPTWs2DsrQf27SQ6vmrADVZqb+681k8M7V0HycfjssXmwFySOWkMmbcaMDQUiohAc5ZX0Vk9XzoeWJcGcL5ekGA6ibqtW1aJBzzOEJPK/jvHcaK1oLsh770osSYOlwRzBOGIppMbzyO5T3LsccXhYYwYo0Q8TDu5kVyRuJN2GlzLkiSlRuvru25/Zpk7jgC86l5r50IeezAcq85Vb1VCig9eyBwvZWz9EqLcQzarEQdXWoXlAEMSyTM8hD2FtK56nWk66I4kAy7AenSB/hgdT287qstdx7nhyYBLBY99CfSi9A2ga5G9lbpnR10wMboaZCRM+A2KrncdtAyWXBGRsdaXihaHoSmapAIAfYeNPxV6YL6og1K5SCiDA/kPurzzj5GiDeix6Qm1+UvHxra1QoIENcHsXCSp9LwYvQ8S+ewmePyxCnHbv1YnX/G9IHOdh0w67nYRqh5bc7Qx0cHFg/ElFibtcrjMi/DhbdFiHSS8+c1DbHnsGUgsQwk52H3nso=
X-IronPort-AV: E=Sophos;i="5.20,396,1444708800";  d="scan'208";a="1114186"
X-IPAS-Result: A2CeBAA61GVW/8r6+gpeDgsBAQEBDwEBAQGEUbsRgiiBboYOAoF/EwEBAQEBAQEBgQmCLYIIAQEEOj8QAgEINhAyJQIEAQ0NyREBAQEBAQEEAQEBAQEBHYZWhHuEKhEBhH8FlmEBjTScdCMBhAU+hSA6gQcBAQE
From: "Ratliff, Stanley" <sratliff@idirect.net>
To: "Wiggins, David - 0665 - MITLL" <David.Wiggins@ll.mit.edu>, Rick Taylor <rick@tropicalstormsoftware.com>, Stan Ratliff <ratliffstan@gmail.com>
Thread-Topic: [manet] DLEP reviews - new info concerning Destination Up
Thread-Index: AQHRLqsI1KVcoQ0pKkS/cuj4RUZzhp7AMCWA//+wtrA=
Date: Mon, 7 Dec 2015 18:52:43 +0000
Message-ID: <d9e96e818b6a4511bc39ba34ddb4060c@VAUSDITCHM2.idirect.net>
References: <CALtoyokXY5aNcZLgCV5hs1aDogi+A4f7SBaC7vZoXhTZtKqbXg@mail.gmail.com> <CAGnRvurDfG_nM47gPUKddSZ1sRY9C_J65Jm46CvruCUS_evYLg@mail.gmail.com> <CALtoyon3CjhN+EoyRDfag4ZtgV424Wmd6-L=_cF08_LBrU37tw@mail.gmail.com> <CAGnRvurZT8OLigxR+pxMtr4GARLYqmQpmeT7+BUKJcxhbKptrA@mail.gmail.com> <CALtoyo=bbeuR+=zG2dV=uO6ak00YENLo_azg7SR4j1+Z3N=3Jg@mail.gmail.com> <CAGnRvupwDbrz+RNojq++B0_B37s72C0BhnDSWArEfhOBi=35XA@mail.gmail.com> <D2874FEE.137A%David.Wiggins@ll.mit.edu> <CALtoyomZHucM7y38N583POKoXexMBCvLzke0A6oU9Rhzqb+pfw@mail.gmail.com> <38A5475DE83986499AEACD2CFAFC3F9801B32FFE4D@tss-server1.home.tropicalstormsoftware.com> <D28B28CE.138C%David.Wiggins@ll.mit.edu>
In-Reply-To: <D28B28CE.138C%David.Wiggins@ll.mit.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.250.250.20]
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/JKtcOcT8lZPOjSgkUHP0JGi7d-E>
Cc: MANET IETF <manet@ietf.org>
Subject: Re: [manet] DLEP reviews - new info concerning Destination Up
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: <https://mailarchive.ietf.org/arch/browse/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: Mon, 07 Dec 2015 18:52:47 -0000

David, =


One item: =


[snip]
> >2) More importantly, a router-originated Destination Up cannot have the
> >same data items that a modem originated D/Up, therefore there has to be
> >if/else text in the spec covering the two use-cases, and at the point
> >one may as well have two messages.
> =

> Allowing different data items in different directions would wipe out most=
 of
> the symmetry benefits that I see.  It would also cause some heartburn in =
our
> implementation.  (Normally I'd just deal with that quietly, but there's b=
een
> some encouragement to discuss implementation issues, so I'll
> oblige.)  In our implementation, tables define which data items are allow=
ed
> on which signals, and the tables are loaded from configuration.
> This makes it easy to adapt to changes in data item/signal mappings.
> However, a fairly deep assumption is that the set of data items is not
> direction-dependent, because so far that's been true (I think).  We could
> change that, but it's not especially easy.  A new message is definitely e=
asier
> for us to integrate.  From a pure protocol design standpoint, it's worth
> considering whether this new wrinkle, direction-dependent data items for
> the same message, is a good idea.  The protocol would need to specify the
> allowed direction(s) for each data item on each signal/message.
> =


The main issue here (for me, at least) goes back to the last email I sent o=
n this thread - Assume that a router originates a Destination Up for a mult=
icast group to a modem. What do the metrics on that Destination Up (if they=
 exist) mean? Just to flesh out the example, let's say the router issues De=
stination Up with CDRR/CDRT set to 100Mb. However, the RF link is somewhere=
 in the neighborhood of 32Mbit. What do you envision happening then?

At a high level, I don't have an issue with the messages and the data items=
 being capable of flowing in both directions. But I wonder how much we have=
 to document for the sake of interoperability. =


Regards,
Stan
 =

[snip]

_____________________________________________________
This electronic message and any files transmitted with it contains
information from iDirect, which may be privileged, proprietary
and/or confidential. It is intended solely for the use of the individual
or entity to whom they are addressed. If you are not the original
recipient or the person responsible for delivering the email to the
intended recipient, be advised that you have received this email
in error, and that any use, dissemination, forwarding, printing, or
copying of this email is strictly prohibited. If you received this email
in error, please delete it and immediately notify the sender.
_____________________________________________________


From nobody Mon Dec  7 11:15:02 2015
Return-Path: <sratliff@idirect.net>
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 2E9D21B3A08 for <manet@ietfa.amsl.com>; Mon,  7 Dec 2015 11:15:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.911
X-Spam-Level: 
X-Spam-Status: No, score=-1.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 ZGUJsrO_Svi2 for <manet@ietfa.amsl.com>; Mon,  7 Dec 2015 11:15:00 -0800 (PST)
Received: from smtp1.idirect.net (smtp1.idirect.net [198.180.159.61]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1E7381B39F1 for <manet@ietf.org>; Mon,  7 Dec 2015 11:15:00 -0800 (PST)
IronPort-PHdr: 9a23:fwcHARVVsdA2TatYsMaflYvBZTfV8LGtZVwlr6E/grcLSJyIuqrYZx2Gt8tkgFKBZ4jH8fUM07OQ6PC+HzVZqs/Y7zgrS99laVwssY0uhQsuAcqIWwXQDcXBSGgEJvlET0Jv5HqhMEJYS47UblzWpWCuv3ZJQk2sfTR8Kum9IIPOlcP/j7n0oM2NJVwRz2PkPvtbF1afk0b4joEum4xsK6I8mFPig0BjXKBo/15uPk+ZhB3m5829r9ZJ+iVUvO89pYYbCf2pN4xxd7FTDSwnPmYp/4Wr8ECbFUrcrkcbBy8pkxVHAg7eqFnWV4nwvmO//rIjhnTSeIXTbIwQfX7qu4tiVh7kzhgGODE49nr/jsg2iaNH5h+tuko7i7TVa4LdCPNveqTHNYcARGFCdtpLUDRACYq4dJcIFe8aOuhEsIDnqh0Fqh7oQUGXGOrpggVBmnv306Nyh/4oDQXH0gI7A9sImHvRpdTxcqwVVLbm4rPPyGCJVfpK3Tbz5syASQwop/WBTPg4JdHLwFUrFg3LplScqJboNC/T0OkR5TvIp9F8XP6i3jZ04zp6pSKik4J10tHE
X-IronPort-AV: E=Sophos;i="5.20,396,1444708800";  d="scan'208";a="1114942"
X-IPAS-Result: A2ChBADx2GVW/8v6+gpeDgsBAQEBDwEBAQGESwa7EYQWhg4CggERAQEBAQEBAQGBCYItggcBAQEBAzo/DAQCAQgRBAEBAR4JByERFAkIAgQBDQUIiBIDvDUNhE0BAQEBAQEBAQEBAQEBAQEBAQEBARmGVoR7glOGaAWHSI8ZAYtEgXCBYpJMbYNng3I3g3I+coRogQcBAQE
From: "Ratliff, Stanley" <sratliff@idirect.net>
To: "Wiggins, David - 0665 - MITLL" <David.Wiggins@ll.mit.edu>, Rick Taylor <rick@tropicalstormsoftware.com>, Stan Ratliff <ratliffstan@gmail.com>
Thread-Topic: [manet] DLEP reviews - new info concerning Destination Up
Thread-Index: AQHRLqsI1KVcoQ0pKkS/cuj4RUZzhp7AMCWA//+3+yA=
Date: Mon, 7 Dec 2015 19:14:58 +0000
Message-ID: <f5e70c5286324298a55edfc5377c3874@VAUSDITCHM2.idirect.net>
References: <CALtoyokXY5aNcZLgCV5hs1aDogi+A4f7SBaC7vZoXhTZtKqbXg@mail.gmail.com> <CAGnRvurDfG_nM47gPUKddSZ1sRY9C_J65Jm46CvruCUS_evYLg@mail.gmail.com> <CALtoyon3CjhN+EoyRDfag4ZtgV424Wmd6-L=_cF08_LBrU37tw@mail.gmail.com> <CAGnRvurZT8OLigxR+pxMtr4GARLYqmQpmeT7+BUKJcxhbKptrA@mail.gmail.com> <CALtoyo=bbeuR+=zG2dV=uO6ak00YENLo_azg7SR4j1+Z3N=3Jg@mail.gmail.com> <CAGnRvupwDbrz+RNojq++B0_B37s72C0BhnDSWArEfhOBi=35XA@mail.gmail.com> <D2874FEE.137A%David.Wiggins@ll.mit.edu> <CALtoyomZHucM7y38N583POKoXexMBCvLzke0A6oU9Rhzqb+pfw@mail.gmail.com> <38A5475DE83986499AEACD2CFAFC3F9801B32FFE4D@tss-server1.home.tropicalstormsoftware.com> <D28B28CE.138C%David.Wiggins@ll.mit.edu>
In-Reply-To: <D28B28CE.138C%David.Wiggins@ll.mit.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.250.250.20]
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/FWUsbZ8vIpCVfI8eRSecwD5aVds>
Cc: MANET IETF <manet@ietf.org>
Subject: Re: [manet] DLEP reviews - new info concerning Destination Up
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: <https://mailarchive.ietf.org/arch/browse/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: Mon, 07 Dec 2015 19:15:02 -0000

David, =


My apologies for the piece-meal response. But I just got to thinking about =
your other point: =


> -----Original Message-----
> From: manet [mailto:manet-bounces@ietf.org] On Behalf Of Wiggins, David -
> 0665 - MITLL
> Sent: Monday, December 07, 2015 1:27 PM
> To: Rick Taylor <rick@tropicalstormsoftware.com>; Stan Ratliff
> <ratliffstan@gmail.com>
> Cc: MANET IETF <manet@ietf.org>
> Subject: Re: [manet] DLEP reviews - new info concerning Destination Up
> =

> Responses inline...
> =

> On 12/5/15, 12:35 AM, "Rick Taylor" <rick@tropicalstormsoftware.com>
> wrote:
> =

> >Sorry for the top post, but I will summarise my side of the discussion
> >Stan and I have been having for a week or two.
> >
> >I have 2 issues with the status-quo of router originated Destination Ups.
> >
> >1) They have been in the document for several years, but until the
> >authors pointed them out on the list, no-one had noticed.  This does
> >not point to good interoperability (or a good document ;) ).
> =

> I first noticed it a few months after I started with DLEP.
> =

> >2) More importantly, a router-originated Destination Up cannot have the
> >same data items that a modem originated D/Up, therefore there has to be
> >if/else text in the spec covering the two use-cases, and at the point
> >one may as well have two messages.
> =

> Allowing different data items in different directions would wipe out most=
 of
> the symmetry benefits that I see.  It would also cause some heartburn in =
our
> implementation.  (Normally I'd just deal with that quietly, but there's b=
een
> some encouragement to discuss implementation issues, so I'll
> oblige.)  In our implementation, tables define which data items are allow=
ed
> on which signals, and the tables are loaded from configuration.
> This makes it easy to adapt to changes in data item/signal mappings.
> However, a fairly deep assumption is that the set of data items is not
> direction-dependent, because so far that's been true (I think).  We could
> change that, but it's not especially easy.  A new message is definitely e=
asier
> for us to integrate.  From a pure protocol design standpoint, it's worth
> considering whether this new wrinkle, direction-dependent data items for
> the same message, is a good idea.  The protocol would need to specify the
> allowed direction(s) for each data item on each signal/message.
> =

> While we are on the topic of Dest Up from the router, and what data items=
 it
> allows... we have been considering having the router send Dest Up to the
> modem with the IP addresses/subnets of other hosts and networks that the
> router can provide access to.  The modem could then propagate this over-
> the-air to remote modems, which could then pass it on (via a regular
> Destination Up) to their routers.  This point is to let the routers commu=
nicate
> what networks they have to each other.  It seemed like this would be
> allowed, since there were no stated restrictions that would prohibit it. =
 If we
> restrict Destination Up in a way that prevents this usage, we'll need some
> other way of accomplishing the same thing.

How do you see this working? Specifically, what MAC address to you announce=
 with the connected subnets? The MAC of the router? Because that's the only=
 way I see this working. =


Regards,
Stan
 =


> =

> >
> >3) The flow of destination messages gets very knotty when some messages
> >are unidrectional (Dest_Update) and some are bi-directional (Dest_Up).
> >Carefully peeling the two use-cases apart and making them explicitly
> >different is clearer.
> =

> Maybe I should just wait for the new text, but I didn't encounter any spe=
cial
> knotty-ness in this area.
> =

> >
> >I have already prototyped the text for a new Destination Interest
> >message for a draft-18, and in my opinion it has the following advantage=
s:
> >
> >A) It reads better and is much clearer, and it was not a lot of extra
> >text.
> >B) It answers Lou's question about how does a router re-acquire a
> >destination that the router has previously replied with 'Not
> >Interested'.  This is an example of a unicast router-originated
> >destination btw.
> >C) It helps with Chris' comments about lots of use of the words 'peer'
> >and 'participant', the text ends up clearer once one sets the
> >originator for each message explicitly.
> >
> >Hopefully that swings the argument in my favour!
> >
> >As an exercise for the reader: How many of you have spotted that
> >Destination Down can flow in both directions?
> =

> Saw that the same time I realized it for Destination Up.
> =

> Thanks,
> =

> David

_____________________________________________________
This electronic message and any files transmitted with it contains
information from iDirect, which may be privileged, proprietary
and/or confidential. It is intended solely for the use of the individual
or entity to whom they are addressed. If you are not the original
recipient or the person responsible for delivering the email to the
intended recipient, be advised that you have received this email
in error, and that any use, dissemination, forwarding, printing, or
copying of this email is strictly prohibited. If you received this email
in error, please delete it and immediately notify the sender.
_____________________________________________________


From nobody Mon Dec  7 11:25:57 2015
Return-Path: <prvs=97838a2a1e=david.wiggins@ll.mit.edu>
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 09A271A00DC for <manet@ietfa.amsl.com>; Mon,  7 Dec 2015 11:25:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.209
X-Spam-Level: 
X-Spam-Status: No, score=-4.209 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, T_RP_MATCHES_RCVD=-0.01, UNPARSEABLE_RELAY=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 gln6ImhBUbqn for <manet@ietfa.amsl.com>; Mon,  7 Dec 2015 11:25:54 -0800 (PST)
Received: from mx1.ll.mit.edu (MX1.LL.MIT.EDU [129.55.12.45]) by ietfa.amsl.com (Postfix) with ESMTP id 858881A009D for <manet@ietf.org>; Mon,  7 Dec 2015 11:25:54 -0800 (PST)
Received: from LLE2K10-HUB02.mitll.ad.local (LLE2K10-HUB02.mitll.ad.local) by mx1.ll.mit.edu (unknown) with ESMTP id tB7JPqPZ020620; Mon, 7 Dec 2015 14:25:52 -0500
From: "Wiggins, David - 0665 - MITLL" <David.Wiggins@ll.mit.edu>
To: "Ratliff, Stanley" <sratliff@idirect.net>, Rick Taylor <rick@tropicalstormsoftware.com>, Stan Ratliff <ratliffstan@gmail.com>
Thread-Topic: [manet] DLEP reviews - new info concerning Destination Up
Thread-Index: AQHRLqshkmjWUwhQX02MwJSPON1o356/3FGAgABhSgD//683AA==
Date: Mon, 7 Dec 2015 19:25:51 +0000
Message-ID: <D28B4659.1396%David.Wiggins@ll.mit.edu>
References: <CALtoyokXY5aNcZLgCV5hs1aDogi+A4f7SBaC7vZoXhTZtKqbXg@mail.gmail.com> <CAGnRvurDfG_nM47gPUKddSZ1sRY9C_J65Jm46CvruCUS_evYLg@mail.gmail.com> <CALtoyon3CjhN+EoyRDfag4ZtgV424Wmd6-L=_cF08_LBrU37tw@mail.gmail.com> <CAGnRvurZT8OLigxR+pxMtr4GARLYqmQpmeT7+BUKJcxhbKptrA@mail.gmail.com> <CALtoyo=bbeuR+=zG2dV=uO6ak00YENLo_azg7SR4j1+Z3N=3Jg@mail.gmail.com> <CAGnRvupwDbrz+RNojq++B0_B37s72C0BhnDSWArEfhOBi=35XA@mail.gmail.com> <D2874FEE.137A%David.Wiggins@ll.mit.edu> <CALtoyomZHucM7y38N583POKoXexMBCvLzke0A6oU9Rhzqb+pfw@mail.gmail.com> <38A5475DE83986499AEACD2CFAFC3F9801B32FFE4D@tss-server1.home.tropicalstormsoftware.com> <D28B28CE.138C%David.Wiggins@ll.mit.edu> <f5e70c5286324298a55edfc5377c3874@VAUSDITCHM2.idirect.net>
In-Reply-To: <f5e70c5286324298a55edfc5377c3874@VAUSDITCHM2.idirect.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [172.25.59.174]
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="B_3532343150_146580493"
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.15.21, 1.0.33,  0.0.0000 definitions=2015-12-07_11:2015-12-07,2015-12-07,1970-01-01 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 suspectscore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=7.0.1-1511060000 definitions=main-1512070306
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/dFinSgmShnMRebmnINgNhHUV9bY>
Cc: MANET IETF <manet@ietf.org>
Subject: Re: [manet] DLEP reviews - new info concerning Destination Up
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: <https://mailarchive.ietf.org/arch/browse/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: Mon, 07 Dec 2015 19:25:57 -0000

--B_3532343150_146580493
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit

Hi Stan,

On 12/7/15, 2:14 PM, "Ratliff, Stanley" <sratliff@idirect.net> wrote:

>David, 
>
>My apologies for the piece-meal response. But I just got to thinking
>about your other point:
>
>> -----Original Message-----
>> From: manet [mailto:manet-bounces@ietf.org] On Behalf Of Wiggins, David
>>-
>> 0665 - MITLL
>>
>> 
>> While we are on the topic of Dest Up from the router, and what data
>>items it
>> allows... we have been considering having the router send Dest Up to the
>> modem with the IP addresses/subnets of other hosts and networks that the
>> router can provide access to.  The modem could then propagate this over-
>> the-air to remote modems, which could then pass it on (via a regular
>> Destination Up) to their routers.  This point is to let the routers
>>communicate
>> what networks they have to each other.  It seemed like this would be
>> allowed, since there were no stated restrictions that would prohibit
>>it.  If we
>> restrict Destination Up in a way that prevents this usage, we'll need
>>some
>> other way of accomplishing the same thing.
>
>How do you see this working? Specifically, what MAC address to you
>announce with the connected subnets? The MAC of the router? Because
>that's the only way I see this working.

Yes, the router's MAC address.

Thanks,

David

--B_3532343150_146580493
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"

MIIMEgYJKoZIhvcNAQcCoIIMAzCCC/8CAQExCzAJBgUrDgMCGgUAMAsGCSqGSIb3DQEHAaCC
CfUwggT1MIID3aADAgECAgpar+vgAAAAADYOMA0GCSqGSIb3DQEBCwUAMFExCzAJBgNVBAYT
AlVTMR8wHQYDVQQKExZNSVQgTGluY29sbiBMYWJvcmF0b3J5MQwwCgYDVQQLEwNQS0kxEzAR
BgNVBAMTCk1JVExMIENBLTMwHhcNMTUwNDA2MTE1OTM4WhcNMTYwNDA1MTE1OTM4WjBiMQsw
CQYDVQQGEwJVUzEfMB0GA1UEChMWTUlUIExpbmNvbG4gTGFib3JhdG9yeTEPMA0GA1UECxMG
UGVvcGxlMSEwHwYDVQQDExhXaWdnaW5zLkRhdmlkLlAuNTAwMTUyMDcwggEiMA0GCSqGSIb3
DQEBAQUAA4IBDwAwggEKAoIBAQDdVA0BrVjbk6NP8JFi7Lks3SHtN8CxSBqFLPNRVWGjTgLG
W9pDcqqOrij0IHmGpAP404gR4dP9mUEb9KfOhKuDdFQFyZnVICDSRbyT4tGOxiTH7MIsV49d
UwrWhj2P/ms6wf1E5L2QwJqjOTMPZj3IClWAkcZsAix5jHkLvNXI5OilCe2u2TDihM1x2kfB
zgQpRy9tuXpxYtFZpoEb0XbqLIzS9FLkTbqlocSm4jwhPXTFQtFwbd6l4zzD4RVPgnpFxg/8
KpuV35lGkp5lbPvpkskz4+n3P9LoCvpoh1pgj3fS0CvCVRzWRAX+oNR/D7RmP1ug+7Ix+JCg
iAB3vLdFAgMBAAGjggG8MIIBuDAdBgNVHQ4EFgQUofYOKn4e6iCZO59iu2f0FxOad4MwDgYD
VR0PAQH/BAQDAgbAMB8GA1UdIwQYMBaAFNdgZg57SY11TA39z0beyMcSh8q/MDMGA1UdHwQs
MCowKKAmoCSGImh0dHA6Ly9jcmwubGwubWl0LmVkdS9nZXRjcmwvTExDQTMwZgYIKwYBBQUH
AQEEWjBYMC0GCCsGAQUFBzAChiFodHRwOi8vY3JsLmxsLm1pdC5lZHUvZ2V0dG8vTExDQTMw
JwYIKwYBBQUHMAGGG2h0dHA6Ly9vY3NwLmxsLm1pdC5lZHUvb2NzcDA9BgkrBgEEAYI3FQcE
MDAuBiYrBgEEAYI3FQiDg+Udh+ynZoathxWD6vBFhbahHx2Fy94yh/+KcwIBZAIBBTAiBgNV
HSUBAf8EGDAWBggrBgEFBQcDBAYKKwYBBAGCNwoDDDAYBgNVHSAEETAPMA0GCyqGSIb3EgIB
AwEIMCMGA1UdEQQcMBqBGERhdmlkLldpZ2dpbnNAbGwubWl0LmVkdTAnBgkrBgEEAYI3FAIE
Gh4YAEwATABVAHMAZQByAFMAaQBnAC0AUwBXMA0GCSqGSIb3DQEBCwUAA4IBAQCgEybvvRIJ
tAlKEfYZyf5DIlcT+LfePOiebFcPxZatSTQW/hJHv4RX/TN8N3bQrx4Jkxe17eQfsKvJXhOi
R6as3vemCxYEMOFIKSsm5LEIC4D4GcXBRZ1CAJIHCY5ezXfKQUxBSdZAq82/fAoNEEP4KPEv
Y07m7OVwXMWpu7kz3CeBVOqL7xlL53pPvkyxtijQRtZrZ5coE9Qh9tHzATi7DW8UWoUv3Yhj
Qz9SnBn3T30ho0GtlTvMXso7UjGZFWLQI2JyR2QW5FYq8GGEq/5PRz/xslsKA5EoHxmSSeRh
eei3gpFbnUrRS+5JSS6kgA/HVoM7CRFo/O8KYXU5z/ihMIIE+DCCA+CgAwIBAgIKWrCpkwAA
AAA2DzANBgkqhkiG9w0BAQsFADBRMQswCQYDVQQGEwJVUzEfMB0GA1UEChMWTUlUIExpbmNv
bG4gTGFib3JhdG9yeTEMMAoGA1UECxMDUEtJMRMwEQYDVQQDEwpNSVRMTCBDQS0zMB4XDTE1
MDQwNjEyMDAyNloXDTE2MDQwNTEyMDAyNlowYjELMAkGA1UEBhMCVVMxHzAdBgNVBAoTFk1J
VCBMaW5jb2xuIExhYm9yYXRvcnkxDzANBgNVBAsTBlBlb3BsZTEhMB8GA1UEAxMYV2lnZ2lu
cy5EYXZpZC5QLjUwMDE1MjA3MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAlEWD
uIm5kuHghfe7O+eMLVena6sNfAZtHLp2mwXLrNshaHM6wVKmml8zhxeSmJJXTF3Owyn7imKs
vHMWcIJD9EoFQyJoeBaFV5Ll75/fE2WKswtGn9ZSSejplI/Iy99SI/9Lna5B7/BDmPozGn66
jdzgl+JVFptqEUGx5NZlRUEEtVtXYUy+PllIq6SpR/242wFiYVslFqSoHu789mexaDDAl7p7
z3W9cYidPtZUoysjW0omzwZIoYMsIhTbUMnv+TkBuhJErBmaNvAXPf8Y3pNf3pYz8pnR4MyI
ibFv2CS/2KLGxJRE9xt1nrgHT8Wx+E6Ro6IYkYLPSdE6YgYAgwIDAQABo4IBvzCCAbswHQYD
VR0OBBYEFGww5LYEZSoVOkuJ7ZVJS+35ChrUMA4GA1UdDwEB/wQEAwIFIDAfBgNVHSMEGDAW
gBTXYGYOe0mNdUwN/c9G3sjHEofKvzAzBgNVHR8ELDAqMCigJqAkhiJodHRwOi8vY3JsLmxs
Lm1pdC5lZHUvZ2V0Y3JsL0xMQ0EzMGYGCCsGAQUFBwEBBFowWDAtBggrBgEFBQcwAoYhaHR0
cDovL2NybC5sbC5taXQuZWR1L2dldHRvL0xMQ0EzMCcGCCsGAQUFBzABhhtodHRwOi8vb2Nz
cC5sbC5taXQuZWR1L29jc3AwPQYJKwYBBAGCNxUHBDAwLgYmKwYBBAGCNxUIg4PlHYfsp2aG
rYcVg+rwRYW2oR8dhevQcIPr7SACAWQCAQQwJQYDVR0lBB4wHAYEVR0lAAYIKwYBBQUHAwQG
CisGAQQBgjcKAwQwGAYDVR0gBBEwDzANBgsqhkiG9xICAQMBCDAjBgNVHREEHDAagRhEYXZp
ZC5XaWdnaW5zQGxsLm1pdC5lZHUwJwYJKwYBBAGCNxQCBBoeGABMAEwAVQBzAGUAcgBFAG4A
YwAtAFMAVzANBgkqhkiG9w0BAQsFAAOCAQEATCsJT66TKeYNh9hrcC1wxRH08CricKt9JktB
I1WWl48F4CqcYDZlLMpvHuSe6GezZzTUH4oq1y2q3um9Txh1NjLPT7j0k5SSwdr2V7d8upDN
WOrXvCi59Cyz5RvuhleCPIE+6wPyDrQwfBRhte/cv8PVOrsG4tio4VOHi/nXcS+HLgC5qNxk
1/w1UBf8QkkNP8kIgum/uItm4QwVdVAJMuwe3te8dYjtp3M5nC2exfqQfk+Mmw/8fdZFpch0
rSYbpchMMOueBuy2UnWaYBF84uXldBH9fkONRX8AL8EQ3sQEOyzxqpwKQ/d0itjAGaPCCJCI
VgnSYSWYoFiN9idyaTGCAeUwggHhAgEBMF8wUTELMAkGA1UEBhMCVVMxHzAdBgNVBAoTFk1J
VCBMaW5jb2xuIExhYm9yYXRvcnkxDDAKBgNVBAsTA1BLSTETMBEGA1UEAxMKTUlUTEwgQ0Et
MwIKWq/r4AAAAAA2DjAJBgUrDgMCGgUAoF0wIwYJKoZIhvcNAQkEMRYEFLVm81Qhv6H5W8+8
VHmogIH7LFz9MBgGCSqGSIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTE1
MTIwNzE5MjU1MFowDQYJKoZIhvcNAQEBBQAEggEAi3gsRgNCIoSXtWKV4wqCyyfin5Z6Ra2b
UCdfJwvdAHrsEkS7oMNeCtrc4ZmyYgKwZqWtfSBx9pMXlzrLbfsyfHl+Seg8153cxnhuD4d5
5gJ9al19zY3ZI5EJtqcMH3T9aFXYy+yGFrH2i50Njokhz68n4o9TnMYfRPYTKRE5SxeKSE8M
bBAqxRClxmVJB5pDc3DbpB1bDyyNRRwYIoI1OeHqz4Hs9GD6q+Fa7qAbeTCrrscm4MRf8ekd
Tj05/D00Jxwu6sCO2FV2IixIfVfj7ngP0MupfPexbPzuQF+mgpba7w5ExvanVgbvW2NQHQOA
NOORTs6YOlvpKZVoCZSQVA==

--B_3532343150_146580493--


From nobody Mon Dec  7 11:40:47 2015
Return-Path: <prvs=97838a2a1e=david.wiggins@ll.mit.edu>
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 172271A6FE9 for <manet@ietfa.amsl.com>; Mon,  7 Dec 2015 11:40:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.209
X-Spam-Level: 
X-Spam-Status: No, score=-4.209 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, T_RP_MATCHES_RCVD=-0.01, UNPARSEABLE_RELAY=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 qhCBXBW6b4MT for <manet@ietfa.amsl.com>; Mon,  7 Dec 2015 11:40:44 -0800 (PST)
Received: from mx1.ll.mit.edu (MX1.LL.MIT.EDU [129.55.12.45]) by ietfa.amsl.com (Postfix) with ESMTP id 0B80A1A6FE5 for <manet@ietf.org>; Mon,  7 Dec 2015 11:40:43 -0800 (PST)
Received: from LLE2K10-HUB01.mitll.ad.local (LLE2K10-HUB01.mitll.ad.local) by mx1.ll.mit.edu (unknown) with ESMTP id tB7Jecq7011806; Mon, 7 Dec 2015 14:40:42 -0500
From: "Wiggins, David - 0665 - MITLL" <David.Wiggins@ll.mit.edu>
To: "Ratliff, Stanley" <sratliff@idirect.net>, Rick Taylor <rick@tropicalstormsoftware.com>, Stan Ratliff <ratliffstan@gmail.com>
Thread-Topic: [manet] DLEP reviews - new info concerning Destination Up
Thread-Index: AQHRLqshkmjWUwhQX02MwJSPON1o356/3FGAgABbEoD//7mTgA==
Date: Mon, 7 Dec 2015 19:40:41 +0000
Message-ID: <D28B49CB.139B%David.Wiggins@ll.mit.edu>
References: <CALtoyokXY5aNcZLgCV5hs1aDogi+A4f7SBaC7vZoXhTZtKqbXg@mail.gmail.com> <CAGnRvurDfG_nM47gPUKddSZ1sRY9C_J65Jm46CvruCUS_evYLg@mail.gmail.com> <CALtoyon3CjhN+EoyRDfag4ZtgV424Wmd6-L=_cF08_LBrU37tw@mail.gmail.com> <CAGnRvurZT8OLigxR+pxMtr4GARLYqmQpmeT7+BUKJcxhbKptrA@mail.gmail.com> <CALtoyo=bbeuR+=zG2dV=uO6ak00YENLo_azg7SR4j1+Z3N=3Jg@mail.gmail.com> <CAGnRvupwDbrz+RNojq++B0_B37s72C0BhnDSWArEfhOBi=35XA@mail.gmail.com> <D2874FEE.137A%David.Wiggins@ll.mit.edu> <CALtoyomZHucM7y38N583POKoXexMBCvLzke0A6oU9Rhzqb+pfw@mail.gmail.com> <38A5475DE83986499AEACD2CFAFC3F9801B32FFE4D@tss-server1.home.tropicalstormsoftware.com> <D28B28CE.138C%David.Wiggins@ll.mit.edu> <d9e96e818b6a4511bc39ba34ddb4060c@VAUSDITCHM2.idirect.net>
In-Reply-To: <d9e96e818b6a4511bc39ba34ddb4060c@VAUSDITCHM2.idirect.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [172.25.59.174]
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="B_3532344039_146589219"
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.15.21, 1.0.33,  0.0.0000 definitions=2015-12-07_11:2015-12-07,2015-12-07,1970-01-01 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 suspectscore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=7.0.1-1511060000 definitions=main-1512070310
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/sv1u0IezCrbCaYZDLhkAVQyWlAo>
Cc: MANET IETF <manet@ietf.org>
Subject: Re: [manet] DLEP reviews - new info concerning Destination Up
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: <https://mailarchive.ietf.org/arch/browse/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: Mon, 07 Dec 2015 19:40:46 -0000

--B_3532344039_146589219
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit

Hi Stan,

On 12/7/15, 1:52 PM, "Ratliff, Stanley" <sratliff@idirect.net> wrote:

>David, 
>
>One item: 
>
>[snip]
>> >2) More importantly, a router-originated Destination Up cannot have the
>> >same data items that a modem originated D/Up, therefore there has to be
>> >if/else text in the spec covering the two use-cases, and at the point
>> >one may as well have two messages.
>> 
>> Allowing different data items in different directions would wipe out
>>most of
>> the symmetry benefits that I see.  It would also cause some heartburn
>>in our
>> implementation.  (Normally I'd just deal with that quietly, but there's
>>been
>> some encouragement to discuss implementation issues, so I'll
>> oblige.)  In our implementation, tables define which data items are
>>allowed
>> on which signals, and the tables are loaded from configuration.
>> This makes it easy to adapt to changes in data item/signal mappings.
>> However, a fairly deep assumption is that the set of data items is not
>> direction-dependent, because so far that's been true (I think).  We
>>could
>> change that, but it's not especially easy.  A new message is definitely
>>easier
>> for us to integrate.  From a pure protocol design standpoint, it's worth
>> considering whether this new wrinkle, direction-dependent data items for
>> the same message, is a good idea.  The protocol would need to specify
>>the
>> allowed direction(s) for each data item on each signal/message.
>> 
>
>The main issue here (for me, at least) goes back to the last email I sent
>on this thread - Assume that a router originates a Destination Up for a
>multicast group to a modem. What do the metrics on that Destination Up
>(if they exist) mean? Just to flesh out the example, let's say the router
>issues Destination Up with CDRR/CDRT set to 100Mb. However, the RF link
>is somewhere in the neighborhood of 32Mbit. What do you envision
>happening then?

I'm not sure.  Probably ignore it.

>
>At a high level, I don't have an issue with the messages and the data
>items being capable of flowing in both directions. But I wonder how much
>we have to document for the sake of interoperability.

It does seem that the data items coming from the router need to be made
more explicit.

David

--B_3532344039_146589219
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"

MIIMEgYJKoZIhvcNAQcCoIIMAzCCC/8CAQExCzAJBgUrDgMCGgUAMAsGCSqGSIb3DQEHAaCC
CfUwggT1MIID3aADAgECAgpar+vgAAAAADYOMA0GCSqGSIb3DQEBCwUAMFExCzAJBgNVBAYT
AlVTMR8wHQYDVQQKExZNSVQgTGluY29sbiBMYWJvcmF0b3J5MQwwCgYDVQQLEwNQS0kxEzAR
BgNVBAMTCk1JVExMIENBLTMwHhcNMTUwNDA2MTE1OTM4WhcNMTYwNDA1MTE1OTM4WjBiMQsw
CQYDVQQGEwJVUzEfMB0GA1UEChMWTUlUIExpbmNvbG4gTGFib3JhdG9yeTEPMA0GA1UECxMG
UGVvcGxlMSEwHwYDVQQDExhXaWdnaW5zLkRhdmlkLlAuNTAwMTUyMDcwggEiMA0GCSqGSIb3
DQEBAQUAA4IBDwAwggEKAoIBAQDdVA0BrVjbk6NP8JFi7Lks3SHtN8CxSBqFLPNRVWGjTgLG
W9pDcqqOrij0IHmGpAP404gR4dP9mUEb9KfOhKuDdFQFyZnVICDSRbyT4tGOxiTH7MIsV49d
UwrWhj2P/ms6wf1E5L2QwJqjOTMPZj3IClWAkcZsAix5jHkLvNXI5OilCe2u2TDihM1x2kfB
zgQpRy9tuXpxYtFZpoEb0XbqLIzS9FLkTbqlocSm4jwhPXTFQtFwbd6l4zzD4RVPgnpFxg/8
KpuV35lGkp5lbPvpkskz4+n3P9LoCvpoh1pgj3fS0CvCVRzWRAX+oNR/D7RmP1ug+7Ix+JCg
iAB3vLdFAgMBAAGjggG8MIIBuDAdBgNVHQ4EFgQUofYOKn4e6iCZO59iu2f0FxOad4MwDgYD
VR0PAQH/BAQDAgbAMB8GA1UdIwQYMBaAFNdgZg57SY11TA39z0beyMcSh8q/MDMGA1UdHwQs
MCowKKAmoCSGImh0dHA6Ly9jcmwubGwubWl0LmVkdS9nZXRjcmwvTExDQTMwZgYIKwYBBQUH
AQEEWjBYMC0GCCsGAQUFBzAChiFodHRwOi8vY3JsLmxsLm1pdC5lZHUvZ2V0dG8vTExDQTMw
JwYIKwYBBQUHMAGGG2h0dHA6Ly9vY3NwLmxsLm1pdC5lZHUvb2NzcDA9BgkrBgEEAYI3FQcE
MDAuBiYrBgEEAYI3FQiDg+Udh+ynZoathxWD6vBFhbahHx2Fy94yh/+KcwIBZAIBBTAiBgNV
HSUBAf8EGDAWBggrBgEFBQcDBAYKKwYBBAGCNwoDDDAYBgNVHSAEETAPMA0GCyqGSIb3EgIB
AwEIMCMGA1UdEQQcMBqBGERhdmlkLldpZ2dpbnNAbGwubWl0LmVkdTAnBgkrBgEEAYI3FAIE
Gh4YAEwATABVAHMAZQByAFMAaQBnAC0AUwBXMA0GCSqGSIb3DQEBCwUAA4IBAQCgEybvvRIJ
tAlKEfYZyf5DIlcT+LfePOiebFcPxZatSTQW/hJHv4RX/TN8N3bQrx4Jkxe17eQfsKvJXhOi
R6as3vemCxYEMOFIKSsm5LEIC4D4GcXBRZ1CAJIHCY5ezXfKQUxBSdZAq82/fAoNEEP4KPEv
Y07m7OVwXMWpu7kz3CeBVOqL7xlL53pPvkyxtijQRtZrZ5coE9Qh9tHzATi7DW8UWoUv3Yhj
Qz9SnBn3T30ho0GtlTvMXso7UjGZFWLQI2JyR2QW5FYq8GGEq/5PRz/xslsKA5EoHxmSSeRh
eei3gpFbnUrRS+5JSS6kgA/HVoM7CRFo/O8KYXU5z/ihMIIE+DCCA+CgAwIBAgIKWrCpkwAA
AAA2DzANBgkqhkiG9w0BAQsFADBRMQswCQYDVQQGEwJVUzEfMB0GA1UEChMWTUlUIExpbmNv
bG4gTGFib3JhdG9yeTEMMAoGA1UECxMDUEtJMRMwEQYDVQQDEwpNSVRMTCBDQS0zMB4XDTE1
MDQwNjEyMDAyNloXDTE2MDQwNTEyMDAyNlowYjELMAkGA1UEBhMCVVMxHzAdBgNVBAoTFk1J
VCBMaW5jb2xuIExhYm9yYXRvcnkxDzANBgNVBAsTBlBlb3BsZTEhMB8GA1UEAxMYV2lnZ2lu
cy5EYXZpZC5QLjUwMDE1MjA3MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAlEWD
uIm5kuHghfe7O+eMLVena6sNfAZtHLp2mwXLrNshaHM6wVKmml8zhxeSmJJXTF3Owyn7imKs
vHMWcIJD9EoFQyJoeBaFV5Ll75/fE2WKswtGn9ZSSejplI/Iy99SI/9Lna5B7/BDmPozGn66
jdzgl+JVFptqEUGx5NZlRUEEtVtXYUy+PllIq6SpR/242wFiYVslFqSoHu789mexaDDAl7p7
z3W9cYidPtZUoysjW0omzwZIoYMsIhTbUMnv+TkBuhJErBmaNvAXPf8Y3pNf3pYz8pnR4MyI
ibFv2CS/2KLGxJRE9xt1nrgHT8Wx+E6Ro6IYkYLPSdE6YgYAgwIDAQABo4IBvzCCAbswHQYD
VR0OBBYEFGww5LYEZSoVOkuJ7ZVJS+35ChrUMA4GA1UdDwEB/wQEAwIFIDAfBgNVHSMEGDAW
gBTXYGYOe0mNdUwN/c9G3sjHEofKvzAzBgNVHR8ELDAqMCigJqAkhiJodHRwOi8vY3JsLmxs
Lm1pdC5lZHUvZ2V0Y3JsL0xMQ0EzMGYGCCsGAQUFBwEBBFowWDAtBggrBgEFBQcwAoYhaHR0
cDovL2NybC5sbC5taXQuZWR1L2dldHRvL0xMQ0EzMCcGCCsGAQUFBzABhhtodHRwOi8vb2Nz
cC5sbC5taXQuZWR1L29jc3AwPQYJKwYBBAGCNxUHBDAwLgYmKwYBBAGCNxUIg4PlHYfsp2aG
rYcVg+rwRYW2oR8dhevQcIPr7SACAWQCAQQwJQYDVR0lBB4wHAYEVR0lAAYIKwYBBQUHAwQG
CisGAQQBgjcKAwQwGAYDVR0gBBEwDzANBgsqhkiG9xICAQMBCDAjBgNVHREEHDAagRhEYXZp
ZC5XaWdnaW5zQGxsLm1pdC5lZHUwJwYJKwYBBAGCNxQCBBoeGABMAEwAVQBzAGUAcgBFAG4A
YwAtAFMAVzANBgkqhkiG9w0BAQsFAAOCAQEATCsJT66TKeYNh9hrcC1wxRH08CricKt9JktB
I1WWl48F4CqcYDZlLMpvHuSe6GezZzTUH4oq1y2q3um9Txh1NjLPT7j0k5SSwdr2V7d8upDN
WOrXvCi59Cyz5RvuhleCPIE+6wPyDrQwfBRhte/cv8PVOrsG4tio4VOHi/nXcS+HLgC5qNxk
1/w1UBf8QkkNP8kIgum/uItm4QwVdVAJMuwe3te8dYjtp3M5nC2exfqQfk+Mmw/8fdZFpch0
rSYbpchMMOueBuy2UnWaYBF84uXldBH9fkONRX8AL8EQ3sQEOyzxqpwKQ/d0itjAGaPCCJCI
VgnSYSWYoFiN9idyaTGCAeUwggHhAgEBMF8wUTELMAkGA1UEBhMCVVMxHzAdBgNVBAoTFk1J
VCBMaW5jb2xuIExhYm9yYXRvcnkxDDAKBgNVBAsTA1BLSTETMBEGA1UEAxMKTUlUTEwgQ0Et
MwIKWq/r4AAAAAA2DjAJBgUrDgMCGgUAoF0wIwYJKoZIhvcNAQkEMRYEFEHq/qaUV3eLqJDt
9ihLfkuICnRUMBgGCSqGSIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTE1
MTIwNzE5NDAzOVowDQYJKoZIhvcNAQEBBQAEggEAVBDqPy5pCtQowtz12HHvlyJRS85jzFZi
CE2s7BxwVA+2tKFS7ZeGHXilnU71K8hBJqYpZcnUsxjg3DBMW10AXGyFj0vdyJGc2j72lEu+
wHDmPfsZBOTFZdC6KJzYd1ft1clxLEPSkQ2EYnR03wrY2sk2+Jgwoeibd4YGop8vO5loFWse
FC6qdnBgN9SKV/tMnjkFIoSpPtsoZg2LdgrLk81pYc4Tu/gjtqFWehjCikha8D25Zooxj13/
mbdSPFCqnD2dhqP8cZaP4bYYbeG9K5vHBx8xZYAUHzZGn9Gnn5Zzf9VyVgBwRw6huyZplTyT
orCLX3blphGM9SHl8Qak5w==

--B_3532344039_146589219--


From nobody Tue Dec  8 08:17:52 2015
Return-Path: <chris.dearlove@baesystems.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 7B0461B2F88 for <manet@ietfa.amsl.com>; Tue,  8 Dec 2015 08:17:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.102
X-Spam-Level: 
X-Spam-Status: No, score=-4.102 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RDNS_NONE=0.793] 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 gv3jKk05JDX6 for <manet@ietfa.amsl.com>; Tue,  8 Dec 2015 08:17:48 -0800 (PST)
Received: from ukmta2.baesystems.com (unknown [20.133.0.56]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F19E61B2F9A for <manet@ietf.org>; Tue,  8 Dec 2015 08:17:45 -0800 (PST)
X-IronPort-AV: E=Sophos; i="5.20,400,1444690800"; d="scan'208,217"; a="22350178"
Received: from unknown (HELO baemasmds017.greenlnk.net) ([10.15.207.104]) by ukmta2.baesystems.com with ESMTP; 08 Dec 2015 16:17:44 +0000
X-IronPort-AV: E=Sophos;i="5.20,400,1444690800";  d="scan'208,217";a="123335896"
Received: from glkxh0001v.greenlnk.net ([10.109.2.32]) by baemasmds017.greenlnk.net with ESMTP; 08 Dec 2015 16:17:45 +0000
Received: from GLKXM0002V.GREENLNK.net ([169.254.5.2]) by GLKXH0001V.GREENLNK.net ([10.109.2.32]) with mapi id 14.03.0248.002; Tue, 8 Dec 2015 16:17:44 +0000
From: "Dearlove, Christopher (UK)" <chris.dearlove@baesystems.com>
To: "manet@ietf.org" <manet@ietf.org>
Thread-Topic: DLEP credit windowing -00 comments
Thread-Index: AdEx0/D7euDKQ+lCS/6EpD/hW4WpwQ==
Date: Tue, 8 Dec 2015 16:17:43 +0000
Message-ID: <B31EEDDDB8ED7E4A93FDF12A4EECD30D7D76FD0B@GLKXM0002V.GREENLNK.net>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.109.62.6]
Content-Type: multipart/alternative; boundary="_000_B31EEDDDB8ED7E4A93FDF12A4EECD30D7D76FD0BGLKXM0002VGREEN_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/8uO9IqTNsfHb8FnEEl-WCldh4HY>
Subject: [manet] DLEP credit windowing -00 comments
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: <https://mailarchive.ietf.org/arch/browse/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: Tue, 08 Dec 2015 16:17:51 -0000

--_000_B31EEDDDB8ED7E4A93FDF12A4EECD30D7D76FD0BGLKXM0002VGREEN_
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable

Section 3, penultimate line, what does "plane" mean? (should it be "data pl=
ane" - or just data, matching previous line?)

Section 4. Why is the credit window counted at L2? If we really are concern=
ed with radio resources, why isn't L1 the issue? (There may be important th=
ings like burst spacing - or even in some cases that actually all that real=
ly matters is the number of packets, the size is secondary.) But even if L2=
, only the radio knows the L3 to L2 relationship - the router really doesn'=
t want to know. And this is about sender/receiver, not router/modem.

Section 6, after table (caption?) where is "below"?

Section 6.3 says can carry Credit Grant only. Plus compulsory MAC address (=
needed both by base protocol and to make this work).

Section 7.1, "for synchronization purposes". Not explained what or why.

Section 7.1, final paragraph, why isn't this an error, rather than saturati=
ng? 2^64 octets is not going to happen due to accidental generosity (it's 1=
8 exabytes).

Section 8, Is there an attack simply inserting a message (not modifying, no=
t MiTM)?

Section 9, I don't think will be good enough for IANA. They (in my experien=
ce) want exact registry names and tables of additions.


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

--_000_B31EEDDDB8ED7E4A93FDF12A4EECD30D7D76FD0BGLKXM0002VGREEN_
Content-Type: text/html; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii">
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-GB" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">Section 3, penultimate line, what does &#8220;plane&=
#8221; mean? (should it be &#8220;data plane&#8221; &#8211; or just data, m=
atching previous line?)<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Section 4. Why is the credit window counted at L2? I=
f we really are concerned with radio resources, why isn&#8217;t L1 the issu=
e? (There may be important things like burst spacing &#8211; or even in som=
e cases that actually all that really matters
 is the number of packets, the size is secondary.) But even if L2, only the=
 radio knows the L3 to L2 relationship &#8211; the router really doesn&#821=
7;t want to know. And this is about sender/receiver, not router/modem.<o:p>=
</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Section 6, after table (caption?) where is &#8220;be=
low&#8221;?<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Section 6.3 says can carry Credit Grant only. Plus c=
ompulsory MAC address (needed both by base protocol and to make this work).=
<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Section 7.1, &#8220;for synchronization purposes&#82=
21;. Not explained what or why.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Section 7.1, final paragraph, why isn&#8217;t this a=
n error, rather than saturating? 2^64 octets is not going to happen due to =
accidental generosity (it&#8217;s 18 exabytes).<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Section 8, Is there an attack simply inserting a mes=
sage (not modifying, not MiTM)?<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Section 9, I don&#8217;t think will be good enough f=
or IANA. They (in my experience) want exact registry names and tables of ad=
ditions.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<p>********************************************************************<br>
This email and any attachments are confidential to the intended<br>
recipient and may also be privileged. If you are not the intended<br>
recipient please delete it from your system and notify the sender.<br>
You should not copy it or use it for any purpose nor disclose or<br>
distribute its contents to any other person.<br>
********************************************************************</p></b=
ody>
</html>

--_000_B31EEDDDB8ED7E4A93FDF12A4EECD30D7D76FD0BGLKXM0002VGREEN_--


From nobody Wed Dec  9 11:02:34 2015
Return-Path: <lberger@labn.net>
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 DB69E1AC41D for <manet@ietfa.amsl.com>; Wed,  9 Dec 2015 11:02:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.232
X-Spam-Level: 
X-Spam-Status: No, score=0.232 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, IP_NOT_FRIENDLY=0.334, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no
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 ZNA81T3bhLfj for <manet@ietfa.amsl.com>; Wed,  9 Dec 2015 11:02:31 -0800 (PST)
Received: from gproxy10-pub.mail.unifiedlayer.com (gproxy10-pub.mail.unifiedlayer.com [69.89.20.226]) by ietfa.amsl.com (Postfix) with SMTP id 80DE21A1B40 for <manet@ietf.org>; Wed,  9 Dec 2015 11:02:31 -0800 (PST)
Received: (qmail 18221 invoked by uid 0); 9 Dec 2015 19:02:26 -0000
Received: from unknown (HELO cmgw4) (10.0.90.85) by gproxy10.mail.unifiedlayer.com with SMTP; 9 Dec 2015 19:02:26 -0000
Received: from box313.bluehost.com ([69.89.31.113]) by cmgw4 with  id rX2N1r01D2SSUrH01X2Rj5; Wed, 09 Dec 2015 12:02:26 -0700
X-Authority-Analysis: v=2.1 cv=IekUBwaa c=1 sm=1 tr=0 a=h1BC+oY+fLhyFmnTBx92Jg==:117 a=wU2YTnxGAAAA:8 a=cNaOj0WVAAAA:8 a=IkcTkHD0fZMA:10 a=-NfooI8aBGcA:10 a=uEJ9t1CZtbIA:10 a=wUQvQvOEmiQA:10 a=ah8mdJEgV2Koc2xaM8gA:9 a=9wjowlHlfPC0l_0r:21 a=VTQ9PKKpHGDdwOKY:21 a=QEXdDO2ut3YA:10
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=labn.net; s=default;  h=Content-Transfer-Encoding:Content-Type:MIME-Version:Date:Message-ID:To:Subject:From; bh=KKIvRqbn71IDeGZFAKive8ij5uas9Z1444/Wt6hyx5w=;  b=FIPuWONHfP/VmXL9qTZC5MmK81N/3g6dIjBPQoIwZRjECM+gq/F1S2piNb2FaRO3BeYbrVgNg2w88ovw6cds7lXnjnw6+9iiwxmW8lz1PI6XGI93cDi7ARd1xUj76Df1;
Received: from box313.bluehost.com ([69.89.31.113]:37122 helo=[127.0.0.1]) by box313.bluehost.com with esmtpa (Exim 4.84) (envelope-from <lberger@labn.net>) id 1a6k0M-0002zW-H7; Wed, 09 Dec 2015 12:02:22 -0700
From: Lou Berger <lberger@labn.net>
X-Enigmail-Draft-Status: N1110
To: draft-ietf-manet-dlep@ietf.org, MANET IETF <manet@ietf.org>
Message-ID: <56687ABA.803@labn.net>
Date: Wed, 9 Dec 2015 14:02:18 -0500
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.4.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-Identified-User: {1038:box313.bluehost.com:labnmobi:labn.net} {sentby:smtp auth 69.89.31.113 authed with lberger@labn.net}
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/yMRtDI2TWTHugmzTqFPgKM0NYyY>
Subject: [manet] DLEP-17: duplicate functions - Options & extensions negotiations
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: <https://mailarchive.ietf.org/arch/browse/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: Wed, 09 Dec 2015 19:02:33 -0000

Authors/WG,

The current version of DLEP contains two negotiations as part of a
Session Initialization transaction:
1) <Extensions Supported> is included in both the <Session
Initialization> and <Session Initialization Response> messages
2) the optional data items, <Resources> and <Relative Link Quality>

Both have parallel allocation policies:

   +-------------+-----------------------------------------------------+
   | Type Code   | Description                                         |
   +-------------+-----------------------------------------------------+
   | 0           | Reserved                                            |
   | 1           | Status (Section 10.1)                               |
     ...
   | 20          | Relative Link Quality (Transmit) (RLQT) (Section    |
   | 21-65407    | Reserved for future extensions                      |
   | 65408-65534 | Private Use. Available for experiments              |
   | 65535       | Reserved                                            |
   +-------------+-----------------------------------------------------+

                       Table 2: DLEP Data Item types

   +-------------+-----------------------------------------------------+
   | Code        | Description                                         |
   +-------------+-----------------------------------------------------+
   | 0           | Reserved                                            |
   | 1           | Credit Windowing                                    |
   | 2-65519     | Reserved for future extensions                      |
   | 65520-65534 | Private Use. Available for experiments              |
   | 65535       | Reserved                                            |
   +-------------+-----------------------------------------------------+

                       Table 4: DLEP Extension types

It seems to me that given the current definition, one of these two
should suffice.  I don't have a strong opinion on which, but do strongly
believe that a single approach should be selected to facilitate
interoperability.

To be clear, the following spells out the options:

Option A: Extensions (aka capabilities) based
  Any optional or new data item or message would need to be indicated
  in <Extensions Supported> to be used.  To cover the current optional
  data items the following would need to be defined:
    | 1 | Resources |
    | 2 | Relative Link Quality |
    | 3 | Credit Windowing |
  <Session Initialization Response> could still contain the optional
  data items, if the corresponding type is present in <Extensions
  Supported>

  Note that other messages will still use optional data items.

Option B: Data item based.
  An optional or new data item must be both Session Initialization
  messages to be used. To allow/enable <Resources> and <Relative Link
  Quality>, they would need to be included in both the <Session
  Initialization> and <Session Initialization Response> messages.

  To enable the Credit Windowing extension, the three credit-related
  state items, <Grant>, <Window Status>, and <Request> would need to be
  included in both session init messages for the full extension to be
  used.

Option C: keep both
  Keep current text

While I like Option A and have seen similar approaches in other
protocols, e.g., BGP Capabilities, I actually have a slight preference
for B.  The reason for this is DLEP uses optional data items in other
places and implementations will already need to handle this, so it seems
like option B will probably require smaller incremental code.

Either way, I think Option C is much less desirable then either of the
other options.

Thoughts? Opinions?

Lou


From nobody Wed Dec  9 11:02:43 2015
Return-Path: <lberger@labn.net>
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 68C941AC439 for <manet@ietfa.amsl.com>; Wed,  9 Dec 2015 11:02:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.667
X-Spam-Level: 
X-Spam-Status: No, score=-1.667 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, IP_NOT_FRIENDLY=0.334, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no
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 HEzQKUipqe7n for <manet@ietfa.amsl.com>; Wed,  9 Dec 2015 11:02:37 -0800 (PST)
Received: from gproxy1-pub.mail.unifiedlayer.com (gproxy1-pub.mail.unifiedlayer.com [69.89.25.95]) by ietfa.amsl.com (Postfix) with SMTP id 5ABB61AC42C for <manet@ietf.org>; Wed,  9 Dec 2015 11:02:37 -0800 (PST)
Received: (qmail 26476 invoked by uid 0); 9 Dec 2015 19:02:35 -0000
Received: from unknown (HELO cmgw2) (10.0.90.83) by gproxy1.mail.unifiedlayer.com with SMTP; 9 Dec 2015 19:02:35 -0000
Received: from box313.bluehost.com ([69.89.31.113]) by cmgw2 with  id rX2U1r00j2SSUrH01X2XSY; Wed, 09 Dec 2015 12:02:33 -0700
X-Authority-Analysis: v=2.1 cv=dqRIVTQ4 c=1 sm=1 tr=0 a=h1BC+oY+fLhyFmnTBx92Jg==:117 a=wU2YTnxGAAAA:8 a=cNaOj0WVAAAA:8 a=IkcTkHD0fZMA:10 a=-NfooI8aBGcA:10 a=uEJ9t1CZtbIA:10 a=wUQvQvOEmiQA:10 a=bLk7FwSUjbl4Xs_UsOYA:9 a=QEXdDO2ut3YA:10
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=labn.net; s=default;  h=Content-Transfer-Encoding:Content-Type:MIME-Version:Date:Message-ID:To:Subject:From; bh=2u9IHLa9QK104YxM1iFpvS/88EMcrzRILuUiaCLE4i0=;  b=ut7fvc4MXCQzm1UuVREOcPsVhDhpLwRl2oqtWeB9BBcEqKMI0Eg7OVh0lxn+rBXMNgUFqm8wjE9VAaql3M37Ib6kdt+IkdvPfHj8VY9wfEoaz5bYwfo4YBEY8YRTPAV1;
Received: from box313.bluehost.com ([69.89.31.113]:37137 helo=[127.0.0.1]) by box313.bluehost.com with esmtpa (Exim 4.84) (envelope-from <lberger@labn.net>) id 1a6k0U-00031W-0Y; Wed, 09 Dec 2015 12:02:30 -0700
From: Lou Berger <lberger@labn.net>
X-Enigmail-Draft-Status: N1110
To: draft-ietf-manet-dlep@ietf.org, MANET IETF <manet@ietf.org>
Message-ID: <56687AC2.9060801@labn.net>
Date: Wed, 9 Dec 2015 14:02:26 -0500
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.4.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-Identified-User: {1038:box313.bluehost.com:labnmobi:labn.net} {sentby:smtp auth 69.89.31.113 authed with lberger@labn.net}
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/0xaxrNSlVG7aa-Zv0p-qvpkhrbA>
Subject: [manet] DLEP-17: Handling of unknown / unexpected messages
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: <https://mailarchive.ietf.org/arch/browse/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: Wed, 09 Dec 2015 19:02:38 -0000

Authors/WG,

The current text has different processing rules for unexpected signals
and messages:

   If an unrecognized, or unexpected signal is received, or a received
   signal contains unrecognized, invalid, or disallowed duplicate data
   items, the receiving peer MUST ignore the signal.

and

   If an unrecognized, or unexpected message is received, or a received
   message contains unrecognized, invalid, or disallowed duplicate data
   items, the receiving peer MUST issue a Session Termination message
   (Section 9.7) with a Status data item (Section 10.1) containing the
   most relevant status code, and transition to the Session Termination
   state.

It seems to me that the approach of resetting a session any time
anything unexpected occurs is overly restrictive and is likely to lead
to instability and interoperability issues as implementations mature and
the protocol is extended.  (As well as add some interesting
vulnerabilities.)  It's also not clear, what real value the approach brings.

Following behavior common in other IETF protocols, and the IETF/Jon's
design maxim of "Be liberal in what you accept..."  I'd propose that
unrecognized, invalid, or disallowed duplicate data items and messages
be ignore.  Counting them and reporting them via the management plane
should also be allowed, and perhaps recommended.

Lou


From nobody Wed Dec  9 11:20:22 2015
Return-Path: <ratliffstan@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 736071A0393; Wed,  9 Dec 2015 11:20:21 -0800 (PST)
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 IbaJCLdpxaBl; Wed,  9 Dec 2015 11:20:17 -0800 (PST)
Received: from mail-lb0-x22c.google.com (mail-lb0-x22c.google.com [IPv6:2a00:1450:4010:c04::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 541051A0398; Wed,  9 Dec 2015 11:20:16 -0800 (PST)
Received: by lbpu9 with SMTP id u9so36140850lbp.2; Wed, 09 Dec 2015 11:20:14 -0800 (PST)
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=k9EDyeRsX8Sdf28FrcRNynYPDD244HkAjCvzTCtLG/g=; b=Oe4UwTFKCt4UGFzep4XJxRppDevCIzxDgLT0E0VMnaVCOt8phKpvlPDkwnCngJMPjG FGeZe0+yAQz3J8PMRagIgqaFKU3iChw1UmuIN8xGPLjE8KH5WVUYZV1rQGhz5MgFe2pH JI0vsrBpJN1hZW8wLaa3VEnSuoLaoNpjcNMXEjknFRoRe6LHn7CqTdEioMAixLTUMzRX PPURoQgEbEgkHVHC5sYs18SbYTNYPg1ZenRl3vB/XkBVCENKBdFcizf0SNcH+ld6/u2l AIQASJIpTNOVBfpEY+ogqa9q4snb02Q4u+lsVAakITOKwZBcGKm+MjwxRsnASacgBv62 Ho9w==
MIME-Version: 1.0
X-Received: by 10.112.202.101 with SMTP id kh5mr3241710lbc.66.1449688814457; Wed, 09 Dec 2015 11:20:14 -0800 (PST)
Received: by 10.25.209.71 with HTTP; Wed, 9 Dec 2015 11:20:14 -0800 (PST)
In-Reply-To: <56687ABA.803@labn.net>
References: <56687ABA.803@labn.net>
Date: Wed, 9 Dec 2015 14:20:14 -0500
Message-ID: <CALtoyonnuk03=FqiyPfQS4t9mKJt81kUfkZP-JB0FD0hfRp-6Q@mail.gmail.com>
From: Stan Ratliff <ratliffstan@gmail.com>
To: Lou Berger <lberger@labn.net>
Content-Type: multipart/alternative; boundary=001a11c3724cd21e2905267bfa75
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/-ScKIAnT2iiUWHpBvEJdTLEHkVU>
Cc: MANET IETF <manet@ietf.org>, draft-ietf-manet-dlep@ietf.org
Subject: Re: [manet] DLEP-17: duplicate functions - Options & extensions negotiations
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: <https://mailarchive.ietf.org/arch/browse/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: Wed, 09 Dec 2015 19:20:21 -0000

--001a11c3724cd21e2905267bfa75
Content-Type: text/plain; charset=UTF-8

Lou,

On Wed, Dec 9, 2015 at 2:02 PM, Lou Berger <lberger@labn.net> wrote:

> Authors/WG,
>
> The current version of DLEP contains two negotiations as part of a
> Session Initialization transaction:
> 1) <Extensions Supported> is included in both the <Session
> Initialization> and <Session Initialization Response> messages
> 2) the optional data items, <Resources> and <Relative Link Quality>
>
> Both have parallel allocation policies:
>
>    +-------------+-----------------------------------------------------+
>    | Type Code   | Description                                         |
>    +-------------+-----------------------------------------------------+
>    | 0           | Reserved                                            |
>    | 1           | Status (Section 10.1)                               |
>      ...
>    | 20          | Relative Link Quality (Transmit) (RLQT) (Section    |
>    | 21-65407    | Reserved for future extensions                      |
>    | 65408-65534 | Private Use. Available for experiments              |
>    | 65535       | Reserved                                            |
>    +-------------+-----------------------------------------------------+
>
>                        Table 2: DLEP Data Item types
>
>    +-------------+-----------------------------------------------------+
>    | Code        | Description                                         |
>    +-------------+-----------------------------------------------------+
>    | 0           | Reserved                                            |
>    | 1           | Credit Windowing                                    |
>    | 2-65519     | Reserved for future extensions                      |
>    | 65520-65534 | Private Use. Available for experiments              |
>    | 65535       | Reserved                                            |
>    +-------------+-----------------------------------------------------+
>
>                        Table 4: DLEP Extension types
>
> It seems to me that given the current definition, one of these two
> should suffice.  I don't have a strong opinion on which, but do strongly
> believe that a single approach should be selected to facilitate
> interoperability.
>
>
Well, I disagree. Extensions defines a process whereby multiple data items,
and/or new *messages*, can be added to DLEP. The other two data items you
mention (Resources and Link Quality) are just optional (not required)
metrics. They are two different things.



> To be clear, the following spells out the options:
>
> Option A: Extensions (aka capabilities) based
>   Any optional or new data item or message would need to be indicated
>   in <Extensions Supported> to be used.  To cover the current optional
>   data items the following would need to be defined:
>     | 1 | Resources |
>     | 2 | Relative Link Quality |
>     | 3 | Credit Windowing |
>   <Session Initialization Response> could still contain the optional
>   data items, if the corresponding type is present in <Extensions
>   Supported>
>
>   Note that other messages will still use optional data items.
>
> Option B: Data item based.
>   An optional or new data item must be both Session Initialization
>   messages to be used. To allow/enable <Resources> and <Relative Link
>   Quality>, they would need to be included in both the <Session
>   Initialization> and <Session Initialization Response> messages.
>
>   To enable the Credit Windowing extension, the three credit-related
>   state items, <Grant>, <Window Status>, and <Request> would need to be
>   included in both session init messages for the full extension to be
>   used.
>
> Option C: keep both
>   Keep current text
>
> While I like Option A and have seen similar approaches in other
> protocols, e.g., BGP Capabilities, I actually have a slight preference
> for B.  The reason for this is DLEP uses optional data items in other
> places and implementations will already need to handle this, so it seems
> like option B will probably require smaller incremental code.
>
> Either way, I think Option C is much less desirable then either of the
> other options.
>
> Thoughts? Opinions?
>

Before I did that, I'd be more inclined to pursue an "Option D":
1. All of the metric data items (e.g. - MDRR, MDRT, CDRR, CDRT, Latency,
RLQR, RLQT, RESR, REST) are listed, with no mention as to whether they are
mandatory or optional - they are just the pool of metrics that MAY be used
by an implementation.
2. In the Peer Init/Peer Init ACK, the peers list the metrics from the
available set that they are going to use. If peers cannot agree, the
session doesn't get established.

... and we're done. Again, the Extensions stuff is for new data
items/messages that might come along (with Credit Windowing being the
first).

Regards,
Stan



>
> Lou
>
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www.ietf.org/mailman/listinfo/manet
>

--001a11c3724cd21e2905267bfa75
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Lou,=C2=A0<div class=3D"gmail_extra"><br><div class=3D"gma=
il_quote">On Wed, Dec 9, 2015 at 2:02 PM, Lou Berger <span dir=3D"ltr">&lt;=
<a href=3D"mailto:lberger@labn.net" target=3D"_blank">lberger@labn.net</a>&=
gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 =
0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Authors/WG,<br>
<br>
The current version of DLEP contains two negotiations as part of a<br>
Session Initialization transaction:<br>
1) &lt;Extensions Supported&gt; is included in both the &lt;Session<br>
Initialization&gt; and &lt;Session Initialization Response&gt; messages<br>
2) the optional data items, &lt;Resources&gt; and &lt;Relative Link Quality=
&gt;<br>
<br>
Both have parallel allocation policies:<br>
<br>
=C2=A0 =C2=A0+-------------+-----------------------------------------------=
------+<br>
=C2=A0 =C2=A0| Type Code=C2=A0 =C2=A0| Description=C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0|<br>
=C2=A0 =C2=A0+-------------+-----------------------------------------------=
------+<br>
=C2=A0 =C2=A0| 0=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0| Reserved=C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 |=
<br>
=C2=A0 =C2=A0| 1=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0| Status (Section =
10.1)=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0|<br>
=C2=A0 =C2=A0 =C2=A0...<br>
=C2=A0 =C2=A0| 20=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 | Relative Link Quality=
 (Transmit) (RLQT) (Section=C2=A0 =C2=A0 |<br>
=C2=A0 =C2=A0| 21-65407=C2=A0 =C2=A0 | Reserved for future extensions=C2=A0=
 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 |<br=
>
=C2=A0 =C2=A0| 65408-65534 | Private Use. Available for experiments=C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 |<br>
=C2=A0 =C2=A0| 65535=C2=A0 =C2=A0 =C2=A0 =C2=A0| Reserved=C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 |<br>
=C2=A0 =C2=A0+-------------+-----------------------------------------------=
------+<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0Table 2: DLEP Data Item types<br>
<br>
=C2=A0 =C2=A0+-------------+-----------------------------------------------=
------+<br>
=C2=A0 =C2=A0| Code=C2=A0 =C2=A0 =C2=A0 =C2=A0 | Description=C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0|<br>
=C2=A0 =C2=A0+-------------+-----------------------------------------------=
------+<br>
=C2=A0 =C2=A0| 0=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0| Reserved=C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 |=
<br>
=C2=A0 =C2=A0| 1=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0| Credit Windowing=
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 |<br>
=C2=A0 =C2=A0| 2-65519=C2=A0 =C2=A0 =C2=A0| Reserved for future extensions=
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 |<br>
=C2=A0 =C2=A0| 65520-65534 | Private Use. Available for experiments=C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 |<br>
=C2=A0 =C2=A0| 65535=C2=A0 =C2=A0 =C2=A0 =C2=A0| Reserved=C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 |<br>
=C2=A0 =C2=A0+-------------+-----------------------------------------------=
------+<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0Table 4: DLEP Extension types<br>
<br>
It seems to me that given the current definition, one of these two<br>
should suffice.=C2=A0 I don&#39;t have a strong opinion on which, but do st=
rongly<br>
believe that a single approach should be selected to facilitate<br>
interoperability.<br>
<br></blockquote><div><br></div><div>Well, I disagree. Extensions defines a=
 process whereby multiple data items, and/or new *messages*, can be added t=
o DLEP. The other two data items you mention (Resources and Link Quality) a=
re just optional (not required) metrics. They are two different things.=C2=
=A0</div><div><br></div><div>=C2=A0</div><blockquote class=3D"gmail_quote" =
style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
To be clear, the following spells out the options:<br>
<br>
Option A: Extensions (aka capabilities) based<br>
=C2=A0 Any optional or new data item or message would need to be indicated<=
br>
=C2=A0 in &lt;Extensions Supported&gt; to be used.=C2=A0 To cover the curre=
nt optional<br>
=C2=A0 data items the following would need to be defined:<br>
=C2=A0 =C2=A0 | 1 | Resources |<br>
=C2=A0 =C2=A0 | 2 | Relative Link Quality |<br>
=C2=A0 =C2=A0 | 3 | Credit Windowing |<br>
=C2=A0 &lt;Session Initialization Response&gt; could still contain the opti=
onal<br>
=C2=A0 data items, if the corresponding type is present in &lt;Extensions<b=
r>
=C2=A0 Supported&gt;<br>
<br>
=C2=A0 Note that other messages will still use optional data items.<br>
<br>
Option B: Data item based.<br>
=C2=A0 An optional or new data item must be both Session Initialization<br>
=C2=A0 messages to be used. To allow/enable &lt;Resources&gt; and &lt;Relat=
ive Link<br>
=C2=A0 Quality&gt;, they would need to be included in both the &lt;Session<=
br>
=C2=A0 Initialization&gt; and &lt;Session Initialization Response&gt; messa=
ges.<br>
<br>
=C2=A0 To enable the Credit Windowing extension, the three credit-related<b=
r>
=C2=A0 state items, &lt;Grant&gt;, &lt;Window Status&gt;, and &lt;Request&g=
t; would need to be<br>
=C2=A0 included in both session init messages for the full extension to be<=
br>
=C2=A0 used.<br>
<br>
Option C: keep both<br>
=C2=A0 Keep current text<br>
<br>
While I like Option A and have seen similar approaches in other<br>
protocols, e.g., BGP Capabilities, I actually have a slight preference<br>
for B.=C2=A0 The reason for this is DLEP uses optional data items in other<=
br>
places and implementations will already need to handle this, so it seems<br=
>
like option B will probably require smaller incremental code.<br>
<br>
Either way, I think Option C is much less desirable then either of the<br>
other options.<br>
<br>
Thoughts? Opinions?<br></blockquote><div><br></div><div>Before I did that, =
I&#39;d be more inclined to pursue an &quot;Option D&quot;:=C2=A0</div><div=
>1. All of the metric data items (e.g. - MDRR, MDRT, CDRR, CDRT, Latency, R=
LQR, RLQT, RESR, REST) are listed, with no mention as to whether they are m=
andatory or optional - they are just the pool of metrics that MAY be used b=
y an implementation.=C2=A0</div><div>2. In the Peer Init/Peer Init ACK, the=
 peers list the metrics from the available set that they are going to use. =
If peers cannot agree, the session doesn&#39;t get established.=C2=A0</div>=
<div><br></div><div>... and we&#39;re done. Again, the Extensions stuff is =
for new data items/messages that might come along (with Credit Windowing be=
ing the first).=C2=A0</div><div><br></div><div>Regards,</div><div>Stan</div=
><div><br></div><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D=
"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Lou<br>
<br>
_______________________________________________<br>
manet mailing list<br>
<a href=3D"mailto:manet@ietf.org">manet@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/manet" rel=3D"noreferrer" =
target=3D"_blank">https://www.ietf.org/mailman/listinfo/manet</a><br>
</blockquote></div><br></div></div>

--001a11c3724cd21e2905267bfa75--


From nobody Wed Dec  9 11:26:51 2015
Return-Path: <ratliffstan@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 E68FB1A0419; Wed,  9 Dec 2015 11:26:50 -0800 (PST)
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 I9zBoDDksH7R; Wed,  9 Dec 2015 11:26:49 -0800 (PST)
Received: from mail-lf0-x22c.google.com (mail-lf0-x22c.google.com [IPv6:2a00:1450:4010:c07::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 748161A03A1; Wed,  9 Dec 2015 11:26:48 -0800 (PST)
Received: by lfdl133 with SMTP id l133so41450015lfd.2; Wed, 09 Dec 2015 11:26:46 -0800 (PST)
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=H9dhfQzlXIe8Lygd6oPlK1sKVKGG927VxtpIbrsc6cg=; b=w3U2HOLI90imIotFGTo47FOuyV5LxRIZi5CIfnkiTeA9p6X2oz9pb74ObVjRm6O6sR zCAcMXsD0rU+jf2r+qpnOQBDPVXEgheNkDUtg/ZK3I5gJk5c8rDs/+5p+cpjboWYcXaZ 8ddb0YgnmyYW/XbT97iffARtJyRd0DamL/W5Gk/MnhjV4w1oqP+Pg3TUWT7ijo7sa0EG 02yCMLJIeOdajiHVDuvUilLuPAQYVR+H58pGXl6NSQxda0w2jdvN/A1TWrLIoAQ72Hd7 2XN0y44NSV/wRBcSMMikMUsbCrYYQpvK6rGzS9Hmgs6jt0PEZocF50tEr9fxcRqMZunJ 2NFA==
MIME-Version: 1.0
X-Received: by 10.25.135.195 with SMTP id j186mr2746689lfd.141.1449689206646;  Wed, 09 Dec 2015 11:26:46 -0800 (PST)
Received: by 10.25.209.71 with HTTP; Wed, 9 Dec 2015 11:26:46 -0800 (PST)
In-Reply-To: <56687AC2.9060801@labn.net>
References: <56687AC2.9060801@labn.net>
Date: Wed, 9 Dec 2015 14:26:46 -0500
Message-ID: <CALtoyomCuki__fyNnhmYoKmBcrQSSuOPGgcg8N-txG1DSaUaAg@mail.gmail.com>
From: Stan Ratliff <ratliffstan@gmail.com>
To: Lou Berger <lberger@labn.net>
Content-Type: multipart/alternative; boundary=001a113fad5232754305267c12bc
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/1GJwO7aKLfohJGZtMBtWpfzXp_s>
Cc: MANET IETF <manet@ietf.org>, draft-ietf-manet-dlep@ietf.org
Subject: Re: [manet] DLEP-17: Handling of unknown / unexpected messages
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: <https://mailarchive.ietf.org/arch/browse/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: Wed, 09 Dec 2015 19:26:51 -0000

--001a113fad5232754305267c12bc
Content-Type: text/plain; charset=UTF-8

On Wed, Dec 9, 2015 at 2:02 PM, Lou Berger <lberger@labn.net> wrote:

> Authors/WG,
>
> The current text has different processing rules for unexpected signals
> and messages:
>
>    If an unrecognized, or unexpected signal is received, or a received
>    signal contains unrecognized, invalid, or disallowed duplicate data
>    items, the receiving peer MUST ignore the signal.
>

Since "signal" refers to "The UDP messages/packets that are sent as a part
of discovery", and therefore, no Peer session exists, ignoring (and maybe
logging) is about all you can do.



>
> and
>
>    If an unrecognized, or unexpected message is received, or a received
>    message contains unrecognized, invalid, or disallowed duplicate data
>    items, the receiving peer MUST issue a Session Termination message
>    (Section 9.7) with a Status data item (Section 10.1) containing the
>    most relevant status code, and transition to the Session Termination
>    state.
>
> It seems to me that the approach of resetting a session any time
> anything unexpected occurs is overly restrictive and is likely to lead
> to instability and interoperability issues as implementations mature and
> the protocol is extended.  (As well as add some interesting
> vulnerabilities.)  It's also not clear, what real value the approach
> brings.
>

This was a compromise, after a lot of discussion. The issue is that
something the receiver doesn't understands, and therefore ignores, may be
crucial to the sender. If the receiver ignores it, and by definition does
not negatively ACK it, then the sender will wind up in a transaction
timeout... the processing there is to pull down the Peer-to-peer session.
We figured it was better for the receiver of a message not understood to go
ahead and proactively tear the session down.


Regards,
Stan






>
> Following behavior common in other IETF protocols, and the IETF/Jon's
> design maxim of "Be liberal in what you accept..."  I'd propose that
> unrecognized, invalid, or disallowed duplicate data items and messages
> be ignore.  Counting them and reporting them via the management plane
> should also be allowed, and perhaps recommended.
>
> Lou
>
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www.ietf.org/mailman/listinfo/manet
>

--001a113fad5232754305267c12bc
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><div class=3D"gmail_quo=
te">On Wed, Dec 9, 2015 at 2:02 PM, Lou Berger <span dir=3D"ltr">&lt;<a hre=
f=3D"mailto:lberger@labn.net" target=3D"_blank">lberger@labn.net</a>&gt;</s=
pan> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex=
;border-left:1px #ccc solid;padding-left:1ex">Authors/WG,<br>
<br>
The current text has different processing rules for unexpected signals<br>
and messages:<br>
<br>
=C2=A0 =C2=A0If an unrecognized, or unexpected signal is received, or a rec=
eived<br>
=C2=A0 =C2=A0signal contains unrecognized, invalid, or disallowed duplicate=
 data<br>
=C2=A0 =C2=A0items, the receiving peer MUST ignore the signal.<br></blockqu=
ote><div><br></div><div>Since &quot;signal&quot; refers to &quot;The UDP me=
ssages/packets that are sent as a part of discovery&quot;, and therefore, n=
o Peer session exists, ignoring (and maybe logging) is about all you can do=
.=C2=A0</div><div><br></div><div>=C2=A0</div><blockquote class=3D"gmail_quo=
te" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"=
>
<br>
and<br>
<br>
=C2=A0 =C2=A0If an unrecognized, or unexpected message is received, or a re=
ceived<br>
=C2=A0 =C2=A0message contains unrecognized, invalid, or disallowed duplicat=
e data<br>
=C2=A0 =C2=A0items, the receiving peer MUST issue a Session Termination mes=
sage<br>
=C2=A0 =C2=A0(Section 9.7) with a Status data item (Section 10.1) containin=
g the<br>
=C2=A0 =C2=A0most relevant status code, and transition to the Session Termi=
nation<br>
=C2=A0 =C2=A0state.<br>
<br>
It seems to me that the approach of resetting a session any time<br>
anything unexpected occurs is overly restrictive and is likely to lead<br>
to instability and interoperability issues as implementations mature and<br=
>
the protocol is extended.=C2=A0 (As well as add some interesting<br>
vulnerabilities.)=C2=A0 It&#39;s also not clear, what real value the approa=
ch brings.<br></blockquote><div><br></div><div>This was a compromise, after=
 a lot of discussion. The issue is that something the receiver doesn&#39;t =
understands, and therefore ignores, may be crucial to the sender. If the re=
ceiver ignores it, and by definition does not negatively ACK it, then the s=
ender will wind up in a transaction timeout... the processing there is to p=
ull down the Peer-to-peer session. We figured it was better for the receive=
r of a message not understood to go ahead and proactively tear the session =
down.=C2=A0</div><div><br></div><div><br></div><div>Regards,</div><div>Stan=
=C2=A0</div><div><br></div><div><br></div><div><br></div><div><br></div><di=
v>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;=
border-left:1px #ccc solid;padding-left:1ex">
<br>
Following behavior common in other IETF protocols, and the IETF/Jon&#39;s<b=
r>
design maxim of &quot;Be liberal in what you accept...&quot;=C2=A0 I&#39;d =
propose that<br>
unrecognized, invalid, or disallowed duplicate data items and messages<br>
be ignore.=C2=A0 Counting them and reporting them via the management plane<=
br>
should also be allowed, and perhaps recommended.<br>
<br>
Lou<br>
<br>
_______________________________________________<br>
manet mailing list<br>
<a href=3D"mailto:manet@ietf.org">manet@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/manet" rel=3D"noreferrer" =
target=3D"_blank">https://www.ietf.org/mailman/listinfo/manet</a><br>
</blockquote></div><br></div></div>

--001a113fad5232754305267c12bc--


From nobody Wed Dec  9 11:52:39 2015
Return-Path: <lberger@labn.net>
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 D88F91A1A52 for <manet@ietfa.amsl.com>; Wed,  9 Dec 2015 11:52:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.667
X-Spam-Level: 
X-Spam-Status: No, score=-1.667 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, IP_NOT_FRIENDLY=0.334, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no
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 5JyY35QFw_W3 for <manet@ietfa.amsl.com>; Wed,  9 Dec 2015 11:52:36 -0800 (PST)
Received: from gproxy6-pub.mail.unifiedlayer.com (gproxy6-pub.mail.unifiedlayer.com [67.222.39.168]) by ietfa.amsl.com (Postfix) with SMTP id 132751A1A54 for <manet@ietf.org>; Wed,  9 Dec 2015 11:52:35 -0800 (PST)
Received: (qmail 32386 invoked by uid 0); 9 Dec 2015 19:52:33 -0000
Received: from unknown (HELO cmgw2) (10.0.90.83) by gproxy6.mail.unifiedlayer.com with SMTP; 9 Dec 2015 19:52:33 -0000
Received: from box313.bluehost.com ([69.89.31.113]) by cmgw2 with  id rXsQ1r00b2SSUrH01XsTkP; Wed, 09 Dec 2015 12:52:31 -0700
X-Authority-Analysis: v=2.1 cv=dqRIVTQ4 c=1 sm=1 tr=0 a=h1BC+oY+fLhyFmnTBx92Jg==:117 a=wU2YTnxGAAAA:8 a=cNaOj0WVAAAA:8 a=IkcTkHD0fZMA:10 a=-NfooI8aBGcA:10 a=uEJ9t1CZtbIA:10 a=wUQvQvOEmiQA:10 a=7WTAPlRSeKpJwEJ6BV4A:9 a=YqdI_v6gzw8DLTcy:21 a=Orb020z8fAEFMSwu:21 a=QEXdDO2ut3YA:10
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=labn.net; s=default;  h=Content-Transfer-Encoding:Content-Type:MIME-Version:Date:Message-ID:To:Subject:From; bh=pXZrki8XBxmXdXYcxziSK7Pf4/nppndeIC4J26lsErA=;  b=bnHK2yM1h7Q9Rkwt9ajYNPsJslTtky2wc3mLDAa/2Se0biqX217KcfWTwAzrXZd75qEaY6E7qNzd1COaOSvIORk3TLw7hk2ioqDc2neAAAYkfgc0NIV7L5pLqijcMKoM;
Received: from box313.bluehost.com ([69.89.31.113]:51750 helo=[127.0.0.1]) by box313.bluehost.com with esmtpa (Exim 4.84) (envelope-from <lberger@labn.net>) id 1a6kmo-00053i-7n; Wed, 09 Dec 2015 12:52:26 -0700
From: Lou Berger <lberger@labn.net>
X-Enigmail-Draft-Status: N1110
To: draft-ietf-manet-dlep@ietf.org, MANET IETF <manet@ietf.org>
Message-ID: <56688675.6000603@labn.net>
Date: Wed, 9 Dec 2015 14:52:21 -0500
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.4.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-Identified-User: {1038:box313.bluehost.com:labnmobi:labn.net} {sentby:smtp auth 69.89.31.113 authed with lberger@labn.net}
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/IAiA1bmzX39J2aFHgKDqCTHQqEE>
Subject: [manet] DLEP-17: Failure processing
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: <https://mailarchive.ietf.org/arch/browse/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: Wed, 09 Dec 2015 19:52:37 -0000

Authors/WG,

DLEP-17 describes  Error handling in terms of a fixed "Failure Mode",
See Table 3.  I like this formalization of something that was previously
implicit.  I'd like to suggest going on step further by making
Terminate|Continue explicit in the Status data item.  This will both
ease initial implementation and facilitate forward compatibility.

To be clear: I'm proposing adding a flags field to the Status data item:

    0                   1                   2                   3
    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   | Data Item Type                | Length                        |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |T|  Reserved   | Status Code   | Text...                       :
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

With a definition of
   T (1-Bit): When set, indicates that the session MUST be
   terminated upon receipt of the containing message.

   Reserved (7-bits): MUST be set to zero by sender and ignored by
                      receiver.

Length also changes to 2 + length of the text field.

Lou


From nobody Wed Dec  9 12:03:44 2015
Return-Path: <lberger@labn.net>
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 87FDC1A1B05 for <manet@ietfa.amsl.com>; Wed,  9 Dec 2015 12:03:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.667
X-Spam-Level: 
X-Spam-Status: No, score=-1.667 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, IP_NOT_FRIENDLY=0.334, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no
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 O5gwdTlUA9nr for <manet@ietfa.amsl.com>; Wed,  9 Dec 2015 12:03:40 -0800 (PST)
Received: from gproxy6-pub.mail.unifiedlayer.com (gproxy6-pub.mail.unifiedlayer.com [67.222.39.168]) by ietfa.amsl.com (Postfix) with SMTP id B33D51A1ABF for <manet@ietf.org>; Wed,  9 Dec 2015 12:02:00 -0800 (PST)
Received: (qmail 18787 invoked by uid 0); 9 Dec 2015 20:02:00 -0000
Received: from unknown (HELO cmgw4) (10.0.90.85) by gproxy6.mail.unifiedlayer.com with SMTP; 9 Dec 2015 20:02:00 -0000
Received: from box313.bluehost.com ([69.89.31.113]) by cmgw4 with  id rY1x1r00B2SSUrH01Y206y; Wed, 09 Dec 2015 13:02:00 -0700
X-Authority-Analysis: v=2.1 cv=IekUBwaa c=1 sm=1 tr=0 a=h1BC+oY+fLhyFmnTBx92Jg==:117 a=wU2YTnxGAAAA:8 a=cNaOj0WVAAAA:8 a=IkcTkHD0fZMA:10 a=-NfooI8aBGcA:10 a=uEJ9t1CZtbIA:10 a=wUQvQvOEmiQA:10 a=48vgC7mUAAAA:8 a=VldBCZ8ok4ySbC3d8vQA:9 a=LtpsEkF_pElASFI1:21 a=Kci1hxlyOwB3UyAM:21 a=QEXdDO2ut3YA:10
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=labn.net; s=default;  h=Content-Transfer-Encoding:Content-Type:In-Reply-To:MIME-Version:Date:Message-ID:From:Cc:References:To:Subject; bh=wCrqKI3XUecRqM+YvAZImCE/Np5AO22b/7ikNYBGTYM=;  b=Nq6fzO8gYmAFRuXwpfR0PUCJNL3l5/q2dlNywfFyDnmhclfTSg6AL5A2SD8sciBgLEpPWGE6YKLs7szdyFZ4sYC0jT303vCVi0epsdyDZ4MNxYw0POjZ2ST9E3qgsbWV;
Received: from box313.bluehost.com ([69.89.31.113]:54753 helo=[127.0.0.1]) by box313.bluehost.com with esmtpa (Exim 4.84) (envelope-from <lberger@labn.net>) id 1a6kw0-0007Lz-VN; Wed, 09 Dec 2015 13:01:57 -0700
To: Stan Ratliff <ratliffstan@gmail.com>
References: <56687ABA.803@labn.net> <CALtoyonnuk03=FqiyPfQS4t9mKJt81kUfkZP-JB0FD0hfRp-6Q@mail.gmail.com>
From: Lou Berger <lberger@labn.net>
X-Enigmail-Draft-Status: N1110
Message-ID: <566888B0.3070806@labn.net>
Date: Wed, 9 Dec 2015 15:01:52 -0500
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.4.0
MIME-Version: 1.0
In-Reply-To: <CALtoyonnuk03=FqiyPfQS4t9mKJt81kUfkZP-JB0FD0hfRp-6Q@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-Identified-User: {1038:box313.bluehost.com:labnmobi:labn.net} {sentby:smtp auth 69.89.31.113 authed with lberger@labn.net}
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/j1mjvNDyKJtWSSvKHvFStAe7sZM>
Cc: MANET IETF <manet@ietf.org>, draft-ietf-manet-dlep@ietf.org
Subject: Re: [manet] DLEP-17: duplicate functions - Options & extensions negotiations
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: <https://mailarchive.ietf.org/arch/browse/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: Wed, 09 Dec 2015 20:03:42 -0000

Stan,

On 12/9/2015 2:20 PM, Stan Ratliff wrote:
> Lou, 
>
> On Wed, Dec 9, 2015 at 2:02 PM, Lou Berger <lberger@labn.net
> <mailto:lberger@labn.net>> wrote:
>
>     Authors/WG,
>
>     The current version of DLEP contains two negotiations as part of a
>     Session Initialization transaction:
>     1) <Extensions Supported> is included in both the <Session
>     Initialization> and <Session Initialization Response> messages
>     2) the optional data items, <Resources> and <Relative Link Quality>
>
>     Both have parallel allocation policies:
>
>      
>      +-------------+-----------------------------------------------------+
>        | Type Code   | Description                                   
>          |
>      
>      +-------------+-----------------------------------------------------+
>        | 0           | Reserved                                       
>         |
>        | 1           | Status (Section 10.1)                         
>          |
>          ...
>        | 20          | Relative Link Quality (Transmit) (RLQT)
>     (Section    |
>        | 21-65407    | Reserved for future extensions                 
>         |
>        | 65408-65534 | Private Use. Available for experiments         
>         |
>        | 65535       | Reserved                                       
>         |
>      
>      +-------------+-----------------------------------------------------+
>
>                            Table 2: DLEP Data Item types
>
>      
>      +-------------+-----------------------------------------------------+
>        | Code        | Description                                   
>          |
>      
>      +-------------+-----------------------------------------------------+
>        | 0           | Reserved                                       
>         |
>        | 1           | Credit Windowing                               
>         |
>        | 2-65519     | Reserved for future extensions                 
>         |
>        | 65520-65534 | Private Use. Available for experiments         
>         |
>        | 65535       | Reserved                                       
>         |
>      
>      +-------------+-----------------------------------------------------+
>
>                            Table 4: DLEP Extension types
>
>     It seems to me that given the current definition, one of these two
>     should suffice.  I don't have a strong opinion on which, but do
>     strongly
>     believe that a single approach should be selected to facilitate
>     interoperability.
>
>
> Well, I disagree. Extensions defines a process whereby multiple data
> items, and/or new *messages*, can be added to DLEP. The other two data
> items you mention (Resources and Link Quality) are just optional (not
> required) metrics. They are two different things.

I understand that their motivation is different, but the end result is
that code needs to be written (and tested!) to cover both.  So if
there's a way to eliminate two ways to do the same function, it's good
design to do so.

>
>  
>
>     To be clear, the following spells out the options:
>
>     Option A: Extensions (aka capabilities) based
>       Any optional or new data item or message would need to be indicated
>       in <Extensions Supported> to be used.  To cover the current optional
>       data items the following would need to be defined:
>         | 1 | Resources |
>         | 2 | Relative Link Quality |
>         | 3 | Credit Windowing |
>       <Session Initialization Response> could still contain the optional
>       data items, if the corresponding type is present in <Extensions
>       Supported>
>
>       Note that other messages will still use optional data items.
>
>     Option B: Data item based.
>       An optional or new data item must be both Session Initialization
>       messages to be used. To allow/enable <Resources> and <Relative Link
>       Quality>, they would need to be included in both the <Session
>       Initialization> and <Session Initialization Response> messages.
>
>       To enable the Credit Windowing extension, the three credit-related
>       state items, <Grant>, <Window Status>, and <Request> would need
>     to be
>       included in both session init messages for the full extension to be
>       used.
>
>     Option C: keep both
>       Keep current text
>
>     While I like Option A and have seen similar approaches in other
>     protocols, e.g., BGP Capabilities, I actually have a slight preference
>     for B.  The reason for this is DLEP uses optional data items in other
>     places and implementations will already need to handle this, so it
>     seems
>     like option B will probably require smaller incremental code.
>
>     Either way, I think Option C is much less desirable then either of the
>     other options.
>
>     Thoughts? Opinions?
>
>
> Before I did that, I'd be more inclined to pursue an "Option D": 
> 1. All of the metric data items (e.g. - MDRR, MDRT, CDRR, CDRT,
> Latency, RLQR, RLQT, RESR, REST) are listed, with no mention as to
> whether they are mandatory or optional - they are just the pool of
> metrics that MAY be used by an implementation.

Right, and this means that implementations need to dynamically track
which data items are in use on a per session, destination, and IP
basis.  This is a fair bit of mechanism already, and exactly why (a) I
raised this topic and (b) favor Option B.

> 2. In the Peer Init/Peer Init ACK, the peers list the metrics from the
> available set that they are going to use. If peers cannot agree, the
> session doesn't get established.

Peer = session and ACK = response, right?  Yup, this is why I say use
this same mechanism for future extension too.  Again, different
motivation doesn't have to mean different mechanisms.

Lou

>
> ... and we're done. Again, the Extensions stuff is for new data
> items/messages that might come along (with Credit Windowing being the
> first). 
>
> Regards,
> Stan
>
>  
>
>
>     Lou
>
>     _______________________________________________
>     manet mailing list
>     manet@ietf.org <mailto:manet@ietf.org>
>     https://www.ietf.org/mailman/listinfo/manet
>
>



From nobody Wed Dec  9 12:14:31 2015
Return-Path: <ratliffstan@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 61C7C1A1B07; Wed,  9 Dec 2015 12:14:29 -0800 (PST)
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 RI9ZRJxPrZAs; Wed,  9 Dec 2015 12:14:26 -0800 (PST)
Received: from mail-lb0-x235.google.com (mail-lb0-x235.google.com [IPv6:2a00:1450:4010:c04::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C865B1A1AE6; Wed,  9 Dec 2015 12:14:25 -0800 (PST)
Received: by lbbkw15 with SMTP id kw15so37240351lbb.0; Wed, 09 Dec 2015 12:14:24 -0800 (PST)
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=wm1kSZc44dHSxquorPubuk302GprFR/1uff0163k+1I=; b=LXAh8rCulHMiyR/DKBWt23SoLeT+mBjquivMIunfyvSrgJu4FYszOHaQlZmpEaXlGk 2RLp49A94ICeS3wHUvKmHsJC+Kpguw6YbF64QcIziwebdU9P/MKuGufH0blW6/ZkXc2r 3R3Ddy0iQIKlxD+mWi8JeJJfAvxRucXS5gN9OpJdhbiXbuvqGEg3NGvOFbvUiiv2XmWD EiBTc2mFHmTfiLZlaYdJ+GaL0WEZE813XDERyI1rLOGPO/bgX5359KPOAyeZKcBOiqeS uzrvUzXhNbtLO1t5oEumfhzlrE6Y1mK3pOkCw/eqnGbAwAJG4sAJByj7hobcl87SiUwB 6SVQ==
MIME-Version: 1.0
X-Received: by 10.112.159.202 with SMTP id xe10mr3385948lbb.122.1449692063895;  Wed, 09 Dec 2015 12:14:23 -0800 (PST)
Received: by 10.25.209.71 with HTTP; Wed, 9 Dec 2015 12:14:23 -0800 (PST)
In-Reply-To: <566888B0.3070806@labn.net>
References: <56687ABA.803@labn.net> <CALtoyonnuk03=FqiyPfQS4t9mKJt81kUfkZP-JB0FD0hfRp-6Q@mail.gmail.com> <566888B0.3070806@labn.net>
Date: Wed, 9 Dec 2015 15:14:23 -0500
Message-ID: <CALtoyomO1YTNydyohqRczjHnivCkfPp_gwv5oRWjdRmC5yOb0Q@mail.gmail.com>
From: Stan Ratliff <ratliffstan@gmail.com>
To: Lou Berger <lberger@labn.net>
Content-Type: multipart/alternative; boundary=001a11c398f2809ceb05267cbc68
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/bUyXCCzUvR8IM8nF300_rf_AhDk>
Cc: MANET IETF <manet@ietf.org>, draft-ietf-manet-dlep@ietf.org
Subject: Re: [manet] DLEP-17: duplicate functions - Options & extensions negotiations
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: <https://mailarchive.ietf.org/arch/browse/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: Wed, 09 Dec 2015 20:14:29 -0000

--001a11c398f2809ceb05267cbc68
Content-Type: text/plain; charset=UTF-8

On Wed, Dec 9, 2015 at 3:01 PM, Lou Berger <lberger@labn.net> wrote:

> Stan,
>
> On 12/9/2015 2:20 PM, Stan Ratliff wrote:
> > Lou,
> >
> > On Wed, Dec 9, 2015 at 2:02 PM, Lou Berger <lberger@labn.net
> > <mailto:lberger@labn.net>> wrote:
> >
> >     Authors/WG,
> >
> >     The current version of DLEP contains two negotiations as part of a
> >     Session Initialization transaction:
> >     1) <Extensions Supported> is included in both the <Session
> >     Initialization> and <Session Initialization Response> messages
> >     2) the optional data items, <Resources> and <Relative Link Quality>
> >
> >     Both have parallel allocation policies:
> >
> >
> >
> +-------------+-----------------------------------------------------+
> >        | Type Code   | Description
> >          |
> >
> >
> +-------------+-----------------------------------------------------+
> >        | 0           | Reserved
> >         |
> >        | 1           | Status (Section 10.1)
> >          |
> >          ...
> >        | 20          | Relative Link Quality (Transmit) (RLQT)
> >     (Section    |
> >        | 21-65407    | Reserved for future extensions
> >         |
> >        | 65408-65534 | Private Use. Available for experiments
> >         |
> >        | 65535       | Reserved
> >         |
> >
> >
> +-------------+-----------------------------------------------------+
> >
> >                            Table 2: DLEP Data Item types
> >
> >
> >
> +-------------+-----------------------------------------------------+
> >        | Code        | Description
> >          |
> >
> >
> +-------------+-----------------------------------------------------+
> >        | 0           | Reserved
> >         |
> >        | 1           | Credit Windowing
> >         |
> >        | 2-65519     | Reserved for future extensions
> >         |
> >        | 65520-65534 | Private Use. Available for experiments
> >         |
> >        | 65535       | Reserved
> >         |
> >
> >
> +-------------+-----------------------------------------------------+
> >
> >                            Table 4: DLEP Extension types
> >
> >     It seems to me that given the current definition, one of these two
> >     should suffice.  I don't have a strong opinion on which, but do
> >     strongly
> >     believe that a single approach should be selected to facilitate
> >     interoperability.
> >
> >
> > Well, I disagree. Extensions defines a process whereby multiple data
> > items, and/or new *messages*, can be added to DLEP. The other two data
> > items you mention (Resources and Link Quality) are just optional (not
> > required) metrics. They are two different things.
>
> I understand that their motivation is different, but the end result is
> that code needs to be written (and tested!) to cover both.  So if
> there's a way to eliminate two ways to do the same function, it's good
> design to do so.
>

An implementation can chose to not support an extension. An implementation
can also chose not to support Resources and/or Link Quality. I guess I'm
missing something, because I'm not following this line of logic. If you
want to use the extension, or the extra metrics, then great - write and
test the code. If you don't, that's great, too.


>
> >
> >
> >
> >     To be clear, the following spells out the options:
> >
> >     Option A: Extensions (aka capabilities) based
> >       Any optional or new data item or message would need to be indicated
> >       in <Extensions Supported> to be used.  To cover the current
> optional
> >       data items the following would need to be defined:
> >         | 1 | Resources |
> >         | 2 | Relative Link Quality |
> >         | 3 | Credit Windowing |
> >       <Session Initialization Response> could still contain the optional
> >       data items, if the corresponding type is present in <Extensions
> >       Supported>
> >
> >       Note that other messages will still use optional data items.
> >
> >     Option B: Data item based.
> >       An optional or new data item must be both Session Initialization
> >       messages to be used. To allow/enable <Resources> and <Relative Link
> >       Quality>, they would need to be included in both the <Session
> >       Initialization> and <Session Initialization Response> messages.
> >
> >       To enable the Credit Windowing extension, the three credit-related
> >       state items, <Grant>, <Window Status>, and <Request> would need
> >     to be
> >       included in both session init messages for the full extension to be
> >       used.
> >
> >     Option C: keep both
> >       Keep current text
> >
> >     While I like Option A and have seen similar approaches in other
> >     protocols, e.g., BGP Capabilities, I actually have a slight
> preference
> >     for B.  The reason for this is DLEP uses optional data items in other
> >     places and implementations will already need to handle this, so it
> >     seems
> >     like option B will probably require smaller incremental code.
> >
> >     Either way, I think Option C is much less desirable then either of
> the
> >     other options.
> >
> >     Thoughts? Opinions?
> >
> >
> > Before I did that, I'd be more inclined to pursue an "Option D":
> > 1. All of the metric data items (e.g. - MDRR, MDRT, CDRR, CDRT,
> > Latency, RLQR, RLQT, RESR, REST) are listed, with no mention as to
> > whether they are mandatory or optional - they are just the pool of
> > metrics that MAY be used by an implementation.
>
> Right, and this means that implementations need to dynamically track
> which data items are in use on a per session, destination, and IP
> basis.  This is a fair bit of mechanism already, and exactly why (a) I
> raised this topic and (b) favor Option B.
>

The current draft states that all metrics supported MUST be announced at
the peer level. I don't see a need to dynamically track at the destination
level, and we really don't have an IP basis.


>
> > 2. In the Peer Init/Peer Init ACK, the peers list the metrics from the
> > available set that they are going to use. If peers cannot agree, the
> > session doesn't get established.
>
> Peer = session and ACK = response, right?  Yup, this is why I say use
> this same mechanism for future extension too.  Again, different
> motivation doesn't have to mean different mechanisms.
>

If what you're advocating is that all optional, and extension-based, data
items be announced in the Peer exchange, then my question would be - what
about new, extension-based messages?

Regards,
Stan



>
> Lou
>
> >
> > ... and we're done. Again, the Extensions stuff is for new data
> > items/messages that might come along (with Credit Windowing being the
> > first).
> >
> > Regards,
> > Stan
> >
> >
> >
> >
> >     Lou
> >
> >     _______________________________________________
> >     manet mailing list
> >     manet@ietf.org <mailto:manet@ietf.org>
> >     https://www.ietf.org/mailman/listinfo/manet
> >
> >
>
>
>

--001a11c398f2809ceb05267cbc68
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><div class=3D"gmail_quo=
te">On Wed, Dec 9, 2015 at 3:01 PM, Lou Berger <span dir=3D"ltr">&lt;<a hre=
f=3D"mailto:lberger@labn.net" target=3D"_blank">lberger@labn.net</a>&gt;</s=
pan> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex=
;border-left:1px #ccc solid;padding-left:1ex">Stan,<br>
<br>
On 12/9/2015 2:20 PM, Stan Ratliff wrote:<br>
&gt; Lou,<br>
&gt;<br>
&gt; On Wed, Dec 9, 2015 at 2:02 PM, Lou Berger &lt;<a href=3D"mailto:lberg=
er@labn.net">lberger@labn.net</a><br>
&gt; &lt;mailto:<a href=3D"mailto:lberger@labn.net">lberger@labn.net</a>&gt=
;&gt; wrote:<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0Authors/WG,<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0The current version of DLEP contains two negotiatio=
ns as part of a<br>
&gt;=C2=A0 =C2=A0 =C2=A0Session Initialization transaction:<br>
&gt;=C2=A0 =C2=A0 =C2=A01) &lt;Extensions Supported&gt; is included in both=
 the &lt;Session<br>
&gt;=C2=A0 =C2=A0 =C2=A0Initialization&gt; and &lt;Session Initialization R=
esponse&gt; messages<br>
&gt;=C2=A0 =C2=A0 =C2=A02) the optional data items, &lt;Resources&gt; and &=
lt;Relative Link Quality&gt;<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0Both have parallel allocation policies:<br>
&gt;<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0 +-------------+-----------------------------------=
------------------+<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 | Type Code=C2=A0 =C2=A0| Description<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 |<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0 +-------------+-----------------------------------=
------------------+<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 | 0=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0| Reserved<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0|<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 | 1=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0| Status (Section 10.1)<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 |<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 ...<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 | 20=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 | Re=
lative Link Quality (Transmit) (RLQT)<br>
&gt;=C2=A0 =C2=A0 =C2=A0(Section=C2=A0 =C2=A0 |<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 | 21-65407=C2=A0 =C2=A0 | Reserved for futu=
re extensions<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0|<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 | 65408-65534 | Private Use. Available for =
experiments<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0|<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 | 65535=C2=A0 =C2=A0 =C2=A0 =C2=A0| Reserve=
d<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0|<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0 +-------------+-----------------------------------=
------------------+<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Table 2: DLEP Data Item types<br>
&gt;<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0 +-------------+-----------------------------------=
------------------+<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 | Code=C2=A0 =C2=A0 =C2=A0 =C2=A0 | Descrip=
tion<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 |<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0 +-------------+-----------------------------------=
------------------+<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 | 0=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0| Reserved<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0|<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 | 1=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0| Credit Windowing<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0|<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 | 2-65519=C2=A0 =C2=A0 =C2=A0| Reserved for=
 future extensions<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0|<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 | 65520-65534 | Private Use. Available for =
experiments<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0|<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 | 65535=C2=A0 =C2=A0 =C2=A0 =C2=A0| Reserve=
d<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0|<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0 +-------------+-----------------------------------=
------------------+<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Table 4: DLEP Extension types<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0It seems to me that given the current definition, o=
ne of these two<br>
&gt;=C2=A0 =C2=A0 =C2=A0should suffice.=C2=A0 I don&#39;t have a strong opi=
nion on which, but do<br>
&gt;=C2=A0 =C2=A0 =C2=A0strongly<br>
&gt;=C2=A0 =C2=A0 =C2=A0believe that a single approach should be selected t=
o facilitate<br>
&gt;=C2=A0 =C2=A0 =C2=A0interoperability.<br>
&gt;<br>
&gt;<br>
&gt; Well, I disagree. Extensions defines a process whereby multiple data<b=
r>
&gt; items, and/or new *messages*, can be added to DLEP. The other two data=
<br>
&gt; items you mention (Resources and Link Quality) are just optional (not<=
br>
&gt; required) metrics. They are two different things.<br>
<br>
I understand that their motivation is different, but the end result is<br>
that code needs to be written (and tested!) to cover both.=C2=A0 So if<br>
there&#39;s a way to eliminate two ways to do the same function, it&#39;s g=
ood<br>
design to do so.<br></blockquote><div><br></div><div>An implementation can =
chose to not support an extension. An implementation can also chose not to =
support Resources and/or Link Quality. I guess I&#39;m missing something, b=
ecause I&#39;m not following this line of logic. If you want to use the ext=
ension, or the extra metrics, then great - write and test the code. If you =
don&#39;t, that&#39;s great, too.=C2=A0</div><div>=C2=A0</div><blockquote c=
lass=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;=
padding-left:1ex">
<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0To be clear, the following spells out the options:<=
br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0Option A: Extensions (aka capabilities) based<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0Any optional or new data item or message wou=
ld need to be indicated<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0in &lt;Extensions Supported&gt; to be used.=
=C2=A0 To cover the current optional<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0data items the following would need to be de=
fined:<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0| 1 | Resources |<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0| 2 | Relative Link Quality |<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0| 3 | Credit Windowing |<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0&lt;Session Initialization Response&gt; coul=
d still contain the optional<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0data items, if the corresponding type is pre=
sent in &lt;Extensions<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0Supported&gt;<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0Note that other messages will still use opti=
onal data items.<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0Option B: Data item based.<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0An optional or new data item must be both Se=
ssion Initialization<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0messages to be used. To allow/enable &lt;Res=
ources&gt; and &lt;Relative Link<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0Quality&gt;, they would need to be included =
in both the &lt;Session<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0Initialization&gt; and &lt;Session Initializ=
ation Response&gt; messages.<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0To enable the Credit Windowing extension, th=
e three credit-related<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0state items, &lt;Grant&gt;, &lt;Window Statu=
s&gt;, and &lt;Request&gt; would need<br>
&gt;=C2=A0 =C2=A0 =C2=A0to be<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0included in both session init messages for t=
he full extension to be<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0used.<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0Option C: keep both<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0Keep current text<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0While I like Option A and have seen similar approac=
hes in other<br>
&gt;=C2=A0 =C2=A0 =C2=A0protocols, e.g., BGP Capabilities, I actually have =
a slight preference<br>
&gt;=C2=A0 =C2=A0 =C2=A0for B.=C2=A0 The reason for this is DLEP uses optio=
nal data items in other<br>
&gt;=C2=A0 =C2=A0 =C2=A0places and implementations will already need to han=
dle this, so it<br>
&gt;=C2=A0 =C2=A0 =C2=A0seems<br>
&gt;=C2=A0 =C2=A0 =C2=A0like option B will probably require smaller increme=
ntal code.<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0Either way, I think Option C is much less desirable=
 then either of the<br>
&gt;=C2=A0 =C2=A0 =C2=A0other options.<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0Thoughts? Opinions?<br>
&gt;<br>
&gt;<br>
&gt; Before I did that, I&#39;d be more inclined to pursue an &quot;Option =
D&quot;:<br>
&gt; 1. All of the metric data items (e.g. - MDRR, MDRT, CDRR, CDRT,<br>
&gt; Latency, RLQR, RLQT, RESR, REST) are listed, with no mention as to<br>
&gt; whether they are mandatory or optional - they are just the pool of<br>
&gt; metrics that MAY be used by an implementation.<br>
<br>
Right, and this means that implementations need to dynamically track<br>
which data items are in use on a per session, destination, and IP<br>
basis.=C2=A0 This is a fair bit of mechanism already, and exactly why (a) I=
<br>
raised this topic and (b) favor Option B.<br></blockquote><div><br></div><d=
iv>The current draft states that all metrics supported MUST be announced at=
 the peer level. I don&#39;t see a need to dynamically track at the destina=
tion level, and we really don&#39;t have an IP basis.=C2=A0</div><div>=C2=
=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;borde=
r-left:1px #ccc solid;padding-left:1ex">
<br>
&gt; 2. In the Peer Init/Peer Init ACK, the peers list the metrics from the=
<br>
&gt; available set that they are going to use. If peers cannot agree, the<b=
r>
&gt; session doesn&#39;t get established.<br>
<br>
Peer =3D session and ACK =3D response, right?=C2=A0 Yup, this is why I say =
use<br>
this same mechanism for future extension too.=C2=A0 Again, different<br>
motivation doesn&#39;t have to mean different mechanisms.<br></blockquote><=
div><br></div><div>If what you&#39;re advocating is that all optional, and =
extension-based, data items be announced in the Peer exchange, then my ques=
tion would be - what about new, extension-based messages?=C2=A0</div><div><=
br></div><div>Regards,</div><div>Stan</div><div><br></div><div>=C2=A0</div>=
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<br>
Lou<br>
<br>
&gt;<br>
&gt; ... and we&#39;re done. Again, the Extensions stuff is for new data<br=
>
&gt; items/messages that might come along (with Credit Windowing being the<=
br>
&gt; first).<br>
&gt;<br>
&gt; Regards,<br>
&gt; Stan<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0Lou<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0_______________________________________________<br>
&gt;=C2=A0 =C2=A0 =C2=A0manet mailing list<br>
&gt;=C2=A0 =C2=A0 =C2=A0<a href=3D"mailto:manet@ietf.org">manet@ietf.org</a=
> &lt;mailto:<a href=3D"mailto:manet@ietf.org">manet@ietf.org</a>&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0<a href=3D"https://www.ietf.org/mailman/listinfo/ma=
net" rel=3D"noreferrer" target=3D"_blank">https://www.ietf.org/mailman/list=
info/manet</a><br>
&gt;<br>
&gt;<br>
<br>
<br>
</blockquote></div><br></div></div>

--001a11c398f2809ceb05267cbc68--


From nobody Wed Dec  9 12:43:42 2015
Return-Path: <lberger@labn.net>
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 097741A9126 for <manet@ietfa.amsl.com>; Wed,  9 Dec 2015 12:43:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.667
X-Spam-Level: 
X-Spam-Status: No, score=-1.667 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, IP_NOT_FRIENDLY=0.334, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no
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 l2vd1x9wnL3g for <manet@ietfa.amsl.com>; Wed,  9 Dec 2015 12:43:39 -0800 (PST)
Received: from gproxy9-pub.mail.unifiedlayer.com (gproxy9-pub.mail.unifiedlayer.com [69.89.20.122]) by ietfa.amsl.com (Postfix) with SMTP id 4BAA21A6F12 for <manet@ietf.org>; Wed,  9 Dec 2015 12:43:39 -0800 (PST)
Received: (qmail 8563 invoked by uid 0); 9 Dec 2015 20:43:37 -0000
Received: from unknown (HELO cmgw2) (10.0.90.83) by gproxy9.mail.unifiedlayer.com with SMTP; 9 Dec 2015 20:43:37 -0000
Received: from box313.bluehost.com ([69.89.31.113]) by cmgw2 with  id rYjY1r00t2SSUrH01Yjbll; Wed, 09 Dec 2015 13:43:36 -0700
X-Authority-Analysis: v=2.1 cv=dqRIVTQ4 c=1 sm=1 tr=0 a=h1BC+oY+fLhyFmnTBx92Jg==:117 a=wU2YTnxGAAAA:8 a=cNaOj0WVAAAA:8 a=IkcTkHD0fZMA:10 a=-NfooI8aBGcA:10 a=uEJ9t1CZtbIA:10 a=wUQvQvOEmiQA:10 a=48vgC7mUAAAA:8 a=jnqYjTZluhsXpHKFDVMA:9 a=QEXdDO2ut3YA:10
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=labn.net; s=default;  h=Content-Transfer-Encoding:Content-Type:In-Reply-To:MIME-Version:Date:Message-ID:From:Cc:References:To:Subject; bh=Siak58zTdVvIUhEui/J6J2IyTKU2sVi3qUafH3egVtE=;  b=qmpDhKQpZNwodygoO0Dst4Olar9PtDKi6OtLZRDYdKjM9GIO8dfQzPIieMW4/+7vqM/m47WPdG5YGYgBpi6XnRoDKNpH8044B9lXLIXWlIyr1Y01lIsQ8RPDpbXlvio1;
Received: from box313.bluehost.com ([69.89.31.113]:40497 helo=[127.0.0.1]) by box313.bluehost.com with esmtpa (Exim 4.84) (envelope-from <lberger@labn.net>) id 1a6laI-0007xw-IA; Wed, 09 Dec 2015 13:43:34 -0700
To: Stan Ratliff <ratliffstan@gmail.com>
References: <56687AC2.9060801@labn.net> <CALtoyomCuki__fyNnhmYoKmBcrQSSuOPGgcg8N-txG1DSaUaAg@mail.gmail.com>
From: Lou Berger <lberger@labn.net>
X-Enigmail-Draft-Status: N1110
Message-ID: <56689271.306@labn.net>
Date: Wed, 9 Dec 2015 15:43:29 -0500
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.4.0
MIME-Version: 1.0
In-Reply-To: <CALtoyomCuki__fyNnhmYoKmBcrQSSuOPGgcg8N-txG1DSaUaAg@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-Identified-User: {1038:box313.bluehost.com:labnmobi:labn.net} {sentby:smtp auth 69.89.31.113 authed with lberger@labn.net}
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/S06ItLkgS__fq2S5RlA2lKP9Ib8>
Cc: MANET IETF <manet@ietf.org>, draft-ietf-manet-dlep@ietf.org
Subject: Re: [manet] DLEP-17: Handling of unknown / unexpected messages
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: <https://mailarchive.ietf.org/arch/browse/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: Wed, 09 Dec 2015 20:43:41 -0000

Stan,

On 12/9/2015 2:26 PM, Stan Ratliff wrote:
>
>
> On Wed, Dec 9, 2015 at 2:02 PM, Lou Berger <lberger@labn.net
> <mailto:lberger@labn.net>> wrote:
>
>     Authors/WG,
>
>     The current text has different processing rules for unexpected signals
>     and messages:
>
>        If an unrecognized, or unexpected signal is received, or a received
>        signal contains unrecognized, invalid, or disallowed duplicate data
>        items, the receiving peer MUST ignore the signal.
>
>
> Since "signal" refers to "The UDP messages/packets that are sent as a
> part of discovery", and therefore, no Peer session exists, ignoring
> (and maybe logging) is about all you can do. 
>
>  
>
>
>     and
>
>        If an unrecognized, or unexpected message is received, or a
>     received
>        message contains unrecognized, invalid, or disallowed duplicate
>     data
>        items, the receiving peer MUST issue a Session Termination message
>        (Section 9.7) with a Status data item (Section 10.1) containing the
>        most relevant status code, and transition to the Session
>     Termination
>        state.
>
>     It seems to me that the approach of resetting a session any time
>     anything unexpected occurs is overly restrictive and is likely to lead
>     to instability and interoperability issues as implementations
>     mature and
>     the protocol is extended.  (As well as add some interesting
>     vulnerabilities.)  It's also not clear, what real value the
>     approach brings.
>
>
> This was a compromise, after a lot of discussion. The issue is that
> something the receiver doesn't understands, and therefore ignores, may
> be crucial to the sender. If the receiver ignores it, and by
> definition does not negatively ACK it, then the sender will wind up in
> a transaction timeout... the processing there is to pull down the
> Peer-to-peer session. We figured it was better for the receiver of a
> message not understood to go ahead and proactively tear the session down. 
>

Is there any real harm in letting the transaction time out?  It seems to
me will be a constantly bouncing session with nothing working, vs having
some base level of stable capability.

Do you object to changing the behavior?

Lou

>
> Regards,
> Stan 
>
>
>
>
>  
>
>
>     Following behavior common in other IETF protocols, and the IETF/Jon's
>     design maxim of "Be liberal in what you accept..."  I'd propose that
>     unrecognized, invalid, or disallowed duplicate data items and messages
>     be ignore.  Counting them and reporting them via the management plane
>     should also be allowed, and perhaps recommended.
>
>     Lou
>
>     _______________________________________________
>     manet mailing list
>     manet@ietf.org <mailto:manet@ietf.org>
>     https://www.ietf.org/mailman/listinfo/manet
>
>



From nobody Wed Dec  9 12:55:44 2015
Return-Path: <lberger@labn.net>
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 BC79F1A7021 for <manet@ietfa.amsl.com>; Wed,  9 Dec 2015 12:55:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.667
X-Spam-Level: 
X-Spam-Status: No, score=-1.667 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, IP_NOT_FRIENDLY=0.334, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no
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 t_HaOzViWuS4 for <manet@ietfa.amsl.com>; Wed,  9 Dec 2015 12:55:40 -0800 (PST)
Received: from gproxy4-pub.mail.unifiedlayer.com (gproxy4-pub.mail.unifiedlayer.com [69.89.23.142]) by ietfa.amsl.com (Postfix) with SMTP id A91F11A6F1F for <manet@ietf.org>; Wed,  9 Dec 2015 12:55:40 -0800 (PST)
Received: (qmail 31542 invoked by uid 0); 9 Dec 2015 20:55:38 -0000
Received: from unknown (HELO CMOut01) (10.0.90.82) by gproxy4.mail.unifiedlayer.com with SMTP; 9 Dec 2015 20:55:38 -0000
Received: from box313.bluehost.com ([69.89.31.113]) by CMOut01 with  id rYva1r00E2SSUrH01Yvd3l; Wed, 09 Dec 2015 13:55:37 -0700
X-Authority-Analysis: v=2.1 cv=Zc6OaKlA c=1 sm=1 tr=0 a=h1BC+oY+fLhyFmnTBx92Jg==:117 a=wU2YTnxGAAAA:8 a=cNaOj0WVAAAA:8 a=IkcTkHD0fZMA:10 a=-NfooI8aBGcA:10 a=uEJ9t1CZtbIA:10 a=wUQvQvOEmiQA:10 a=48vgC7mUAAAA:8 a=NPznG2CuiZKFB5fNDjcA:9 a=jhb4IWmricxwxdJK:21 a=XTKcx0gN_eTa3B5x:21 a=QEXdDO2ut3YA:10
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=labn.net; s=default;  h=Content-Transfer-Encoding:Content-Type:In-Reply-To:MIME-Version:Date:Message-ID:From:Cc:References:To:Subject; bh=ZZ7kJc8AggoA1/tAmy+QXdFLM7q5H2NOtLKSS0oTIIQ=;  b=Ez4g5+9JyTFIRF+r3TgkG9rBp54fFx+oFTL/5E5I/u0ylp8qRghKO+6/+NxuEbKfhz3MR6RbT+3L7dgwgpHkkilhjg01xci4TaxJxIAVW7mxQdT5AqgDeZju7ino3Fs3;
Received: from box313.bluehost.com ([69.89.31.113]:43473 helo=[127.0.0.1]) by box313.bluehost.com with esmtpa (Exim 4.84) (envelope-from <lberger@labn.net>) id 1a6llv-0001m5-61; Wed, 09 Dec 2015 13:55:35 -0700
To: Stan Ratliff <ratliffstan@gmail.com>
References: <56687ABA.803@labn.net> <CALtoyonnuk03=FqiyPfQS4t9mKJt81kUfkZP-JB0FD0hfRp-6Q@mail.gmail.com> <566888B0.3070806@labn.net> <CALtoyomO1YTNydyohqRczjHnivCkfPp_gwv5oRWjdRmC5yOb0Q@mail.gmail.com>
From: Lou Berger <lberger@labn.net>
X-Enigmail-Draft-Status: N1110
Message-ID: <56689542.2080303@labn.net>
Date: Wed, 9 Dec 2015 15:55:30 -0500
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.4.0
MIME-Version: 1.0
In-Reply-To: <CALtoyomO1YTNydyohqRczjHnivCkfPp_gwv5oRWjdRmC5yOb0Q@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-Identified-User: {1038:box313.bluehost.com:labnmobi:labn.net} {sentby:smtp auth 69.89.31.113 authed with lberger@labn.net}
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/WvIow7QlXZgkCfajdR1NfHDnfbU>
Cc: MANET IETF <manet@ietf.org>, draft-ietf-manet-dlep@ietf.org
Subject: Re: [manet] DLEP-17: duplicate functions - Options & extensions negotiations
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: <https://mailarchive.ietf.org/arch/browse/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: Wed, 09 Dec 2015 20:55:42 -0000

Stan,


On 12/9/2015 3:14 PM, Stan Ratliff wrote:
>
>
> On Wed, Dec 9, 2015 at 3:01 PM, Lou Berger <lberger@labn.net
> <mailto:lberger@labn.net>> wrote:
>
>     Stan,
>
>     On 12/9/2015 2:20 PM, Stan Ratliff wrote:
>     > Lou,
>     >
>     > On Wed, Dec 9, 2015 at 2:02 PM, Lou Berger <lberger@labn.net
>     <mailto:lberger@labn.net>
>     > <mailto:lberger@labn.net <mailto:lberger@labn.net>>> wrote:
>     >
>     >     Authors/WG,
>     >
>     >     The current version of DLEP contains two negotiations as
>     part of a
>     >     Session Initialization transaction:
>     >     1) <Extensions Supported> is included in both the <Session
>     >     Initialization> and <Session Initialization Response> messages
>     >     2) the optional data items, <Resources> and <Relative Link
>     Quality>
>     >
>     >     Both have parallel allocation policies:
>     >
>     >
>     >     
>     +-------------+-----------------------------------------------------+
>     >        | Type Code   | Description
>     >          |
>     >
>     >     
>     +-------------+-----------------------------------------------------+
>     >        | 0           | Reserved
>     >         |
>     >        | 1           | Status (Section 10.1)
>     >          |
>     >          ...
>     >        | 20          | Relative Link Quality (Transmit) (RLQT)
>     >     (Section    |
>     >        | 21-65407    | Reserved for future extensions
>     >         |
>     >        | 65408-65534 | Private Use. Available for experiments
>     >         |
>     >        | 65535       | Reserved
>     >         |
>     >
>     >     
>     +-------------+-----------------------------------------------------+
>     >
>     >                            Table 2: DLEP Data Item types
>     >
>     >
>     >     
>     +-------------+-----------------------------------------------------+
>     >        | Code        | Description
>     >          |
>     >
>     >     
>     +-------------+-----------------------------------------------------+
>     >        | 0           | Reserved
>     >         |
>     >        | 1           | Credit Windowing
>     >         |
>     >        | 2-65519     | Reserved for future extensions
>     >         |
>     >        | 65520-65534 | Private Use. Available for experiments
>     >         |
>     >        | 65535       | Reserved
>     >         |
>     >
>     >     
>     +-------------+-----------------------------------------------------+
>     >
>     >                            Table 4: DLEP Extension types
>     >
>     >     It seems to me that given the current definition, one of
>     these two
>     >     should suffice.  I don't have a strong opinion on which, but do
>     >     strongly
>     >     believe that a single approach should be selected to facilitate
>     >     interoperability.
>     >
>     >
>     > Well, I disagree. Extensions defines a process whereby multiple data
>     > items, and/or new *messages*, can be added to DLEP. The other
>     two data
>     > items you mention (Resources and Link Quality) are just optional
>     (not
>     > required) metrics. They are two different things.
>
>     I understand that their motivation is different, but the end result is
>     that code needs to be written (and tested!) to cover both.  So if
>     there's a way to eliminate two ways to do the same function, it's good
>     design to do so.
>
>
> An implementation can chose to not support an extension. An
> implementation can also chose not to support Resources and/or Link
> Quality. I guess I'm missing something, because I'm not following this
> line of logic. If you want to use the extension, or the extra metrics,
> then great - write and test the code. If you don't, that's great, too.

The point is there are different mechanisms that essentially do the same
function, so why not use one?

e.g., to indicate use of Resources and/or Link Quality, they are
included in the Session Init Response. (Which parallels use optional
data items in other messages.)  but to indicate use of Credit data
items, an extension value is used.

My point is that rather than coding two ways of 'negotiating' use of
options, it would be easier to define/use just one.

>  
>
>
>     >
>     >
>     >
>     >     To be clear, the following spells out the options:
>     >
>     >     Option A: Extensions (aka capabilities) based
>     >       Any optional or new data item or message would need to be
>     indicated
>     >       in <Extensions Supported> to be used.  To cover the
>     current optional
>     >       data items the following would need to be defined:
>     >         | 1 | Resources |
>     >         | 2 | Relative Link Quality |
>     >         | 3 | Credit Windowing |
>     >       <Session Initialization Response> could still contain the
>     optional
>     >       data items, if the corresponding type is present in
>     <Extensions
>     >       Supported>
>     >
>     >       Note that other messages will still use optional data items.
>     >
>     >     Option B: Data item based.
>     >       An optional or new data item must be both Session
>     Initialization
>     >       messages to be used. To allow/enable <Resources> and
>     <Relative Link
>     >       Quality>, they would need to be included in both the <Session
>     >       Initialization> and <Session Initialization Response>
>     messages.
>     >
>     >       To enable the Credit Windowing extension, the three
>     credit-related
>     >       state items, <Grant>, <Window Status>, and <Request> would
>     need
>     >     to be
>     >       included in both session init messages for the full
>     extension to be
>     >       used.
>     >
>     >     Option C: keep both
>     >       Keep current text
>     >
>     >     While I like Option A and have seen similar approaches in other
>     >     protocols, e.g., BGP Capabilities, I actually have a slight
>     preference
>     >     for B.  The reason for this is DLEP uses optional data items
>     in other
>     >     places and implementations will already need to handle this,
>     so it
>     >     seems
>     >     like option B will probably require smaller incremental code.
>     >
>     >     Either way, I think Option C is much less desirable then
>     either of the
>     >     other options.
>     >
>     >     Thoughts? Opinions?
>     >
>     >
>     > Before I did that, I'd be more inclined to pursue an "Option D":
>     > 1. All of the metric data items (e.g. - MDRR, MDRT, CDRR, CDRT,
>     > Latency, RLQR, RLQT, RESR, REST) are listed, with no mention as to
>     > whether they are mandatory or optional - they are just the pool of
>     > metrics that MAY be used by an implementation.
>
>     Right, and this means that implementations need to dynamically track
>     which data items are in use on a per session, destination, and IP
>     basis.  This is a fair bit of mechanism already, and exactly why (a) I
>     raised this topic and (b) favor Option B.
>
>
> The current draft states that all metrics supported MUST be announced
> at the peer level. I don't see a need to dynamically track at the
> destination level, and we really don't have an IP basis. 
>  
Not that it's critical, but if the destination mac is of the router and
they are always announced/updated together, you essentially do. 

>
>     > 2. In the Peer Init/Peer Init ACK, the peers list the metrics
>     from the
>     > available set that they are going to use. If peers cannot agree, the
>     > session doesn't get established.
>
>     Peer = session and ACK = response, right?  Yup, this is why I say use
>     this same mechanism for future extension too.  Again, different
>     motivation doesn't have to mean different mechanisms.
>
>
> If what you're advocating is that all optional, and extension-based,
> data items be announced in the Peer exchange, then my question would be
This is option B.

> - what about new, extension-based messages?
Then either it can be implicit based on a negotiated data item, or less
cleanly, it can just be sent and ignored.

Lou

>
> Regards,
> Stan
>
>  
>
>
>     Lou
>
>     >
>     > ... and we're done. Again, the Extensions stuff is for new data
>     > items/messages that might come along (with Credit Windowing
>     being the
>     > first).
>     >
>     > Regards,
>     > Stan
>     >
>     >
>     >
>     >
>     >     Lou
>     >
>     >     _______________________________________________
>     >     manet mailing list
>     >     manet@ietf.org <mailto:manet@ietf.org>
>     <mailto:manet@ietf.org <mailto:manet@ietf.org>>
>     >     https://www.ietf.org/mailman/listinfo/manet
>     >
>     >
>
>
>



From nobody Wed Dec  9 13:02:00 2015
Return-Path: <ratliffstan@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 5D1CD1ACEB4; Wed,  9 Dec 2015 13:01:58 -0800 (PST)
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 554pLPtZra_a; Wed,  9 Dec 2015 13:01:54 -0800 (PST)
Received: from mail-lf0-x22b.google.com (mail-lf0-x22b.google.com [IPv6:2a00:1450:4010:c07::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CAF331B2D6F; Wed,  9 Dec 2015 13:01:51 -0800 (PST)
Received: by lfdl133 with SMTP id l133so43142616lfd.2; Wed, 09 Dec 2015 13:01:50 -0800 (PST)
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=pNQJVJEtZADcG1Rlo7rpMeNxsbG947CBE/ual++P488=; b=NBT97WRI2ErjW2i7y7JqWrMjieVFQUs88pPPoC2qVdwFQY/EJUGeW5nepPbH3cM/QH QRY3S5LIBPfvYu6z2JACMJHyKeLBD/C0i33SKU0T6/zNqA7jfkVsa8iYIhorDYPzNQJd xIJWI6kj4aYFibwW89Ld3wcYQE15lmcShNFxTBKzJaHrqzjSyBZvnKPfRAug4mE/8Az1 RUAsw4RpDBSV3c1MP5cG8cGlkrc7K96APeVy4g3Bw0v9nOS5gzRgGhzmy31hukcyOH4q tTLIJo8Dr6QZYYLqxYS9EWrhBjVIBs/zy+M9JfWaaZEKPz3AVa6pwEM9pM3j5F/cqMdO 7GDg==
MIME-Version: 1.0
X-Received: by 10.25.152.133 with SMTP id a127mr3395717lfe.152.1449694909952;  Wed, 09 Dec 2015 13:01:49 -0800 (PST)
Received: by 10.25.209.71 with HTTP; Wed, 9 Dec 2015 13:01:49 -0800 (PST)
In-Reply-To: <56689271.306@labn.net>
References: <56687AC2.9060801@labn.net> <CALtoyomCuki__fyNnhmYoKmBcrQSSuOPGgcg8N-txG1DSaUaAg@mail.gmail.com> <56689271.306@labn.net>
Date: Wed, 9 Dec 2015 16:01:49 -0500
Message-ID: <CALtoyo=JqgbqsBPo5jG-UzFR56qmAEk9zbtDBoLQUoJfcuooew@mail.gmail.com>
From: Stan Ratliff <ratliffstan@gmail.com>
To: Lou Berger <lberger@labn.net>
Content-Type: multipart/alternative; boundary=001a114020ac23fae305267d669d
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/3lRvCL9H6lKSOMZHSBgwHYgxedk>
Cc: MANET IETF <manet@ietf.org>, draft-ietf-manet-dlep@ietf.org
Subject: Re: [manet] DLEP-17: Handling of unknown / unexpected messages
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: <https://mailarchive.ietf.org/arch/browse/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: Wed, 09 Dec 2015 21:01:58 -0000

--001a114020ac23fae305267d669d
Content-Type: text/plain; charset=UTF-8

Lou,


On Wed, Dec 9, 2015 at 3:43 PM, Lou Berger <lberger@labn.net> wrote:

> Stan,
>
> On 12/9/2015 2:26 PM, Stan Ratliff wrote:
> >
> >
> > On Wed, Dec 9, 2015 at 2:02 PM, Lou Berger <lberger@labn.net
> > <mailto:lberger@labn.net>> wrote:
> >
> >     Authors/WG,
> >
> >     The current text has different processing rules for unexpected
> signals
> >     and messages:
> >
> >        If an unrecognized, or unexpected signal is received, or a
> received
> >        signal contains unrecognized, invalid, or disallowed duplicate
> data
> >        items, the receiving peer MUST ignore the signal.
> >
> >
> > Since "signal" refers to "The UDP messages/packets that are sent as a
> > part of discovery", and therefore, no Peer session exists, ignoring
> > (and maybe logging) is about all you can do.
> >
> >
> >
> >
> >     and
> >
> >        If an unrecognized, or unexpected message is received, or a
> >     received
> >        message contains unrecognized, invalid, or disallowed duplicate
> >     data
> >        items, the receiving peer MUST issue a Session Termination message
> >        (Section 9.7) with a Status data item (Section 10.1) containing
> the
> >        most relevant status code, and transition to the Session
> >     Termination
> >        state.
> >
> >     It seems to me that the approach of resetting a session any time
> >     anything unexpected occurs is overly restrictive and is likely to
> lead
> >     to instability and interoperability issues as implementations
> >     mature and
> >     the protocol is extended.  (As well as add some interesting
> >     vulnerabilities.)  It's also not clear, what real value the
> >     approach brings.
> >
> >
> > This was a compromise, after a lot of discussion. The issue is that
> > something the receiver doesn't understands, and therefore ignores, may
> > be crucial to the sender. If the receiver ignores it, and by
> > definition does not negatively ACK it, then the sender will wind up in
> > a transaction timeout... the processing there is to pull down the
> > Peer-to-peer session. We figured it was better for the receiver of a
> > message not understood to go ahead and proactively tear the session down.
> >
>
> Is there any real harm in letting the transaction time out?  It seems to
> me will be a constantly bouncing session with nothing working, vs having
> some base level of stable capability.
>

First off, I have to back-track and retract what I said. It's sad when you
don't correctly remember what's in your own document... ;-)  Section 4.1,
last para states "DLEP transactions do not time out and are not
cancellable." My profound apologies for mis-stating this earlier.


>
> Do you object to changing the behavior?
>

I need to be careful about which hat I'm wearing here - speaking just as a
WG participant, and a person that's interested in DLEP, I think that the
processing rules have gotten too restrictive - basically, on any error, the
only answer is to activate the nuclear self-destruct device, and blow
everything to kingdom-come. Just in my little-ole opinion, that's a tad
harsh...

As I mentioned earlier, this text was the result of much (too much)
haggling, talking, and discussing of options. I feel like I was pretty much
"in the rough" when the text was adopted; there are others on the list that
I hope will comment. What I believe is that:
1. An invalid or mis-understood *message* needs to be countered with
termination, since based on Section 4.1, the sender will have a transaction
"hanging out in space" that will never time out, and can't be cancelled.
2. As to invalid *Data Items*, I think the rules should be loosened -
specifically, I believe that "If an unrecognized, or unexpected message is
received, or a received message contains unrecognized, invalid, or
disallowed duplicate data items", then the receiving implementation should
negatively acknowledge, with an appropriate status Data Item/error code.

But that's just my $0.02-worth. Looking for other opinions on the list...

Regards,
Stan





>
> Lou
>
> >
> > Regards,
> > Stan
> >
> >
> >
> >
> >
> >
> >
> >     Following behavior common in other IETF protocols, and the IETF/Jon's
> >     design maxim of "Be liberal in what you accept..."  I'd propose that
> >     unrecognized, invalid, or disallowed duplicate data items and
> messages
> >     be ignore.  Counting them and reporting them via the management plane
> >     should also be allowed, and perhaps recommended.
> >
> >     Lou
> >
> >     _______________________________________________
> >     manet mailing list
> >     manet@ietf.org <mailto:manet@ietf.org>
> >     https://www.ietf.org/mailman/listinfo/manet
> >
> >
>
>
>

--001a114020ac23fae305267d669d
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Lou,=C2=A0<div><br><div class=3D"gmail_extra"><br><div cla=
ss=3D"gmail_quote">On Wed, Dec 9, 2015 at 3:43 PM, Lou Berger <span dir=3D"=
ltr">&lt;<a href=3D"mailto:lberger@labn.net" target=3D"_blank">lberger@labn=
.net</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"ma=
rgin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,=
204);border-left-style:solid;padding-left:1ex">Stan,<br>
<br>
On 12/9/2015 2:26 PM, Stan Ratliff wrote:<br>
&gt;<br>
&gt;<br>
&gt; On Wed, Dec 9, 2015 at 2:02 PM, Lou Berger &lt;<a href=3D"mailto:lberg=
er@labn.net">lberger@labn.net</a><br>
&gt; &lt;mailto:<a href=3D"mailto:lberger@labn.net">lberger@labn.net</a>&gt=
;&gt; wrote:<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0Authors/WG,<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0The current text has different processing rules for=
 unexpected signals<br>
&gt;=C2=A0 =C2=A0 =C2=A0and messages:<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 If an unrecognized, or unexpected signal is=
 received, or a received<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 signal contains unrecognized, invalid, or d=
isallowed duplicate data<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 items, the receiving peer MUST ignore the s=
ignal.<br>
&gt;<br>
&gt;<br>
&gt; Since &quot;signal&quot; refers to &quot;The UDP messages/packets that=
 are sent as a<br>
&gt; part of discovery&quot;, and therefore, no Peer session exists, ignori=
ng<br>
&gt; (and maybe logging) is about all you can do.<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0and<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 If an unrecognized, or unexpected message i=
s received, or a<br>
&gt;=C2=A0 =C2=A0 =C2=A0received<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 message contains unrecognized, invalid, or =
disallowed duplicate<br>
&gt;=C2=A0 =C2=A0 =C2=A0data<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 items, the receiving peer MUST issue a Sess=
ion Termination message<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 (Section 9.7) with a Status data item (Sect=
ion 10.1) containing the<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 most relevant status code, and transition t=
o the Session<br>
&gt;=C2=A0 =C2=A0 =C2=A0Termination<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 state.<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0It seems to me that the approach of resetting a ses=
sion any time<br>
&gt;=C2=A0 =C2=A0 =C2=A0anything unexpected occurs is overly restrictive an=
d is likely to lead<br>
&gt;=C2=A0 =C2=A0 =C2=A0to instability and interoperability issues as imple=
mentations<br>
&gt;=C2=A0 =C2=A0 =C2=A0mature and<br>
&gt;=C2=A0 =C2=A0 =C2=A0the protocol is extended.=C2=A0 (As well as add som=
e interesting<br>
&gt;=C2=A0 =C2=A0 =C2=A0vulnerabilities.)=C2=A0 It&#39;s also not clear, wh=
at real value the<br>
&gt;=C2=A0 =C2=A0 =C2=A0approach brings.<br>
&gt;<br>
&gt;<br>
&gt; This was a compromise, after a lot of discussion. The issue is that<br=
>
&gt; something the receiver doesn&#39;t understands, and therefore ignores,=
 may<br>
&gt; be crucial to the sender. If the receiver ignores it, and by<br>
&gt; definition does not negatively ACK it, then the sender will wind up in=
<br>
&gt; a transaction timeout... the processing there is to pull down the<br>
&gt; Peer-to-peer session. We figured it was better for the receiver of a<b=
r>
&gt; message not understood to go ahead and proactively tear the session do=
wn.<br>
&gt;<br>
<br>
Is there any real harm in letting the transaction time out?=C2=A0 It seems =
to<br>
me will be a constantly bouncing session with nothing working, vs having<br=
>
some base level of stable capability.<br></blockquote><div><br></div><div>F=
irst off, I have to back-track and retract what I said. It&#39;s sad when y=
ou don&#39;t correctly remember what&#39;s in your own document... ;-) =C2=
=A0Section 4.1, last para states &quot;DLEP transactions do not time out an=
d are not cancellable.&quot; My profound apologies for mis-stating this ear=
lier.=C2=A0</div><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=
=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(20=
4,204,204);border-left-style:solid;padding-left:1ex">
<br>
Do you object to changing the behavior?<br></blockquote><div><br></div><div=
>I need to be careful about which hat I&#39;m wearing here - speaking just =
as a WG participant, and a person that&#39;s interested in DLEP, I think th=
at the processing rules have gotten too restrictive - basically, on any err=
or, the only answer is to activate the nuclear self-destruct device, and bl=
ow everything to kingdom-come. Just in my little-ole opinion, that&#39;s a =
tad harsh...=C2=A0</div><div><br></div><div>As I mentioned earlier, this te=
xt was the result of much (too much) haggling, talking, and discussing of o=
ptions. I feel like I was pretty much &quot;in the rough&quot; when the tex=
t was adopted; there are others on the list that I hope will comment. What =
I believe is that:=C2=A0</div><div>1. An invalid or mis-understood *message=
* needs to be countered with termination, since based on Section 4.1, the s=
ender will have a transaction &quot;hanging out in space&quot; that will ne=
ver time out, and can&#39;t be cancelled.=C2=A0</div><div>2. As to invalid =
*Data Items*, I think the rules should be loosened - specifically, I believ=
e that &quot;If an unrecognized, or unexpected message is received, or a re=
ceived message contains unrecognized, invalid, or disallowed duplicate data=
 items&quot;, then the receiving implementation should negatively acknowled=
ge, with an appropriate status Data Item/error code.=C2=A0</div><div><br></=
div><div>But that&#39;s just my $0.02-worth. Looking for other opinions on =
the list...=C2=A0</div><div><br></div><div>Regards,</div><div>Stan</div><di=
v><br></div><div><br></div><div><br></div><div>=C2=A0</div><blockquote clas=
s=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;b=
order-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"=
>
<br>
Lou<br>
<br>
&gt;<br>
&gt; Regards,<br>
&gt; Stan<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0Following behavior common in other IETF protocols, =
and the IETF/Jon&#39;s<br>
&gt;=C2=A0 =C2=A0 =C2=A0design maxim of &quot;Be liberal in what you accept=
...&quot;=C2=A0 I&#39;d propose that<br>
&gt;=C2=A0 =C2=A0 =C2=A0unrecognized, invalid, or disallowed duplicate data=
 items and messages<br>
&gt;=C2=A0 =C2=A0 =C2=A0be ignore.=C2=A0 Counting them and reporting them v=
ia the management plane<br>
&gt;=C2=A0 =C2=A0 =C2=A0should also be allowed, and perhaps recommended.<br=
>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0Lou<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0_______________________________________________<br>
&gt;=C2=A0 =C2=A0 =C2=A0manet mailing list<br>
&gt;=C2=A0 =C2=A0 =C2=A0<a href=3D"mailto:manet@ietf.org">manet@ietf.org</a=
> &lt;mailto:<a href=3D"mailto:manet@ietf.org">manet@ietf.org</a>&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0<a href=3D"https://www.ietf.org/mailman/listinfo/ma=
net" rel=3D"noreferrer" target=3D"_blank">https://www.ietf.org/mailman/list=
info/manet</a><br>
&gt;<br>
&gt;<br>
<br>
<br>
</blockquote></div><br></div></div></div>

--001a114020ac23fae305267d669d--


From nobody Wed Dec  9 13:23:05 2015
Return-Path: <hrogge@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 4723F1A6F40; Wed,  9 Dec 2015 13:23:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 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, 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 qFP9jL1erel5; Wed,  9 Dec 2015 13:23:02 -0800 (PST)
Received: from mail-wm0-x22c.google.com (mail-wm0-x22c.google.com [IPv6:2a00:1450:400c:c09::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 72F761B2E06; Wed,  9 Dec 2015 13:21:53 -0800 (PST)
Received: by mail-wm0-x22c.google.com with SMTP id c201so4536543wme.0; Wed, 09 Dec 2015 13:21:53 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=pvGPC/qfX1zxF1taUe9IUFXqjsTk/1vbRM+0e05RGQI=; b=UHM3AQAhL/DwK7ZVqMmpwLVjJ6TaKRztNKQeuq294nAJjVw4OywMPWvkx7o7tR8D/f xOMvHDLtYukv0si/lLMlqyCUjCl8y67oMs87VgkUDo7yXSQxY908FCnvmHyr1GkGQLfa vxzyRYd48EWXsP6Rt0cdiiJN61703YewIzZhk39+D2fFGMJIAiF54+DExcUDDLMABlaI zc5E2vEMYHF/0gTW00oNAe+mBfLB0zAn59YrbtAaJxmnMXGPJHuKLhNGrm4jE4O/lo+W 1NnF6wXKi9CNfTW1VHD4neBBIPZsOubuiYEvke+p5IqPRaFa+Mf8j3Qds2z2Zs3wsAeh raTw==
X-Received: by 10.28.135.149 with SMTP id j143mr11916320wmd.37.1449696112074;  Wed, 09 Dec 2015 13:21:52 -0800 (PST)
MIME-Version: 1.0
Received: by 10.27.94.70 with HTTP; Wed, 9 Dec 2015 13:21:22 -0800 (PST)
In-Reply-To: <CALtoyo=JqgbqsBPo5jG-UzFR56qmAEk9zbtDBoLQUoJfcuooew@mail.gmail.com>
References: <56687AC2.9060801@labn.net> <CALtoyomCuki__fyNnhmYoKmBcrQSSuOPGgcg8N-txG1DSaUaAg@mail.gmail.com> <56689271.306@labn.net> <CALtoyo=JqgbqsBPo5jG-UzFR56qmAEk9zbtDBoLQUoJfcuooew@mail.gmail.com>
From: Henning Rogge <hrogge@gmail.com>
Date: Wed, 9 Dec 2015 22:21:22 +0100
Message-ID: <CAGnRvuqi14Hz2ge-QLt7drfF1k9PeG9Gyft4ERWtLv_PcC=KfA@mail.gmail.com>
To: Stan Ratliff <ratliffstan@gmail.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/RsneRfjUsGKzDZvye9GtQdVvljI>
Cc: MANET IETF <manet@ietf.org>, draft-ietf-manet-dlep@ietf.org
Subject: Re: [manet] DLEP-17: Handling of unknown / unexpected messages
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: <https://mailarchive.ietf.org/arch/browse/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: Wed, 09 Dec 2015 21:23:04 -0000

On Wed, Dec 9, 2015 at 10:01 PM, Stan Ratliff <ratliffstan@gmail.com> wrote:
> Lou,
>> Is there any real harm in letting the transaction time out?  It seems to
>> me will be a constantly bouncing session with nothing working, vs having
>> some base level of stable capability.
>
>
> First off, I have to back-track and retract what I said. It's sad when you
> don't correctly remember what's in your own document... ;-)  Section 4.1,
> last para states "DLEP transactions do not time out and are not
> cancellable." My profound apologies for mis-stating this earlier.
>
>>
>>
>> Do you object to changing the behavior?
>
>
> I need to be careful about which hat I'm wearing here - speaking just as a
> WG participant, and a person that's interested in DLEP, I think that the
> processing rules have gotten too restrictive - basically, on any error, the
> only answer is to activate the nuclear self-destruct device, and blow
> everything to kingdom-come. Just in my little-ole opinion, that's a tad
> harsh...
>
> As I mentioned earlier, this text was the result of much (too much)
> haggling, talking, and discussing of options. I feel like I was pretty much
> "in the rough" when the text was adopted; there are others on the list that
> I hope will comment. What I believe is that:
> 1. An invalid or mis-understood *message* needs to be countered with
> termination, since based on Section 4.1, the sender will have a transaction
> "hanging out in space" that will never time out, and can't be cancelled.
> 2. As to invalid *Data Items*, I think the rules should be loosened -
> specifically, I believe that "If an unrecognized, or unexpected message is
> received, or a received message contains unrecognized, invalid, or
> disallowed duplicate data items", then the receiving implementation should
> negatively acknowledge, with an appropriate status Data Item/error code.

I don't think there is a second good solution... when something goes
wrong, the endpoint (either radio or router) has no real way to know
what happened.

* Was the data stream malformed?
* Did the client mis-implement an extension (or forgot to announce one)?
* Alien Space Bats happend?

The only thing the endpoint knows that the communication coming from
the other side turned bad and cannot be trusted anymore.

The sending of the "session termination" is just nice window dressing
to give the other side a chance to quickly tear down its session data,
there is not much else to do except for dropping the session.

Henning Rogge


From nobody Wed Dec  9 13:27:41 2015
Return-Path: <lberger@labn.net>
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 EBB071B2DBD for <manet@ietfa.amsl.com>; Wed,  9 Dec 2015 13:27:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.457
X-Spam-Level: 
X-Spam-Status: No, score=-1.457 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, IP_NOT_FRIENDLY=0.334, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIM_INVALID=0.01] autolearn=no
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 FR8OEd9mmgms for <manet@ietfa.amsl.com>; Wed,  9 Dec 2015 13:27:40 -0800 (PST)
Received: from gproxy8-pub.mail.unifiedlayer.com (gproxy8-pub.mail.unifiedlayer.com [67.222.33.93]) by ietfa.amsl.com (Postfix) with SMTP id F2B531B2DAF for <manet@ietf.org>; Wed,  9 Dec 2015 13:27:39 -0800 (PST)
Received: (qmail 2071 invoked by uid 0); 9 Dec 2015 21:27:36 -0000
Received: from unknown (HELO cmgw2) (10.0.90.83) by gproxy8.mail.unifiedlayer.com with SMTP; 9 Dec 2015 21:27:36 -0000
Received: from box313.bluehost.com ([69.89.31.113]) by cmgw2 with  id rZTX1r00X2SSUrH01ZTal1; Wed, 09 Dec 2015 14:27:34 -0700
X-Authority-Analysis: v=2.1 cv=dqRIVTQ4 c=1 sm=1 tr=0 a=h1BC+oY+fLhyFmnTBx92Jg==:117 a=wU2YTnxGAAAA:8 a=cNaOj0WVAAAA:8 a=IkcTkHD0fZMA:10 a=-NfooI8aBGcA:10 a=uEJ9t1CZtbIA:10 a=wUQvQvOEmiQA:10 a=QOCz7gyBLQo1852GvXoA:9 a=QEXdDO2ut3YA:10
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=labn.net; s=default;  h=Content-Transfer-Encoding:Content-Type:In-Reply-To:MIME-Version:Date:Message-ID:From:Cc:References:To:Subject; bh=KqAnBzTMtMH/S0u9a1c6cr92AlCq9PoY1z3NGtbCq/w=;  b=r47VhHZAxLdL+GYVCxig66ihOY8kljgctBB3fnF6lQq+4Z1xvyaK9YntmdZFZ3YWNJT7dp089jnKYWgGqTBXQnDeabHLCHVMdLjCeWRk+EE0Pl6ccDj5GnMdhWKzw1uv;
Received: from box313.bluehost.com ([69.89.31.113]:51138 helo=[127.0.0.1]) by box313.bluehost.com with esmtpa (Exim 4.84) (envelope-from <lberger@labn.net>) id 1a6mGr-0008J8-8m; Wed, 09 Dec 2015 14:27:33 -0700
To: Henning Rogge <hrogge@gmail.com>, Stan Ratliff <ratliffstan@gmail.com>
References: <56687AC2.9060801@labn.net> <CALtoyomCuki__fyNnhmYoKmBcrQSSuOPGgcg8N-txG1DSaUaAg@mail.gmail.com> <56689271.306@labn.net> <CALtoyo=JqgbqsBPo5jG-UzFR56qmAEk9zbtDBoLQUoJfcuooew@mail.gmail.com> <CAGnRvuqi14Hz2ge-QLt7drfF1k9PeG9Gyft4ERWtLv_PcC=KfA@mail.gmail.com>
From: Lou Berger <lberger@labn.net>
Message-ID: <56689CC0.3020408@labn.net>
Date: Wed, 9 Dec 2015 16:27:28 -0500
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.4.0
MIME-Version: 1.0
In-Reply-To: <CAGnRvuqi14Hz2ge-QLt7drfF1k9PeG9Gyft4ERWtLv_PcC=KfA@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-Identified-User: {1038:box313.bluehost.com:labnmobi:labn.net} {sentby:smtp auth 69.89.31.113 authed with lberger@labn.net}
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/gOWcIfTf5jrnZ6udd0CNHsj3KPg>
Cc: MANET IETF <manet@ietf.org>, draft-ietf-manet-dlep@ietf.org
Subject: Re: [manet] DLEP-17: Handling of unknown / unexpected messages
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: <https://mailarchive.ietf.org/arch/browse/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: Wed, 09 Dec 2015 21:27:41 -0000

On 12/9/2015 4:21 PM, Henning Rogge wrote:
> The sending of the "session termination" is just nice window dressing
> to give the other side a chance to quickly tear down its session data,
> there is not much else to do except for dropping the session.

The problem is that this "window dressing" introduces limitations on
future compatibility/partial interoperability and vulnerabilities.  It
seems to me to be an unnecessary "optimization".

Lou
 


From nobody Wed Dec  9 13:33:02 2015
Return-Path: <hrogge@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 528071A86DD; Wed,  9 Dec 2015 13:33:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 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, 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 eilCLXtRAHGy; Wed,  9 Dec 2015 13:33:00 -0800 (PST)
Received: from mail-wm0-x235.google.com (mail-wm0-x235.google.com [IPv6:2a00:1450:400c:c09::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AF2661A7002; Wed,  9 Dec 2015 13:32:59 -0800 (PST)
Received: by wmec201 with SMTP id c201so92449787wme.1; Wed, 09 Dec 2015 13:32:58 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=vnjFXgJy0tGFQF/4yFsMzUb8uv76ey7eFJWVBCVJqfg=; b=SfSntIiCzvejO0HRMqUG/I6N2x+wtsL8+0MNQf21pF54iidfFaGKNMTJdPvgzBLEHj Bwqe3zAGDb3lQYBTzUoPU8xoTpHr6IT/im7WEL2ocmmSt9lTLAZ9nWoV2eFAmxVpe/Bp nlya6VGAb59zQ94vRTSldDfWQ/6oI2CYc1w5C7997FACRQ1npnA9N2UtYpG+b4OH4Dp0 i1dV/Yzyg696b4d4ucbrD9DOpJFyu+ebEPPXWr3WRtsgfCl2qL+mWtl1v4mDRN5mMjiW xvuAoCDNiTe7Y5/PWxmBKP+8jIahdWcJTa+9n22CXAAg2ffR5wCqMaqC/fHXa5sHaWJQ ob6g==
X-Received: by 10.28.141.17 with SMTP id p17mr13358744wmd.35.1449696778293; Wed, 09 Dec 2015 13:32:58 -0800 (PST)
MIME-Version: 1.0
Received: by 10.27.94.70 with HTTP; Wed, 9 Dec 2015 13:32:28 -0800 (PST)
In-Reply-To: <56689CC0.3020408@labn.net>
References: <56687AC2.9060801@labn.net> <CALtoyomCuki__fyNnhmYoKmBcrQSSuOPGgcg8N-txG1DSaUaAg@mail.gmail.com> <56689271.306@labn.net> <CALtoyo=JqgbqsBPo5jG-UzFR56qmAEk9zbtDBoLQUoJfcuooew@mail.gmail.com> <CAGnRvuqi14Hz2ge-QLt7drfF1k9PeG9Gyft4ERWtLv_PcC=KfA@mail.gmail.com> <56689CC0.3020408@labn.net>
From: Henning Rogge <hrogge@gmail.com>
Date: Wed, 9 Dec 2015 22:32:28 +0100
Message-ID: <CAGnRvuqQHzJge5PmjR3Z6ax3rSDxQG2xko6UA-CsO7BF9HQX2Q@mail.gmail.com>
To: Lou Berger <lberger@labn.net>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/RozEwC2AINLwyGzpnHagpmvp3aI>
Cc: MANET IETF <manet@ietf.org>, draft-ietf-manet-dlep@ietf.org
Subject: Re: [manet] DLEP-17: Handling of unknown / unexpected messages
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: <https://mailarchive.ietf.org/arch/browse/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: Wed, 09 Dec 2015 21:33:01 -0000

On Wed, Dec 9, 2015 at 10:27 PM, Lou Berger <lberger@labn.net> wrote:
> On 12/9/2015 4:21 PM, Henning Rogge wrote:
>> The sending of the "session termination" is just nice window dressing
>> to give the other side a chance to quickly tear down its session data,
>> there is not much else to do except for dropping the session.
>
> The problem is that this "window dressing" introduces limitations on
> future compatibility/partial interoperability and vulnerabilities.  It
> seems to me to be an unnecessary "optimization".

No, it does not.

Because you have to announce all your endpoints functionality in the
first Message (Peer Init/Peer Init Ack).

If you do something the other side does not understand after this your
implementation is defective.

Henning Rogge


From nobody Wed Dec  9 13:34:47 2015
Return-Path: <reller@cococorp.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 9AE751B2DB5 for <manet@ietfa.amsl.com>; Wed,  9 Dec 2015 13:34:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.378
X-Spam-Level: 
X-Spam-Status: No, score=-1.378 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=no
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 RmXNLhi9B5Hk for <manet@ietfa.amsl.com>; Wed,  9 Dec 2015 13:34:41 -0800 (PST)
Received: from mail-ig0-x22f.google.com (mail-ig0-x22f.google.com [IPv6:2607:f8b0:4001:c05::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 68BF91A86DD for <manet@ietf.org>; Wed,  9 Dec 2015 13:34:41 -0800 (PST)
Received: by igcto18 with SMTP id to18so50379525igc.0 for <manet@ietf.org>; Wed, 09 Dec 2015 13:34:40 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cococorp.com; s=google150814; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=hc7vhKe6v1+ehdCCHTBIroLooTlCCTfpNlbeIjNllTM=; b=e5dv7CWuXC8DSdzUrk70VWNJBoXyFqtuIjzOEauBmgUTy5iNkUG/DZ0tFXbVS85yAh qOuD7ilZCPPNEgzONMNoCysoZMcowp+CeT8iV+E+XIpybaP/gphHcM8n5VgdxGgph7Oa 2XPIsY2iu+7wqUAKrDJh9JMEvbRwNiqLqS8Lo=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=hc7vhKe6v1+ehdCCHTBIroLooTlCCTfpNlbeIjNllTM=; b=UL4jlwuxhd7b+T3brW1gNyFU03hlbBfaKYqRCeYvwTCa4sL+hpb2x19eJLBSHE4F1O 4RpfbmBhJiDe14a3S02gA8wBBnU8OylIQ9TtgX8vxn7HNE5Wv+gUtaTbWq1xUFXAUxwz DQ8tRb8OPXbpjpP9K5kcxa1plSR6U31YFACHeYWDnFNeXOY5gcqDSOW9FHJRp3acb8uL 4mNv6wX3rp4luZexNLEB0erXMAdbKV1PW5yB1c00yqJvhq6uZZcFEcDKiYuTwYZyKeHQ m7iQVIebdLbZafMlPohSdXlLT6JPLDWGZlB8dD9Ebgz6rS2X6WoqiFFs6FvoLZVMo8UN TQvQ==
X-Gm-Message-State: ALoCoQmBt0JS9meYNzrGbnRy1YEQqyOqMvlto+mDy9iDut0LkTEwtrKK5Wkz2ivZc8XV87LIR0YiyFe7ZyuQIeUI0offPBUlGA==
MIME-Version: 1.0
X-Received: by 10.50.112.102 with SMTP id ip6mr5539622igb.88.1449696880809; Wed, 09 Dec 2015 13:34:40 -0800 (PST)
Received: by 10.36.7.212 with HTTP; Wed, 9 Dec 2015 13:34:40 -0800 (PST)
In-Reply-To: <56689CC0.3020408@labn.net>
References: <56687AC2.9060801@labn.net> <CALtoyomCuki__fyNnhmYoKmBcrQSSuOPGgcg8N-txG1DSaUaAg@mail.gmail.com> <56689271.306@labn.net> <CALtoyo=JqgbqsBPo5jG-UzFR56qmAEk9zbtDBoLQUoJfcuooew@mail.gmail.com> <CAGnRvuqi14Hz2ge-QLt7drfF1k9PeG9Gyft4ERWtLv_PcC=KfA@mail.gmail.com> <56689CC0.3020408@labn.net>
Date: Wed, 9 Dec 2015 13:34:40 -0800
Message-ID: <CAN+0cZsEidsCUJdSyaQNG90Ky2CX3aORhzQ44_bDjN1qR4aevg@mail.gmail.com>
From: "A .Riley Eller" <reller@cococorp.com>
To: Lou Berger <lberger@labn.net>
Content-Type: multipart/alternative; boundary=047d7b4144709d1cbb05267ddb8b
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/WMiy0HR-SiLKO3yDcVpbWr5vEls>
Cc: MANET IETF <manet@ietf.org>, draft-ietf-manet-dlep@ietf.org
Subject: Re: [manet] DLEP-17: Handling of unknown / unexpected messages
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: <https://mailarchive.ietf.org/arch/browse/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: Wed, 09 Dec 2015 21:34:42 -0000

--047d7b4144709d1cbb05267ddb8b
Content-Type: text/plain; charset=UTF-8

(Hi all, long time reader.)

On Wed, Dec 9, 2015 at 1:27 PM, Lou Berger <lberger@labn.net> wrote:

>
> On 12/9/2015 4:21 PM, Henning Rogge wrote:
> > The sending of the "session termination" is just nice window dressing
> > to give the other side a chance to quickly tear down its session data,
> > there is not much else to do except for dropping the session.
>
> The problem is that this "window dressing" introduces limitations on
> future compatibility/partial interoperability and vulnerabilities.  It
> seems to me to be an unnecessary "optimization".
>

Perhaps I have lost track of the context of this thread, but isn't the
"session termination" response merely an unambiguous transfer of state in
the event of unsuccessful (and possibly partial) inter-operation? Each
party need a means to reset the other's expectation of shared context.

Riley

--047d7b4144709d1cbb05267ddb8b
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">(Hi =
all, long time reader.)<br></div><div class=3D"gmail_quote"><br></div><div =
class=3D"gmail_quote">On Wed, Dec 9, 2015 at 1:27 PM, Lou Berger <span dir=
=3D"ltr">&lt;<a href=3D"mailto:lberger@labn.net" target=3D"_blank">lberger@=
labn.net</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=
=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(20=
4,204,204);border-left-style:solid;padding-left:1ex"><span class=3D""><br>
On 12/9/2015 4:21 PM, Henning Rogge wrote:<br>
&gt; The sending of the &quot;session termination&quot; is just nice window=
 dressing<br>
&gt; to give the other side a chance to quickly tear down its session data,=
<br>
&gt; there is not much else to do except for dropping the session.<br>
<br>
</span>The problem is that this &quot;window dressing&quot; introduces limi=
tations on<br>
future compatibility/partial interoperability and vulnerabilities.=C2=A0 It=
<br>
seems to me to be an unnecessary &quot;optimization&quot;.<br></blockquote>=
<div><br></div><div>Perhaps I have lost track of the context of this thread=
, but isn&#39;t the &quot;session termination&quot; response merely an unam=
biguous transfer of state in the event of unsuccessful (and possibly partia=
l) inter-operation? Each party need a means to reset the other&#39;s expect=
ation of shared context.</div><div><br></div><div>Riley</div></div></div></=
div>

--047d7b4144709d1cbb05267ddb8b--


From nobody Wed Dec  9 13:52:55 2015
Return-Path: <ratliffstan@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 5F5291B2E58; Wed,  9 Dec 2015 13:52:53 -0800 (PST)
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 5vd5BxutBG3N; Wed,  9 Dec 2015 13:52:48 -0800 (PST)
Received: from mail-lf0-x234.google.com (mail-lf0-x234.google.com [IPv6:2a00:1450:4010:c07::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 03AA31B2E55; Wed,  9 Dec 2015 13:52:48 -0800 (PST)
Received: by lffu14 with SMTP id u14so44209513lff.1; Wed, 09 Dec 2015 13:52:46 -0800 (PST)
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=85JQzlVu16xEadIADI1fuWww+51L+nCfnK65OX3P17E=; b=U2q6rjx4d4XB8Xw8We3DxlfZbu8j7YwxtGa9LRbOGqX+pZoav7j4y8ET+N1+Iekneg 0eJNF5rF6WNekFWFKxD2bNcWm89H7tUhRIBMMhkteQ9G9nmxArp+aX1Nfds4C27/Hh2r kr3TLXsflK5AU2G0C88rckMZFouE4sRxEFcaLUD8ccbZKHUsmrEhWslRRUoVOYL2tAz6 rz8iBtnG9VPaT1wNtl/zdi6cXNCtzfXdHS/jaKnzmZHU6i6/oca7AGl8MEpsPcEg4Ty3 xyljWX5WKSRS21hP+XDDNcRl8jDpYbvb3SPA3c7DzokzP5hgTXBwEILp+QnlEF7OAtXh cOcw==
MIME-Version: 1.0
X-Received: by 10.25.43.138 with SMTP id r132mr3465436lfr.103.1449697964154; Wed, 09 Dec 2015 13:52:44 -0800 (PST)
Received: by 10.25.209.71 with HTTP; Wed, 9 Dec 2015 13:52:43 -0800 (PST)
In-Reply-To: <56689542.2080303@labn.net>
References: <56687ABA.803@labn.net> <CALtoyonnuk03=FqiyPfQS4t9mKJt81kUfkZP-JB0FD0hfRp-6Q@mail.gmail.com> <566888B0.3070806@labn.net> <CALtoyomO1YTNydyohqRczjHnivCkfPp_gwv5oRWjdRmC5yOb0Q@mail.gmail.com> <56689542.2080303@labn.net>
Date: Wed, 9 Dec 2015 16:52:43 -0500
Message-ID: <CALtoyomdxY8P4QgxDMgkkFg452f=rC70xKCJOEkpyJH8K+u9AA@mail.gmail.com>
From: Stan Ratliff <ratliffstan@gmail.com>
To: Lou Berger <lberger@labn.net>
Content-Type: multipart/alternative; boundary=001a113fadfc30dd0405267e1c18
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/NmVHZ1aPrgti4eMhzPApOQ5N9DA>
Cc: MANET IETF <manet@ietf.org>, draft-ietf-manet-dlep@ietf.org
Subject: Re: [manet] DLEP-17: duplicate functions - Options & extensions negotiations
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: <https://mailarchive.ietf.org/arch/browse/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: Wed, 09 Dec 2015 21:52:53 -0000

--001a113fadfc30dd0405267e1c18
Content-Type: text/plain; charset=UTF-8

Lou,


On Wed, Dec 9, 2015 at 3:55 PM, Lou Berger <lberger@labn.net> wrote:

> Stan,
>
>
> On 12/9/2015 3:14 PM, Stan Ratliff wrote:
> >
> >
> > On Wed, Dec 9, 2015 at 3:01 PM, Lou Berger <lberger@labn.net
> > <mailto:lberger@labn.net>> wrote:
> >
> >     Stan,
> >
> >     On 12/9/2015 2:20 PM, Stan Ratliff wrote:
> >     > Lou,
> >     >
> >     > On Wed, Dec 9, 2015 at 2:02 PM, Lou Berger <lberger@labn.net
> >     <mailto:lberger@labn.net>
> >     > <mailto:lberger@labn.net <mailto:lberger@labn.net>>> wrote:
> >     >
> >     >     Authors/WG,
> >     >
> >     >     The current version of DLEP contains two negotiations as
> >     part of a
> >     >     Session Initialization transaction:
> >     >     1) <Extensions Supported> is included in both the <Session
> >     >     Initialization> and <Session Initialization Response> messages
> >     >     2) the optional data items, <Resources> and <Relative Link
> >     Quality>
> >     >
> >     >     Both have parallel allocation policies:
> >     >
> >     >
> >     >
> >     +-------------+-----------------------------------------------------+
> >     >        | Type Code   | Description
> >     >          |
> >     >
> >     >
> >     +-------------+-----------------------------------------------------+
> >     >        | 0           | Reserved
> >     >         |
> >     >        | 1           | Status (Section 10.1)
> >     >          |
> >     >          ...
> >     >        | 20          | Relative Link Quality (Transmit) (RLQT)
> >     >     (Section    |
> >     >        | 21-65407    | Reserved for future extensions
> >     >         |
> >     >        | 65408-65534 | Private Use. Available for experiments
> >     >         |
> >     >        | 65535       | Reserved
> >     >         |
> >     >
> >     >
> >     +-------------+-----------------------------------------------------+
> >     >
> >     >                            Table 2: DLEP Data Item types
> >     >
> >     >
> >     >
> >     +-------------+-----------------------------------------------------+
> >     >        | Code        | Description
> >     >          |
> >     >
> >     >
> >     +-------------+-----------------------------------------------------+
> >     >        | 0           | Reserved
> >     >         |
> >     >        | 1           | Credit Windowing
> >     >         |
> >     >        | 2-65519     | Reserved for future extensions
> >     >         |
> >     >        | 65520-65534 | Private Use. Available for experiments
> >     >         |
> >     >        | 65535       | Reserved
> >     >         |
> >     >
> >     >
> >     +-------------+-----------------------------------------------------+
> >     >
> >     >                            Table 4: DLEP Extension types
> >     >
> >     >     It seems to me that given the current definition, one of
> >     these two
> >     >     should suffice.  I don't have a strong opinion on which, but do
> >     >     strongly
> >     >     believe that a single approach should be selected to facilitate
> >     >     interoperability.
> >     >
> >     >
> >     > Well, I disagree. Extensions defines a process whereby multiple
> data
> >     > items, and/or new *messages*, can be added to DLEP. The other
> >     two data
> >     > items you mention (Resources and Link Quality) are just optional
> >     (not
> >     > required) metrics. They are two different things.
> >
> >     I understand that their motivation is different, but the end result
> is
> >     that code needs to be written (and tested!) to cover both.  So if
> >     there's a way to eliminate two ways to do the same function, it's
> good
> >     design to do so.
> >
> >
> > An implementation can chose to not support an extension. An
> > implementation can also chose not to support Resources and/or Link
> > Quality. I guess I'm missing something, because I'm not following this
> > line of logic. If you want to use the extension, or the extra metrics,
> > then great - write and test the code. If you don't, that's great, too.
>
> The point is there are different mechanisms that essentially do the same
> function, so why not use one?
>
> e.g., to indicate use of Resources and/or Link Quality, they are
> included in the Session Init Response. (Which parallels use optional
> data items in other messages.)  but to indicate use of Credit data
> items, an extension value is used.
>
> My point is that rather than coding two ways of 'negotiating' use of
> options, it would be easier to define/use just one.
>


The point of putting the metrics in the Session Init/Session Init ACK
sequence was two-fold:  (1) to announce metrics in use for this radio, and
(2) to provide radio-specific defaults for those metrics. That way,
subsequent DLEP messages could focus only on metrics that had changed.
That's all documented in Section 3. So it wasn't really a negotiation, it
was an announcement and initialization of the metric values.

In the case of credit windowing, the same "announcement and init" notion
could apply, but in general, I'm opposed to just listing all Data Items in
the Session Init/Session Init ACK sequence - future, documented
enhancements to the protocol is what Extensions is for. But thinking about
this *did* lead me to something I perceive as a problem with the protocol:

Let's assume that someone comes up with an Extension that is a collection
of metric data items. Theoretically, that set of metric items would be
documented in the WG, discussed, approved, and a registry entry assigned.
So far, so good. But, on initialization, implementations would need to:
1. Announce support for the extension, via the "Extensions Supported" data
item, *and*
2. Announce the defaults, by plopping the new data items into the Session
Init/Session Init ACK sequence.

But, since there are *no* restrictions on ordering of Data Items in the
messages, I could well encounter the defaults *before* I encounter the
Extensions Supported data item - hence, I may (or may not) recognize those
new default metric data items as valid...

To clean up the misunderstanding, I propose that we add a new message (and
the corresponding ACK) to the sequence. Default metrics would be removed
from the Session Init/Session Init ACK sequence. After that exchange, the
modem issues the new message (I propose calling it the Session Metric
Initialization message) with the defaults for the metrics to be used. That
message is acknowledged, and then the router and modem drop into the
"In-Session" state.

Oh, and we can (and I think we should) remove the restrictions on what
metric items are MANDATORY... If an implementation receives the Session
Metric Initialization message, and it (for example) indicates "I'm only
going to use Resources-Transmit", there needs to be a status code for
"Well, in that case, you are a silly implementation, and I will not
continue with you". Followed, of course, by Session Termination.

WG participants? Thoughts? Flames?

Regards,
Stan






>
> >
> >
> >
> >     >
> >     >
> >     >
> >     >     To be clear, the following spells out the options:
> >     >
> >     >     Option A: Extensions (aka capabilities) based
> >     >       Any optional or new data item or message would need to be
> >     indicated
> >     >       in <Extensions Supported> to be used.  To cover the
> >     current optional
> >     >       data items the following would need to be defined:
> >     >         | 1 | Resources |
> >     >         | 2 | Relative Link Quality |
> >     >         | 3 | Credit Windowing |
> >     >       <Session Initialization Response> could still contain the
> >     optional
> >     >       data items, if the corresponding type is present in
> >     <Extensions
> >     >       Supported>
> >     >
> >     >       Note that other messages will still use optional data items.
> >     >
> >     >     Option B: Data item based.
> >     >       An optional or new data item must be both Session
> >     Initialization
> >     >       messages to be used. To allow/enable <Resources> and
> >     <Relative Link
> >     >       Quality>, they would need to be included in both the <Session
> >     >       Initialization> and <Session Initialization Response>
> >     messages.
> >     >
> >     >       To enable the Credit Windowing extension, the three
> >     credit-related
> >     >       state items, <Grant>, <Window Status>, and <Request> would
> >     need
> >     >     to be
> >     >       included in both session init messages for the full
> >     extension to be
> >     >       used.
> >     >
> >     >     Option C: keep both
> >     >       Keep current text
> >     >
> >     >     While I like Option A and have seen similar approaches in other
> >     >     protocols, e.g., BGP Capabilities, I actually have a slight
> >     preference
> >     >     for B.  The reason for this is DLEP uses optional data items
> >     in other
> >     >     places and implementations will already need to handle this,
> >     so it
> >     >     seems
> >     >     like option B will probably require smaller incremental code.
> >     >
> >     >     Either way, I think Option C is much less desirable then
> >     either of the
> >     >     other options.
> >     >
> >     >     Thoughts? Opinions?
> >     >
> >     >
> >     > Before I did that, I'd be more inclined to pursue an "Option D":
> >     > 1. All of the metric data items (e.g. - MDRR, MDRT, CDRR, CDRT,
> >     > Latency, RLQR, RLQT, RESR, REST) are listed, with no mention as to
> >     > whether they are mandatory or optional - they are just the pool of
> >     > metrics that MAY be used by an implementation.
> >
> >     Right, and this means that implementations need to dynamically track
> >     which data items are in use on a per session, destination, and IP
> >     basis.  This is a fair bit of mechanism already, and exactly why (a)
> I
> >     raised this topic and (b) favor Option B.
> >
> >
> > The current draft states that all metrics supported MUST be announced
> > at the peer level. I don't see a need to dynamically track at the
> > destination level, and we really don't have an IP basis.
> >
> Not that it's critical, but if the destination mac is of the router and
> they are always announced/updated together, you essentially do.
>
> >
> >     > 2. In the Peer Init/Peer Init ACK, the peers list the metrics
> >     from the
> >     > available set that they are going to use. If peers cannot agree,
> the
> >     > session doesn't get established.
> >
> >     Peer = session and ACK = response, right?  Yup, this is why I say use
> >     this same mechanism for future extension too.  Again, different
> >     motivation doesn't have to mean different mechanisms.
> >
> >
> > If what you're advocating is that all optional, and extension-based,
> > data items be announced in the Peer exchange, then my question would be
> This is option B.
>
> > - what about new, extension-based messages?
> Then either it can be implicit based on a negotiated data item, or less
> cleanly, it can just be sent and ignored.
>
> Lou
>
> >
> > Regards,
> > Stan
> >
> >
> >
> >
> >     Lou
> >
> >     >
> >     > ... and we're done. Again, the Extensions stuff is for new data
> >     > items/messages that might come along (with Credit Windowing
> >     being the
> >     > first).
> >     >
> >     > Regards,
> >     > Stan
> >     >
> >     >
> >     >
> >     >
> >     >     Lou
> >     >
> >     >     _______________________________________________
> >     >     manet mailing list
> >     >     manet@ietf.org <mailto:manet@ietf.org>
> >     <mailto:manet@ietf.org <mailto:manet@ietf.org>>
> >     >     https://www.ietf.org/mailman/listinfo/manet
> >     >
> >     >
> >
> >
> >
>
>
>

--001a113fadfc30dd0405267e1c18
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Lou,<div><br><div class=3D"gmail_extra"><br><div class=3D"=
gmail_quote">On Wed, Dec 9, 2015 at 3:55 PM, Lou Berger <span dir=3D"ltr">&=
lt;<a href=3D"mailto:lberger@labn.net" target=3D"_blank">lberger@labn.net</=
a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0=
 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Stan,<br>
<br>
<br>
On 12/9/2015 3:14 PM, Stan Ratliff wrote:<br>
&gt;<br>
&gt;<br>
&gt; On Wed, Dec 9, 2015 at 3:01 PM, Lou Berger &lt;<a href=3D"mailto:lberg=
er@labn.net">lberger@labn.net</a><br>
&gt; &lt;mailto:<a href=3D"mailto:lberger@labn.net">lberger@labn.net</a>&gt=
;&gt; wrote:<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0Stan,<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0On 12/9/2015 2:20 PM, Stan Ratliff wrote:<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; Lou,<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; On Wed, Dec 9, 2015 at 2:02 PM, Lou Berger &lt=
;<a href=3D"mailto:lberger@labn.net">lberger@labn.net</a><br>
&gt;=C2=A0 =C2=A0 =C2=A0&lt;mailto:<a href=3D"mailto:lberger@labn.net">lber=
ger@labn.net</a>&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; &lt;mailto:<a href=3D"mailto:lberger@labn.net"=
>lberger@labn.net</a> &lt;mailto:<a href=3D"mailto:lberger@labn.net">lberge=
r@labn.net</a>&gt;&gt;&gt; wrote:<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0Authors/WG,<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0The current version of DLEP=
 contains two negotiations as<br>
&gt;=C2=A0 =C2=A0 =C2=A0part of a<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0Session Initialization tran=
saction:<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A01) &lt;Extensions Supported=
&gt; is included in both the &lt;Session<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0Initialization&gt; and &lt;=
Session Initialization Response&gt; messages<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A02) the optional data items,=
 &lt;Resources&gt; and &lt;Relative Link<br>
&gt;=C2=A0 =C2=A0 =C2=A0Quality&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0Both have parallel allocati=
on policies:<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0+-------------+------------------------------------=
-----------------+<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 | Type Code=C2=A0 =
=C2=A0| Description<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 |<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0+-------------+------------------------------------=
-----------------+<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 | 0=C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0| Reserved<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0|<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 | 1=C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0| Status (Section 10.1)<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 |<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 ...<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 | 20=C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 | Relative Link Quality (Transmit) (RLQT)<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0(Section=C2=A0 =C2=A0 |<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 | 21-65407=C2=A0 =
=C2=A0 | Reserved for future extensions<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0|<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 | 65408-65534 | Pri=
vate Use. Available for experiments<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0|<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 | 65535=C2=A0 =C2=
=A0 =C2=A0 =C2=A0| Reserved<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0|<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0+-------------+------------------------------------=
-----------------+<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Table 2: DLEP Data Ite=
m types<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0+-------------+------------------------------------=
-----------------+<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 | Code=C2=A0 =C2=A0=
 =C2=A0 =C2=A0 | Description<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 |<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0+-------------+------------------------------------=
-----------------+<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 | 0=C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0| Reserved<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0|<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 | 1=C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0| Credit Windowing<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0|<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 | 2-65519=C2=A0 =C2=
=A0 =C2=A0| Reserved for future extensions<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0|<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 | 65520-65534 | Pri=
vate Use. Available for experiments<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0|<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 | 65535=C2=A0 =C2=
=A0 =C2=A0 =C2=A0| Reserved<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0|<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0+-------------+------------------------------------=
-----------------+<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Table 4: DLEP Extensio=
n types<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0It seems to me that given t=
he current definition, one of<br>
&gt;=C2=A0 =C2=A0 =C2=A0these two<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0should suffice.=C2=A0 I don=
&#39;t have a strong opinion on which, but do<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0strongly<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0believe that a single appro=
ach should be selected to facilitate<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0interoperability.<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; Well, I disagree. Extensions defines a process=
 whereby multiple data<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; items, and/or new *messages*, can be added to =
DLEP. The other<br>
&gt;=C2=A0 =C2=A0 =C2=A0two data<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; items you mention (Resources and Link Quality)=
 are just optional<br>
&gt;=C2=A0 =C2=A0 =C2=A0(not<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; required) metrics. They are two different thin=
gs.<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0I understand that their motivation is different, bu=
t the end result is<br>
&gt;=C2=A0 =C2=A0 =C2=A0that code needs to be written (and tested!) to cove=
r both.=C2=A0 So if<br>
&gt;=C2=A0 =C2=A0 =C2=A0there&#39;s a way to eliminate two ways to do the s=
ame function, it&#39;s good<br>
&gt;=C2=A0 =C2=A0 =C2=A0design to do so.<br>
&gt;<br>
&gt;<br>
&gt; An implementation can chose to not support an extension. An<br>
&gt; implementation can also chose not to support Resources and/or Link<br>
&gt; Quality. I guess I&#39;m missing something, because I&#39;m not follow=
ing this<br>
&gt; line of logic. If you want to use the extension, or the extra metrics,=
<br>
&gt; then great - write and test the code. If you don&#39;t, that&#39;s gre=
at, too.<br>
<br>
The point is there are different mechanisms that essentially do the same<br=
>
function, so why not use one?<br>
<br>
e.g., to indicate use of Resources and/or Link Quality, they are<br>
included in the Session Init Response. (Which parallels use optional<br>
data items in other messages.)=C2=A0 but to indicate use of Credit data<br>
items, an extension value is used.<br>
<br>
My point is that rather than coding two ways of &#39;negotiating&#39; use o=
f<br>
options, it would be easier to define/use just one.<br></blockquote><div><b=
r></div><div><br></div><div>The point of putting the metrics in the Session=
 Init/Session Init ACK sequence was two-fold: =C2=A0(1) to announce metrics=
 in use for this radio, and (2) to provide radio-specific defaults for thos=
e metrics. That way, subsequent DLEP messages could focus only on metrics t=
hat had changed. That&#39;s all documented in Section 3. So it wasn&#39;t r=
eally a negotiation, it was an announcement and initialization of the metri=
c values.=C2=A0</div><div><br></div><div>In the case of credit windowing, t=
he same &quot;announcement and init&quot; notion could apply, but in genera=
l, I&#39;m opposed to just listing all Data Items in the Session Init/Sessi=
on Init ACK sequence - future, documented enhancements to the protocol is w=
hat Extensions is for. But thinking about this *did* lead me to something I=
 perceive as a problem with the protocol:=C2=A0</div><div><br></div><div>Le=
t&#39;s assume that someone comes up with an Extension that is a collection=
 of metric data items. Theoretically, that set of metric items would be doc=
umented in the WG, discussed, approved, and a registry entry assigned. So f=
ar, so good. But, on initialization, implementations would need to:=C2=A0</=
div><div>1. Announce support for the extension, via the &quot;Extensions Su=
pported&quot; data item, *and*</div><div>2. Announce the defaults, by plopp=
ing the new data items into the Session Init/Session Init ACK sequence.=C2=
=A0</div><div><br></div><div>But, since there are *no* restrictions on orde=
ring of Data Items in the messages, I could well encounter the defaults *be=
fore* I encounter the Extensions Supported data item - hence, I may (or may=
 not) recognize those new default metric data items as valid...=C2=A0</div>=
<div><br></div><div>To clean up the misunderstanding, I propose that we add=
 a new message (and the corresponding ACK) to the sequence. Default metrics=
 would be removed from the Session Init/Session Init ACK sequence. After th=
at exchange, the modem issues the new message (I propose calling it the Ses=
sion Metric Initialization message) with the defaults for the metrics to be=
 used. That message is acknowledged, and then the router and modem drop int=
o the &quot;In-Session&quot; state.=C2=A0</div><div><br></div><div>Oh, and =
we can (and I think we should) remove the restrictions on what metric items=
 are MANDATORY... If an implementation receives the Session Metric Initiali=
zation message, and it (for example) indicates &quot;I&#39;m only going to =
use Resources-Transmit&quot;, there needs to be a status code for &quot;Wel=
l, in that case, you are a silly implementation, and I will not continue wi=
th you&quot;. Followed, of course, by Session Termination.</div><div><br></=
div><div>WG participants? Thoughts? Flames?=C2=A0</div><div><br></div><div>=
Regards,</div><div>Stan</div><div><br></div><div><br></div><div><br></div><=
div><br></div><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"m=
argin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0To be clear, the following =
spells out the options:<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0Option A: Extensions (aka c=
apabilities) based<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0Any optional or new =
data item or message would need to be<br>
&gt;=C2=A0 =C2=A0 =C2=A0indicated<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0in &lt;Extensions Su=
pported&gt; to be used.=C2=A0 To cover the<br>
&gt;=C2=A0 =C2=A0 =C2=A0current optional<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0data items the follo=
wing would need to be defined:<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0| 1 | Resourc=
es |<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0| 2 | Relativ=
e Link Quality |<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0| 3 | Credit =
Windowing |<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0&lt;Session Initiali=
zation Response&gt; could still contain the<br>
&gt;=C2=A0 =C2=A0 =C2=A0optional<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0data items, if the c=
orresponding type is present in<br>
&gt;=C2=A0 =C2=A0 =C2=A0&lt;Extensions<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0Supported&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0Note that other mess=
ages will still use optional data items.<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0Option B: Data item based.<=
br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0An optional or new d=
ata item must be both Session<br>
&gt;=C2=A0 =C2=A0 =C2=A0Initialization<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0messages to be used.=
 To allow/enable &lt;Resources&gt; and<br>
&gt;=C2=A0 =C2=A0 =C2=A0&lt;Relative Link<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0Quality&gt;, they wo=
uld need to be included in both the &lt;Session<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0Initialization&gt; a=
nd &lt;Session Initialization Response&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0messages.<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0To enable the Credit=
 Windowing extension, the three<br>
&gt;=C2=A0 =C2=A0 =C2=A0credit-related<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0state items, &lt;Gra=
nt&gt;, &lt;Window Status&gt;, and &lt;Request&gt; would<br>
&gt;=C2=A0 =C2=A0 =C2=A0need<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0to be<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0included in both ses=
sion init messages for the full<br>
&gt;=C2=A0 =C2=A0 =C2=A0extension to be<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0used.<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0Option C: keep both<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0Keep current text<br=
>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0While I like Option A and h=
ave seen similar approaches in other<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0protocols, e.g., BGP Capabi=
lities, I actually have a slight<br>
&gt;=C2=A0 =C2=A0 =C2=A0preference<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0for B.=C2=A0 The reason for=
 this is DLEP uses optional data items<br>
&gt;=C2=A0 =C2=A0 =C2=A0in other<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0places and implementations =
will already need to handle this,<br>
&gt;=C2=A0 =C2=A0 =C2=A0so it<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0seems<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0like option B will probably=
 require smaller incremental code.<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0Either way, I think Option =
C is much less desirable then<br>
&gt;=C2=A0 =C2=A0 =C2=A0either of the<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0other options.<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0Thoughts? Opinions?<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; Before I did that, I&#39;d be more inclined to=
 pursue an &quot;Option D&quot;:<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; 1. All of the metric data items (e.g. - MDRR, =
MDRT, CDRR, CDRT,<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; Latency, RLQR, RLQT, RESR, REST) are listed, w=
ith no mention as to<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; whether they are mandatory or optional - they =
are just the pool of<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; metrics that MAY be used by an implementation.=
<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0Right, and this means that implementations need to =
dynamically track<br>
&gt;=C2=A0 =C2=A0 =C2=A0which data items are in use on a per session, desti=
nation, and IP<br>
&gt;=C2=A0 =C2=A0 =C2=A0basis.=C2=A0 This is a fair bit of mechanism alread=
y, and exactly why (a) I<br>
&gt;=C2=A0 =C2=A0 =C2=A0raised this topic and (b) favor Option B.<br>
&gt;<br>
&gt;<br>
&gt; The current draft states that all metrics supported MUST be announced<=
br>
&gt; at the peer level. I don&#39;t see a need to dynamically track at the<=
br>
&gt; destination level, and we really don&#39;t have an IP basis.<br>
&gt;<br>
Not that it&#39;s critical, but if the destination mac is of the router and=
<br>
they are always announced/updated together, you essentially do.<br>
<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; 2. In the Peer Init/Peer Init ACK, the peers l=
ist the metrics<br>
&gt;=C2=A0 =C2=A0 =C2=A0from the<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; available set that they are going to use. If p=
eers cannot agree, the<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; session doesn&#39;t get established.<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0Peer =3D session and ACK =3D response, right?=C2=A0=
 Yup, this is why I say use<br>
&gt;=C2=A0 =C2=A0 =C2=A0this same mechanism for future extension too.=C2=A0=
 Again, different<br>
&gt;=C2=A0 =C2=A0 =C2=A0motivation doesn&#39;t have to mean different mecha=
nisms.<br>
&gt;<br>
&gt;<br>
&gt; If what you&#39;re advocating is that all optional, and extension-base=
d,<br>
&gt; data items be announced in the Peer exchange, then my question would b=
e<br>
This is option B.<br>
<br>
&gt; - what about new, extension-based messages?<br>
Then either it can be implicit based on a negotiated data item, or less<br>
cleanly, it can just be sent and ignored.<br>
<br>
Lou<br>
<br>
&gt;<br>
&gt; Regards,<br>
&gt; Stan<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0Lou<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; ... and we&#39;re done. Again, the Extensions =
stuff is for new data<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; items/messages that might come along (with Cre=
dit Windowing<br>
&gt;=C2=A0 =C2=A0 =C2=A0being the<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; first).<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; Regards,<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; Stan<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0Lou<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0___________________________=
____________________<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0manet mailing list<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0<a href=3D"mailto:manet@iet=
f.org">manet@ietf.org</a> &lt;mailto:<a href=3D"mailto:manet@ietf.org">mane=
t@ietf.org</a>&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0&lt;mailto:<a href=3D"mailto:manet@ietf.org">manet@=
ietf.org</a> &lt;mailto:<a href=3D"mailto:manet@ietf.org">manet@ietf.org</a=
>&gt;&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0<a href=3D"https://www.ietf=
.org/mailman/listinfo/manet" rel=3D"noreferrer" target=3D"_blank">https://w=
ww.ietf.org/mailman/listinfo/manet</a><br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
<br>
<br>
</blockquote></div><br></div></div></div>

--001a113fadfc30dd0405267e1c18--


From nobody Wed Dec  9 14:01:15 2015
Return-Path: <hrogge@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 B3EB81A882D; Wed,  9 Dec 2015 14:01:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 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, 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 LK20xz-hV8fD; Wed,  9 Dec 2015 14:01:12 -0800 (PST)
Received: from mail-wm0-x22c.google.com (mail-wm0-x22c.google.com [IPv6:2a00:1450:400c:c09::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3AD1F1B2E72; Wed,  9 Dec 2015 14:01:01 -0800 (PST)
Received: by wmww144 with SMTP id w144so140561wmw.0; Wed, 09 Dec 2015 14:00:59 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=PD3OKzH+UOuf4cFL1yKWHp7aj+lW2OtWD/9izGCWIC0=; b=viZXWSvq6EHgSHkRdwGUnh302UJ6No0wPEgsEhIvZBmErZCU96/Q8rwCTmxn6s9zpy w8kPJhpf/w50mKGYI6y2gL0wBxcsLzAqrPM0UMhmN1Z1kKxTrwtR7mLLSXZfCVcfOEZ5 GJb2uZcQBxWsuTQyYPuFrKDIgOQeVs8C4URadJMZzfVafqzjXWJoBZp5hflRFCR0D+PF ZWKrL0CNO2DjTyJh9JjSHfDBV3IQ2llyWjMxkGTjwhaMLp4BCSpfoagMlNjCQsfs3PU6 a5ojkwTNANOrja2KwBfLeisLtwPWdHITqykZj4O3ELovlSEGdb+BhD14ziXSPLJxq/+s IH9A==
X-Received: by 10.28.135.149 with SMTP id j143mr12067391wmd.37.1449698459842;  Wed, 09 Dec 2015 14:00:59 -0800 (PST)
MIME-Version: 1.0
Received: by 10.27.94.70 with HTTP; Wed, 9 Dec 2015 14:00:30 -0800 (PST)
In-Reply-To: <CALtoyomdxY8P4QgxDMgkkFg452f=rC70xKCJOEkpyJH8K+u9AA@mail.gmail.com>
References: <56687ABA.803@labn.net> <CALtoyonnuk03=FqiyPfQS4t9mKJt81kUfkZP-JB0FD0hfRp-6Q@mail.gmail.com> <566888B0.3070806@labn.net> <CALtoyomO1YTNydyohqRczjHnivCkfPp_gwv5oRWjdRmC5yOb0Q@mail.gmail.com> <56689542.2080303@labn.net> <CALtoyomdxY8P4QgxDMgkkFg452f=rC70xKCJOEkpyJH8K+u9AA@mail.gmail.com>
From: Henning Rogge <hrogge@gmail.com>
Date: Wed, 9 Dec 2015 23:00:30 +0100
Message-ID: <CAGnRvuofzTvTjNWq2d9oA+0Cxpy8mnRc6mkpuKnLp0LLsb7M-A@mail.gmail.com>
To: Stan Ratliff <ratliffstan@gmail.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/Xsx5yhzUyxZZjfzbgjmPs3HogeE>
Cc: MANET IETF <manet@ietf.org>, draft-ietf-manet-dlep@ietf.org
Subject: Re: [manet] DLEP-17: duplicate functions - Options & extensions negotiations
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: <https://mailarchive.ietf.org/arch/browse/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: Wed, 09 Dec 2015 22:01:14 -0000

On Wed, Dec 9, 2015 at 10:52 PM, Stan Ratliff <ratliffstan@gmail.com> wrote:
> The point of putting the metrics in the Session Init/Session Init ACK
> sequence was two-fold:  (1) to announce metrics in use for this radio, and
> (2) to provide radio-specific defaults for those metrics. That way,
> subsequent DLEP messages could focus only on metrics that had changed.
> That's all documented in Section 3. So it wasn't really a negotiation, it
> was an announcement and initialization of the metric values.
>
> In the case of credit windowing, the same "announcement and init" notion
> could apply, but in general, I'm opposed to just listing all Data Items in
> the Session Init/Session Init ACK sequence - future, documented enhancements
> to the protocol is what Extensions is for. But thinking about this *did*
> lead me to something I perceive as a problem with the protocol:
>
> Let's assume that someone comes up with an Extension that is a collection of
> metric data items. Theoretically, that set of metric items would be
> documented in the WG, discussed, approved, and a registry entry assigned. So
> far, so good. But, on initialization, implementations would need to:
> 1. Announce support for the extension, via the "Extensions Supported" data
> item, *and*
> 2. Announce the defaults, by plopping the new data items into the Session
> Init/Session Init ACK sequence.
>
> But, since there are *no* restrictions on ordering of Data Items in the
> messages, I could well encounter the defaults *before* I encounter the
> Extensions Supported data item - hence, I may (or may not) recognize those
> new default metric data items as valid...

A TLV (type length value) parser should not depend on the order of the TLVs...

so either you have to temporarily store all default metrics, or you
just do a two-stage parsing of the same message.

> To clean up the misunderstanding, I propose that we add a new message (and
> the corresponding ACK) to the sequence. Default metrics would be removed
> from the Session Init/Session Init ACK sequence. After that exchange, the
> modem issues the new message (I propose calling it the Session Metric
> Initialization message) with the defaults for the metrics to be used. That
> message is acknowledged, and then the router and modem drop into the
> "In-Session" state.
>
> Oh, and we can (and I think we should) remove the restrictions on what
> metric items are MANDATORY... If an implementation receives the Session
> Metric Initialization message, and it (for example) indicates "I'm only
> going to use Resources-Transmit", there needs to be a status code for "Well,
> in that case, you are a silly implementation, and I will not continue with
> you". Followed, of course, by Session Termination.

We only have a few mandatory metrics (link speed related things,
right?)... I am not sure I am good with dropping them too.

This gives a router at least a chance to determine what this radio is
useful for.

Henning Rogge


From nobody Wed Dec  9 14:09:31 2015
Return-Path: <ratliffstan@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 693D11B2E8D; Wed,  9 Dec 2015 14:09:30 -0800 (PST)
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 Y8Ppb8kVwVOy; Wed,  9 Dec 2015 14:09:23 -0800 (PST)
Received: from mail-lf0-x22d.google.com (mail-lf0-x22d.google.com [IPv6:2a00:1450:4010:c07::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8E9A71B2CD4; Wed,  9 Dec 2015 14:09:10 -0800 (PST)
Received: by lfaz4 with SMTP id z4so44421246lfa.0; Wed, 09 Dec 2015 14:09:08 -0800 (PST)
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=tuKeCmSScWTYVKGlkwTOX+H3tcbnfZy8DqE6zgDhYAU=; b=j2AyYXYBbz+JwKMLJtBXxj83Vwt5sP/SeqOjxNccn7g89a6bQwttHZ5T0JJaV4vf7+ jZMp0tZbhZbrxHzqBBuSlierPiSurg9qTMQodReY50dde6T6H0wFlLCqrdADRE0cjox1 tWdKEfz3ITii6I/sXnHbugPyACSoTjX11JPhS34QFK3+T2yDSwr9FtiJvHOpQXuM8OKN mauzQn3bBpOpiO4Uizjay/V1KxV9+X6LfSHrmhVamvCDCM325gip94zIYhHLlsTx3Xqw ki64oHfcSBrqco/9fBBBRGgSULSxIcM613f2hdf8+8VXpxZmqfWurSKVmi0iIA9MndHR zYoA==
MIME-Version: 1.0
X-Received: by 10.25.152.133 with SMTP id a127mr3519619lfe.152.1449698948737;  Wed, 09 Dec 2015 14:09:08 -0800 (PST)
Received: by 10.25.209.71 with HTTP; Wed, 9 Dec 2015 14:09:08 -0800 (PST)
In-Reply-To: <CAGnRvuofzTvTjNWq2d9oA+0Cxpy8mnRc6mkpuKnLp0LLsb7M-A@mail.gmail.com>
References: <56687ABA.803@labn.net> <CALtoyonnuk03=FqiyPfQS4t9mKJt81kUfkZP-JB0FD0hfRp-6Q@mail.gmail.com> <566888B0.3070806@labn.net> <CALtoyomO1YTNydyohqRczjHnivCkfPp_gwv5oRWjdRmC5yOb0Q@mail.gmail.com> <56689542.2080303@labn.net> <CALtoyomdxY8P4QgxDMgkkFg452f=rC70xKCJOEkpyJH8K+u9AA@mail.gmail.com> <CAGnRvuofzTvTjNWq2d9oA+0Cxpy8mnRc6mkpuKnLp0LLsb7M-A@mail.gmail.com>
Date: Wed, 9 Dec 2015 17:09:08 -0500
Message-ID: <CALtoyomqbnTJer9ekYLZ1sseFRbVv19pNXR+Y7pridCGPghejA@mail.gmail.com>
From: Stan Ratliff <ratliffstan@gmail.com>
To: Henning Rogge <hrogge@gmail.com>
Content-Type: multipart/alternative; boundary=001a114020acdef43905267e566e
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/hlLcJ-0TBOOao7MhHbr_hvifHbk>
Cc: MANET IETF <manet@ietf.org>, draft-ietf-manet-dlep@ietf.org
Subject: Re: [manet] DLEP-17: duplicate functions - Options & extensions negotiations
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: <https://mailarchive.ietf.org/arch/browse/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: Wed, 09 Dec 2015 22:09:30 -0000

--001a114020acdef43905267e566e
Content-Type: text/plain; charset=UTF-8

On Wed, Dec 9, 2015 at 5:00 PM, Henning Rogge <hrogge@gmail.com> wrote:

> On Wed, Dec 9, 2015 at 10:52 PM, Stan Ratliff <ratliffstan@gmail.com>
> wrote:
> > The point of putting the metrics in the Session Init/Session Init ACK
> > sequence was two-fold:  (1) to announce metrics in use for this radio,
> and
> > (2) to provide radio-specific defaults for those metrics. That way,
> > subsequent DLEP messages could focus only on metrics that had changed.
> > That's all documented in Section 3. So it wasn't really a negotiation, it
> > was an announcement and initialization of the metric values.
> >
> > In the case of credit windowing, the same "announcement and init" notion
> > could apply, but in general, I'm opposed to just listing all Data Items
> in
> > the Session Init/Session Init ACK sequence - future, documented
> enhancements
> > to the protocol is what Extensions is for. But thinking about this *did*
> > lead me to something I perceive as a problem with the protocol:
> >
> > Let's assume that someone comes up with an Extension that is a
> collection of
> > metric data items. Theoretically, that set of metric items would be
> > documented in the WG, discussed, approved, and a registry entry
> assigned. So
> > far, so good. But, on initialization, implementations would need to:
> > 1. Announce support for the extension, via the "Extensions Supported"
> data
> > item, *and*
> > 2. Announce the defaults, by plopping the new data items into the Session
> > Init/Session Init ACK sequence.
> >
> > But, since there are *no* restrictions on ordering of Data Items in the
> > messages, I could well encounter the defaults *before* I encounter the
> > Extensions Supported data item - hence, I may (or may not) recognize
> those
> > new default metric data items as valid...
>
> A TLV (type length value) parser should not depend on the order of the
> TLVs...
>
> so either you have to temporarily store all default metrics, or you
> just do a two-stage parsing of the same message.
>

Yeah... two-stage parsing... don't know about you, but I'd like to avoid
that.


>
> > To clean up the misunderstanding, I propose that we add a new message
> (and
> > the corresponding ACK) to the sequence. Default metrics would be removed
> > from the Session Init/Session Init ACK sequence. After that exchange, the
> > modem issues the new message (I propose calling it the Session Metric
> > Initialization message) with the defaults for the metrics to be used.
> That
> > message is acknowledged, and then the router and modem drop into the
> > "In-Session" state.
> >
> > Oh, and we can (and I think we should) remove the restrictions on what
> > metric items are MANDATORY... If an implementation receives the Session
> > Metric Initialization message, and it (for example) indicates "I'm only
> > going to use Resources-Transmit", there needs to be a status code for
> "Well,
> > in that case, you are a silly implementation, and I will not continue
> with
> > you". Followed, of course, by Session Termination.
>
> We only have a few mandatory metrics (link speed related things,
> right?)... I am not sure I am good with dropping them too.


> This gives a router at least a chance to determine what this radio is
> useful for.
>

IMO, being able to negatively acknowledge the Session Metrics Init message
does the same thing, I think - a router has the opportunity to look at the
metrics being advertised by a modem, and make the determination you speak
of. Just for the record - I think a modem implementation that doesn't
announce link speed is pretty silly. But then, I don't claim to understand
each and every possible use case. Something that is totally absurd to us
might actually work for someone...

Regards,
Stan

P.S. In an earlier email on this thread, you mentioned "Alien Space Bats".
You're not going to write that up as a DLEP extension, are you? ;-) ;-) ;-)

--001a114020acdef43905267e566e
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><div class=3D"gmail_quo=
te">On Wed, Dec 9, 2015 at 5:00 PM, Henning Rogge <span dir=3D"ltr">&lt;<a =
href=3D"mailto:hrogge@gmail.com" target=3D"_blank">hrogge@gmail.com</a>&gt;=
</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .=
8ex;border-left:1px #ccc solid;padding-left:1ex">On Wed, Dec 9, 2015 at 10:=
52 PM, Stan Ratliff &lt;<a href=3D"mailto:ratliffstan@gmail.com">ratliffsta=
n@gmail.com</a>&gt; wrote:<br>
&gt; The point of putting the metrics in the Session Init/Session Init ACK<=
br>
&gt; sequence was two-fold:=C2=A0 (1) to announce metrics in use for this r=
adio, and<br>
&gt; (2) to provide radio-specific defaults for those metrics. That way,<br=
>
&gt; subsequent DLEP messages could focus only on metrics that had changed.=
<br>
&gt; That&#39;s all documented in Section 3. So it wasn&#39;t really a nego=
tiation, it<br>
&gt; was an announcement and initialization of the metric values.<br>
&gt;<br>
&gt; In the case of credit windowing, the same &quot;announcement and init&=
quot; notion<br>
&gt; could apply, but in general, I&#39;m opposed to just listing all Data =
Items in<br>
&gt; the Session Init/Session Init ACK sequence - future, documented enhanc=
ements<br>
&gt; to the protocol is what Extensions is for. But thinking about this *di=
d*<br>
&gt; lead me to something I perceive as a problem with the protocol:<br>
&gt;<br>
&gt; Let&#39;s assume that someone comes up with an Extension that is a col=
lection of<br>
&gt; metric data items. Theoretically, that set of metric items would be<br=
>
&gt; documented in the WG, discussed, approved, and a registry entry assign=
ed. So<br>
&gt; far, so good. But, on initialization, implementations would need to:<b=
r>
&gt; 1. Announce support for the extension, via the &quot;Extensions Suppor=
ted&quot; data<br>
&gt; item, *and*<br>
&gt; 2. Announce the defaults, by plopping the new data items into the Sess=
ion<br>
&gt; Init/Session Init ACK sequence.<br>
&gt;<br>
&gt; But, since there are *no* restrictions on ordering of Data Items in th=
e<br>
&gt; messages, I could well encounter the defaults *before* I encounter the=
<br>
&gt; Extensions Supported data item - hence, I may (or may not) recognize t=
hose<br>
&gt; new default metric data items as valid...<br>
<br>
A TLV (type length value) parser should not depend on the order of the TLVs=
...<br>
<br>
so either you have to temporarily store all default metrics, or you<br>
just do a two-stage parsing of the same message.<br></blockquote><div><br><=
/div><div>Yeah... two-stage parsing... don&#39;t know about you, but I&#39;=
d like to avoid that.=C2=A0</div><div>=C2=A0</div><blockquote class=3D"gmai=
l_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left=
:1ex">
<br>
&gt; To clean up the misunderstanding, I propose that we add a new message =
(and<br>
&gt; the corresponding ACK) to the sequence. Default metrics would be remov=
ed<br>
&gt; from the Session Init/Session Init ACK sequence. After that exchange, =
the<br>
&gt; modem issues the new message (I propose calling it the Session Metric<=
br>
&gt; Initialization message) with the defaults for the metrics to be used. =
That<br>
&gt; message is acknowledged, and then the router and modem drop into the<b=
r>
&gt; &quot;In-Session&quot; state.<br>
&gt;<br>
&gt; Oh, and we can (and I think we should) remove the restrictions on what=
<br>
&gt; metric items are MANDATORY... If an implementation receives the Sessio=
n<br>
&gt; Metric Initialization message, and it (for example) indicates &quot;I&=
#39;m only<br>
&gt; going to use Resources-Transmit&quot;, there needs to be a status code=
 for &quot;Well,<br>
&gt; in that case, you are a silly implementation, and I will not continue =
with<br>
&gt; you&quot;. Followed, of course, by Session Termination.<br>
<br>
We only have a few mandatory metrics (link speed related things,<br>
right?)... I am not sure I am good with dropping them too.=C2=A0</blockquot=
e><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:=
1px #ccc solid;padding-left:1ex">
<br>
This gives a router at least a chance to determine what this radio is<br>
useful for.<br></blockquote><div><br></div><div>IMO, being able to negative=
ly acknowledge the Session Metrics Init message does the same thing, I thin=
k - a router has the opportunity to look at the metrics being advertised by=
 a modem, and make the determination you speak of. Just for the record - I =
think a modem implementation that doesn&#39;t announce link speed is pretty=
 silly. But then, I don&#39;t claim to understand each and every possible u=
se case. Something that is totally absurd to us might actually work for som=
eone...</div><div><br></div><div>Regards,</div><div>Stan</div><div><br></di=
v><div>P.S. In an earlier email on this thread, you mentioned &quot;Alien S=
pace Bats&quot;. You&#39;re not going to write that up as a DLEP extension,=
 are you? ;-) ;-) ;-)=C2=A0</div></div><br></div></div>

--001a114020acdef43905267e566e--


From nobody Wed Dec  9 14:22:50 2015
Return-Path: <lberger@labn.net>
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 6AB221B2EB9 for <manet@ietfa.amsl.com>; Wed,  9 Dec 2015 14:22:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.667
X-Spam-Level: 
X-Spam-Status: No, score=-1.667 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, IP_NOT_FRIENDLY=0.334, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no
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 VKDpDlXO9MxI for <manet@ietfa.amsl.com>; Wed,  9 Dec 2015 14:22:48 -0800 (PST)
Received: from gproxy6-pub.mail.unifiedlayer.com (gproxy6-pub.mail.unifiedlayer.com [67.222.39.168]) by ietfa.amsl.com (Postfix) with SMTP id 7035D1B2EB7 for <manet@ietf.org>; Wed,  9 Dec 2015 14:22:48 -0800 (PST)
Received: (qmail 21257 invoked by uid 0); 9 Dec 2015 22:22:46 -0000
Received: from unknown (HELO cmgw4) (10.0.90.85) by gproxy6.mail.unifiedlayer.com with SMTP; 9 Dec 2015 22:22:46 -0000
Received: from box313.bluehost.com ([69.89.31.113]) by cmgw4 with  id raNj1r0062SSUrH01aNmlw; Wed, 09 Dec 2015 15:22:46 -0700
X-Authority-Analysis: v=2.1 cv=IekUBwaa c=1 sm=1 tr=0 a=h1BC+oY+fLhyFmnTBx92Jg==:117 a=wU2YTnxGAAAA:8 a=cNaOj0WVAAAA:8 a=IkcTkHD0fZMA:10 a=-NfooI8aBGcA:10 a=uEJ9t1CZtbIA:10 a=wUQvQvOEmiQA:10 a=ylhjtIYREcszZgSPmjAA:9 a=QEXdDO2ut3YA:10
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=labn.net; s=default;  h=Content-Transfer-Encoding:Content-Type:In-Reply-To:MIME-Version:Date:Message-ID:From:Cc:References:To:Subject; bh=qK4DMYdmJThY6b566tB4/ENy6UQSOoo5dUDAwHjM02Q=;  b=iVOCF0IzWxQHPIcR45Ri/cP7ezp7VS3MVelHRPWoWHHGrT+1CJFUTd+DV5KfQUM7iz9ffznvUjQzDuT8mhztwwJ4qASRfgjbQy4Z0F0plCrH/U79tppiQvux3YIvhb29;
Received: from box313.bluehost.com ([69.89.31.113]:41774 helo=[127.0.0.1]) by box313.bluehost.com with esmtpa (Exim 4.84) (envelope-from <lberger@labn.net>) id 1a6n8F-0002rF-2u; Wed, 09 Dec 2015 15:22:43 -0700
To: Henning Rogge <hrogge@gmail.com>
References: <56687AC2.9060801@labn.net> <CALtoyomCuki__fyNnhmYoKmBcrQSSuOPGgcg8N-txG1DSaUaAg@mail.gmail.com> <56689271.306@labn.net> <CALtoyo=JqgbqsBPo5jG-UzFR56qmAEk9zbtDBoLQUoJfcuooew@mail.gmail.com> <CAGnRvuqi14Hz2ge-QLt7drfF1k9PeG9Gyft4ERWtLv_PcC=KfA@mail.gmail.com> <56689CC0.3020408@labn.net> <CAGnRvuqQHzJge5PmjR3Z6ax3rSDxQG2xko6UA-CsO7BF9HQX2Q@mail.gmail.com>
From: Lou Berger <lberger@labn.net>
Message-ID: <5668A9AD.5000108@labn.net>
Date: Wed, 9 Dec 2015 17:22:37 -0500
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.4.0
MIME-Version: 1.0
In-Reply-To: <CAGnRvuqQHzJge5PmjR3Z6ax3rSDxQG2xko6UA-CsO7BF9HQX2Q@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-Identified-User: {1038:box313.bluehost.com:labnmobi:labn.net} {sentby:smtp auth 69.89.31.113 authed with lberger@labn.net}
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/hRJEY4QxIDn3AUsr2kyP2BPuyXA>
Cc: MANET IETF <manet@ietf.org>, draft-ietf-manet-dlep@ietf.org
Subject: Re: [manet] DLEP-17: Handling of unknown / unexpected messages
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: <https://mailarchive.ietf.org/arch/browse/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: Wed, 09 Dec 2015 22:22:49 -0000

On 12/9/2015 4:32 PM, Henning Rogge wrote:
> On Wed, Dec 9, 2015 at 10:27 PM, Lou Berger <lberger@labn.net> wrote:
>> On 12/9/2015 4:21 PM, Henning Rogge wrote:
>>> The sending of the "session termination" is just nice window dressing
>>> to give the other side a chance to quickly tear down its session data,
>>> there is not much else to do except for dropping the session.
>> The problem is that this "window dressing" introduces limitations on
>> future compatibility/partial interoperability and vulnerabilities.  It
>> seems to me to be an unnecessary "optimization".
> No, it does not.
>
> Because you have to announce all your endpoints functionality in the
> first Message (Peer Init/Peer Init Ack).
>
> If you do something the other side does not understand after this your
> implementation is defective.

okay, I wouldn't go this way but not my call. 

The principle of "be liberal in what you accept..." has served may
protocols well....


Lou

> Henning Rogge
>



From nobody Wed Dec  9 14:23:23 2015
Return-Path: <hrogge@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 67EA21B2EC0; Wed,  9 Dec 2015 14:23:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 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, 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 FSdAXw0FZc1f; Wed,  9 Dec 2015 14:23:20 -0800 (PST)
Received: from mail-wm0-x229.google.com (mail-wm0-x229.google.com [IPv6:2a00:1450:400c:c09::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EC1E11B2EB9; Wed,  9 Dec 2015 14:23:12 -0800 (PST)
Received: by mail-wm0-x229.google.com with SMTP id u63so709521wmu.0; Wed, 09 Dec 2015 14:23:12 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=ZXNabGLuJiyzLj95WpYLhRl7wCXLjHfgqqR0RKAACcM=; b=eXMO6Nmn6CIv3CYB+1uZcedzUpdjeIiNCtMktlv8Kh3O3JKz4HaySOztG+sj4SEg/O okWIUioA6/7F62f5FqiZi+dHtW5aIRbWYfO1HDa2jookH3AWyZuqT2tCQvO7IA2pmL23 UlynaK0hFmUXFRPtwXUYEGdJFchx6mUQe/vjDD4o8IxcPGZVkPZ9hiH8VoXOdmxdeKQo RV06skP7hGUQ4ocfkl5iRRjRjd9D7umJTwG5CyzvmNrkdF33XLgVPZToapRO43aRS2Bk 4qS3Sm4AdVAezlnz9PJARlDr+SuGgSpBWPyfeYjiOYv1Nv4n7NzBg5JuFYIsgGvqgABP BtSQ==
X-Received: by 10.194.2.193 with SMTP id 1mr8882704wjw.26.1449699791573; Wed, 09 Dec 2015 14:23:11 -0800 (PST)
MIME-Version: 1.0
Received: by 10.27.94.70 with HTTP; Wed, 9 Dec 2015 14:22:42 -0800 (PST)
In-Reply-To: <CALtoyomqbnTJer9ekYLZ1sseFRbVv19pNXR+Y7pridCGPghejA@mail.gmail.com>
References: <56687ABA.803@labn.net> <CALtoyonnuk03=FqiyPfQS4t9mKJt81kUfkZP-JB0FD0hfRp-6Q@mail.gmail.com> <566888B0.3070806@labn.net> <CALtoyomO1YTNydyohqRczjHnivCkfPp_gwv5oRWjdRmC5yOb0Q@mail.gmail.com> <56689542.2080303@labn.net> <CALtoyomdxY8P4QgxDMgkkFg452f=rC70xKCJOEkpyJH8K+u9AA@mail.gmail.com> <CAGnRvuofzTvTjNWq2d9oA+0Cxpy8mnRc6mkpuKnLp0LLsb7M-A@mail.gmail.com> <CALtoyomqbnTJer9ekYLZ1sseFRbVv19pNXR+Y7pridCGPghejA@mail.gmail.com>
From: Henning Rogge <hrogge@gmail.com>
Date: Wed, 9 Dec 2015 23:22:42 +0100
Message-ID: <CAGnRvuqja8ngi7+mWb8zCsvUMq6anjwuVit01GWxC=2Ee9iQ6w@mail.gmail.com>
To: Stan Ratliff <ratliffstan@gmail.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/vQrdGo0pbJNpyIVl8RMtzi7uw2g>
Cc: MANET IETF <manet@ietf.org>, draft-ietf-manet-dlep@ietf.org
Subject: Re: [manet] DLEP-17: duplicate functions - Options & extensions negotiations
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: <https://mailarchive.ietf.org/arch/browse/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: Wed, 09 Dec 2015 22:23:21 -0000

On Wed, Dec 9, 2015 at 11:09 PM, Stan Ratliff <ratliffstan@gmail.com> wrote:
> Yeah... two-stage parsing... don't know about you, but I'd like to avoid
> that.

What I am doing at the moment is having a place to store every data
item I support... this way its possible to do a single-stage parsing.

Default values are only delivered by the radio to the router if I
remember it correctly, which happens after the router tells the radio
what it supports.

This means the router can instantly drop the session if it gets a
metric it does not support.

>> We only have a few mandatory metrics (link speed related things,
>> right?)... I am not sure I am good with dropping them too.
>>
>>
>> This gives a router at least a chance to determine what this radio is
>> useful for.
>
>
> IMO, being able to negatively acknowledge the Session Metrics Init message
> does the same thing, I think - a router has the opportunity to look at the
> metrics being advertised by a modem, and make the determination you speak
> of. Just for the record - I think a modem implementation that doesn't
> announce link speed is pretty silly. But then, I don't claim to understand
> each and every possible use case. Something that is totally absurd to us
> might actually work for someone...

In fact its even "okay" to report both link speed and maximum link
speed once at a constant... so this should be EASY for any kind of
implementation.

Link speed is hard to measure for the router... lets keep it in there.

Henning


From nobody Wed Dec  9 14:28:26 2015
Return-Path: <lberger@labn.net>
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 CA0571B2EE5 for <manet@ietfa.amsl.com>; Wed,  9 Dec 2015 14:28:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.667
X-Spam-Level: 
X-Spam-Status: No, score=-1.667 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, IP_NOT_FRIENDLY=0.334, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no
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 zHYcokIVB-SF for <manet@ietfa.amsl.com>; Wed,  9 Dec 2015 14:28:24 -0800 (PST)
Received: from gproxy1-pub.mail.unifiedlayer.com (gproxy1-pub.mail.unifiedlayer.com [69.89.25.95]) by ietfa.amsl.com (Postfix) with SMTP id E0F641B2EE8 for <manet@ietf.org>; Wed,  9 Dec 2015 14:28:22 -0800 (PST)
Received: (qmail 26861 invoked by uid 0); 9 Dec 2015 22:28:20 -0000
Received: from unknown (HELO cmgw2) (10.0.90.83) by gproxy1.mail.unifiedlayer.com with SMTP; 9 Dec 2015 22:28:20 -0000
Received: from box313.bluehost.com ([69.89.31.113]) by cmgw2 with  id raUF1r00v2SSUrH01aUJxv; Wed, 09 Dec 2015 15:28:19 -0700
X-Authority-Analysis: v=2.1 cv=dqRIVTQ4 c=1 sm=1 tr=0 a=h1BC+oY+fLhyFmnTBx92Jg==:117 a=wU2YTnxGAAAA:8 a=cNaOj0WVAAAA:8 a=IkcTkHD0fZMA:10 a=-NfooI8aBGcA:10 a=uEJ9t1CZtbIA:10 a=wUQvQvOEmiQA:10 a=LCrvZSPe5ZrvG1smmBsA:9 a=QEXdDO2ut3YA:10
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=labn.net; s=default;  h=Content-Transfer-Encoding:Content-Type:In-Reply-To:MIME-Version:Date:Message-ID:From:Cc:References:To:Subject; bh=3Qs8MN+WsSAAfDSBFtql7iz610zaQOJevtrAOv7Xfik=;  b=1K86BqT9o5fHjw8uIRDlUJpxI90Vc3NJZ/zebu8sC7xy3iC/Xj1cOIs4MRhrCp65dPYMP7ggyeFu068XFOO6TQQ28gMzXfVhTDjJ2+HclbzzQETJCGVGhTwOIBZOk/LK;
Received: from box313.bluehost.com ([69.89.31.113]:43866 helo=[127.0.0.1]) by box313.bluehost.com with esmtpa (Exim 4.84) (envelope-from <lberger@labn.net>) id 1a6nDd-00048s-H0; Wed, 09 Dec 2015 15:28:17 -0700
To: Stan Ratliff <ratliffstan@gmail.com>
References: <56687ABA.803@labn.net> <CALtoyonnuk03=FqiyPfQS4t9mKJt81kUfkZP-JB0FD0hfRp-6Q@mail.gmail.com> <566888B0.3070806@labn.net> <CALtoyomO1YTNydyohqRczjHnivCkfPp_gwv5oRWjdRmC5yOb0Q@mail.gmail.com> <56689542.2080303@labn.net> <CALtoyomdxY8P4QgxDMgkkFg452f=rC70xKCJOEkpyJH8K+u9AA@mail.gmail.com>
From: Lou Berger <lberger@labn.net>
Message-ID: <5668AAFC.7010406@labn.net>
Date: Wed, 9 Dec 2015 17:28:12 -0500
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.4.0
MIME-Version: 1.0
In-Reply-To: <CALtoyomdxY8P4QgxDMgkkFg452f=rC70xKCJOEkpyJH8K+u9AA@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-Identified-User: {1038:box313.bluehost.com:labnmobi:labn.net} {sentby:smtp auth 69.89.31.113 authed with lberger@labn.net}
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/Kyct9A3AKTtUNOdjb9rxGT4W6jQ>
Cc: MANET IETF <manet@ietf.org>, draft-ietf-manet-dlep@ietf.org
Subject: Re: [manet] DLEP-17: duplicate functions - Options & extensions negotiations
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: <https://mailarchive.ietf.org/arch/browse/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: Wed, 09 Dec 2015 22:28:25 -0000

Stan,

On 12/9/2015 4:52 PM, Stan Ratliff wrote:
> But, since there are *no* restrictions on ordering of Data Items in
> the messages, I could well encounter the defaults *before* I encounter
> the Extensions Supported data item - hence, I may (or may not)
> recognize those new default metric data items as valid... 
>
I don't see this is a big deal, just means your code has to first parse
for syntax and then semantics.  Having implement similar (lack of)
ordering requirements before, it's not a big deal to code.

> To clean up the misunderstanding, I propose that we add a new message
> (and the corresponding ACK) to the sequence. Default metrics would be
> removed from the Session Init/Session Init ACK sequence. After that
> exchange, the modem issues the new message (I propose calling it the
> Session Metric Initialization message) with the defaults for the
> metrics to be used.

If you're trying to solve other issues, sure, but if you're just dealing
with the parsing issue, I'd simply highlight this possibility in the
text to help implementers.  Better to have two pass processing of one
message than two message exchanges. 

> That message is acknowledged, and then the router and modem drop into
> the "In-Session" state. 
>

I still think there may be holes in the protocol state machine, but
haven't had the time to do the full state analysis.

Lou


From nobody Thu Dec 10 01:45:15 2015
Return-Path: <hrogge@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 4CC821A0233 for <manet@ietfa.amsl.com>; Thu, 10 Dec 2015 01:45:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 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, 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 JyUWsU3yIOjF for <manet@ietfa.amsl.com>; Thu, 10 Dec 2015 01:45:13 -0800 (PST)
Received: from mail-wm0-x22f.google.com (mail-wm0-x22f.google.com [IPv6:2a00:1450:400c:c09::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B48681A884F for <manet@ietf.org>; Thu, 10 Dec 2015 01:45:12 -0800 (PST)
Received: by mail-wm0-x22f.google.com with SMTP id c201so23912305wme.0 for <manet@ietf.org>; Thu, 10 Dec 2015 01:45:12 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=ojx3k5ukVMHdFM0npBuxujO0hjI70aElIpgD2yFEPdE=; b=TFwCKNEJijiUVARL1LvfQsMEs3Nj6F5yD3cWrCIeUTZ3SNgJzH4CsiF3Owa1ze3dhz qvFhzD49hadLvdhby6QcK/wHXJbFb/i/xQ5sTBJDMaMdl2xyerc/wrh4FlU2VQoeLq4V q+8Be0FwU8SpfHXHGK+1Kugn9ojItjn0P/H6dGeIVDHgpNqMzLlWcHXrMpvqgBY4EEjK 3xCmUZawUfpyrkHGKIAnC/T+sJxTjqnoj3eoeLznG6TpHV+fdjHSIL5Xd1jTAsXiwXX0 dZbdyA9Ft/uJgJ3g9a19dqmOFv2LZsuxbrNTyEdzyxGsiCQUlRMK3XtqTGsFj9Zu8RGJ 3q9g==
X-Received: by 10.28.86.196 with SMTP id k187mr38746789wmb.61.1449740711377; Thu, 10 Dec 2015 01:45:11 -0800 (PST)
MIME-Version: 1.0
Received: by 10.27.94.70 with HTTP; Thu, 10 Dec 2015 01:44:41 -0800 (PST)
In-Reply-To: <CALtoyomqbnTJer9ekYLZ1sseFRbVv19pNXR+Y7pridCGPghejA@mail.gmail.com>
References: <56687ABA.803@labn.net> <CALtoyonnuk03=FqiyPfQS4t9mKJt81kUfkZP-JB0FD0hfRp-6Q@mail.gmail.com> <566888B0.3070806@labn.net> <CALtoyomO1YTNydyohqRczjHnivCkfPp_gwv5oRWjdRmC5yOb0Q@mail.gmail.com> <56689542.2080303@labn.net> <CALtoyomdxY8P4QgxDMgkkFg452f=rC70xKCJOEkpyJH8K+u9AA@mail.gmail.com> <CAGnRvuofzTvTjNWq2d9oA+0Cxpy8mnRc6mkpuKnLp0LLsb7M-A@mail.gmail.com> <CALtoyomqbnTJer9ekYLZ1sseFRbVv19pNXR+Y7pridCGPghejA@mail.gmail.com>
From: Henning Rogge <hrogge@gmail.com>
Date: Thu, 10 Dec 2015 10:44:41 +0100
Message-ID: <CAGnRvur_1hL+jTrxa29GZTdStyWuWygVO6GhoSPdih8voRd+BA@mail.gmail.com>
To: Stan Ratliff <ratliffstan@gmail.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/DAjHP7fUiaE4weX0QFcP-KULN6Q>
Cc: MANET IETF <manet@ietf.org>
Subject: Re: [manet] DLEP-17: duplicate functions - Options & extensions negotiations
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: <https://mailarchive.ietf.org/arch/browse/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: Thu, 10 Dec 2015 09:45:14 -0000

On Wed, Dec 9, 2015 at 11:09 PM, Stan Ratliff <ratliffstan@gmail.com> wrote:
> P.S. In an earlier email on this thread, you mentioned "Alien Space Bats".
> You're not going to write that up as a DLEP extension, are you? ;-) ;-) ;-)

Might become useful for satellite communication, right? ^^

Henning


From nobody Thu Dec 10 01:58:57 2015
Return-Path: <steven.matty@airbus.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 3CD9C1A88CB; Thu, 10 Dec 2015 01:58:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.001
X-Spam-Level: 
X-Spam-Status: No, score=-0.001 tagged_above=-999 required=5 tests=[BAYES_20=-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 HLCq2mlpjNll; Thu, 10 Dec 2015 01:58:53 -0800 (PST)
Received: from mirabel.astrium.eads.net (mirabel.astrium.eads.net [194.62.210.46]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2A5C41A88CA; Thu, 10 Dec 2015 01:58:52 -0800 (PST)
Received: from rosout.astrium.eads.net ([10.221.0.46]) by mirabel.astrium.eads.net (8.14.4/8.14.4) with ESMTP id tBA9wnc6026387; Thu, 10 Dec 2015 09:58:49 GMT
Received: from rosout.astrium.eads.net (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 6CF213C805F; Thu, 10 Dec 2015 09:58:49 +0000 (GMT)
Received: from localhost (unknown [127.0.0.1]) by IMSVA (Postfix) with SMTP id 52B883C805E; Thu, 10 Dec 2015 09:58:49 +0000 (GMT)
X-IMSS-HAND-OFF-DIRECTIVE: 127.0.0.1:10026
Received: from AUK52839.UKN.UKNROOT.ASTRIUM.CORP (unknown [10.221.1.32]) by rosout.astrium.eads.net (Postfix) with ESMTPS id AEB523C805D; Thu, 10 Dec 2015 09:58:43 +0000 (GMT)
Received: from AUK52982.UKN.UKNROOT.ASTRIUM.CORP ([fe80::543e:db1:48aa:1c6]) by AUK52839.UKN.UKNROOT.ASTRIUM.CORP ([fe80::cdf2:d214:a3a9:7510%15]) with mapi id 14.03.0123.003; Thu, 10 Dec 2015 09:58:43 +0000
From: "MATTY, Steven" <steven.matty@airbus.com>
To: "'Stan Ratliff'" <ratliffstan@gmail.com>, Lou Berger <lberger@labn.net>
Thread-Topic: [manet] DLEP-17: Handling of unknown / unexpected messages
Thread-Index: AQHRMsTSFIV5+Z+1uEy9h/bEW5lkZZ7D+byw
Date: Thu, 10 Dec 2015 09:58:42 +0000
Message-ID: <D9712B947A4CCA43AB42F01B90AF1DEC011F5B8E2A@AUK52982.UKN.UKNROOT.ASTRIUM.CORP>
References: <56687AC2.9060801@labn.net> <CALtoyomCuki__fyNnhmYoKmBcrQSSuOPGgcg8N-txG1DSaUaAg@mail.gmail.com> <56689271.306@labn.net> <23834_1449694925_566896CB_23834_3552_3_CALtoyo=JqgbqsBPo5jG-UzFR56qmAEk9zbtDBoLQUoJfcuooew@mail.gmail.com>
In-Reply-To: <23834_1449694925_566896CB_23834_3552_3_CALtoyo=JqgbqsBPo5jG-UzFR56qmAEk9zbtDBoLQUoJfcuooew@mail.gmail.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.221.1.73]
X-TM-AS-Product-Ver: IMSVA-9.0.0.1383-8.0.0.1202-21992.006
X-TM-AS-Result: No--10.960-5.0-31-10
x-tm-as-user-approved-sender: No
x-tm-as-user-blocked-sender: No
Content-Type: multipart/alternative; boundary="_000_D9712B947A4CCA43AB42F01B90AF1DEC011F5B8E2AAUK52982UKNUK_"
MIME-Version: 1.0
X-TM-AS-GCONF: 00
X-imss-scan-details: No--10.960-5.0-31-10
X-TMASE-Version: IMSVA-9.0.0.1383-8.0.1202-21992.006
X-TMASE-Result: 10--10.959700-5.000000
X-TMASE-MatchedRID: cxtZ8fwm3r84HKI/yaqRm521GZGE81yGyeUl7aCTy8g4WUsA5A23IVj/ a5i8jvLC0bcUYjtVv/Kv0nQBLOKorfQPRH4blNMceUyVZX4ivrusvgu4NQN9u99RlPzeVuQQKZq 4mYV61HZEpOCumutgtaATi6ZxGoS0WONZnYJ3/09PuMJi/ZAk8Q/80a3o2lzSIFBEE5CFomId3E uWNq2ydp6QSKvJTnodGcqRvuFMKK1PxIXOhlk+6RLuW4a3q2WG7q8FE7Y/iI1x1e3NhjX9AqGK2 YfreERwh2MXirDwWUCwRRF6v5JQYE0eOhDHYyZW4bl1FkKDELcLYBs7g6kS/ClwAFvgc5IPlRYi Q0nafjuhT+bh/OEvVe9p9tzbK7RuKfTp3wVRUm0XS9gNEgP5ymlOPrrbBmagB4sIhfTjqIGM0vG tzEpWJSKGAlWs2eIFfQy9PJSV1p/3qcrPVgBfOYoLoibgjVEXMrX+p1uNztC/a2V+CepJRxZXGB ej2Wbe8B1Eq8wDKAG07Lom4c+W62HIw6FQ9nuexjmDsee4erK//vF0tCNdIs2ywP+/2jMq3SlEg VuyN9tvuYnoduGWEYAy6p60ZV62gWyBTm39yBmDGx/OQ1GV8rI7zVffJqTzG8nH3bCqOdhSsEAj WJIkQkgM+iOGnM5gnYAn86EAAmEpC4cFcbfcwIzpqHi3MRhaRxbj4oLWvoNOZYF9wyk02tDpEY9 nU9pd
X-TMASE-SNAP-Result: 1.801202.0001-0-1-22:0,12:0
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/cQEaf7LSYLXEg9nVrUfdzk1fwCU>
Cc: MANET IETF <manet@ietf.org>, "draft-ietf-manet-dlep@ietf.org" <draft-ietf-manet-dlep@ietf.org>
Subject: Re: [manet] DLEP-17: Handling of unknown / unexpected messages
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: <https://mailarchive.ietf.org/arch/browse/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: Thu, 10 Dec 2015 09:58:56 -0000

--_000_D9712B947A4CCA43AB42F01B90AF1DEC011F5B8E2AAUK52982UKNUK_
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: base64

RnJvbTogbWFuZXQgW21haWx0bzptYW5ldC1ib3VuY2VzQGlldGYub3JnXSBPbiBCZWhhbGYgT2Yg
U3RhbiBSYXRsaWZmDQoNCj5JIG5lZWQgdG8gYmUgY2FyZWZ1bCBhYm91dCB3aGljaCBoYXQgSSdt
IHdlYXJpbmcgaGVyZSAtIHNwZWFraW5nIGp1c3QgYXMgYSBXRyBwYXJ0aWNpcGFudCwgYW5kIGEg
cGVyc29uIHRoYXQncw0KPmludGVyZXN0ZWQgaW4gRExFUCwgSSB0aGluayB0aGF0IHRoZSBwcm9j
ZXNzaW5nIHJ1bGVzIGhhdmUgZ290dGVuIHRvbyByZXN0cmljdGl2ZSAtIGJhc2ljYWxseSwgb24g
YW55IGVycm9yLA0KPnRoZSBvbmx5IGFuc3dlciBpcyB0byBhY3RpdmF0ZSB0aGUgbnVjbGVhciBz
ZWxmLT5kZXN0cnVjdCBkZXZpY2UsIGFuZCBibG93IGV2ZXJ5dGhpbmcgdG8ga2luZ2RvbS1jb21l
LiBKdXN0IGluDQo+bXkgbGl0dGxlLW9sZSBvcGluaW9uLCB0aGF0J3MgYSB0YWQgaGFyc2guLi4N
Cg0KPkFzIEkgbWVudGlvbmVkIGVhcmxpZXIsIHRoaXMgdGV4dCB3YXMgdGhlIHJlc3VsdCBvZiBt
dWNoICh0b28gbXVjaCkgaGFnZ2xpbmcsIHRhbGtpbmcsIGFuZCBkaXNjdXNzaW5nIG9mDQo+b3B0
aW9ucy4gSSBmZWVsIGxpa2UgSSB3YXMgcHJldHR5IG11Y2ggImluIHRoZSByb3VnaCIgd2hlbiB0
aGUgdGV4dCB3YXMgYWRvcHRlZDsgdGhlcmUgYXJlIG90aGVycyBvbiB0aGUgbGlzdA0KPnRoYXQg
SSBob3BlIHdpbGwgY29tbWVudC4gV2hhdCBJIGJlbGlldmUgaXMgdGhhdDoNCg0KPjEuIEFuIGlu
dmFsaWQgb3IgbWlzLXVuZGVyc3Rvb2QgKm1lc3NhZ2UqIG5lZWRzIHRvIGJlIGNvdW50ZXJlZCB3
aXRoIHRlcm1pbmF0aW9uLCBzaW5jZSBiYXNlZCBvbiBTZWN0aW9uIDQuMSwNCj50aGUgc2VuZGVy
IHdpbGwgaGF2ZSBhIHRyYW5zYWN0aW9uICJoYW5naW5nIG91dCBpbiBzcGFjZSIgdGhhdCB3aWxs
IG5ldmVyIHRpbWUgb3V0LCBhbmQgY2FuJ3QgYmUgY2FuY2VsbGVkLg0KDQo+Mi4gQXMgdG8gaW52
YWxpZCAqRGF0YSBJdGVtcyosIEkgdGhpbmsgdGhlIHJ1bGVzIHNob3VsZCBiZSBsb29zZW5lZCAt
IHNwZWNpZmljYWxseSwgSSBiZWxpZXZlIHRoYXQgIklmIGFuDQo+dW5yZWNvZ25pemVkLCBvciB1
bmV4cGVjdGVkIG1lc3NhZ2UgaXMgcmVjZWl2ZWQsIG9yIGEgcmVjZWl2ZWQgbWVzc2FnZSBjb250
YWlucyB1bnJlY29nbml6ZWQsIGludmFsaWQsIG9yDQo+ZGlzYWxsb3dlZCBkdXBsaWNhdGUgZGF0
YSBpdGVtcyIsIHRoZW4gdGhlIHJlY2VpdmluZyA+aW1wbGVtZW50YXRpb24gc2hvdWxkIG5lZ2F0
aXZlbHkgYWNrbm93bGVkZ2UsIHdpdGggYW4NCj5hcHByb3ByaWF0ZSBzdGF0dXMgRGF0YSBJdGVt
L2Vycm9yIGNvZGUuDQoNCj5CdXQgdGhhdCdzIGp1c3QgbXkgJDAuMDItd29ydGguIExvb2tpbmcg
Zm9yIG90aGVyIG9waW5pb25zIG9uIHRoZSBsaXN0Li4uDQoNCldlbGwgYXMgeW91IGFza2VkIGZv
ciBpdOKApg0KDQoxKSBNeSBpbmNsaW5hdGlvbiBpcyB0b3dhcmRzIHRoZSDigJxCZSBnZW5lcm91
cyBpbiB3aGF0IHlvdSBhY2NlcHTigJ0gc2lkZSBvZiB0aGluZ3MuIEJ1dCB0aGVyZSBpcyBhIHRy
YWRlLW9mZiB3aGVuIHlvdQ0KYXJlIGJlaW5nIGEgZnJpZW5kbHkgRExFUCBhcHBsaWNhdGlvbiB0
aGF0IGFjY2VwdHMgYW55IGFuZCBhbGwgbWVzc2FnZXMgdmVyc3VzIHRyeWluZyB0byBlbnN1cmUg
YWxsIERMRVANCmltcGxlbWVudGF0aW9ucyBhcmUgY29tcGxpYW50LiBJZiB5b3UgdGVhciBkb3du
IHRoZSBzZXNzaW9uIHdoZW5ldmVyIHlvdSBnZXQgYW4gaW52YWxpZCBETEVQIG1lc3NhZ2UgdGhl
biBpdA0Kd2lsbCBiZWNvbWUgVkVSWSBvYnZpb3VzLCBWRVJZIHF1aWNrbHkgdGhhdCB5b3UgYXJl
IHRhbGtpbmcgd2l0aCBhIOKAmGJhZOKAmSBpbXBsZW1lbnRhdGlvbi4gSG93ZXZlciwgbGV04oCZ
cyBzYXkgdGhhdA0KdGhpcyBpbXBsZW1lbnRhdGlvbiBvbiBhIHJvdXRlciBpcyBubyBsb25nZXIg
c3VwcG9ydGVkIGJ1dCBpcyBhY3R1YWxseSB2ZXJ5IHVzZWZ1bCBpbiBldmVyeXRoaW5nIGVsc2Ug
aXQgZG9lcyByaWdodC4NCg0KV291bGQgaXQgYmUgYW4gb3B0aW9uIHRvIGludHJvZHVjZSBhbiBb
b3B0aW9uYWxdIE5BQ0sgRExFUCBtZXNzYWdlIHR5cGUgc28gdGhhdCB5b3UgY2FuIHJlcG9ydCB0
byB0aGUgc2VuZGVyDQrigJxIZXksIHlvdSBzZW50IG1lIHRoaXMgYW5kIHNvbWV0aGluZyB3YXMg
dXAgdGhlcmXigJ0gcmF0aGVyIHRoYW4ganVzdCBhIHNpbGVudCBkaXNjYXJkPw0KDQpJZiB3ZSB3
ZXJlIHRvIGxvb3NlbiB0aGlzIHJ1bGUsIHRoZW4gdGhlIHF1ZXN0aW9uIHdvdWxkIGJlIOKAnFVu
ZGVyIHdoYXQgY2lyY3Vtc3RhbmNlcyB3b3VsZCB5b3UgdGVybWluYXRlIHRoZSBzZXNzaW9u4oCd
DQphbmQgaXQgd291bGQgYmUgaGVscGZ1bCBpZiB0aGUgRExFUCBkcmFmdCB3ZXJlIHVwZGF0ZSB0
byBpbmNsdWRlIHBlcmhhcHMgYSB0YWJsZSBzdW1tYXJpemluZyBzdWNoIGV2ZW50cy4NCg0KSWYg
SSB3ZXJlIGFza2VkIHRvIGdldCBvZmYgdGhlIGZlbmNlLCBJ4oCZZCBwcm9iYWJseSBsYW5kIG9u
IHRoZSBzaWRlIHdoZXJlIHlvdSBzaWxlbnRseSAoYW5kIG9wdGlvbmFsbHkgcmVwb3J0IHRvIHlv
dXINCm1hbmFnZW1lbnQgaW50ZXJmYWNlLCB1cCB0byB5b3VyIGltcGxlbWVudGF0aW9uIHJlYWxs
eSkgaWdub3JlIGludmFsaWQgb3IgaWxsZWdhbCBETEVQIG1lc3NhZ2VzLiBFdmVuIGlmIGl0IG1l
YW5zDQp0aGUgc2VuZGVyIG9mIHN1Y2ggaWxsaWNpdCBtYXRlcmlhbCBtYXkgY29tcGxhaW4gYWJv
dXQgbWlzc2luZyBBQ0tzLCB3ZWxsIHRvdWdoIG9uIHRoZW0gcmVhbGx5Lg0KDQoyKSBJbnZhbGlk
IERhdGEgSXRlbXMgLSBJIHRoaW5rIHRoZXNlIGNhbiBjZXJ0YWlubHkgYmUgbG9vc2VuZWQgYW5k
IEkgYWdyZWUgd2l0aCByZXNwb25kaW5nIHdpdGggYSBOQUNLIG9yIHN1aXRhYmxlDQplcXVpdmFs
ZW50Lg0KDQpSZWdhcmRzDQoNClN0ZXZlDQoNCg0KVGhpcyBlbWFpbCAoaW5jbHVkaW5nIGFueSBh
dHRhY2htZW50cykgbWF5IGNvbnRhaW4gY29uZmlkZW50aWFsIGFuZC9vciBwcml2aWxlZ2VkIGlu
Zm9ybWF0aW9uIG9yIGluZm9ybWF0aW9uIG90aGVyd2lzZSBwcm90ZWN0ZWQgZnJvbSBkaXNjbG9z
dXJlLiBJZiB5b3UgYXJlIG5vdCB0aGUgaW50ZW5kZWQgcmVjaXBpZW50LCBwbGVhc2Ugbm90aWZ5
IHRoZSBzZW5kZXIgaW1tZWRpYXRlbHksIGRvIG5vdCBjb3B5IHRoaXMgbWVzc2FnZSBvciBhbnkg
YXR0YWNobWVudHMgYW5kIGRvIG5vdCB1c2UgaXQgZm9yIGFueSBwdXJwb3NlIG9yIGRpc2Nsb3Nl
IGl0cyBjb250ZW50IHRvIGFueSBwZXJzb24sIGJ1dCBkZWxldGUgdGhpcyBtZXNzYWdlIGFuZCBh
bnkgYXR0YWNobWVudHMgZnJvbSB5b3VyIHN5c3RlbS4gQWlyYnVzIERlZmVuY2UgYW5kIFNwYWNl
IExpbWl0ZWQgZGlzY2xhaW1zIGFueSBhbmQgYWxsIGxpYWJpbGl0eSBpZiB0aGlzIGVtYWlsIHRy
YW5zbWlzc2lvbiB3YXMgdmlydXMgY29ycnVwdGVkLCBhbHRlcmVkIG9yIGZhbHNpZmllZC4NCi1v
LQ0KRW1haWxzIHRvIEFpcmJ1cyBEZWZlbmNlIGFuZCBTcGFjZSBMaW1pdGVkIG1heSBiZSBwcm9j
ZXNzZWQsIHJlY29yZGVkIGFuZCBtb25pdG9yZWQgb3V0c2lkZSB0aGUgVUsuDQotby0NCkFpcmJ1
cyBEZWZlbmNlIGFuZCBTcGFjZSBMaW1pdGVkLCBSZWdpc3RlcmVkIGluIEVuZ2xhbmQgYW5kIFdh
bGVzIE5vLiAyNDQ5MjU5DQpSZWdpc3RlcmVkIE9mZmljZTogR3VubmVscyBXb29kIFJvYWQsIFN0
ZXZlbmFnZSwgSGVydGZvcmRzaGlyZSwgU0cxIDJBUywgRW5nbGFuZA==

--_000_D9712B947A4CCA43AB42F01B90AF1DEC011F5B8E2AAUK52982UKNUK_
Content-Type: text/html;
	charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWw+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIgY29udGVudD0i
dGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRvciIgY29udGVu
dD0iTWljcm9zb2Z0IEV4Y2hhbmdlIFNlcnZlciI+DQo8IS0tIGNvbnZlcnRlZCBmcm9tIHJ0ZiAt
LT4NCjxzdHlsZT48IS0tIC5FbWFpbFF1b3RlIHsgbWFyZ2luLWxlZnQ6IDFwdDsgcGFkZGluZy1s
ZWZ0OiA0cHQ7IGJvcmRlci1sZWZ0OiAjODAwMDAwIDJweCBzb2xpZDsgfSAtLT48L3N0eWxlPg0K
PC9oZWFkPg0KPGJvZHk+DQo8Zm9udCBmYWNlPSJDb3VyaWVyIE5ldyIgc2l6ZT0iMiI+PHNwYW4g
c3R5bGU9ImZvbnQtc2l6ZToxMHB0OyI+DQo8ZGl2PkZyb206IG1hbmV0IFs8YSBocmVmPSJtYWls
dG86bWFuZXQtYm91bmNlc0BpZXRmLm9yZyI+bWFpbHRvOm1hbmV0LWJvdW5jZXNAaWV0Zi5vcmc8
L2E+XSBPbiBCZWhhbGYgT2YgU3RhbiBSYXRsaWZmPC9kaXY+DQo8ZGl2PiZuYnNwOzwvZGl2Pg0K
PGRpdj4mZ3Q7SSBuZWVkIHRvIGJlIGNhcmVmdWwgYWJvdXQgd2hpY2ggaGF0IEknbSB3ZWFyaW5n
IGhlcmUgLSBzcGVha2luZyBqdXN0IGFzIGEgV0cgcGFydGljaXBhbnQsIGFuZCBhIHBlcnNvbiB0
aGF0J3M8L2Rpdj4NCjxkaXY+Jmd0O2ludGVyZXN0ZWQgaW4gRExFUCwgSSB0aGluayB0aGF0IHRo
ZSBwcm9jZXNzaW5nIHJ1bGVzIGhhdmUgZ290dGVuIHRvbyByZXN0cmljdGl2ZSAtIGJhc2ljYWxs
eSwgb24gYW55IGVycm9yLDwvZGl2Pg0KPGRpdj4mZ3Q7dGhlIG9ubHkgYW5zd2VyIGlzIHRvIGFj
dGl2YXRlIHRoZSBudWNsZWFyIHNlbGYtJmd0O2Rlc3RydWN0IGRldmljZSwgYW5kIGJsb3cgZXZl
cnl0aGluZyB0byBraW5nZG9tLWNvbWUuIEp1c3QgaW48L2Rpdj4NCjxkaXY+Jmd0O215IGxpdHRs
ZS1vbGUgb3BpbmlvbiwgdGhhdCdzIGEgdGFkIGhhcnNoLi4uJm5ic3A7PC9kaXY+DQo8ZGl2PiZu
YnNwOzwvZGl2Pg0KPGRpdj4mZ3Q7QXMgSSBtZW50aW9uZWQgZWFybGllciwgdGhpcyB0ZXh0IHdh
cyB0aGUgcmVzdWx0IG9mIG11Y2ggKHRvbyBtdWNoKSBoYWdnbGluZywgdGFsa2luZywgYW5kIGRp
c2N1c3Npbmcgb2Y8L2Rpdj4NCjxkaXY+Jmd0O29wdGlvbnMuIEkgZmVlbCBsaWtlIEkgd2FzIHBy
ZXR0eSBtdWNoICZxdW90O2luIHRoZSByb3VnaCZxdW90OyB3aGVuIHRoZSB0ZXh0IHdhcyBhZG9w
dGVkOyB0aGVyZSBhcmUgb3RoZXJzIG9uIHRoZSBsaXN0PC9kaXY+DQo8ZGl2PiZndDt0aGF0IEkg
aG9wZSB3aWxsIGNvbW1lbnQuIFdoYXQgSSBiZWxpZXZlIGlzIHRoYXQ6Jm5ic3A7PC9kaXY+DQo8
ZGl2Pjxmb250IGZhY2U9IkNhbGlicmkiIHNpemU9IjIiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6
MTFwdDsiPiZuYnNwOzwvc3Bhbj48L2ZvbnQ+PC9kaXY+DQo8ZGl2PiZndDsxLiBBbiBpbnZhbGlk
IG9yIG1pcy11bmRlcnN0b29kICptZXNzYWdlKiBuZWVkcyB0byBiZSBjb3VudGVyZWQgd2l0aCB0
ZXJtaW5hdGlvbiwgc2luY2UgYmFzZWQgb24gU2VjdGlvbiA0LjEsPC9kaXY+DQo8ZGl2PiZndDt0
aGUgc2VuZGVyIHdpbGwgaGF2ZSBhIHRyYW5zYWN0aW9uICZxdW90O2hhbmdpbmcgb3V0IGluIHNw
YWNlJnF1b3Q7IHRoYXQgd2lsbCBuZXZlciB0aW1lIG91dCwgYW5kIGNhbid0IGJlIGNhbmNlbGxl
ZC4mbmJzcDs8L2Rpdj4NCjxkaXY+PGZvbnQgZmFjZT0iQ2FsaWJyaSIgc2l6ZT0iMiI+PHNwYW4g
c3R5bGU9ImZvbnQtc2l6ZToxMXB0OyI+Jm5ic3A7PC9zcGFuPjwvZm9udD48L2Rpdj4NCjxkaXY+
Jmd0OzIuIEFzIHRvIGludmFsaWQgKkRhdGEgSXRlbXMqLCBJIHRoaW5rIHRoZSBydWxlcyBzaG91
bGQgYmUgbG9vc2VuZWQgLSBzcGVjaWZpY2FsbHksIEkgYmVsaWV2ZSB0aGF0ICZxdW90O0lmIGFu
PC9kaXY+DQo8ZGl2PiZndDt1bnJlY29nbml6ZWQsIG9yIHVuZXhwZWN0ZWQgbWVzc2FnZSBpcyBy
ZWNlaXZlZCwgb3IgYSByZWNlaXZlZCBtZXNzYWdlIGNvbnRhaW5zIHVucmVjb2duaXplZCwgaW52
YWxpZCwgb3I8L2Rpdj4NCjxkaXY+Jmd0O2Rpc2FsbG93ZWQgZHVwbGljYXRlIGRhdGEgaXRlbXMm
cXVvdDssIHRoZW4gdGhlIHJlY2VpdmluZyAmZ3Q7aW1wbGVtZW50YXRpb24gc2hvdWxkIG5lZ2F0
aXZlbHkgYWNrbm93bGVkZ2UsIHdpdGggYW48L2Rpdj4NCjxkaXY+Jmd0O2FwcHJvcHJpYXRlIHN0
YXR1cyBEYXRhIEl0ZW0vZXJyb3IgY29kZS4mbmJzcDs8L2Rpdj4NCjxkaXY+Jm5ic3A7PC9kaXY+
DQo8ZGl2PiZndDtCdXQgdGhhdCdzIGp1c3QgbXkgJDAuMDItd29ydGguIExvb2tpbmcgZm9yIG90
aGVyIG9waW5pb25zIG9uIHRoZSBsaXN0Li4uJm5ic3A7PC9kaXY+DQo8ZGl2Pjxmb250IGZhY2U9
IkNhbGlicmkiIHNpemU9IjIiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTFwdDsiPiZuYnNwOzwv
c3Bhbj48L2ZvbnQ+PC9kaXY+DQo8ZGl2PldlbGwgYXMgeW91IGFza2VkIGZvciBpdOKApiA8L2Rp
dj4NCjxkaXY+Jm5ic3A7PC9kaXY+DQo8ZGl2PjEpIE15IGluY2xpbmF0aW9uIGlzIHRvd2FyZHMg
dGhlIOKAnEJlIGdlbmVyb3VzIGluIHdoYXQgeW91IGFjY2VwdOKAnSBzaWRlIG9mIHRoaW5ncy4g
QnV0IHRoZXJlIGlzIGEgdHJhZGUtb2ZmIHdoZW4geW91PC9kaXY+DQo8ZGl2PmFyZSBiZWluZyBh
IGZyaWVuZGx5IERMRVAgYXBwbGljYXRpb24gdGhhdCBhY2NlcHRzIGFueSBhbmQgYWxsIG1lc3Nh
Z2VzIHZlcnN1cyB0cnlpbmcgdG8gZW5zdXJlIGFsbCBETEVQPC9kaXY+DQo8ZGl2PmltcGxlbWVu
dGF0aW9ucyBhcmUgY29tcGxpYW50LiBJZiB5b3UgdGVhciBkb3duIHRoZSBzZXNzaW9uIHdoZW5l
dmVyIHlvdSBnZXQgYW4gaW52YWxpZCBETEVQIG1lc3NhZ2UgdGhlbiBpdDwvZGl2Pg0KPGRpdj53
aWxsIGJlY29tZSBWRVJZIG9idmlvdXMsIFZFUlkgcXVpY2tseSB0aGF0IHlvdSBhcmUgdGFsa2lu
ZyB3aXRoIGEg4oCYYmFk4oCZIGltcGxlbWVudGF0aW9uLiBIb3dldmVyLCBsZXTigJlzIHNheSB0
aGF0PC9kaXY+DQo8ZGl2PnRoaXMgaW1wbGVtZW50YXRpb24gb24gYSByb3V0ZXIgaXMgbm8gbG9u
Z2VyIHN1cHBvcnRlZCBidXQgaXMgYWN0dWFsbHkgdmVyeSB1c2VmdWwgaW4gZXZlcnl0aGluZyBl
bHNlIGl0IGRvZXMgcmlnaHQuPC9kaXY+DQo8ZGl2Pjxmb250IGZhY2U9IkNhbGlicmkiIHNpemU9
IjIiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTFwdDsiPiZuYnNwOzwvc3Bhbj48L2ZvbnQ+PC9k
aXY+DQo8ZGl2PldvdWxkIGl0IGJlIGFuIG9wdGlvbiB0byBpbnRyb2R1Y2UgYW4gW29wdGlvbmFs
XSBOQUNLIERMRVAgbWVzc2FnZSB0eXBlIHNvIHRoYXQgeW91IGNhbiByZXBvcnQgdG8gdGhlIHNl
bmRlcjwvZGl2Pg0KPGRpdj7igJxIZXksIHlvdSBzZW50IG1lIHRoaXMgYW5kIHNvbWV0aGluZyB3
YXMgdXAgdGhlcmXigJ0gcmF0aGVyIHRoYW4ganVzdCBhIHNpbGVudCBkaXNjYXJkPzwvZGl2Pg0K
PGRpdj48Zm9udCBmYWNlPSJDYWxpYnJpIiBzaXplPSIyIj48c3BhbiBzdHlsZT0iZm9udC1zaXpl
OjExcHQ7Ij4mbmJzcDs8L3NwYW4+PC9mb250PjwvZGl2Pg0KPGRpdj5JZiB3ZSB3ZXJlIHRvIGxv
b3NlbiB0aGlzIHJ1bGUsIHRoZW4gdGhlIHF1ZXN0aW9uIHdvdWxkIGJlIOKAnFVuZGVyIHdoYXQg
Y2lyY3Vtc3RhbmNlcyB3b3VsZCB5b3UgdGVybWluYXRlIHRoZSBzZXNzaW9u4oCdPC9kaXY+DQo8
ZGl2PmFuZCBpdCB3b3VsZCBiZSBoZWxwZnVsIGlmIHRoZSBETEVQIGRyYWZ0IHdlcmUgdXBkYXRl
IHRvIGluY2x1ZGUgcGVyaGFwcyBhIHRhYmxlIHN1bW1hcml6aW5nIHN1Y2ggZXZlbnRzLjwvZGl2
Pg0KPGRpdj48Zm9udCBmYWNlPSJDYWxpYnJpIiBzaXplPSIyIj48c3BhbiBzdHlsZT0iZm9udC1z
aXplOjExcHQ7Ij4mbmJzcDs8L3NwYW4+PC9mb250PjwvZGl2Pg0KPGRpdj5JZiBJIHdlcmUgYXNr
ZWQgdG8gZ2V0IG9mZiB0aGUgZmVuY2UsIEnigJlkIHByb2JhYmx5IGxhbmQgb24gdGhlIHNpZGUg
d2hlcmUgeW91IHNpbGVudGx5IChhbmQgb3B0aW9uYWxseSByZXBvcnQgdG8geW91cjwvZGl2Pg0K
PGRpdj5tYW5hZ2VtZW50IGludGVyZmFjZSwgdXAgdG8geW91ciBpbXBsZW1lbnRhdGlvbiByZWFs
bHkpIGlnbm9yZSBpbnZhbGlkIG9yIGlsbGVnYWwgRExFUCBtZXNzYWdlcy4gRXZlbiBpZiBpdCBt
ZWFuczwvZGl2Pg0KPGRpdj50aGUgc2VuZGVyIG9mIHN1Y2ggaWxsaWNpdCBtYXRlcmlhbCBtYXkg
Y29tcGxhaW4gYWJvdXQgbWlzc2luZyBBQ0tzLCB3ZWxsIHRvdWdoIG9uIHRoZW0gcmVhbGx5Ljwv
ZGl2Pg0KPGRpdj48Zm9udCBmYWNlPSJDYWxpYnJpIiBzaXplPSIyIj48c3BhbiBzdHlsZT0iZm9u
dC1zaXplOjExcHQ7Ij4mbmJzcDs8L3NwYW4+PC9mb250PjwvZGl2Pg0KPGRpdj4yKSBJbnZhbGlk
IERhdGEgSXRlbXMgLSBJIHRoaW5rIHRoZXNlIGNhbiBjZXJ0YWlubHkgYmUgbG9vc2VuZWQgYW5k
IEkgYWdyZWUgd2l0aCByZXNwb25kaW5nIHdpdGggYSBOQUNLIG9yIHN1aXRhYmxlPC9kaXY+DQo8
ZGl2PmVxdWl2YWxlbnQuPC9kaXY+DQo8ZGl2Pjxmb250IGZhY2U9IkNhbGlicmkiIHNpemU9IjIi
PjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTFwdDsiPiZuYnNwOzwvc3Bhbj48L2ZvbnQ+PC9kaXY+
DQo8ZGl2PlJlZ2FyZHM8L2Rpdj4NCjxkaXY+Jm5ic3A7PC9kaXY+DQo8ZGl2PlN0ZXZlPC9kaXY+
DQo8ZGl2Pjxmb250IGZhY2U9IkNhbGlicmkiIHNpemU9IjIiPjxzcGFuIHN0eWxlPSJmb250LXNp
emU6MTFwdDsiPiZuYnNwOzwvc3Bhbj48L2ZvbnQ+PC9kaXY+DQo8L3NwYW4+PC9mb250Pg0KPC9i
b2R5Pg0KPC9odG1sPg0KDQo8dGFibGU+PHRyPjx0ZCBiZ2NvbG9yPSNmZmZmZmY+PGZvbnQgY29s
b3I9IzAwMDAwMD48cHJlPlRoaXMgZW1haWwgKGluY2x1ZGluZyBhbnkgYXR0YWNobWVudHMpIG1h
eSBjb250YWluIGNvbmZpZGVudGlhbCBhbmQvb3IgcHJpdmlsZWdlZCBpbmZvcm1hdGlvbiBvciBp
bmZvcm1hdGlvbiBvdGhlcndpc2UgcHJvdGVjdGVkIGZyb20gZGlzY2xvc3VyZS4gSWYgeW91IGFy
ZSBub3QgdGhlIGludGVuZGVkIHJlY2lwaWVudCwgcGxlYXNlIG5vdGlmeSB0aGUgc2VuZGVyIGlt
bWVkaWF0ZWx5LCBkbyBub3QgY29weSB0aGlzIG1lc3NhZ2Ugb3IgYW55IGF0dGFjaG1lbnRzIGFu
ZCBkbyBub3QgdXNlIGl0IGZvciBhbnkgcHVycG9zZSBvciBkaXNjbG9zZSBpdHMgY29udGVudCB0
byBhbnkgcGVyc29uLCBidXQgZGVsZXRlIHRoaXMgbWVzc2FnZSBhbmQgYW55IGF0dGFjaG1lbnRz
IGZyb20geW91ciBzeXN0ZW0uIEFpcmJ1cyBEZWZlbmNlIGFuZCBTcGFjZSBMaW1pdGVkIGRpc2Ns
YWltcyBhbnkgYW5kIGFsbCBsaWFiaWxpdHkgaWYgdGhpcyBlbWFpbCB0cmFuc21pc3Npb24gd2Fz
IHZpcnVzIGNvcnJ1cHRlZCwgYWx0ZXJlZCBvciBmYWxzaWZpZWQuDQotby0NCkVtYWlscyB0byBB
aXJidXMgRGVmZW5jZSBhbmQgU3BhY2UgTGltaXRlZCBtYXkgYmUgcHJvY2Vzc2VkLCByZWNvcmRl
ZCBhbmQgbW9uaXRvcmVkIG91dHNpZGUgdGhlIFVLLg0KLW8tDQpBaXJidXMgRGVmZW5jZSBhbmQg
U3BhY2UgTGltaXRlZCwgUmVnaXN0ZXJlZCBpbiBFbmdsYW5kIGFuZCBXYWxlcyBOby4gMjQ0OTI1
OQ0KUmVnaXN0ZXJlZCBPZmZpY2U6IEd1bm5lbHMgV29vZCBSb2FkLCBTdGV2ZW5hZ2UsIEhlcnRm
b3Jkc2hpcmUsIFNHMSAyQVMsIEVuZ2xhbmQ8L3ByZT48L2ZvbnQ+PC90ZD48L3RyPjwvdGFibGU+

--_000_D9712B947A4CCA43AB42F01B90AF1DEC011F5B8E2AAUK52982UKNUK_--


From nobody Thu Dec 10 02:06:57 2015
Return-Path: <hrogge@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 91EA91A88BC; Thu, 10 Dec 2015 02:06:55 -0800 (PST)
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 PlUglTc7rBqC; Thu, 10 Dec 2015 02:06:54 -0800 (PST)
Received: from mail-wm0-x236.google.com (mail-wm0-x236.google.com [IPv6:2a00:1450:400c:c09::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 913241A8938; Thu, 10 Dec 2015 02:06:26 -0800 (PST)
Received: by mail-wm0-x236.google.com with SMTP id c201so24790922wme.0; Thu, 10 Dec 2015 02:06:26 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=6NRw4MMuXSFReUeyRgS1IrOR0WJ8qem04ebFqg/E57k=; b=BvqnGUe/wZc5Aa506Rpm5L6geeUXF9wTYSrJr8xqnF/o+opwb9R8DA+0221QOekPYD HMmcKQrCAT7KdQZan5jSkDFCKzdkRL5RtlyuqRlIcDgI/g+NVgYZ5vUBLDiWWHjUNkwg tftnFPlTIH0BIusWpfuwJcC4B74qyMNqErVo0hAxQWbBBhuZqFyO20/m5zMMAGvjekO0 dXzZipwMtQvZk5fez+EpB6BHXGHHdJXqZ7GbsEkZrbfbamDNXnws/vdQ8/ChElaqljzE C9/3GW/qwU3WP9mSjoA0gcCk6cbNLie/oHyXS7pPgL+zIbeNglGI4kYVmzo73EFJCJrD ifew==
X-Received: by 10.28.46.137 with SMTP id u131mr16656252wmu.61.1449741985223; Thu, 10 Dec 2015 02:06:25 -0800 (PST)
MIME-Version: 1.0
Received: by 10.27.94.70 with HTTP; Thu, 10 Dec 2015 02:05:55 -0800 (PST)
In-Reply-To: <D9712B947A4CCA43AB42F01B90AF1DEC011F5B8E2A@AUK52982.UKN.UKNROOT.ASTRIUM.CORP>
References: <56687AC2.9060801@labn.net> <CALtoyomCuki__fyNnhmYoKmBcrQSSuOPGgcg8N-txG1DSaUaAg@mail.gmail.com> <56689271.306@labn.net> <23834_1449694925_566896CB_23834_3552_3_CALtoyo=JqgbqsBPo5jG-UzFR56qmAEk9zbtDBoLQUoJfcuooew@mail.gmail.com> <D9712B947A4CCA43AB42F01B90AF1DEC011F5B8E2A@AUK52982.UKN.UKNROOT.ASTRIUM.CORP>
From: Henning Rogge <hrogge@gmail.com>
Date: Thu, 10 Dec 2015 11:05:55 +0100
Message-ID: <CAGnRvurPEbzhvFGL0OrtDTvSXN9FoCfEXAfXzcAOXM27oRHPsg@mail.gmail.com>
To: "MATTY, Steven" <steven.matty@airbus.com>
Content-Type: multipart/alternative; boundary=001a11422f3c0b9fcf0526885cca
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/2-l_bpr_yqe3_63Me88d31bBjqE>
Cc: MANET IETF <manet@ietf.org>, "draft-ietf-manet-dlep@ietf.org" <draft-ietf-manet-dlep@ietf.org>
Subject: Re: [manet] DLEP-17: Handling of unknown / unexpected messages
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: <https://mailarchive.ietf.org/arch/browse/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: Thu, 10 Dec 2015 10:06:55 -0000

--001a11422f3c0b9fcf0526885cca
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Thu, Dec 10, 2015 at 10:58 AM, MATTY, Steven <steven.matty@airbus.com>
wrote:

> From: manet [mailto:manet-bounces@ietf.org <manet-bounces@ietf.org>] On
> Behalf Of Stan Ratliff
>
> 1) My inclination is towards the =E2=80=9CBe generous in what you accept=
=E2=80=9D side of
> things. But there is a trade-off when you
> are being a friendly DLEP application that accepts any and all messages
> versus trying to ensure all DLEP
> implementations are compliant. If you tear down the session whenever you
> get an invalid DLEP message then it
> will become VERY obvious, VERY quickly that you are talking with a =E2=80=
=98bad=E2=80=99
> implementation. However, let=E2=80=99s say that
> this implementation on a router is no longer supported but is actually
> very useful in everything else it does right.
>
> Would it be an option to introduce an [optional] NACK DLEP message type s=
o
> that you can report to the sender
> =E2=80=9CHey, you sent me this and something was up there=E2=80=9D rather=
 than just a
> silent discard?
>

The problem is you cannot be sure that the message was not malformed if
something goes wrong... which means you don't know where to  start the next
message in the incoming TCP stream.

Henning Rogge

--001a11422f3c0b9fcf0526885cca
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On T=
hu, Dec 10, 2015 at 10:58 AM, MATTY, Steven <span dir=3D"ltr">&lt;<a href=
=3D"mailto:steven.matty@airbus.com" target=3D"_blank">steven.matty@airbus.c=
om</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"marg=
in:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">






<div>
<font face=3D"Courier New" size=3D"2"><span style=3D"font-size:10pt">
<div>From: manet [<a href=3D"mailto:manet-bounces@ietf.org" target=3D"_blan=
k">mailto:manet-bounces@ietf.org</a>] On Behalf Of Stan Ratliff</div><span =
class=3D"">
<div>=C2=A0</div>
<div><span style=3D"font-size:10pt">1) My inclination is towards the =E2=80=
=9CBe generous in what you accept=E2=80=9D side of things. But there is a t=
rade-off when you</span><br></div></span>
<div>are being a friendly DLEP application that accepts any and all message=
s versus trying to ensure all DLEP</div>
<div>implementations are compliant. If you tear down the session whenever y=
ou get an invalid DLEP message then it</div>
<div>will become VERY obvious, VERY quickly that you are talking with a =E2=
=80=98bad=E2=80=99 implementation. However, let=E2=80=99s say that</div>
<div>this implementation on a router is no longer supported but is actually=
 very useful in everything else it does right.</div>
<div><font face=3D"Calibri" size=3D"2"><span style=3D"font-size:11pt">=C2=
=A0</span></font></div>
<div>Would it be an option to introduce an [optional] NACK DLEP message typ=
e so that you can report to the sender</div>
<div>=E2=80=9CHey, you sent me this and something was up there=E2=80=9D rat=
her than just a silent discard?</div></span></font></div></blockquote><div>=
<br></div><div>The problem is you cannot be sure that the message was not m=
alformed if something goes wrong... which means you don&#39;t know where to=
 =C2=A0start the next message in the incoming TCP stream.</div><div><br></d=
iv><div>Henning Rogge</div></div></div></div>

--001a11422f3c0b9fcf0526885cca--


From nobody Thu Dec 10 02:19:23 2015
Return-Path: <rick@tropicalstormsoftware.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 9C61A1A8965; Thu, 10 Dec 2015 02:19:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.911
X-Spam-Level: 
X-Spam-Status: No, score=-1.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 yQ1lpFrsxk0v; Thu, 10 Dec 2015 02:19:20 -0800 (PST)
Received: from mail.tropicalstormsoftware.com (mail.tropicalstormsoftware.com [188.94.42.120]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3B26A1A895C; Thu, 10 Dec 2015 02:19:20 -0800 (PST)
Received: from tss-server1.home.tropicalstormsoftware.com ([fe80::753b:fa82:5c0:af0d]) by tss-server1.home.tropicalstormsoftware.com ([fe80::753b:fa82:5c0:af0d%10]) with mapi; Thu, 10 Dec 2015 10:18:43 +0000
From: Rick Taylor <rick@tropicalstormsoftware.com>
To: Henning Rogge <hrogge@gmail.com>, Stan Ratliff <ratliffstan@gmail.com>
Thread-Topic: [manet] DLEP-17: duplicate functions - Options & extensions negotiations
Thread-Index: AQHRMralbsLpmb3j7U2fXTxohWyKMg==
Date: Thu, 10 Dec 2015 10:18:41 +0000
Message-ID: <38A5475DE83986499AEACD2CFAFC3F9801B8E96052@tss-server1.home.tropicalstormsoftware.com>
References: <56687ABA.803@labn.net> <CALtoyonnuk03=FqiyPfQS4t9mKJt81kUfkZP-JB0FD0hfRp-6Q@mail.gmail.com> <566888B0.3070806@labn.net> <CALtoyomO1YTNydyohqRczjHnivCkfPp_gwv5oRWjdRmC5yOb0Q@mail.gmail.com> <56689542.2080303@labn.net> <CALtoyomdxY8P4QgxDMgkkFg452f=rC70xKCJOEkpyJH8K+u9AA@mail.gmail.com> <CAGnRvuofzTvTjNWq2d9oA+0Cxpy8mnRc6mkpuKnLp0LLsb7M-A@mail.gmail.com> <CALtoyomqbnTJer9ekYLZ1sseFRbVv19pNXR+Y7pridCGPghejA@mail.gmail.com> <CAGnRvuqja8ngi7+mWb8zCsvUMq6anjwuVit01GWxC=2Ee9iQ6w@mail.gmail.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/_Qut15KyVSmrQYJIy2CTgaSVTbo>
Cc: MANET IETF <manet@ietf.org>, "draft-ietf-manet-dlep@ietf.org" <draft-ietf-manet-dlep@ietf.org>
Subject: Re: [manet] DLEP-17: duplicate functions - Options & extensions negotiations
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: <https://mailarchive.ietf.org/arch/browse/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: Thu, 10 Dec 2015 10:19:22 -0000

I have previously used a Session Update message to carry extension data=0A=
items after Session Init.  Rather than include 'unknown' data items too=0A=
early (check my dlep destination service announcement draft)=0A=
=0A=
I must admit to not being keen on adding an extra Init step to the state=0A=
machine with another message.=0A=
=0A=
There might be some cross-over here however.  If we handle 'unexpected=0A=
data item' as a 'continue' status code, rather than a 'terminate', then=0A=
the issue disappears (apart from the 2-pass parse, but it's only at=0A=
session init, so I don't care about performance here).=0A=
=0A=
Rick (still on vacation...)=0A=
=0A=
=0A=
On 09/12/15 22:23, Henning Rogge wrote:=0A=
> On Wed, Dec 9, 2015 at 11:09 PM, Stan Ratliff <ratliffstan@gmail.com> wro=
te:=0A=
>> Yeah... two-stage parsing... don't know about you, but I'd like to avoid=
=0A=
>> that.=0A=
> What I am doing at the moment is having a place to store every data=0A=
> item I support... this way its possible to do a single-stage parsing.=0A=
>=0A=
> Default values are only delivered by the radio to the router if I=0A=
> remember it correctly, which happens after the router tells the radio=0A=
> what it supports.=0A=
>=0A=
> This means the router can instantly drop the session if it gets a=0A=
> metric it does not support.=0A=
>=0A=
>>> We only have a few mandatory metrics (link speed related things,=0A=
>>> right?)... I am not sure I am good with dropping them too.=0A=
>>>=0A=
>>>=0A=
>>> This gives a router at least a chance to determine what this radio is=
=0A=
>>> useful for.=0A=
>>=0A=
>> IMO, being able to negatively acknowledge the Session Metrics Init messa=
ge=0A=
>> does the same thing, I think - a router has the opportunity to look at t=
he=0A=
>> metrics being advertised by a modem, and make the determination you spea=
k=0A=
>> of. Just for the record - I think a modem implementation that doesn't=0A=
>> announce link speed is pretty silly. But then, I don't claim to understa=
nd=0A=
>> each and every possible use case. Something that is totally absurd to us=
=0A=
>> might actually work for someone...=0A=
> In fact its even "okay" to report both link speed and maximum link=0A=
> speed once at a constant... so this should be EASY for any kind of=0A=
> implementation.=0A=
>=0A=
> Link speed is hard to measure for the router... lets keep it in there.=0A=
>=0A=
> Henning=0A=
>=0A=
> _______________________________________________=0A=
> manet mailing list=0A=
> manet@ietf.org=0A=
> https://www.ietf.org/mailman/listinfo/manet=0A=
>=0A=
=0A=


From nobody Thu Dec 10 02:21:05 2015
Return-Path: <chris.dearlove@baesystems.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 A80ED1A896B; Thu, 10 Dec 2015 02:21:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] 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 9PTmHcz_5Bwq; Thu, 10 Dec 2015 02:21:00 -0800 (PST)
Received: from ukmta4.baesystems.com (ukmta4.baesystems.com [20.133.40.56]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EB0341A8968; Thu, 10 Dec 2015 02:20:59 -0800 (PST)
X-IronPort-AV: E=Sophos;i="5.20,407,1444690800"; d="scan'208";a="19872043"
Received: from unknown (HELO baemasodc005.greenlnk.net) ([10.108.52.29]) by ukmta4.baesystems.com with ESMTP; 10 Dec 2015 10:20:58 +0000
X-IronPort-AV: E=Sophos;i="5.20,407,1444690800"; d="scan'208";a="126837261"
Received: from glkxh0005v.greenlnk.net ([10.109.2.36]) by baemasodc005.greenlnk.net with ESMTP; 10 Dec 2015 10:20:58 +0000
Received: from GLKXM0002V.GREENLNK.net ([169.254.5.210]) by GLKXH0005V.GREENLNK.net ([10.109.2.36]) with mapi id 14.03.0248.002; Thu, 10 Dec 2015 10:20:58 +0000
From: "Dearlove, Christopher (UK)" <chris.dearlove@baesystems.com>
To: Lou Berger <lberger@labn.net>, "draft-ietf-manet-dlep@ietf.org" <draft-ietf-manet-dlep@ietf.org>, MANET IETF <manet@ietf.org>
Thread-Topic: [manet] DLEP-17: duplicate functions - Options & extensions negotiations
Thread-Index: AQHRMrQsg/agj/RxDUmZYnE4zJhtUZ7D/oWw
Date: Thu, 10 Dec 2015 10:20:57 +0000
Message-ID: <B31EEDDDB8ED7E4A93FDF12A4EECD30D848E753E@GLKXM0002V.GREENLNK.net>
References: <56687ABA.803@labn.net>
In-Reply-To: <56687ABA.803@labn.net>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.109.62.6]
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/FC99oZbecZ1zhncDVqv7MUHO4Qs>
Subject: Re: [manet] DLEP-17: duplicate functions - Options & extensions negotiations
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: <https://mailarchive.ietf.org/arch/browse/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: Thu, 10 Dec 2015 10:21:03 -0000

I commented (and so far I've had one comment on one detail I noted, nothing=
 else) on that the draft makes reference to an extensions register, and the=
n really doesn't specify it.

I think part of this issue is that what an extension is needs more specific=
ation.

Is an extension defined completely by a list of new messages and/or data it=
ems that it consists of?

If no, what else? (Yes of course a new message requires new processing, but=
 is that fully defined by the message type?)

If yes, why not drop the extensions register, and just list the messages an=
d data items directly? OK, then there's an issue of what needs listing? And=
 then you end up at Lou's comment, just list everything you are using. (Whi=
ch needs to interact correctly with indicating default values.)

This does depend on the yes/no question above - and I think that regardless=
, the draft needs to be clearer on what an extension is to allow it to be a=
nswered.

There might be an issue with listing lots of items. Except you need to do t=
his anyway for default values if I understand correctly.



-----Original Message-----
From: manet [mailto:manet-bounces@ietf.org] On Behalf Of Lou Berger
Sent: 09 December 2015 19:02
To: draft-ietf-manet-dlep@ietf.org; MANET IETF
Subject: [manet] DLEP-17: duplicate functions - Options & extensions negoti=
ations

----------------------! WARNING ! ---------------------- This message origi=
nates from outside our organisation, either from an external partner or fro=
m the internet.
Consider carefully whether you should click on any links, open any attachme=
nts or reply.
Follow the 'Report Suspicious Emails' link on IT matters for instructions o=
n reporting suspicious email messages.
--------------------------------------------------------

*** WARNING ***
EXTERNAL EMAIL -- This message originates from outside our organization.


Authors/WG,

The current version of DLEP contains two negotiations as part of a Session =
Initialization transaction:
1) <Extensions Supported> is included in both the <Session
Initialization> and <Session Initialization Response> messages
2) the optional data items, <Resources> and <Relative Link Quality>

Both have parallel allocation policies:

   +-------------+-----------------------------------------------------+
   | Type Code   | Description                                         |
   +-------------+-----------------------------------------------------+
   | 0           | Reserved                                            |
   | 1           | Status (Section 10.1)                               |
     ...
   | 20          | Relative Link Quality (Transmit) (RLQT) (Section    |
   | 21-65407    | Reserved for future extensions                      |
   | 65408-65534 | Private Use. Available for experiments              |
   | 65535       | Reserved                                            |
   +-------------+-----------------------------------------------------+

                       Table 2: DLEP Data Item types

   +-------------+-----------------------------------------------------+
   | Code        | Description                                         |
   +-------------+-----------------------------------------------------+
   | 0           | Reserved                                            |
   | 1           | Credit Windowing                                    |
   | 2-65519     | Reserved for future extensions                      |
   | 65520-65534 | Private Use. Available for experiments              |
   | 65535       | Reserved                                            |
   +-------------+-----------------------------------------------------+

                       Table 4: DLEP Extension types

It seems to me that given the current definition, one of these two should s=
uffice.  I don't have a strong opinion on which, but do strongly believe th=
at a single approach should be selected to facilitate interoperability.

To be clear, the following spells out the options:

Option A: Extensions (aka capabilities) based
  Any optional or new data item or message would need to be indicated
  in <Extensions Supported> to be used.  To cover the current optional
  data items the following would need to be defined:
    | 1 | Resources |
    | 2 | Relative Link Quality |
    | 3 | Credit Windowing |
  <Session Initialization Response> could still contain the optional
  data items, if the corresponding type is present in <Extensions
  Supported>

  Note that other messages will still use optional data items.

Option B: Data item based.
  An optional or new data item must be both Session Initialization
  messages to be used. To allow/enable <Resources> and <Relative Link
  Quality>, they would need to be included in both the <Session
  Initialization> and <Session Initialization Response> messages.

  To enable the Credit Windowing extension, the three credit-related
  state items, <Grant>, <Window Status>, and <Request> would need to be
  included in both session init messages for the full extension to be
  used.

Option C: keep both
  Keep current text

While I like Option A and have seen similar approaches in other protocols, =
e.g., BGP Capabilities, I actually have a slight preference for B.  The rea=
son for this is DLEP uses optional data items in other places and implement=
ations will already need to handle this, so it seems like option B will pro=
bably require smaller incremental code.

Either way, I think Option C is much less desirable then either of the othe=
r options.

Thoughts? Opinions?

Lou

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


From nobody Thu Dec 10 03:25:41 2015
Return-Path: <hrogge@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 BD67B1ACDC6; Thu, 10 Dec 2015 03:25:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 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, 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 snGwLNROlBGH; Thu, 10 Dec 2015 03:25:39 -0800 (PST)
Received: from mail-wm0-x22a.google.com (mail-wm0-x22a.google.com [IPv6:2a00:1450:400c:c09::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 063711ACDC3; Thu, 10 Dec 2015 03:25:39 -0800 (PST)
Received: by mail-wm0-x22a.google.com with SMTP id w144so19431042wmw.1; Thu, 10 Dec 2015 03:25:38 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; bh=aOD4KYqfOwlBDQJK1SMfDxHONN7q0mjMKQSdUXAXf3I=; b=udUT42qKdAB0X6PPSFzkx14ybFMZ+2AM0A3xLtNtiHEnBEjQvEcctpaNmESdBJcoYx /UgGaKSkwwiOOOzGAN7QW3mJ2nyLOSReD2jmwofbF0u0aB+ISTAjNCDOFbJgRfFSm+li lwMWWyzOVWaaFQpppBwZEvSUpSIlGwfLJf4UX0ox+DqG8m3MkrdORabQ7NofNl6wIc3j A467uTl6UrYWMhLKDipHYrcHEmFU97TcdPerPv6jrwUbdBM+J3SnamHVKRJ22ZD6UUQH zR+3hXfzt/gA37I9W+Lm2Ss7t7vPWXCDeWX2Yxq+yxNANFKN8Jd55/LHN4RFNB0Phhme vvwQ==
X-Received: by 10.194.2.193 with SMTP id 1mr12466078wjw.26.1449746737662; Thu, 10 Dec 2015 03:25:37 -0800 (PST)
MIME-Version: 1.0
Received: by 10.27.94.70 with HTTP; Thu, 10 Dec 2015 03:25:08 -0800 (PST)
In-Reply-To: <B31EEDDDB8ED7E4A93FDF12A4EECD30D848E753E@GLKXM0002V.GREENLNK.net>
References: <56687ABA.803@labn.net> <B31EEDDDB8ED7E4A93FDF12A4EECD30D848E753E@GLKXM0002V.GREENLNK.net>
From: Henning Rogge <hrogge@gmail.com>
Date: Thu, 10 Dec 2015 12:25:08 +0100
Message-ID: <CAGnRvurVT2OF8sFa6va6k=zt4dA4gk2vK4Y+UnRd8d1WjBocMA@mail.gmail.com>
To: "Dearlove, Christopher (UK)" <chris.dearlove@baesystems.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/-Qdjk3N8JyYC6CuHtzYzDue-DvU>
Cc: MANET IETF <manet@ietf.org>, "draft-ietf-manet-dlep@ietf.org" <draft-ietf-manet-dlep@ietf.org>
Subject: Re: [manet] DLEP-17: duplicate functions - Options & extensions negotiations
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: <https://mailarchive.ietf.org/arch/browse/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: Thu, 10 Dec 2015 11:25:40 -0000

On Thu, Dec 10, 2015 at 11:20 AM, Dearlove, Christopher (UK)
<chris.dearlove@baesystems.com> wrote:
> I commented (and so far I've had one comment on one detail I noted, nothi=
ng else) on that the draft makes reference to an extensions register, and t=
hen really doesn't specify it.

Maybe it should be something like an "extension id" registry?

> I think part of this issue is that what an extension is needs more specif=
ication.
>
> Is an extension defined completely by a list of new messages and/or data =
items that it consists of?

Not necessarily.

> If no, what else? (Yes of course a new message requires new processing, b=
ut is that fully defined by the message type?)

We don't know... that is why it is an extension... to add protocol
functionality we don't know yet.

> If yes, why not drop the extensions register, and just list the messages =
and data items directly? OK, then there's an issue of what needs listing? A=
nd then you end up at Lou's comment, just list everything you are using. (W=
hich needs to interact correctly with indicating default values.)
>
> This does depend on the yes/no question above - and I think that regardle=
ss, the draft needs to be clearer on what an extension is to allow it to be=
 answered.
>
> There might be an issue with listing lots of items. Except you need to do=
 this anyway for default values if I understand correctly.

Henning Rogge


From nobody Thu Dec 10 04:33:08 2015
Return-Path: <chris.dearlove@baesystems.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 412F61AD371; Thu, 10 Dec 2015 04:33:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] 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 Owj65IZk8aSa; Thu, 10 Dec 2015 04:33:05 -0800 (PST)
Received: from ukmta4.baesystems.com (ukmta4.baesystems.com [20.133.40.56]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0B3061AD373; Thu, 10 Dec 2015 04:33:03 -0800 (PST)
X-IronPort-AV: E=Sophos;i="5.20,408,1444690800"; d="scan'208";a="19906319"
Received: from unknown (HELO baemasodc005.greenlnk.net) ([10.108.52.29]) by ukmta4.baesystems.com with ESMTP; 10 Dec 2015 12:33:01 +0000
X-IronPort-AV: E=Sophos;i="5.20,408,1444690800"; d="scan'208";a="126871393"
Received: from glkxh0005v.greenlnk.net ([10.109.2.36]) by baemasodc005.greenlnk.net with ESMTP; 10 Dec 2015 12:33:01 +0000
Received: from GLKXM0002V.GREENLNK.net ([169.254.5.210]) by GLKXH0005V.GREENLNK.net ([10.109.2.36]) with mapi id 14.03.0248.002; Thu, 10 Dec 2015 12:33:01 +0000
From: "Dearlove, Christopher (UK)" <chris.dearlove@baesystems.com>
To: Henning Rogge <hrogge@gmail.com>
Thread-Topic: [manet] DLEP-17: duplicate functions - Options & extensions negotiations
Thread-Index: AQHRMz2Hhbdl5RU/lkCjbmocngG5VJ7EJjZw
Date: Thu, 10 Dec 2015 12:33:00 +0000
Message-ID: <B31EEDDDB8ED7E4A93FDF12A4EECD30D848E75EB@GLKXM0002V.GREENLNK.net>
References: <56687ABA.803@labn.net> <B31EEDDDB8ED7E4A93FDF12A4EECD30D848E753E@GLKXM0002V.GREENLNK.net> <CAGnRvurVT2OF8sFa6va6k=zt4dA4gk2vK4Y+UnRd8d1WjBocMA@mail.gmail.com>
In-Reply-To: <CAGnRvurVT2OF8sFa6va6k=zt4dA4gk2vK4Y+UnRd8d1WjBocMA@mail.gmail.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.109.62.6]
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/gZ8orx3igvLeyvrxATzLcCcv-lg>
Cc: MANET IETF <manet@ietf.org>, "draft-ietf-manet-dlep@ietf.org" <draft-ietf-manet-dlep@ietf.org>
Subject: Re: [manet] DLEP-17: duplicate functions - Options & extensions negotiations
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: <https://mailarchive.ietf.org/arch/browse/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: Thu, 10 Dec 2015 12:33:07 -0000

SSB0aGluayBpdCdzIHdvcnRoIGp1c3QgdGhpbmtpbmcgYWJvdXQgdGhpcy4gQ2FuIHlvdSBzdWdn
ZXN0IGEgcGxhdXNpYmxlIGV4YW1wbGUgd2hlcmUgeW91IG5lZWQgbW9yZSBpbmZvcm1hdGlvbiB0
aGFuIGp1c3QgbmV3IG1lc3NhZ2UgYW5kIGRhdGEgaXRlbSB0eXBlcz8gSXQgY2FuIGJlIGFuIGFs
aWVuIHNwYWNlIGJhdHMgZXhhbXBsZSA7KQ0KDQooT2YgY291cnNlIHRoZXJlJ3MgbW9yZSBuZWVk
ZWQgaW1wbGljaXRseSAtIHN1Y2ggYXMgd2hhdCB0byBkbyB3aXRoIGEgbmV3IG1lc3NhZ2UgdHlw
ZS4gQnV0IHRoZSByZXF1aXJlZCBpbmZvcm1hdGlvbiBjYW4gYmUgY2FycmllZCBieSBqdXN0IHRo
ZSBuZXcgbWVzc2FnZSB0eXBlIG51bWJlci4pDQoNCg0KLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0t
LS0NCkZyb206IEhlbm5pbmcgUm9nZ2UgW21haWx0bzpocm9nZ2VAZ21haWwuY29tXSANClNlbnQ6
IDEwIERlY2VtYmVyIDIwMTUgMTE6MjUNClRvOiBEZWFybG92ZSwgQ2hyaXN0b3BoZXIgKFVLKQ0K
Q2M6IExvdSBCZXJnZXI7IGRyYWZ0LWlldGYtbWFuZXQtZGxlcEBpZXRmLm9yZzsgTUFORVQgSUVU
Rg0KU3ViamVjdDogUmU6IFttYW5ldF0gRExFUC0xNzogZHVwbGljYXRlIGZ1bmN0aW9ucyAtIE9w
dGlvbnMgJiBleHRlbnNpb25zIG5lZ290aWF0aW9ucw0KDQotLS0tLS0tLS0tLS0tLS0tLS0tLS0t
ISBXQVJOSU5HICEgLS0tLS0tLS0tLS0tLS0tLS0tLS0tLSBUaGlzIG1lc3NhZ2Ugb3JpZ2luYXRl
cyBmcm9tIG91dHNpZGUgb3VyIG9yZ2FuaXNhdGlvbiwgZWl0aGVyIGZyb20gYW4gZXh0ZXJuYWwg
cGFydG5lciBvciBmcm9tIHRoZSBpbnRlcm5ldC4NCkNvbnNpZGVyIGNhcmVmdWxseSB3aGV0aGVy
IHlvdSBzaG91bGQgY2xpY2sgb24gYW55IGxpbmtzLCBvcGVuIGFueSBhdHRhY2htZW50cyBvciBy
ZXBseS4NCkZvbGxvdyB0aGUgJ1JlcG9ydCBTdXNwaWNpb3VzIEVtYWlscycgbGluayBvbiBJVCBt
YXR0ZXJzIGZvciBpbnN0cnVjdGlvbnMgb24gcmVwb3J0aW5nIHN1c3BpY2lvdXMgZW1haWwgbWVz
c2FnZXMuDQotLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLQ0KDQpPbiBUaHUsIERlYyAxMCwgMjAxNSBhdCAxMToyMCBBTSwgRGVhcmxvdmUsIENo
cmlzdG9waGVyIChVSykgPGNocmlzLmRlYXJsb3ZlQGJhZXN5c3RlbXMuY29tPiB3cm90ZToNCj4g
SSBjb21tZW50ZWQgKGFuZCBzbyBmYXIgSSd2ZSBoYWQgb25lIGNvbW1lbnQgb24gb25lIGRldGFp
bCBJIG5vdGVkLCBub3RoaW5nIGVsc2UpIG9uIHRoYXQgdGhlIGRyYWZ0IG1ha2VzIHJlZmVyZW5j
ZSB0byBhbiBleHRlbnNpb25zIHJlZ2lzdGVyLCBhbmQgdGhlbiByZWFsbHkgZG9lc24ndCBzcGVj
aWZ5IGl0Lg0KDQpNYXliZSBpdCBzaG91bGQgYmUgc29tZXRoaW5nIGxpa2UgYW4gImV4dGVuc2lv
biBpZCIgcmVnaXN0cnk/DQoNCj4gSSB0aGluayBwYXJ0IG9mIHRoaXMgaXNzdWUgaXMgdGhhdCB3
aGF0IGFuIGV4dGVuc2lvbiBpcyBuZWVkcyBtb3JlIHNwZWNpZmljYXRpb24uDQo+DQo+IElzIGFu
IGV4dGVuc2lvbiBkZWZpbmVkIGNvbXBsZXRlbHkgYnkgYSBsaXN0IG9mIG5ldyBtZXNzYWdlcyBh
bmQvb3IgZGF0YSBpdGVtcyB0aGF0IGl0IGNvbnNpc3RzIG9mPw0KDQpOb3QgbmVjZXNzYXJpbHku
DQoNCj4gSWYgbm8sIHdoYXQgZWxzZT8gKFllcyBvZiBjb3Vyc2UgYSBuZXcgbWVzc2FnZSByZXF1
aXJlcyBuZXcgDQo+IHByb2Nlc3NpbmcsIGJ1dCBpcyB0aGF0IGZ1bGx5IGRlZmluZWQgYnkgdGhl
IG1lc3NhZ2UgdHlwZT8pDQoNCldlIGRvbid0IGtub3cuLi4gdGhhdCBpcyB3aHkgaXQgaXMgYW4g
ZXh0ZW5zaW9uLi4uIHRvIGFkZCBwcm90b2NvbCBmdW5jdGlvbmFsaXR5IHdlIGRvbid0IGtub3cg
eWV0Lg0KDQo+IElmIHllcywgd2h5IG5vdCBkcm9wIHRoZSBleHRlbnNpb25zIHJlZ2lzdGVyLCBh
bmQganVzdCBsaXN0IHRoZSANCj4gbWVzc2FnZXMgYW5kIGRhdGEgaXRlbXMgZGlyZWN0bHk/IE9L
LCB0aGVuIHRoZXJlJ3MgYW4gaXNzdWUgb2Ygd2hhdCANCj4gbmVlZHMgbGlzdGluZz8gQW5kIHRo
ZW4geW91IGVuZCB1cCBhdCBMb3UncyBjb21tZW50LCBqdXN0IGxpc3QgDQo+IGV2ZXJ5dGhpbmcg
eW91IGFyZSB1c2luZy4gKFdoaWNoIG5lZWRzIHRvIGludGVyYWN0IGNvcnJlY3RseSB3aXRoIA0K
PiBpbmRpY2F0aW5nIGRlZmF1bHQgdmFsdWVzLikNCj4NCj4gVGhpcyBkb2VzIGRlcGVuZCBvbiB0
aGUgeWVzL25vIHF1ZXN0aW9uIGFib3ZlIC0gYW5kIEkgdGhpbmsgdGhhdCByZWdhcmRsZXNzLCB0
aGUgZHJhZnQgbmVlZHMgdG8gYmUgY2xlYXJlciBvbiB3aGF0IGFuIGV4dGVuc2lvbiBpcyB0byBh
bGxvdyBpdCB0byBiZSBhbnN3ZXJlZC4NCj4NCj4gVGhlcmUgbWlnaHQgYmUgYW4gaXNzdWUgd2l0
aCBsaXN0aW5nIGxvdHMgb2YgaXRlbXMuIEV4Y2VwdCB5b3UgbmVlZCB0byBkbyB0aGlzIGFueXdh
eSBmb3IgZGVmYXVsdCB2YWx1ZXMgaWYgSSB1bmRlcnN0YW5kIGNvcnJlY3RseS4NCg0KSGVubmlu
ZyBSb2dnZQ0KKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioq
KioqKioqKioqKioqKioqKioqKioKVGhpcyBlbWFpbCBhbmQgYW55IGF0dGFjaG1lbnRzIGFyZSBj
b25maWRlbnRpYWwgdG8gdGhlIGludGVuZGVkCnJlY2lwaWVudCBhbmQgbWF5IGFsc28gYmUgcHJp
dmlsZWdlZC4gSWYgeW91IGFyZSBub3QgdGhlIGludGVuZGVkCnJlY2lwaWVudCBwbGVhc2UgZGVs
ZXRlIGl0IGZyb20geW91ciBzeXN0ZW0gYW5kIG5vdGlmeSB0aGUgc2VuZGVyLgpZb3Ugc2hvdWxk
IG5vdCBjb3B5IGl0IG9yIHVzZSBpdCBmb3IgYW55IHB1cnBvc2Ugbm9yIGRpc2Nsb3NlIG9yCmRp
c3RyaWJ1dGUgaXRzIGNvbnRlbnRzIHRvIGFueSBvdGhlciBwZXJzb24uCioqKioqKioqKioqKioq
KioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqCg==


From nobody Thu Dec 10 04:40:29 2015
Return-Path: <hrogge@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 8D8C31A8A81; Thu, 10 Dec 2015 04:40:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 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, 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 6NJc2TndeobT; Thu, 10 Dec 2015 04:40:24 -0800 (PST)
Received: from mail-wm0-x22c.google.com (mail-wm0-x22c.google.com [IPv6:2a00:1450:400c:c09::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 39F651B29BD; Thu, 10 Dec 2015 04:39:34 -0800 (PST)
Received: by wmww144 with SMTP id w144so22884869wmw.0; Thu, 10 Dec 2015 04:39:32 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=zLqyn36nTwCvfECPtcvwW7loiKBvSXtlCqAaPoyPqPU=; b=Ca902qpgC+LK3wOSDF3LsvMpiPkHtZJlucC1vq5sNmlfoTkhbBtT0dU+A3D/FPH4G5 Kpgp4xeBv4ZPVHVk8ApOl3+r4eCzG98VTTafO1GhtRIuvzHh/5RIi39sZalZJN0tsvOg sS+ybbUqiSMZVkbasePqsIiPxQCa+/2ArpZBPpYUFsm5MtYLmuQi0tE/Rq9/C7CQBGPm HXx6kxFztIXdbFdq09NyCJ49K0ZfmlQr9iOWQ8ZeZxjckjc51qWr1S2SdanoTDMpizMW jB3xBzkGrzQsoSMa0NWYLoogmHS1w4Qmpo7jGcEeV4tFgT4RKaFLkTk+FekA/+mKhRnN mf4A==
X-Received: by 10.194.109.194 with SMTP id hu2mr12200731wjb.134.1449751172839;  Thu, 10 Dec 2015 04:39:32 -0800 (PST)
MIME-Version: 1.0
Received: by 10.27.94.70 with HTTP; Thu, 10 Dec 2015 04:39:03 -0800 (PST)
In-Reply-To: <B31EEDDDB8ED7E4A93FDF12A4EECD30D848E75EB@GLKXM0002V.GREENLNK.net>
References: <56687ABA.803@labn.net> <B31EEDDDB8ED7E4A93FDF12A4EECD30D848E753E@GLKXM0002V.GREENLNK.net> <CAGnRvurVT2OF8sFa6va6k=zt4dA4gk2vK4Y+UnRd8d1WjBocMA@mail.gmail.com> <B31EEDDDB8ED7E4A93FDF12A4EECD30D848E75EB@GLKXM0002V.GREENLNK.net>
From: Henning Rogge <hrogge@gmail.com>
Date: Thu, 10 Dec 2015 13:39:03 +0100
Message-ID: <CAGnRvupVxGfhBEws8ntpTf=bWi9SSXfLUGpz8f2XAigaiPanCg@mail.gmail.com>
To: "Dearlove, Christopher (UK)" <chris.dearlove@baesystems.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/bYwsknTN16obWrVjIaCyF82DI34>
Cc: MANET IETF <manet@ietf.org>, "draft-ietf-manet-dlep@ietf.org" <draft-ietf-manet-dlep@ietf.org>
Subject: Re: [manet] DLEP-17: duplicate functions - Options & extensions negotiations
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: <https://mailarchive.ietf.org/arch/browse/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: Thu, 10 Dec 2015 12:40:26 -0000

On Thu, Dec 10, 2015 at 1:33 PM, Dearlove, Christopher (UK)
<chris.dearlove@baesystems.com> wrote:
> I think it's worth just thinking about this. Can you suggest a plausible example where you need more information than just new message and data item types? It can be an alien space bats example ;)
>
> (Of course there's more needed implicitly - such as what to do with a new message type. But the required information can be carried by just the new message type number.)

We might have different kinds of "flow control" extensions using the
same kind of message.

Someone write "Flow Control Extension A"... and from the experiments
we learned that we can do a bit better than it, but its still a mutual
exclusive choice. So the author writes "Flow Control Extension B"
which reuse the messages he designed for A.

Henning Rogge


From nobody Thu Dec 10 05:15:22 2015
Return-Path: <chris.dearlove@baesystems.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 8BD911B29F3; Thu, 10 Dec 2015 05:15:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] 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 vifh4MSFQOAH; Thu, 10 Dec 2015 05:15:20 -0800 (PST)
Received: from ukmta4.baesystems.com (ukmta4.baesystems.com [20.133.40.56]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A9F161B2AF8; Thu, 10 Dec 2015 05:15:18 -0800 (PST)
X-IronPort-AV: E=Sophos;i="5.20,408,1444690800"; d="scan'208";a="19915618"
Received: from unknown (HELO baemasodc005.greenlnk.net) ([10.108.52.29]) by ukmta4.baesystems.com with ESMTP; 10 Dec 2015 13:15:17 +0000
X-IronPort-AV: E=Sophos;i="5.20,408,1444690800"; d="scan'208";a="126880098"
Received: from glkxh0005v.greenlnk.net ([10.109.2.36]) by baemasodc005.greenlnk.net with ESMTP; 10 Dec 2015 13:15:16 +0000
Received: from GLKXM0002V.GREENLNK.net ([169.254.5.210]) by GLKXH0005V.GREENLNK.net ([10.109.2.36]) with mapi id 14.03.0248.002; Thu, 10 Dec 2015 13:15:16 +0000
From: "Dearlove, Christopher (UK)" <chris.dearlove@baesystems.com>
To: Henning Rogge <hrogge@gmail.com>
Thread-Topic: [manet] DLEP-17: duplicate functions - Options & extensions negotiations
Thread-Index: AQHRMz2Hhbdl5RU/lkCjbmocngG5VJ7EJjZwgAACz4CAAAm4gA==
Date: Thu, 10 Dec 2015 13:15:15 +0000
Message-ID: <B31EEDDDB8ED7E4A93FDF12A4EECD30D848E7635@GLKXM0002V.GREENLNK.net>
References: <56687ABA.803@labn.net> <B31EEDDDB8ED7E4A93FDF12A4EECD30D848E753E@GLKXM0002V.GREENLNK.net> <CAGnRvurVT2OF8sFa6va6k=zt4dA4gk2vK4Y+UnRd8d1WjBocMA@mail.gmail.com> <B31EEDDDB8ED7E4A93FDF12A4EECD30D848E75EB@GLKXM0002V.GREENLNK.net> <CAGnRvupVxGfhBEws8ntpTf=bWi9SSXfLUGpz8f2XAigaiPanCg@mail.gmail.com>
In-Reply-To: <CAGnRvupVxGfhBEws8ntpTf=bWi9SSXfLUGpz8f2XAigaiPanCg@mail.gmail.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.109.62.6]
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/zeDdTkRKb_KFZlPN82ou3K4jYJo>
Cc: MANET IETF <manet@ietf.org>, "draft-ietf-manet-dlep@ietf.org" <draft-ietf-manet-dlep@ietf.org>
Subject: Re: [manet] DLEP-17: duplicate functions - Options & extensions negotiations
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: <https://mailarchive.ietf.org/arch/browse/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: Thu, 10 Dec 2015 13:15:21 -0000

SSdtIG5vdCBjb252aW5jZWQgYnkgdGhhdCBleGFtcGxlLiBUd28gZXh0ZW5zaW9ucyBvcGVyYXRp
bmcgdGhlIHdheSB5b3UgZGVzY3JpYmUgaXMgYSBwb3RlbnRpYWwgaW50ZXJvcGVyYWJpbGl0eSBu
aWdodG1hcmUuIERpZmZlcmVudCBhbGdvcml0aG1zIGZvciBjYWxjdWxhdGluZyB0aGUgZmxvdyBj
b250cm9sIGlzIGFscmVhZHkgYW4gaXNzdWUgLSBidXQgaXMgdGhlIHNhbWUgZXh0ZW5zaW9uLg0K
DQotLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KRnJvbTogSGVubmluZyBSb2dnZSBbbWFpbHRv
Omhyb2dnZUBnbWFpbC5jb21dIA0KU2VudDogMTAgRGVjZW1iZXIgMjAxNSAxMjozOQ0KVG86IERl
YXJsb3ZlLCBDaHJpc3RvcGhlciAoVUspDQpDYzogTG91IEJlcmdlcjsgZHJhZnQtaWV0Zi1tYW5l
dC1kbGVwQGlldGYub3JnOyBNQU5FVCBJRVRGDQpTdWJqZWN0OiBSZTogW21hbmV0XSBETEVQLTE3
OiBkdXBsaWNhdGUgZnVuY3Rpb25zIC0gT3B0aW9ucyAmIGV4dGVuc2lvbnMgbmVnb3RpYXRpb25z
DQoNCi0tLS0tLS0tLS0tLS0tLS0tLS0tLS0hIFdBUk5JTkcgISAtLS0tLS0tLS0tLS0tLS0tLS0t
LS0tIFRoaXMgbWVzc2FnZSBvcmlnaW5hdGVzIGZyb20gb3V0c2lkZSBvdXIgb3JnYW5pc2F0aW9u
LCBlaXRoZXIgZnJvbSBhbiBleHRlcm5hbCBwYXJ0bmVyIG9yIGZyb20gdGhlIGludGVybmV0Lg0K
Q29uc2lkZXIgY2FyZWZ1bGx5IHdoZXRoZXIgeW91IHNob3VsZCBjbGljayBvbiBhbnkgbGlua3Ms
IG9wZW4gYW55IGF0dGFjaG1lbnRzIG9yIHJlcGx5Lg0KRm9sbG93IHRoZSAnUmVwb3J0IFN1c3Bp
Y2lvdXMgRW1haWxzJyBsaW5rIG9uIElUIG1hdHRlcnMgZm9yIGluc3RydWN0aW9ucyBvbiByZXBv
cnRpbmcgc3VzcGljaW91cyBlbWFpbCBtZXNzYWdlcy4NCi0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tDQoNCk9uIFRodSwgRGVjIDEwLCAyMDE1
IGF0IDE6MzMgUE0sIERlYXJsb3ZlLCBDaHJpc3RvcGhlciAoVUspIDxjaHJpcy5kZWFybG92ZUBi
YWVzeXN0ZW1zLmNvbT4gd3JvdGU6DQo+IEkgdGhpbmsgaXQncyB3b3J0aCBqdXN0IHRoaW5raW5n
IGFib3V0IHRoaXMuIENhbiB5b3Ugc3VnZ2VzdCBhIA0KPiBwbGF1c2libGUgZXhhbXBsZSB3aGVy
ZSB5b3UgbmVlZCBtb3JlIGluZm9ybWF0aW9uIHRoYW4ganVzdCBuZXcgDQo+IG1lc3NhZ2UgYW5k
IGRhdGEgaXRlbSB0eXBlcz8gSXQgY2FuIGJlIGFuIGFsaWVuIHNwYWNlIGJhdHMgZXhhbXBsZSA7
KQ0KPg0KPiAoT2YgY291cnNlIHRoZXJlJ3MgbW9yZSBuZWVkZWQgaW1wbGljaXRseSAtIHN1Y2gg
YXMgd2hhdCB0byBkbyB3aXRoIGEgDQo+IG5ldyBtZXNzYWdlIHR5cGUuIEJ1dCB0aGUgcmVxdWly
ZWQgaW5mb3JtYXRpb24gY2FuIGJlIGNhcnJpZWQgYnkganVzdCANCj4gdGhlIG5ldyBtZXNzYWdl
IHR5cGUgbnVtYmVyLikNCg0KV2UgbWlnaHQgaGF2ZSBkaWZmZXJlbnQga2luZHMgb2YgImZsb3cg
Y29udHJvbCIgZXh0ZW5zaW9ucyB1c2luZyB0aGUgc2FtZSBraW5kIG9mIG1lc3NhZ2UuDQoNClNv
bWVvbmUgd3JpdGUgIkZsb3cgQ29udHJvbCBFeHRlbnNpb24gQSIuLi4gYW5kIGZyb20gdGhlIGV4
cGVyaW1lbnRzIHdlIGxlYXJuZWQgdGhhdCB3ZSBjYW4gZG8gYSBiaXQgYmV0dGVyIHRoYW4gaXQs
IGJ1dCBpdHMgc3RpbGwgYSBtdXR1YWwgZXhjbHVzaXZlIGNob2ljZS4gU28gdGhlIGF1dGhvciB3
cml0ZXMgIkZsb3cgQ29udHJvbCBFeHRlbnNpb24gQiINCndoaWNoIHJldXNlIHRoZSBtZXNzYWdl
cyBoZSBkZXNpZ25lZCBmb3IgQS4NCg0KSGVubmluZyBSb2dnZQ0KKioqKioqKioqKioqKioqKioq
KioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioKVGhpcyBl
bWFpbCBhbmQgYW55IGF0dGFjaG1lbnRzIGFyZSBjb25maWRlbnRpYWwgdG8gdGhlIGludGVuZGVk
CnJlY2lwaWVudCBhbmQgbWF5IGFsc28gYmUgcHJpdmlsZWdlZC4gSWYgeW91IGFyZSBub3QgdGhl
IGludGVuZGVkCnJlY2lwaWVudCBwbGVhc2UgZGVsZXRlIGl0IGZyb20geW91ciBzeXN0ZW0gYW5k
IG5vdGlmeSB0aGUgc2VuZGVyLgpZb3Ugc2hvdWxkIG5vdCBjb3B5IGl0IG9yIHVzZSBpdCBmb3Ig
YW55IHB1cnBvc2Ugbm9yIGRpc2Nsb3NlIG9yCmRpc3RyaWJ1dGUgaXRzIGNvbnRlbnRzIHRvIGFu
eSBvdGhlciBwZXJzb24uCioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioq
KioqKioqKioqKioqKioqKioqKioqKioqKioqCg==


From nobody Thu Dec 10 05:57:33 2015
Return-Path: <ratliffstan@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 0493A1B2EA7; Thu, 10 Dec 2015 05:57:32 -0800 (PST)
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 QQLGCEzhdnXE; Thu, 10 Dec 2015 05:57:25 -0800 (PST)
Received: from mail-lb0-x233.google.com (mail-lb0-x233.google.com [IPv6:2a00:1450:4010:c04::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1D8481B308B; Thu, 10 Dec 2015 05:57:09 -0800 (PST)
Received: by lbbcs9 with SMTP id cs9so51174293lbb.1; Thu, 10 Dec 2015 05:57:07 -0800 (PST)
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=XEL3PiPQEvT6J+wqpM+jzvXngXyqPnpB8W2Prou8tjw=; b=LKfOBM/Kfy7y4IlJG6Fkkja4SGdifm0uFgerXU9wa12cOSSw7qxiqlWffKuNPOKsVj WRHFYlqOfR6VrHXa012k+jshpuJfaLLy/ycAf9EK1AoDPLqmwLhYzNuKtDnNpvoClyvQ MFhjn2+wVoh9ffhpAFSUqYO+KHtIj5tExqQPn+nKx8Mn8oI4Xg3JCzJ99cSiDNd4uK6y p5+UnAhFF2M1Bo18eG4SV1ZgMPNfKXH/roMttrfZ7ozLEb/MxEt6RM7figzBTlJRNk+n 86R8QeoWVw116j+YjBMgDcJI39+66ygtDmJTeoI74qO2ypCIL8afE8Tb5Tho5avzJmT6 yhyg==
MIME-Version: 1.0
X-Received: by 10.112.200.40 with SMTP id jp8mr5363410lbc.104.1449755827214; Thu, 10 Dec 2015 05:57:07 -0800 (PST)
Received: by 10.25.209.71 with HTTP; Thu, 10 Dec 2015 05:57:07 -0800 (PST)
In-Reply-To: <B31EEDDDB8ED7E4A93FDF12A4EECD30D848E753E@GLKXM0002V.GREENLNK.net>
References: <56687ABA.803@labn.net> <B31EEDDDB8ED7E4A93FDF12A4EECD30D848E753E@GLKXM0002V.GREENLNK.net>
Date: Thu, 10 Dec 2015 08:57:07 -0500
Message-ID: <CALtoyo=kyOkv5nv8rsud-Q25=aSf-XW1EC7KT295-n4gXBi=5A@mail.gmail.com>
From: Stan Ratliff <ratliffstan@gmail.com>
To: "Dearlove, Christopher (UK)" <chris.dearlove@baesystems.com>
Content-Type: multipart/alternative; boundary=001a11c36b2a17a78205268b95ea
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/y9-uTIBhvYXy-kr61R3PdicsLoA>
Cc: MANET IETF <manet@ietf.org>, "draft-ietf-manet-dlep@ietf.org" <draft-ietf-manet-dlep@ietf.org>
Subject: Re: [manet] DLEP-17: duplicate functions - Options & extensions negotiations
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: <https://mailarchive.ietf.org/arch/browse/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: Thu, 10 Dec 2015 13:57:32 -0000

--001a11c36b2a17a78205268b95ea
Content-Type: text/plain; charset=UTF-8

Chris,

First up, I'm in the process of looking at your review comments - I've just
been buried by the other threads, along with the day job.


On Thu, Dec 10, 2015 at 5:20 AM, Dearlove, Christopher (UK) <
chris.dearlove@baesystems.com> wrote:

> I commented (and so far I've had one comment on one detail I noted,
> nothing else) on that the draft makes reference to an extensions register,
> and then really doesn't specify it.
>
> I think part of this issue is that what an extension is needs more
> specification.
>
> Is an extension defined completely by a list of new messages and/or data
> items that it consists of?
>

The short answer is Yes. An extension could be a group of data items,
and/or new messages to the protocol.


>
> If no, what else? (Yes of course a new message requires new processing,
> but is that fully defined by the message type?)
>
> If yes, why not drop the extensions register, and just list the messages
> and data items directly? OK, then there's an issue of what needs listing?
> And then you end up at Lou's comment, just list everything you are using.
> (Which needs to interact correctly with indicating default values.)
>

The idea with the currently documented mechanism is that new functionality,
whether that's a collection of Data Items (potentially strewn about
multiple existing messages), and/or new messages, is grouped according to
functionality and assigned an extension number. As I envision it, an
extension number would map one-to-one with a DLEP follow-on draft. The
extension, regardless of its component make-up, is either supported (it
appears in Extensions Supported) or it's not.

If you simple list *everything* (both Data Items and messages), then it's
up to the receiver to make sure that the "everything" listed actually works
- for example, if I create an extension that has 4 new messages, but your
implementation lists only 3 of them, now what? It seems easier to me to
write up a spec and introduce it into the MANET WG, talk about the 4 new
messages (because the 4 messages make up a logical function that I want to
accomplish), then add the whole logical function as an Extension.
Implementations then either support it, or they don't.


>
> This does depend on the yes/no question above - and I think that
> regardless, the draft needs to be clearer on what an extension is to allow
> it to be answered.
>
> There might be an issue with listing lots of items. Except you need to do
> this anyway for default values if I understand correctly.
>

The default notion only applies to metrics. Right now, there are 9:
MDRR/MDRT
CDRR/CDRT
Latency
RESR/REST
RLQR/RLQT

That's why I'm proposing to add the "Session Metric Initialization" message
- to clear up some of the confusion, let's not use the session init to both
(a) establish the protocol level with Extensions Supported, and (b)
establish default values for metrics that are to be flowed over the
session. Let's let the Session Init establish the effective protocol level
and "bells & whistles" in play (the Extensions), and then explicitly set
the default metric values.

Regards,
Stan



>
>
>
> -----Original Message-----
> From: manet [mailto:manet-bounces@ietf.org] On Behalf Of Lou Berger
> Sent: 09 December 2015 19:02
> To: draft-ietf-manet-dlep@ietf.org; MANET IETF
> Subject: [manet] DLEP-17: duplicate functions - Options & extensions
> negotiations
>
> ----------------------! 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.
> --------------------------------------------------------
>
> *** WARNING ***
> EXTERNAL EMAIL -- This message originates from outside our organization.
>
>
> Authors/WG,
>
> The current version of DLEP contains two negotiations as part of a Session
> Initialization transaction:
> 1) <Extensions Supported> is included in both the <Session
> Initialization> and <Session Initialization Response> messages
> 2) the optional data items, <Resources> and <Relative Link Quality>
>
> Both have parallel allocation policies:
>
>    +-------------+-----------------------------------------------------+
>    | Type Code   | Description                                         |
>    +-------------+-----------------------------------------------------+
>    | 0           | Reserved                                            |
>    | 1           | Status (Section 10.1)                               |
>      ...
>    | 20          | Relative Link Quality (Transmit) (RLQT) (Section    |
>    | 21-65407    | Reserved for future extensions                      |
>    | 65408-65534 | Private Use. Available for experiments              |
>    | 65535       | Reserved                                            |
>    +-------------+-----------------------------------------------------+
>
>                        Table 2: DLEP Data Item types
>
>    +-------------+-----------------------------------------------------+
>    | Code        | Description                                         |
>    +-------------+-----------------------------------------------------+
>    | 0           | Reserved                                            |
>    | 1           | Credit Windowing                                    |
>    | 2-65519     | Reserved for future extensions                      |
>    | 65520-65534 | Private Use. Available for experiments              |
>    | 65535       | Reserved                                            |
>    +-------------+-----------------------------------------------------+
>
>                        Table 4: DLEP Extension types
>
> It seems to me that given the current definition, one of these two should
> suffice.  I don't have a strong opinion on which, but do strongly believe
> that a single approach should be selected to facilitate interoperability.
>
> To be clear, the following spells out the options:
>
> Option A: Extensions (aka capabilities) based
>   Any optional or new data item or message would need to be indicated
>   in <Extensions Supported> to be used.  To cover the current optional
>   data items the following would need to be defined:
>     | 1 | Resources |
>     | 2 | Relative Link Quality |
>     | 3 | Credit Windowing |
>   <Session Initialization Response> could still contain the optional
>   data items, if the corresponding type is present in <Extensions
>   Supported>
>
>   Note that other messages will still use optional data items.
>
> Option B: Data item based.
>   An optional or new data item must be both Session Initialization
>   messages to be used. To allow/enable <Resources> and <Relative Link
>   Quality>, they would need to be included in both the <Session
>   Initialization> and <Session Initialization Response> messages.
>
>   To enable the Credit Windowing extension, the three credit-related
>   state items, <Grant>, <Window Status>, and <Request> would need to be
>   included in both session init messages for the full extension to be
>   used.
>
> Option C: keep both
>   Keep current text
>
> While I like Option A and have seen similar approaches in other protocols,
> e.g., BGP Capabilities, I actually have a slight preference for B.  The
> reason for this is DLEP uses optional data items in other places and
> implementations will already need to handle this, so it seems like option B
> will probably require smaller incremental code.
>
> Either way, I think Option C is much less desirable then either of the
> other options.
>
> Thoughts? Opinions?
>
> Lou
>
> _______________________________________________
> 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.
> ********************************************************************
>
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www.ietf.org/mailman/listinfo/manet
>

--001a11c36b2a17a78205268b95ea
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Chris,=C2=A0<div><br></div><div>First up, I&#39;m in the p=
rocess of looking at your review comments - I&#39;ve just been buried by th=
e other threads, along with the day job.=C2=A0</div><div><br><div class=3D"=
gmail_extra"><br><div class=3D"gmail_quote">On Thu, Dec 10, 2015 at 5:20 AM=
, Dearlove, Christopher (UK) <span dir=3D"ltr">&lt;<a href=3D"mailto:chris.=
dearlove@baesystems.com" target=3D"_blank">chris.dearlove@baesystems.com</a=
>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 =
0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I commented (and so f=
ar I&#39;ve had one comment on one detail I noted, nothing else) on that th=
e draft makes reference to an extensions register, and then really doesn&#3=
9;t specify it.<br>
<br>
I think part of this issue is that what an extension is needs more specific=
ation.<br>
<br>
Is an extension defined completely by a list of new messages and/or data it=
ems that it consists of?<br></blockquote><div><br></div><div>The short answ=
er is Yes. An extension could be a group of data items, and/or new messages=
 to the protocol.=C2=A0</div><div>=C2=A0</div><blockquote class=3D"gmail_qu=
ote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex=
">
<br>
If no, what else? (Yes of course a new message requires new processing, but=
 is that fully defined by the message type?)<br>
<br>
If yes, why not drop the extensions register, and just list the messages an=
d data items directly? OK, then there&#39;s an issue of what needs listing?=
 And then you end up at Lou&#39;s comment, just list everything you are usi=
ng. (Which needs to interact correctly with indicating default values.)<br>=
</blockquote><div><br></div><div>The idea with the currently documented mec=
hanism is that new functionality, whether that&#39;s a collection of Data I=
tems (potentially strewn about multiple existing messages), and/or new mess=
ages, is grouped according to functionality and assigned an extension numbe=
r. As I envision it, an extension number would map one-to-one with a DLEP f=
ollow-on draft. The extension, regardless of its component make-up, is eith=
er supported (it appears in Extensions Supported) or it&#39;s not.=C2=A0</d=
iv><div><br></div><div>If you simple list *everything* (both Data Items and=
 messages), then it&#39;s up to the receiver to make sure that the &quot;ev=
erything&quot; listed actually works - for example, if I create an extensio=
n that has 4 new messages, but your implementation lists only 3 of them, no=
w what? It seems easier to me to write up a spec and introduce it into the =
MANET WG, talk about the 4 new messages (because the 4 messages make up a l=
ogical function that I want to accomplish), then add the whole logical func=
tion as an Extension. Implementations then either support it, or they don&#=
39;t.=C2=A0</div><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=
=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
This does depend on the yes/no question above - and I think that regardless=
, the draft needs to be clearer on what an extension is to allow it to be a=
nswered.<br>
<br>
There might be an issue with listing lots of items. Except you need to do t=
his anyway for default values if I understand correctly.<br></blockquote><d=
iv><br></div><div>The default notion only applies to metrics. Right now, th=
ere are 9:</div><div>MDRR/MDRT</div><div>CDRR/CDRT</div><div>Latency</div><=
div>RESR/REST</div><div>RLQR/RLQT</div><div><br></div><div>That&#39;s why I=
&#39;m proposing to add the &quot;Session Metric Initialization&quot; messa=
ge - to clear up some of the confusion, let&#39;s not use the session init =
to both (a) establish the protocol level with Extensions Supported, and (b)=
 establish default values for metrics that are to be flowed over the sessio=
n. Let&#39;s let the Session Init establish the effective protocol level an=
d &quot;bells &amp; whistles&quot; in play (the Extensions), and then expli=
citly set the default metric values.=C2=A0</div><div><br></div><div>Regards=
,</div><div>Stan</div><div><br></div><div>=C2=A0</div><blockquote class=3D"=
gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-=
left:1ex">
<br>
<br>
<br>
-----Original Message-----<br>
From: manet [mailto:<a href=3D"mailto:manet-bounces@ietf.org">manet-bounces=
@ietf.org</a>] On Behalf Of Lou Berger<br>
Sent: 09 December 2015 19:02<br>
To: <a href=3D"mailto:draft-ietf-manet-dlep@ietf.org">draft-ietf-manet-dlep=
@ietf.org</a>; MANET IETF<br>
Subject: [manet] DLEP-17: duplicate functions - Options &amp; extensions ne=
gotiations<br>
<br>
----------------------! WARNING ! ---------------------- This message origi=
nates from outside our organisation, either from an external partner or fro=
m the internet.<br>
Consider carefully whether you should click on any links, open any attachme=
nts or reply.<br>
Follow the &#39;Report Suspicious Emails&#39; link on IT matters for instru=
ctions on reporting suspicious email messages.<br>
--------------------------------------------------------<br>
<br>
*** WARNING ***<br>
EXTERNAL EMAIL -- This message originates from outside our organization.<br=
>
<br>
<br>
Authors/WG,<br>
<br>
The current version of DLEP contains two negotiations as part of a Session =
Initialization transaction:<br>
1) &lt;Extensions Supported&gt; is included in both the &lt;Session<br>
Initialization&gt; and &lt;Session Initialization Response&gt; messages<br>
2) the optional data items, &lt;Resources&gt; and &lt;Relative Link Quality=
&gt;<br>
<br>
Both have parallel allocation policies:<br>
<br>
=C2=A0 =C2=A0+-------------+-----------------------------------------------=
------+<br>
=C2=A0 =C2=A0| Type Code=C2=A0 =C2=A0| Description=C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0|<br>
=C2=A0 =C2=A0+-------------+-----------------------------------------------=
------+<br>
=C2=A0 =C2=A0| 0=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0| Reserved=C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 |=
<br>
=C2=A0 =C2=A0| 1=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0| Status (Section =
10.1)=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0|<br>
=C2=A0 =C2=A0 =C2=A0...<br>
=C2=A0 =C2=A0| 20=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 | Relative Link Quality=
 (Transmit) (RLQT) (Section=C2=A0 =C2=A0 |<br>
=C2=A0 =C2=A0| 21-65407=C2=A0 =C2=A0 | Reserved for future extensions=C2=A0=
 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 |<br=
>
=C2=A0 =C2=A0| 65408-65534 | Private Use. Available for experiments=C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 |<br>
=C2=A0 =C2=A0| 65535=C2=A0 =C2=A0 =C2=A0 =C2=A0| Reserved=C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 |<br>
=C2=A0 =C2=A0+-------------+-----------------------------------------------=
------+<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0Table 2: DLEP Data Item types<br>
<br>
=C2=A0 =C2=A0+-------------+-----------------------------------------------=
------+<br>
=C2=A0 =C2=A0| Code=C2=A0 =C2=A0 =C2=A0 =C2=A0 | Description=C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0|<br>
=C2=A0 =C2=A0+-------------+-----------------------------------------------=
------+<br>
=C2=A0 =C2=A0| 0=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0| Reserved=C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 |=
<br>
=C2=A0 =C2=A0| 1=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0| Credit Windowing=
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 |<br>
=C2=A0 =C2=A0| 2-65519=C2=A0 =C2=A0 =C2=A0| Reserved for future extensions=
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 |<br>
=C2=A0 =C2=A0| 65520-65534 | Private Use. Available for experiments=C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 |<br>
=C2=A0 =C2=A0| 65535=C2=A0 =C2=A0 =C2=A0 =C2=A0| Reserved=C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 |<br>
=C2=A0 =C2=A0+-------------+-----------------------------------------------=
------+<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0Table 4: DLEP Extension types<br>
<br>
It seems to me that given the current definition, one of these two should s=
uffice.=C2=A0 I don&#39;t have a strong opinion on which, but do strongly b=
elieve that a single approach should be selected to facilitate interoperabi=
lity.<br>
<br>
To be clear, the following spells out the options:<br>
<br>
Option A: Extensions (aka capabilities) based<br>
=C2=A0 Any optional or new data item or message would need to be indicated<=
br>
=C2=A0 in &lt;Extensions Supported&gt; to be used.=C2=A0 To cover the curre=
nt optional<br>
=C2=A0 data items the following would need to be defined:<br>
=C2=A0 =C2=A0 | 1 | Resources |<br>
=C2=A0 =C2=A0 | 2 | Relative Link Quality |<br>
=C2=A0 =C2=A0 | 3 | Credit Windowing |<br>
=C2=A0 &lt;Session Initialization Response&gt; could still contain the opti=
onal<br>
=C2=A0 data items, if the corresponding type is present in &lt;Extensions<b=
r>
=C2=A0 Supported&gt;<br>
<br>
=C2=A0 Note that other messages will still use optional data items.<br>
<br>
Option B: Data item based.<br>
=C2=A0 An optional or new data item must be both Session Initialization<br>
=C2=A0 messages to be used. To allow/enable &lt;Resources&gt; and &lt;Relat=
ive Link<br>
=C2=A0 Quality&gt;, they would need to be included in both the &lt;Session<=
br>
=C2=A0 Initialization&gt; and &lt;Session Initialization Response&gt; messa=
ges.<br>
<br>
=C2=A0 To enable the Credit Windowing extension, the three credit-related<b=
r>
=C2=A0 state items, &lt;Grant&gt;, &lt;Window Status&gt;, and &lt;Request&g=
t; would need to be<br>
=C2=A0 included in both session init messages for the full extension to be<=
br>
=C2=A0 used.<br>
<br>
Option C: keep both<br>
=C2=A0 Keep current text<br>
<br>
While I like Option A and have seen similar approaches in other protocols, =
e.g., BGP Capabilities, I actually have a slight preference for B.=C2=A0 Th=
e reason for this is DLEP uses optional data items in other places and impl=
ementations will already need to handle this, so it seems like option B wil=
l probably require smaller incremental code.<br>
<br>
Either way, I think Option C is much less desirable then either of the othe=
r options.<br>
<br>
Thoughts? Opinions?<br>
<br>
Lou<br>
<br>
_______________________________________________<br>
manet mailing list<br>
<a href=3D"mailto:manet@ietf.org">manet@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/manet" rel=3D"noreferrer" =
target=3D"_blank">https://www.ietf.org/mailman/listinfo/manet</a><br>
<br>
<br>
********************************************************************<br>
This email and any attachments are confidential to the intended<br>
recipient and may also be privileged. If you are not the intended<br>
recipient please delete it from your system and notify the sender.<br>
You should not copy it or use it for any purpose nor disclose or<br>
distribute its contents to any other person.<br>
********************************************************************<br>
<br>
_______________________________________________<br>
manet mailing list<br>
<a href=3D"mailto:manet@ietf.org">manet@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/manet" rel=3D"noreferrer" =
target=3D"_blank">https://www.ietf.org/mailman/listinfo/manet</a><br>
</blockquote></div><br></div></div></div>

--001a11c36b2a17a78205268b95ea--


From nobody Thu Dec 10 06:02:42 2015
Return-Path: <sratliff@idirect.net>
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 19D901B3257; Thu, 10 Dec 2015 06:02:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 lYjRLboU15bC; Thu, 10 Dec 2015 06:02:37 -0800 (PST)
Received: from smtp2.idirect.net (smtp2.idirect.net [198.180.159.66]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7F1AD1B3254; Thu, 10 Dec 2015 06:02:36 -0800 (PST)
IronPort-PHdr: 9a23:8HH5bR3Ww6xHooW0smDT+DRfVm0co7zxezQtwd8ZsekUKPad9pjvdHbS+e9qxAeQG96LtbQd1KGL6ujJYi8p39WoiDg6aptCVhsI2409vjcLJ4q7M3D9N+PgdCcgHc5PBxdP9nC/NlVJSo6lPwWB6kO74TNaIBjjLw09fr2zQd6MyZ3onL3rs7ToICx2xxOFKYtoKxu3qQiD/uI3uqBFbpgL9x3Sv3FTcP5Xz247bXianhL7+9vitMU7q3cYk7sb+sVBSaT3ebgjBfwdVWx+cjN92Mq+lRTFSwqJ6TMmVWoZn1IcAxLC4x73dpj0uyr+8OF63X/edYfTZIwIaHDq1LtmVhLuwm9TLCI07mzRzMl5kL5KiBugvRZi2MjfZ4TDZ9RkeaaIN+kTWW5AUMgVHxddC4W4YppFR74aJ+9Eq4jzqXMPoRqkCAKwQuXi1mkb1TfNwaQm3rF5Qkn91ws6EodL6SyMoQ==
X-IronPort-AV: E=Sophos;i="5.20,408,1444708800"; d="scan'208,217";a="329203"
X-IPAS-Result: A2DNAQC9hGlW/8n6+gpeGQEBAQEPAQEBAYI+gR9uBrsbghkBDYFbBxcBhXYCHIFOFAEBAQEBAQEBgQmCLYIHAQEBAQMjCkwQAgEIDgMEAQEoAwICAh8RFAkIAgQOBQiIEgOtbI1QDYRFAQEBAQEBAQEBAQEBAQEBAQEBAQEBGIZYhHuCU4I+giw6E4E2BZZvAYtKgXGVNodaHwEBglMdgVZyhFOBBwEBAQ
From: "Ratliff, Stanley" <sratliff@idirect.net>
To: Henning Rogge <hrogge@gmail.com>, "MATTY, Steven" <steven.matty@airbus.com>
Thread-Topic: [manet] DLEP-17: Handling of unknown / unexpected messages
Thread-Index: AQHRMrQuMo44RBQj2kmfS+UdHBISJp7D+bywgABZZID//+2z8A==
Date: Thu, 10 Dec 2015 14:02:33 +0000
Message-ID: <6e04810b1c1147a49f52a3aee1062202@VAUSDITCHM2.idirect.net>
References: <56687AC2.9060801@labn.net> <CALtoyomCuki__fyNnhmYoKmBcrQSSuOPGgcg8N-txG1DSaUaAg@mail.gmail.com> <56689271.306@labn.net> <23834_1449694925_566896CB_23834_3552_3_CALtoyo=JqgbqsBPo5jG-UzFR56qmAEk9zbtDBoLQUoJfcuooew@mail.gmail.com> <D9712B947A4CCA43AB42F01B90AF1DEC011F5B8E2A@AUK52982.UKN.UKNROOT.ASTRIUM.CORP> <CAGnRvurPEbzhvFGL0OrtDTvSXN9FoCfEXAfXzcAOXM27oRHPsg@mail.gmail.com>
In-Reply-To: <CAGnRvurPEbzhvFGL0OrtDTvSXN9FoCfEXAfXzcAOXM27oRHPsg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.250.250.20]
Content-Type: multipart/alternative; boundary="_000_6e04810b1c1147a49f52a3aee1062202VAUSDITCHM2idirectnet_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/2ozdA17y-Y4j9A-X5TqgzSd6-kg>
Cc: MANET IETF <manet@ietf.org>, "draft-ietf-manet-dlep@ietf.org" <draft-ietf-manet-dlep@ietf.org>
Subject: Re: [manet] DLEP-17: Handling of unknown / unexpected messages
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: <https://mailarchive.ietf.org/arch/browse/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: Thu, 10 Dec 2015 14:02:41 -0000

--_000_6e04810b1c1147a49f52a3aee1062202VAUSDITCHM2idirectnet_
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64

SGVubmluZywNCg0KQXMgbG9uZyBhcyB0aGUgb3ZlcmFsbCBtZXNzYWdlIGxlbmd0aCBpc27igJl0
IHNjcmV3ZWQgdXAsIHlvdeKAmWQgYmUgT0suIEp1c3QgdGFrZSB0aGF0IHZhbHVlIGFuZCDigJxz
dGVwIG92ZXLigJ0gdGhlIG5leHQgPGJsYWg+IG9jdGV0cyBpbiB0aGUgaW5jb21pbmcgVENQIHN0
cmVhbeKApg0KdGhhdCBzYWlkLCBJIG11c3QgYWRtaXQgdGhhdCBJIGRvbuKAmXQgbGlrZSB0aGUg
aWRlYS4gSWYgdGhlIG1lc3NhZ2UgaXMgdGhhdCBtZXNzZWQgdXAsIHRoaXMgcHJvYmFibHkgaXMg
dGhlIHJpZ2h0IHRpbWUgZm9yIHRoZSDigJxudWNsZWFyIG9wdGlvbuKAnS4gSSBqdXN0IHRoaW5r
IHdl4oCZdmUgZ29uZSBhIGJpdCB0b28gZmFyIHdpdGggYWxsIG9mIHRoZSBkYXRhIGl0ZW1zLg0K
DQpSZWdhcmRzLA0KU3Rhbg0KDQoNCkZyb206IEhlbm5pbmcgUm9nZ2UgW21haWx0bzpocm9nZ2VA
Z21haWwuY29tXQ0KU2VudDogVGh1cnNkYXksIERlY2VtYmVyIDEwLCAyMDE1IDU6MDYgQU0NClRv
OiBNQVRUWSwgU3RldmVuIDxzdGV2ZW4ubWF0dHlAYWlyYnVzLmNvbT4NCkNjOiBTdGFuIFJhdGxp
ZmYgPHJhdGxpZmZzdGFuQGdtYWlsLmNvbT47IExvdSBCZXJnZXIgPGxiZXJnZXJAbGFibi5uZXQ+
OyBNQU5FVCBJRVRGIDxtYW5ldEBpZXRmLm9yZz47IGRyYWZ0LWlldGYtbWFuZXQtZGxlcEBpZXRm
Lm9yZw0KU3ViamVjdDogUmU6IFttYW5ldF0gRExFUC0xNzogSGFuZGxpbmcgb2YgdW5rbm93biAv
IHVuZXhwZWN0ZWQgbWVzc2FnZXMNCg0KT24gVGh1LCBEZWMgMTAsIDIwMTUgYXQgMTA6NTggQU0s
IE1BVFRZLCBTdGV2ZW4gPHN0ZXZlbi5tYXR0eUBhaXJidXMuY29tPG1haWx0bzpzdGV2ZW4ubWF0
dHlAYWlyYnVzLmNvbT4+IHdyb3RlOg0KRnJvbTogbWFuZXQgW21haWx0bzptYW5ldC1ib3VuY2Vz
QGlldGYub3JnXSBPbiBCZWhhbGYgT2YgU3RhbiBSYXRsaWZmDQoNCjEpIE15IGluY2xpbmF0aW9u
IGlzIHRvd2FyZHMgdGhlIOKAnEJlIGdlbmVyb3VzIGluIHdoYXQgeW91IGFjY2VwdOKAnSBzaWRl
IG9mIHRoaW5ncy4gQnV0IHRoZXJlIGlzIGEgdHJhZGUtb2ZmIHdoZW4geW91DQphcmUgYmVpbmcg
YSBmcmllbmRseSBETEVQIGFwcGxpY2F0aW9uIHRoYXQgYWNjZXB0cyBhbnkgYW5kIGFsbCBtZXNz
YWdlcyB2ZXJzdXMgdHJ5aW5nIHRvIGVuc3VyZSBhbGwgRExFUA0KaW1wbGVtZW50YXRpb25zIGFy
ZSBjb21wbGlhbnQuIElmIHlvdSB0ZWFyIGRvd24gdGhlIHNlc3Npb24gd2hlbmV2ZXIgeW91IGdl
dCBhbiBpbnZhbGlkIERMRVAgbWVzc2FnZSB0aGVuIGl0DQp3aWxsIGJlY29tZSBWRVJZIG9idmlv
dXMsIFZFUlkgcXVpY2tseSB0aGF0IHlvdSBhcmUgdGFsa2luZyB3aXRoIGEg4oCYYmFk4oCZIGlt
cGxlbWVudGF0aW9uLiBIb3dldmVyLCBsZXTigJlzIHNheSB0aGF0DQp0aGlzIGltcGxlbWVudGF0
aW9uIG9uIGEgcm91dGVyIGlzIG5vIGxvbmdlciBzdXBwb3J0ZWQgYnV0IGlzIGFjdHVhbGx5IHZl
cnkgdXNlZnVsIGluIGV2ZXJ5dGhpbmcgZWxzZSBpdCBkb2VzIHJpZ2h0Lg0KDQpXb3VsZCBpdCBi
ZSBhbiBvcHRpb24gdG8gaW50cm9kdWNlIGFuIFtvcHRpb25hbF0gTkFDSyBETEVQIG1lc3NhZ2Ug
dHlwZSBzbyB0aGF0IHlvdSBjYW4gcmVwb3J0IHRvIHRoZSBzZW5kZXINCuKAnEhleSwgeW91IHNl
bnQgbWUgdGhpcyBhbmQgc29tZXRoaW5nIHdhcyB1cCB0aGVyZeKAnSByYXRoZXIgdGhhbiBqdXN0
IGEgc2lsZW50IGRpc2NhcmQ/DQoNClRoZSBwcm9ibGVtIGlzIHlvdSBjYW5ub3QgYmUgc3VyZSB0
aGF0IHRoZSBtZXNzYWdlIHdhcyBub3QgbWFsZm9ybWVkIGlmIHNvbWV0aGluZyBnb2VzIHdyb25n
Li4uIHdoaWNoIG1lYW5zIHlvdSBkb24ndCBrbm93IHdoZXJlIHRvICBzdGFydCB0aGUgbmV4dCBt
ZXNzYWdlIGluIHRoZSBpbmNvbWluZyBUQ1Agc3RyZWFtLg0KDQpIZW5uaW5nIFJvZ2dlDQoKX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KVGhpcyBl
bGVjdHJvbmljIG1lc3NhZ2UgYW5kIGFueSBmaWxlcyB0cmFuc21pdHRlZCB3aXRoIGl0IGNvbnRh
aW5zCmluZm9ybWF0aW9uIGZyb20gaURpcmVjdCwgd2hpY2ggbWF5IGJlIHByaXZpbGVnZWQsIHBy
b3ByaWV0YXJ5CmFuZC9vciBjb25maWRlbnRpYWwuIEl0IGlzIGludGVuZGVkIHNvbGVseSBmb3Ig
dGhlIHVzZSBvZiB0aGUgaW5kaXZpZHVhbApvciBlbnRpdHkgdG8gd2hvbSB0aGV5IGFyZSBhZGRy
ZXNzZWQuIElmIHlvdSBhcmUgbm90IHRoZSBvcmlnaW5hbApyZWNpcGllbnQgb3IgdGhlIHBlcnNv
biByZXNwb25zaWJsZSBmb3IgZGVsaXZlcmluZyB0aGUgZW1haWwgdG8gdGhlCmludGVuZGVkIHJl
Y2lwaWVudCwgYmUgYWR2aXNlZCB0aGF0IHlvdSBoYXZlIHJlY2VpdmVkIHRoaXMgZW1haWwKaW4g
ZXJyb3IsIGFuZCB0aGF0IGFueSB1c2UsIGRpc3NlbWluYXRpb24sIGZvcndhcmRpbmcsIHByaW50
aW5nLCBvcgpjb3B5aW5nIG9mIHRoaXMgZW1haWwgaXMgc3RyaWN0bHkgcHJvaGliaXRlZC4gSWYg
eW91IHJlY2VpdmVkIHRoaXMgZW1haWwKaW4gZXJyb3IsIHBsZWFzZSBkZWxldGUgaXQgYW5kIGlt
bWVkaWF0ZWx5IG5vdGlmeSB0aGUgc2VuZGVyLgpfX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fXwo=

--_000_6e04810b1c1147a49f52a3aee1062202VAUSDITCHM2idirectnet_
Content-Type: text/html; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTUgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
IkNhbWJyaWEgTWF0aCI7DQoJcGFub3NlLTE6MiA0IDUgMyA1IDQgNiAzIDIgNDt9DQpAZm9udC1m
YWNlDQoJe2ZvbnQtZmFtaWx5OkNhbGlicmk7DQoJcGFub3NlLTE6MiAxNSA1IDIgMiAyIDQgMyAy
IDQ7fQ0KLyogU3R5bGUgRGVmaW5pdGlvbnMgKi8NCnAuTXNvTm9ybWFsLCBsaS5Nc29Ob3JtYWws
IGRpdi5Nc29Ob3JtYWwNCgl7bWFyZ2luOjBpbjsNCgltYXJnaW4tYm90dG9tOi4wMDAxcHQ7DQoJ
Zm9udC1zaXplOjEyLjBwdDsNCglmb250LWZhbWlseToiVGltZXMgTmV3IFJvbWFuIixzZXJpZjt9
DQphOmxpbmssIHNwYW4uTXNvSHlwZXJsaW5rDQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsNCglj
b2xvcjpibHVlOw0KCXRleHQtZGVjb3JhdGlvbjp1bmRlcmxpbmU7fQ0KYTp2aXNpdGVkLCBzcGFu
Lk1zb0h5cGVybGlua0ZvbGxvd2VkDQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsNCgljb2xvcjpw
dXJwbGU7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZTt9DQpzcGFuLkVtYWlsU3R5bGUxNw0K
CXttc28tc3R5bGUtdHlwZTpwZXJzb25hbC1yZXBseTsNCglmb250LWZhbWlseToiQ2FsaWJyaSIs
c2Fucy1zZXJpZjsNCgljb2xvcjojMUY0OTdEO30NCi5Nc29DaHBEZWZhdWx0DQoJe21zby1zdHls
ZS10eXBlOmV4cG9ydC1vbmx5Ow0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIixzYW5zLXNlcmlmO30N
CkBwYWdlIFdvcmRTZWN0aW9uMQ0KCXtzaXplOjguNWluIDExLjBpbjsNCgltYXJnaW46MS4waW4g
MS4waW4gMS4waW4gMS4waW47fQ0KZGl2LldvcmRTZWN0aW9uMQ0KCXtwYWdlOldvcmRTZWN0aW9u
MTt9DQotLT48L3N0eWxlPjwhLS1baWYgZ3RlIG1zbyA5XT48eG1sPg0KPG86c2hhcGVkZWZhdWx0
cyB2OmV4dD0iZWRpdCIgc3BpZG1heD0iMTAyNiIgLz4NCjwveG1sPjwhW2VuZGlmXS0tPjwhLS1b
aWYgZ3RlIG1zbyA5XT48eG1sPg0KPG86c2hhcGVsYXlvdXQgdjpleHQ9ImVkaXQiPg0KPG86aWRt
YXAgdjpleHQ9ImVkaXQiIGRhdGE9IjEiIC8+DQo8L286c2hhcGVsYXlvdXQ+PC94bWw+PCFbZW5k
aWZdLS0+DQo8L2hlYWQ+DQo8Ym9keSBsYW5nPSJFTi1VUyIgbGluaz0iYmx1ZSIgdmxpbms9InB1
cnBsZSI+DQo8ZGl2IGNsYXNzPSJXb3JkU2VjdGlvbjEiPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+
PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZx
dW90OyxzYW5zLXNlcmlmO2NvbG9yOiMxRjQ5N0QiPkhlbm5pbmcsDQo8bzpwPjwvbzpwPjwvc3Bh
bj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBw
dDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6IzFGNDk3
RCI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNw
YW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90
OyxzYW5zLXNlcmlmO2NvbG9yOiMxRjQ5N0QiPkFzIGxvbmcgYXMgdGhlIG92ZXJhbGwgbWVzc2Fn
ZSBsZW5ndGggaXNu4oCZdCBzY3Jld2VkIHVwLCB5b3XigJlkIGJlIE9LLiBKdXN0IHRha2UgdGhh
dCB2YWx1ZSBhbmQg4oCcc3RlcCBvdmVy4oCdIHRoZSBuZXh0ICZsdDtibGFoJmd0OyBvY3RldHMg
aW4gdGhlIGluY29taW5nIFRDUCBzdHJlYW3igKYNCjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFt
aWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjojMUY0OTdEIj50aGF0IHNh
aWQsIEkgbXVzdCBhZG1pdCB0aGF0IEkgZG9u4oCZdCBsaWtlIHRoZSBpZGVhLiBJZiB0aGUgbWVz
c2FnZSBpcyB0aGF0IG1lc3NlZCB1cCwgdGhpcyBwcm9iYWJseSBpcyB0aGUgcmlnaHQgdGltZSBm
b3IgdGhlIOKAnG51Y2xlYXIgb3B0aW9u4oCdLiBJIGp1c3QgdGhpbmsgd2XigJl2ZQ0KIGdvbmUg
YSBiaXQgdG9vIGZhciB3aXRoIGFsbCBvZiB0aGUgZGF0YSBpdGVtcy4gPG86cD48L286cD48L3Nw
YW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4w
cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOiMxRjQ5
N0QiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxz
cGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVv
dDssc2Fucy1zZXJpZjtjb2xvcjojMUY0OTdEIj5SZWdhcmRzLDxvOnA+PC9vOnA+PC9zcGFuPjwv
cD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2Zv
bnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjojMUY0OTdEIj5T
dGFuPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5
bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5z
LXNlcmlmO2NvbG9yOiMxRjQ5N0QiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5
OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjojMUY0OTdEIj48bzpwPiZuYnNw
OzwvbzpwPjwvc3Bhbj48L3A+DQo8ZGl2IHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXItbGVmdDpz
b2xpZCBibHVlIDEuNXB0O3BhZGRpbmc6MGluIDBpbiAwaW4gNC4wcHQiPg0KPGRpdj4NCjxkaXYg
c3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci10b3A6c29saWQgI0UxRTFFMSAxLjBwdDtwYWRkaW5n
OjMuMHB0IDBpbiAwaW4gMGluIj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxiPjxzcGFuIHN0eWxl
PSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1z
ZXJpZiI+RnJvbTo8L3NwYW4+PC9iPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQt
ZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZiI+IEhlbm5pbmcgUm9nZ2UgW21h
aWx0bzpocm9nZ2VAZ21haWwuY29tXQ0KPGJyPg0KPGI+U2VudDo8L2I+IFRodXJzZGF5LCBEZWNl
bWJlciAxMCwgMjAxNSA1OjA2IEFNPGJyPg0KPGI+VG86PC9iPiBNQVRUWSwgU3RldmVuICZsdDtz
dGV2ZW4ubWF0dHlAYWlyYnVzLmNvbSZndDs8YnI+DQo8Yj5DYzo8L2I+IFN0YW4gUmF0bGlmZiAm
bHQ7cmF0bGlmZnN0YW5AZ21haWwuY29tJmd0OzsgTG91IEJlcmdlciAmbHQ7bGJlcmdlckBsYWJu
Lm5ldCZndDs7IE1BTkVUIElFVEYgJmx0O21hbmV0QGlldGYub3JnJmd0OzsgZHJhZnQtaWV0Zi1t
YW5ldC1kbGVwQGlldGYub3JnPGJyPg0KPGI+U3ViamVjdDo8L2I+IFJlOiBbbWFuZXRdIERMRVAt
MTc6IEhhbmRsaW5nIG9mIHVua25vd24gLyB1bmV4cGVjdGVkIG1lc3NhZ2VzPG86cD48L286cD48
L3NwYW4+PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5i
c3A7PC9vOnA+PC9wPg0KPGRpdj4NCjxkaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+
T24gVGh1LCBEZWMgMTAsIDIwMTUgYXQgMTA6NTggQU0sIE1BVFRZLCBTdGV2ZW4gJmx0OzxhIGhy
ZWY9Im1haWx0bzpzdGV2ZW4ubWF0dHlAYWlyYnVzLmNvbSIgdGFyZ2V0PSJfYmxhbmsiPnN0ZXZl
bi5tYXR0eUBhaXJidXMuY29tPC9hPiZndDsgd3JvdGU6PG86cD48L286cD48L3A+DQo8YmxvY2tx
dW90ZSBzdHlsZT0iYm9yZGVyOm5vbmU7Ym9yZGVyLWxlZnQ6c29saWQgI0NDQ0NDQyAxLjBwdDtw
YWRkaW5nOjBpbiAwaW4gMGluIDYuMHB0O21hcmdpbi1sZWZ0OjQuOHB0O21hcmdpbi1yaWdodDow
aW4iPg0KPGRpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9u
dC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtDb3VyaWVyIE5ldyZxdW90OyI+RnJvbTog
bWFuZXQgWzxhIGhyZWY9Im1haWx0bzptYW5ldC1ib3VuY2VzQGlldGYub3JnIiB0YXJnZXQ9Il9i
bGFuayI+bWFpbHRvOm1hbmV0LWJvdW5jZXNAaWV0Zi5vcmc8L2E+XSBPbiBCZWhhbGYgT2YgU3Rh
biBSYXRsaWZmPG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1
b3Q7Q291cmllciBOZXcmcXVvdDsiPiZuYnNwOzxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2
Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAu
MHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NvdXJpZXIgTmV3JnF1b3Q7Ij4xKSBNeSBpbmNsaW5hdGlv
biBpcyB0b3dhcmRzIHRoZSDigJxCZSBnZW5lcm91cyBpbiB3aGF0IHlvdSBhY2NlcHTigJ0gc2lk
ZSBvZiB0aGluZ3MuIEJ1dCB0aGVyZSBpcyBhIHRyYWRlLW9mZiB3aGVuIHlvdTxvOnA+PC9vOnA+
PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0
eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NvdXJpZXIgTmV3JnF1b3Q7
Ij5hcmUgYmVpbmcgYSBmcmllbmRseSBETEVQIGFwcGxpY2F0aW9uIHRoYXQgYWNjZXB0cyBhbnkg
YW5kIGFsbCBtZXNzYWdlcyB2ZXJzdXMgdHJ5aW5nIHRvIGVuc3VyZSBhbGwgRExFUDxvOnA+PC9v
OnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFu
IHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NvdXJpZXIgTmV3JnF1
b3Q7Ij5pbXBsZW1lbnRhdGlvbnMgYXJlIGNvbXBsaWFudC4gSWYgeW91IHRlYXIgZG93biB0aGUg
c2Vzc2lvbiB3aGVuZXZlciB5b3UgZ2V0IGFuIGludmFsaWQgRExFUCBtZXNzYWdlIHRoZW4gaXQ8
bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtDb3VyaWVy
IE5ldyZxdW90OyI+d2lsbCBiZWNvbWUgVkVSWSBvYnZpb3VzLCBWRVJZIHF1aWNrbHkgdGhhdCB5
b3UgYXJlIHRhbGtpbmcgd2l0aCBhIOKAmGJhZOKAmSBpbXBsZW1lbnRhdGlvbi4gSG93ZXZlciwg
bGV04oCZcyBzYXkgdGhhdDxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFt
aWx5OiZxdW90O0NvdXJpZXIgTmV3JnF1b3Q7Ij50aGlzIGltcGxlbWVudGF0aW9uIG9uIGEgcm91
dGVyIGlzIG5vIGxvbmdlciBzdXBwb3J0ZWQgYnV0IGlzIGFjdHVhbGx5IHZlcnkgdXNlZnVsIGlu
IGV2ZXJ5dGhpbmcgZWxzZSBpdCBkb2VzIHJpZ2h0LjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwv
ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6
MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZiI+Jm5ic3A7
PC9zcGFuPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0Nv
dXJpZXIgTmV3JnF1b3Q7Ij48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZh
bWlseTomcXVvdDtDb3VyaWVyIE5ldyZxdW90OyI+V291bGQgaXQgYmUgYW4gb3B0aW9uIHRvIGlu
dHJvZHVjZSBhbiBbb3B0aW9uYWxdIE5BQ0sgRExFUCBtZXNzYWdlIHR5cGUgc28gdGhhdCB5b3Ug
Y2FuIHJlcG9ydCB0byB0aGUgc2VuZGVyPG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8
ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7
Zm9udC1mYW1pbHk6JnF1b3Q7Q291cmllciBOZXcmcXVvdDsiPuKAnEhleSwgeW91IHNlbnQgbWUg
dGhpcyBhbmQgc29tZXRoaW5nIHdhcyB1cCB0aGVyZeKAnSByYXRoZXIgdGhhbiBqdXN0IGEgc2ls
ZW50IGRpc2NhcmQ/PG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjwvYmxv
Y2txdW90ZT4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwv
cD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPlRoZSBwcm9ibGVtIGlzIHlv
dSBjYW5ub3QgYmUgc3VyZSB0aGF0IHRoZSBtZXNzYWdlIHdhcyBub3QgbWFsZm9ybWVkIGlmIHNv
bWV0aGluZyBnb2VzIHdyb25nLi4uIHdoaWNoIG1lYW5zIHlvdSBkb24ndCBrbm93IHdoZXJlIHRv
ICZuYnNwO3N0YXJ0IHRoZSBuZXh0IG1lc3NhZ2UgaW4gdGhlIGluY29taW5nIFRDUCBzdHJlYW0u
PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpw
PiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPkhl
bm5pbmcgUm9nZ2U8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2
Pg0KPC9kaXY+DQo8L2Rpdj4NCjxicj48c3BhbiBzdHlsZT0iZm9udC1zaXplOiA4cHQ7IGZvbnQt
ZmFtaWx5OiBBcmlhbCwgc2Fucy1zZXJpZjsgY29sb3I6ICMwMDMzNjY7Ij5fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXzxicj5UaGlzIGVsZWN0cm9u
aWMgbWVzc2FnZSBhbmQgYW55IGZpbGVzIHRyYW5zbWl0dGVkIHdpdGggaXQgY29udGFpbnM8YnI+
aW5mb3JtYXRpb24gZnJvbSBpRGlyZWN0LCB3aGljaCBtYXkgYmUgcHJpdmlsZWdlZCwgcHJvcHJp
ZXRhcnk8YnI+YW5kL29yIGNvbmZpZGVudGlhbC4gSXQgaXMgaW50ZW5kZWQgc29sZWx5IGZvciB0
aGUgdXNlIG9mIHRoZSBpbmRpdmlkdWFsPGJyPm9yIGVudGl0eSB0byB3aG9tIHRoZXkgYXJlIGFk
ZHJlc3NlZC4gSWYgeW91IGFyZSBub3QgdGhlIG9yaWdpbmFsPGJyPnJlY2lwaWVudCBvciB0aGUg
cGVyc29uIHJlc3BvbnNpYmxlIGZvciBkZWxpdmVyaW5nIHRoZSBlbWFpbCB0byB0aGU8YnI+aW50
ZW5kZWQgcmVjaXBpZW50LCBiZSBhZHZpc2VkIHRoYXQgeW91IGhhdmUgcmVjZWl2ZWQgdGhpcyBl
bWFpbDxicj5pbiBlcnJvciwgYW5kIHRoYXQgYW55IHVzZSwgZGlzc2VtaW5hdGlvbiwgZm9yd2Fy
ZGluZywgcHJpbnRpbmcsIG9yPGJyPmNvcHlpbmcgb2YgdGhpcyBlbWFpbCBpcyBzdHJpY3RseSBw
cm9oaWJpdGVkLiBJZiB5b3UgcmVjZWl2ZWQgdGhpcyBlbWFpbDxicj5pbiBlcnJvciwgcGxlYXNl
IGRlbGV0ZSBpdCBhbmQgaW1tZWRpYXRlbHkgbm90aWZ5IHRoZSBzZW5kZXIuPGJyPl9fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fPC9zcGFuPjwvYm9k
eT4NCjwvaHRtbD4NCg==

--_000_6e04810b1c1147a49f52a3aee1062202VAUSDITCHM2idirectnet_--


From nobody Thu Dec 10 06:39:56 2015
Return-Path: <prvs=978689fa14=david.wiggins@ll.mit.edu>
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 D8B0F1B2A58; Thu, 10 Dec 2015 06:39:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.209
X-Spam-Level: 
X-Spam-Status: No, score=-4.209 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, T_RP_MATCHES_RCVD=-0.01, UNPARSEABLE_RELAY=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 IpzDljFLad57; Thu, 10 Dec 2015 06:39:52 -0800 (PST)
Received: from mx1.ll.mit.edu (MX1.LL.MIT.EDU [129.55.12.45]) by ietfa.amsl.com (Postfix) with ESMTP id B0C141B2A4E; Thu, 10 Dec 2015 06:39:51 -0800 (PST)
Received: from LLE2K10-HUB02.mitll.ad.local (LLE2K10-HUB02.mitll.ad.local) by mx1.ll.mit.edu (unknown) with ESMTP id tBAEdcId010944; Thu, 10 Dec 2015 09:39:49 -0500
From: "Wiggins, David - 0665 - MITLL" <David.Wiggins@ll.mit.edu>
To: "Dearlove, Christopher (UK)" <chris.dearlove@baesystems.com>, "Henning Rogge" <hrogge@gmail.com>
Thread-Topic: [manet] DLEP-17: duplicate functions - Options & extensions negotiations
Thread-Index: AQHRMzSBW2DUA5VXZ0WuSS20V0/no57EaEIAgAAS9gCAAAGwgIAACh6A///DJYA=
Date: Thu, 10 Dec 2015 14:37:29 +0000
Message-ID: <D28EF1C5.13EB%David.Wiggins@ll.mit.edu>
References: <56687ABA.803@labn.net> <B31EEDDDB8ED7E4A93FDF12A4EECD30D848E753E@GLKXM0002V.GREENLNK.net> <CAGnRvurVT2OF8sFa6va6k=zt4dA4gk2vK4Y+UnRd8d1WjBocMA@mail.gmail.com> <B31EEDDDB8ED7E4A93FDF12A4EECD30D848E75EB@GLKXM0002V.GREENLNK.net> <CAGnRvupVxGfhBEws8ntpTf=bWi9SSXfLUGpz8f2XAigaiPanCg@mail.gmail.com> <B31EEDDDB8ED7E4A93FDF12A4EECD30D848E7635@GLKXM0002V.GREENLNK.net>
In-Reply-To: <B31EEDDDB8ED7E4A93FDF12A4EECD30D848E7635@GLKXM0002V.GREENLNK.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [172.25.59.174]
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="B_3532585047_161084732"
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.15.21, 1.0.33,  0.0.0000 definitions=2015-12-10_08:2015-12-10,2015-12-10,1970-01-01 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 suspectscore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=7.0.1-1511060000 definitions=main-1512100244
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/r04HY0ZBP6ikpG7caH62jzFiDpM>
Cc: MANET IETF <manet@ietf.org>, "draft-ietf-manet-dlep@ietf.org" <draft-ietf-manet-dlep@ietf.org>
Subject: Re: [manet] DLEP-17: duplicate functions - Options & extensions negotiations
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: <https://mailarchive.ietf.org/arch/browse/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: Thu, 10 Dec 2015 14:39:55 -0000

--B_3532585047_161084732
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit

Extensions can add status codes too.

I can see a use for an extension that does not add any signals/messages,
data items, or status codes; it just adds behavior.  In particular, it
allows new combinations of the protocol elements that were previously
disallowed.  For example, an extension could allow an existing data item
on an existing signal.  dlep-17 appears to allow this, section 6 paragraph
1: 

    Such extensions are defined as *additional rules of behaviour,*
    messages, data items and/or status codes that are not defined in this
    document.


I've been thinking about this because of the discussion about which data
items (if any) should be allowed to appear on a Destination Up coming from
the router.  Let's say the result of that discussion is that we clamp down
hard and don't allow any data items other than the MAC address, and that
MAC address MUST represent a multicast address.  However, someone :) would
like the router to be able to advertise IP addresses and subnets that it
provides access to so that the modem can propagate this to the other side
(using a non-DLEP protocol).  So, we could add an extension that relaxes
Destination Up and Update to allow 1) unicast MAC addresses coming from
the router (the router would put its own MAC address), and 2) IP address
and IP subnet data items.  The extension would of course define what this
new combination means.  It adds no new messages or data items, but it's a
useful extension (to us).

You could certainly do this with a new message too, but a small tweak to
the allowed data items seems cleaner and easier to deal with to me.

David

On 12/10/15, 8:15 AM, "manet on behalf of Dearlove, Christopher (UK)"
<manet-bounces@ietf.org on behalf of chris.dearlove@baesystems.com> wrote:

>I'm not convinced by that example. Two extensions operating the way you
>describe is a potential interoperability nightmare. Different algorithms
>for calculating the flow control is already an issue - but is the same
>extension.
>
>-----Original Message-----
>From: Henning Rogge [mailto:hrogge@gmail.com]
>Sent: 10 December 2015 12:39
>To: Dearlove, Christopher (UK)
>Cc: Lou Berger; draft-ietf-manet-dlep@ietf.org; MANET IETF
>Subject: Re: [manet] DLEP-17: duplicate functions - Options & extensions
>negotiations
>
>----------------------! 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.
>--------------------------------------------------------
>
>On Thu, Dec 10, 2015 at 1:33 PM, Dearlove, Christopher (UK)
><chris.dearlove@baesystems.com> wrote:
>> I think it's worth just thinking about this. Can you suggest a
>> plausible example where you need more information than just new
>> message and data item types? It can be an alien space bats example ;)
>>
>> (Of course there's more needed implicitly - such as what to do with a
>> new message type. But the required information can be carried by just
>> the new message type number.)
>
>We might have different kinds of "flow control" extensions using the same
>kind of message.
>
>Someone write "Flow Control Extension A"... and from the experiments we
>learned that we can do a bit better than it, but its still a mutual
>exclusive choice. So the author writes "Flow Control Extension B"
>which reuse the messages he designed for A.
>
>Henning Rogge
>********************************************************************
>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.
>********************************************************************
>_______________________________________________
>manet mailing list
>manet@ietf.org
>https://www.ietf.org/mailman/listinfo/manet

--B_3532585047_161084732
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"

MIIMEgYJKoZIhvcNAQcCoIIMAzCCC/8CAQExCzAJBgUrDgMCGgUAMAsGCSqGSIb3DQEHAaCC
CfUwggT1MIID3aADAgECAgpar+vgAAAAADYOMA0GCSqGSIb3DQEBCwUAMFExCzAJBgNVBAYT
AlVTMR8wHQYDVQQKExZNSVQgTGluY29sbiBMYWJvcmF0b3J5MQwwCgYDVQQLEwNQS0kxEzAR
BgNVBAMTCk1JVExMIENBLTMwHhcNMTUwNDA2MTE1OTM4WhcNMTYwNDA1MTE1OTM4WjBiMQsw
CQYDVQQGEwJVUzEfMB0GA1UEChMWTUlUIExpbmNvbG4gTGFib3JhdG9yeTEPMA0GA1UECxMG
UGVvcGxlMSEwHwYDVQQDExhXaWdnaW5zLkRhdmlkLlAuNTAwMTUyMDcwggEiMA0GCSqGSIb3
DQEBAQUAA4IBDwAwggEKAoIBAQDdVA0BrVjbk6NP8JFi7Lks3SHtN8CxSBqFLPNRVWGjTgLG
W9pDcqqOrij0IHmGpAP404gR4dP9mUEb9KfOhKuDdFQFyZnVICDSRbyT4tGOxiTH7MIsV49d
UwrWhj2P/ms6wf1E5L2QwJqjOTMPZj3IClWAkcZsAix5jHkLvNXI5OilCe2u2TDihM1x2kfB
zgQpRy9tuXpxYtFZpoEb0XbqLIzS9FLkTbqlocSm4jwhPXTFQtFwbd6l4zzD4RVPgnpFxg/8
KpuV35lGkp5lbPvpkskz4+n3P9LoCvpoh1pgj3fS0CvCVRzWRAX+oNR/D7RmP1ug+7Ix+JCg
iAB3vLdFAgMBAAGjggG8MIIBuDAdBgNVHQ4EFgQUofYOKn4e6iCZO59iu2f0FxOad4MwDgYD
VR0PAQH/BAQDAgbAMB8GA1UdIwQYMBaAFNdgZg57SY11TA39z0beyMcSh8q/MDMGA1UdHwQs
MCowKKAmoCSGImh0dHA6Ly9jcmwubGwubWl0LmVkdS9nZXRjcmwvTExDQTMwZgYIKwYBBQUH
AQEEWjBYMC0GCCsGAQUFBzAChiFodHRwOi8vY3JsLmxsLm1pdC5lZHUvZ2V0dG8vTExDQTMw
JwYIKwYBBQUHMAGGG2h0dHA6Ly9vY3NwLmxsLm1pdC5lZHUvb2NzcDA9BgkrBgEEAYI3FQcE
MDAuBiYrBgEEAYI3FQiDg+Udh+ynZoathxWD6vBFhbahHx2Fy94yh/+KcwIBZAIBBTAiBgNV
HSUBAf8EGDAWBggrBgEFBQcDBAYKKwYBBAGCNwoDDDAYBgNVHSAEETAPMA0GCyqGSIb3EgIB
AwEIMCMGA1UdEQQcMBqBGERhdmlkLldpZ2dpbnNAbGwubWl0LmVkdTAnBgkrBgEEAYI3FAIE
Gh4YAEwATABVAHMAZQByAFMAaQBnAC0AUwBXMA0GCSqGSIb3DQEBCwUAA4IBAQCgEybvvRIJ
tAlKEfYZyf5DIlcT+LfePOiebFcPxZatSTQW/hJHv4RX/TN8N3bQrx4Jkxe17eQfsKvJXhOi
R6as3vemCxYEMOFIKSsm5LEIC4D4GcXBRZ1CAJIHCY5ezXfKQUxBSdZAq82/fAoNEEP4KPEv
Y07m7OVwXMWpu7kz3CeBVOqL7xlL53pPvkyxtijQRtZrZ5coE9Qh9tHzATi7DW8UWoUv3Yhj
Qz9SnBn3T30ho0GtlTvMXso7UjGZFWLQI2JyR2QW5FYq8GGEq/5PRz/xslsKA5EoHxmSSeRh
eei3gpFbnUrRS+5JSS6kgA/HVoM7CRFo/O8KYXU5z/ihMIIE+DCCA+CgAwIBAgIKWrCpkwAA
AAA2DzANBgkqhkiG9w0BAQsFADBRMQswCQYDVQQGEwJVUzEfMB0GA1UEChMWTUlUIExpbmNv
bG4gTGFib3JhdG9yeTEMMAoGA1UECxMDUEtJMRMwEQYDVQQDEwpNSVRMTCBDQS0zMB4XDTE1
MDQwNjEyMDAyNloXDTE2MDQwNTEyMDAyNlowYjELMAkGA1UEBhMCVVMxHzAdBgNVBAoTFk1J
VCBMaW5jb2xuIExhYm9yYXRvcnkxDzANBgNVBAsTBlBlb3BsZTEhMB8GA1UEAxMYV2lnZ2lu
cy5EYXZpZC5QLjUwMDE1MjA3MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAlEWD
uIm5kuHghfe7O+eMLVena6sNfAZtHLp2mwXLrNshaHM6wVKmml8zhxeSmJJXTF3Owyn7imKs
vHMWcIJD9EoFQyJoeBaFV5Ll75/fE2WKswtGn9ZSSejplI/Iy99SI/9Lna5B7/BDmPozGn66
jdzgl+JVFptqEUGx5NZlRUEEtVtXYUy+PllIq6SpR/242wFiYVslFqSoHu789mexaDDAl7p7
z3W9cYidPtZUoysjW0omzwZIoYMsIhTbUMnv+TkBuhJErBmaNvAXPf8Y3pNf3pYz8pnR4MyI
ibFv2CS/2KLGxJRE9xt1nrgHT8Wx+E6Ro6IYkYLPSdE6YgYAgwIDAQABo4IBvzCCAbswHQYD
VR0OBBYEFGww5LYEZSoVOkuJ7ZVJS+35ChrUMA4GA1UdDwEB/wQEAwIFIDAfBgNVHSMEGDAW
gBTXYGYOe0mNdUwN/c9G3sjHEofKvzAzBgNVHR8ELDAqMCigJqAkhiJodHRwOi8vY3JsLmxs
Lm1pdC5lZHUvZ2V0Y3JsL0xMQ0EzMGYGCCsGAQUFBwEBBFowWDAtBggrBgEFBQcwAoYhaHR0
cDovL2NybC5sbC5taXQuZWR1L2dldHRvL0xMQ0EzMCcGCCsGAQUFBzABhhtodHRwOi8vb2Nz
cC5sbC5taXQuZWR1L29jc3AwPQYJKwYBBAGCNxUHBDAwLgYmKwYBBAGCNxUIg4PlHYfsp2aG
rYcVg+rwRYW2oR8dhevQcIPr7SACAWQCAQQwJQYDVR0lBB4wHAYEVR0lAAYIKwYBBQUHAwQG
CisGAQQBgjcKAwQwGAYDVR0gBBEwDzANBgsqhkiG9xICAQMBCDAjBgNVHREEHDAagRhEYXZp
ZC5XaWdnaW5zQGxsLm1pdC5lZHUwJwYJKwYBBAGCNxQCBBoeGABMAEwAVQBzAGUAcgBFAG4A
YwAtAFMAVzANBgkqhkiG9w0BAQsFAAOCAQEATCsJT66TKeYNh9hrcC1wxRH08CricKt9JktB
I1WWl48F4CqcYDZlLMpvHuSe6GezZzTUH4oq1y2q3um9Txh1NjLPT7j0k5SSwdr2V7d8upDN
WOrXvCi59Cyz5RvuhleCPIE+6wPyDrQwfBRhte/cv8PVOrsG4tio4VOHi/nXcS+HLgC5qNxk
1/w1UBf8QkkNP8kIgum/uItm4QwVdVAJMuwe3te8dYjtp3M5nC2exfqQfk+Mmw/8fdZFpch0
rSYbpchMMOueBuy2UnWaYBF84uXldBH9fkONRX8AL8EQ3sQEOyzxqpwKQ/d0itjAGaPCCJCI
VgnSYSWYoFiN9idyaTGCAeUwggHhAgEBMF8wUTELMAkGA1UEBhMCVVMxHzAdBgNVBAoTFk1J
VCBMaW5jb2xuIExhYm9yYXRvcnkxDDAKBgNVBAsTA1BLSTETMBEGA1UEAxMKTUlUTEwgQ0Et
MwIKWq/r4AAAAAA2DjAJBgUrDgMCGgUAoF0wIwYJKoZIhvcNAQkEMRYEFGHpyn57RJaVjO8S
P98jrjBsbVgvMBgGCSqGSIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTE1
MTIxMDE0MzcyN1owDQYJKoZIhvcNAQEBBQAEggEAh8KZkysEf0JA8JNyHrUt0tGNbpXCZxG3
nPiajsQDG5RJ6gf7HTkMUQLaR/lC1g8ueekOaqhxzQMLXBIunSwggTY/JanP3s3ljOAx/6VM
DxQCb9Lc8G13huZdjn0m5vMDNFXOByuSB+0En6UXyIsh+hH4yoNGQYyvjLRmFHeElW/oN8JD
OCim2SvT3tgCV9S6lmVNI+KDmJwSsWUJXGPTApk22DImWLUHKdOHH2wtBWwDD75qz3/Q0IxX
5FwiCZ92UDuyB94QflYDhMRE+VYZgeYuuR4UWi31Zir+pUEULBxJNSarUsCUiLr2kEcy9Gfh
ohawDLoXSpXQvWPfbHgzBQ==

--B_3532585047_161084732--


From nobody Thu Dec 10 21:27:42 2015
Return-Path: <rick@tropicalstormsoftware.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 E6DFA1A8760; Thu, 10 Dec 2015 21:27:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.911
X-Spam-Level: 
X-Spam-Status: No, score=-1.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 Mpkee-ULEqwJ; Thu, 10 Dec 2015 21:27:38 -0800 (PST)
Received: from mail.tropicalstormsoftware.com (mail.tropicalstormsoftware.com [188.94.42.120]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F003A1A8756; Thu, 10 Dec 2015 21:27:37 -0800 (PST)
Received: from tss-server1.home.tropicalstormsoftware.com ([fe80::753b:fa82:5c0:af0d]) by tss-server1.home.tropicalstormsoftware.com ([fe80::753b:fa82:5c0:af0d%10]) with mapi; Fri, 11 Dec 2015 05:27:10 +0000
From: Rick Taylor <rick@tropicalstormsoftware.com>
To: "Wiggins, David - 0665 - MITLL" <David.Wiggins@ll.mit.edu>, "Dearlove, Christopher (UK)" <chris.dearlove@baesystems.com>, Henning Rogge <hrogge@gmail.com>
Thread-Topic: [manet] DLEP-17: duplicate functions - Options & extensions negotiations
Thread-Index: AQHRMzR12ImxKdW8OkaJvkKDzo96Xw==
Date: Fri, 11 Dec 2015 05:27:09 +0000
Message-ID: <38A5475DE83986499AEACD2CFAFC3F9801B8E9A39B@tss-server1.home.tropicalstormsoftware.com>
References: <56687ABA.803@labn.net> <B31EEDDDB8ED7E4A93FDF12A4EECD30D848E753E@GLKXM0002V.GREENLNK.net> <CAGnRvurVT2OF8sFa6va6k=zt4dA4gk2vK4Y+UnRd8d1WjBocMA@mail.gmail.com> <B31EEDDDB8ED7E4A93FDF12A4EECD30D848E75EB@GLKXM0002V.GREENLNK.net> <CAGnRvupVxGfhBEws8ntpTf=bWi9SSXfLUGpz8f2XAigaiPanCg@mail.gmail.com> <B31EEDDDB8ED7E4A93FDF12A4EECD30D848E7635@GLKXM0002V.GREENLNK.net> <D28EF1C5.13EB%David.Wiggins@ll.mit.edu>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/tv26EssXTlSUAUuzagXguS4WXGw>
Cc: MANET IETF <manet@ietf.org>, "draft-ietf-manet-dlep@ietf.org" <draft-ietf-manet-dlep@ietf.org>
Subject: Re: [manet] DLEP-17: duplicate functions - Options & extensions negotiations
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: <https://mailarchive.ietf.org/arch/browse/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, 11 Dec 2015 05:27:41 -0000

On 10/12/15 14:39, Wiggins, David - 0665 - MITLL wrote:=0A=
> Extensions can add status codes too.=0A=
>=0A=
> I can see a use for an extension that does not add any signals/messages,=
=0A=
> data items, or status codes; it just adds behavior.  In particular, it=0A=
> allows new combinations of the protocol elements that were previously=0A=
> disallowed.  For example, an extension could allow an existing data item=
=0A=
> on an existing signal.  dlep-17 appears to allow this, section 6 paragrap=
h=0A=
> 1: =0A=
>=0A=
>     Such extensions are defined as *additional rules of behaviour,*=0A=
>     messages, data items and/or status codes that are not defined in this=
=0A=
>     document.=0A=
>=0A=
>=0A=
> I've been thinking about this because of the discussion about which data=
=0A=
> items (if any) should be allowed to appear on a Destination Up coming fro=
m=0A=
> the router.  Let's say the result of that discussion is that we clamp dow=
n=0A=
> hard and don't allow any data items other than the MAC address, and that=
=0A=
> MAC address MUST represent a multicast address.  However, someone :) woul=
d=0A=
> like the router to be able to advertise IP addresses and subnets that it=
=0A=
> provides access to so that the modem can propagate this to the other side=
=0A=
> (using a non-DLEP protocol).  So, we could add an extension that relaxes=
=0A=
> Destination Up and Update to allow 1) unicast MAC addresses coming from=
=0A=
> the router (the router would put its own MAC address), and 2) IP address=
=0A=
> and IP subnet data items.  The extension would of course define what this=
=0A=
> new combination means.  It adds no new messages or data items, but it's a=
=0A=
> useful extension (to us).=0A=
>=0A=
> You could certainly do this with a new message too, but a small tweak to=
=0A=
> the allowed data items seems cleaner and easier to deal with to me.=0A=
=0A=
I completely agree here.  This is exactly how I see extensions being used.=
=0A=
>=0A=
> David=0A=
>=0A=
> On 12/10/15, 8:15 AM, "manet on behalf of Dearlove, Christopher (UK)"=0A=
> <manet-bounces@ietf.org on behalf of chris.dearlove@baesystems.com> wrote=
:=0A=
>=0A=
>> I'm not convinced by that example. Two extensions operating the way you=
=0A=
>> describe is a potential interoperability nightmare. Different algorithms=
=0A=
>> for calculating the flow control is already an issue - but is the same=
=0A=
>> extension.=0A=
>>=0A=
>> -----Original Message-----=0A=
>> From: Henning Rogge [mailto:hrogge@gmail.com]=0A=
>> Sent: 10 December 2015 12:39=0A=
>> To: Dearlove, Christopher (UK)=0A=
>> Cc: Lou Berger; draft-ietf-manet-dlep@ietf.org; MANET IETF=0A=
>> Subject: Re: [manet] DLEP-17: duplicate functions - Options & extensions=
=0A=
>> negotiations=0A=
>>=0A=
>> ----------------------! WARNING ! ---------------------- This message=0A=
>> originates from outside our organisation, either from an external partne=
r=0A=
>> or from the internet.=0A=
>> Consider carefully whether you should click on any links, open any=0A=
>> attachments or reply.=0A=
>> Follow the 'Report Suspicious Emails' link on IT matters for instruction=
s=0A=
>> on reporting suspicious email messages.=0A=
>> --------------------------------------------------------=0A=
>>=0A=
>> On Thu, Dec 10, 2015 at 1:33 PM, Dearlove, Christopher (UK)=0A=
>> <chris.dearlove@baesystems.com> wrote:=0A=
>>> I think it's worth just thinking about this. Can you suggest a=0A=
>>> plausible example where you need more information than just new=0A=
>>> message and data item types? It can be an alien space bats example ;)=
=0A=
>>>=0A=
>>> (Of course there's more needed implicitly - such as what to do with a=
=0A=
>>> new message type. But the required information can be carried by just=
=0A=
>>> the new message type number.)=0A=
>> We might have different kinds of "flow control" extensions using the sam=
e=0A=
>> kind of message.=0A=
>>=0A=
>> Someone write "Flow Control Extension A"... and from the experiments we=
=0A=
>> learned that we can do a bit better than it, but its still a mutual=0A=
>> exclusive choice. So the author writes "Flow Control Extension B"=0A=
>> which reuse the messages he designed for A.=0A=
>>=0A=
>> Henning Rogge=0A=
>> ********************************************************************=0A=
>> This email and any attachments are confidential to the intended=0A=
>> recipient and may also be privileged. If you are not the intended=0A=
>> recipient please delete it from your system and notify the sender.=0A=
>> You should not copy it or use it for any purpose nor disclose or=0A=
>> distribute its contents to any other person.=0A=
>> ********************************************************************=0A=
>> _______________________________________________=0A=
>> manet mailing list=0A=
>> manet@ietf.org=0A=
>> https://www.ietf.org/mailman/listinfo/manet=0A=
=0A=


From nobody Tue Dec 15 08:26:32 2015
Return-Path: <internet-drafts@ietf.org>
X-Original-To: manet@ietf.org
Delivered-To: manet@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 5972A1AC425; Tue, 15 Dec 2015 08:26:31 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.11.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20151215162631.19509.72940.idtracker@ietfa.amsl.com>
Date: Tue, 15 Dec 2015 08:26:31 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/CeFc76_mQSjVDU_imqZUrQ7eeLE>
Cc: manet@ietf.org
Subject: [manet] I-D Action: draft-ietf-manet-olsrv2-dat-metric-11.txt
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
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: <https://mailarchive.ietf.org/arch/browse/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: Tue, 15 Dec 2015 16:26:31 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
 This draft is a work item of the Mobile Ad-hoc Networks Working Group of the IETF.

        Title           : Packet Sequence Number based directional airtime metric for OLSRv2
        Authors         : Henning Rogge
                          Emmanuel Baccelli
	Filename        : draft-ietf-manet-olsrv2-dat-metric-11.txt
	Pages           : 20
	Date            : 2015-12-15

Abstract:
   This document specifies an Directional Airtime (DAT) link metric for
   usage in OLSRv2.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-manet-olsrv2-dat-metric/

There's also a htmlized version available at:
https://tools.ietf.org/html/draft-ietf-manet-olsrv2-dat-metric-11

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-manet-olsrv2-dat-metric-11


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Tue Dec 15 08:54:43 2015
Return-Path: <emmanuel.baccelli@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 006EB1A8AEE for <manet@ietfa.amsl.com>; Tue, 15 Dec 2015 08:54:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.277
X-Spam-Level: 
X-Spam-Status: No, score=-1.277 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=no
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 YqniafLLZ1ks for <manet@ietfa.amsl.com>; Tue, 15 Dec 2015 08:54:39 -0800 (PST)
Received: from mail-ig0-x22a.google.com (mail-ig0-x22a.google.com [IPv6:2607:f8b0:4001:c05::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A7F971A916F for <manet@ietf.org>; Tue, 15 Dec 2015 08:42:15 -0800 (PST)
Received: by mail-ig0-x22a.google.com with SMTP id to4so34650063igc.0 for <manet@ietf.org>; Tue, 15 Dec 2015 08:42:15 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:sender:from:date:message-id:subject:to:content-type;  bh=76m2ssOWMEGdW+DIbNGwTe+s8eZlyPVTUOtJ7JX+jys=; b=PTdqxBSaSV6VfRa+jhQhA7XoUet5C+/e699nClPIqHIOq9uDIwYPy+DQSiEdJILrDj ReIMtolVrMYx3Nm2GOaj/nXER26sloGTHYpbczzy97JeXW1mDKI+VD8RofulCEOYiq0x DbN2cxVV/Ko0DrNJuJ7hUe61X3xoLiIjfUMBZ84RM4en62l9Nc7PN3+3ZtQHOPBaBH6I hdhKbbFw1RMB3jx7OloXO/fMVNqHNfydC9I852ZnyOVGt1r0QeG5bhAxqDN7EOAq1slT iLVhQz5tpv5kNfqqInTD2+1JNzd5XCC9fB/1s0FFsv++3Lb4OXPVNeY6BRtf2SJPwBN3 ncZQ==
X-Received: by 10.50.55.66 with SMTP id q2mr4556746igp.97.1450197735069; Tue, 15 Dec 2015 08:42:15 -0800 (PST)
MIME-Version: 1.0
Sender: emmanuel.baccelli@gmail.com
Received: by 10.79.104.199 with HTTP; Tue, 15 Dec 2015 08:41:55 -0800 (PST)
From: Emmanuel Baccelli <Emmanuel.Baccelli@inria.fr>
Date: Tue, 15 Dec 2015 17:41:55 +0100
X-Google-Sender-Auth: 5JXtWfMHObo9YkCby0AxRpaKsrQ
Message-ID: <CANK0pbYLhvDvNp3qesU+SDW9HiOrsmXtguttaBTHRvPchNmKXQ@mail.gmail.com>
To: MANET IETF <manet@ietf.org>
Content-Type: multipart/alternative; boundary=089e010d9bdada5d2f0526f2789b
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/1JrdQQrRDVKsZe9FdTKYwYQGm38>
Subject: [manet] draft-ietf-manet-olsrv2-dat-metric
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: <https://mailarchive.ietf.org/arch/browse/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: Tue, 15 Dec 2015 16:54:42 -0000

--089e010d9bdada5d2f0526f2789b
Content-Type: text/plain; charset=UTF-8

Dear all,

following the IESG review, we have polished/updated the draft. You can find
it at: https://tools.ietf.org/html/draft-ietf-manet-olsrv2-dat-metric-11

Aside of nits, the most significant change since -10 is the explicit
mention of potential MITM attacks in the security section, as suggested in
the reviews, and the hint that such metric might be also considered and
experimented with outside of the OLSRv2 framework.

Cheers,

Emmanuel

--089e010d9bdada5d2f0526f2789b
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Dear all,<div><br></div><div>following the IESG review, we=
 have polished/updated the draft. You can find it at:=C2=A0<a href=3D"https=
://tools.ietf.org/html/draft-ietf-manet-olsrv2-dat-metric-11" rel=3D"norefe=
rrer" target=3D"_blank" style=3D"font-size:13px">https://tools.ietf.org/htm=
l/draft-ietf-manet-olsrv2-dat-metric-11</a></div><div><br></div><div>Aside =
of nits, the most significant change since -10 is the explicit mention of p=
otential MITM attacks in the security section, as suggested in the reviews,=
 and the hint that such metric might be also considered and experimented wi=
th outside of the OLSRv2 framework.</div><div><br></div><div>Cheers,</div><=
div><br></div><div>Emmanuel</div></div>

--089e010d9bdada5d2f0526f2789b--


From nobody Tue Dec 15 12:09:48 2015
Return-Path: <internet-drafts@ietf.org>
X-Original-To: manet@ietf.org
Delivered-To: manet@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id B52551ACD43; Tue, 15 Dec 2015 12:09:46 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.11.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20151215200946.27583.83329.idtracker@ietfa.amsl.com>
Date: Tue, 15 Dec 2015 12:09:46 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/RFseMpEju3tCfZT-fnaL9LTXMeU>
Cc: manet@ietf.org
Subject: [manet] I-D Action: draft-ietf-manet-olsrv2-dat-metric-12.txt
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
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: <https://mailarchive.ietf.org/arch/browse/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: Tue, 15 Dec 2015 20:09:46 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
 This draft is a work item of the Mobile Ad-hoc Networks Working Group of the IETF.

        Title           : Packet Sequence Number based directional airtime metric for OLSRv2
        Authors         : Henning Rogge
                          Emmanuel Baccelli
	Filename        : draft-ietf-manet-olsrv2-dat-metric-12.txt
	Pages           : 20
	Date            : 2015-12-15

Abstract:
   This document specifies an Directional Airtime (DAT) link metric for
   usage in OLSRv2.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-manet-olsrv2-dat-metric/

There's also a htmlized version available at:
https://tools.ietf.org/html/draft-ietf-manet-olsrv2-dat-metric-12

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-manet-olsrv2-dat-metric-12


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Wed Dec 16 06:44:19 2015
Return-Path: <iesg-secretary@ietf.org>
X-Original-To: manet@ietf.org
Delivered-To: manet@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id A4BD91B2E00; Wed, 16 Dec 2015 06:44:18 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: "IETF-Announce" <ietf-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.11.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20151216144418.18985.45795.idtracker@ietfa.amsl.com>
Date: Wed, 16 Dec 2015 06:44:18 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/q8fP-GEKTyaVQDWU3IWyjHhHqUw>
Cc: manet-chairs@ietf.org, manet@ietf.org, draft-ietf-manet-olsrv2-dat-metric@ietf.org, The IESG <iesg@ietf.org>, rfc-editor@rfc-editor.org
Subject: [manet] Document Action: 'Packet Sequence Number based directional airtime metric for OLSRv2' to Experimental RFC (draft-ietf-manet-olsrv2-dat-metric-12.txt)
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
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: <https://mailarchive.ietf.org/arch/browse/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: Wed, 16 Dec 2015 14:44:18 -0000

The IESG has approved the following document:
- 'Packet Sequence Number based directional airtime metric for OLSRv2'
  (draft-ietf-manet-olsrv2-dat-metric-12.txt) as Experimental RFC

This document is the product of the Mobile Ad-hoc Networks Working Group.

The IESG contact persons are Alvaro Retana, Alia Atlas and Deborah
Brungard.

A URL of this Internet Draft is:
https://datatracker.ietf.org/doc/draft-ietf-manet-olsrv2-dat-metric/





Technical Summary

   This document specifies an directional airtime link 
   metric for usage in OLSRv2.  A major shortcoming of 
   OLSR was the use of hop count as a routing metric for 
   MANET networks, which can have highly variable and 
   heterogeneous link properties.  OLSRv2 integrates the 
   concept of link metrics directly into the core specification 
   but the calculation and/or acquisition of this dimensionless 
   additive link cost is not specified.  

Working Group Summary

  There were no working group issues with any specific points.  


Document Quality

   There are at least 3 different independent implementations.  
   Most OLSRv2 implementation authors have either implemented 
   this draft or at least voiced the desire to do so. 

Personnel

   Document Shepherd:  Justin Dean (bebemaster@gmail.com)
   Responsible Area Director:  Alvaro Retana (aretana@cisco.com)


From nobody Fri Dec 18 07:27:42 2015
Return-Path: <debarshisanyal@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 16D571B2ED3 for <manet@ietfa.amsl.com>; Fri, 18 Dec 2015 07:27:36 -0800 (PST)
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 8Lhe1yPX2ags for <manet@ietfa.amsl.com>; Fri, 18 Dec 2015 07:27:31 -0800 (PST)
Received: from mail-lf0-x235.google.com (mail-lf0-x235.google.com [IPv6:2a00:1450:4010:c07::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 754EF1B3698 for <manet@ietf.org>; Fri, 18 Dec 2015 07:27:31 -0800 (PST)
Received: by mail-lf0-x235.google.com with SMTP id l133so74486356lfd.2 for <manet@ietf.org>; Fri, 18 Dec 2015 07:27:31 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:date:message-id:subject:from:to:content-type; bh=p7tKMXV98I40OF8FPk0XI6+CQwr1xiVwi6Y1vwq93Rk=; b=fFbseXKZQBK7UJAUymru7Ot4PwzRfjVg0KWkbKPkCu5aHB58oCCfYhqmjTITwgBtai zCYEOOewJac9MlWdGePJiTG1/gRFTUpXyw75MIwIJKe9XJ29lypqF1QdfVfGzlPsCsVD 8UdFjb+eqO3Uc1W/AXWo//+Ro8HWiZIKQBsNQl6ag29kC9B/2lVJe2RvWPSR6Izewg+S brkT6KR0z86L9rnkuoc+f2KxLvJBZdYx6naL+uk0dr7n47qS/3KCVXYFa9n6TrKpkL+c U2PQZ1sZcQyB1iV77rgeghDd26iXUOh2JnOjK9uzFJp5YZsstrcMLHTRn0s1VTkZgrs6 PBJg==
MIME-Version: 1.0
X-Received: by 10.25.32.144 with SMTP id g138mr1452996lfg.26.1450452449692; Fri, 18 Dec 2015 07:27:29 -0800 (PST)
Received: by 10.112.43.231 with HTTP; Fri, 18 Dec 2015 07:27:29 -0800 (PST)
Date: Fri, 18 Dec 2015 20:57:29 +0530
Message-ID: <CAMM4Rd_AwF3OEz=w5EzHnqW_n15DDwa3KrROBaNxWMWdkf=vuQ@mail.gmail.com>
From: Debarshi Sanyal <debarshisanyal@gmail.com>
To: "manet@ietf.org" <manet@ietf.org>
Content-Type: multipart/alternative; boundary=001a1140168a07145c05272dc773
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/Ai8MAGJRETm3HbwnzrrMVQAbAZU>
Subject: [manet] Query regarding IEEE 802.11 MAC
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: <https://mailarchive.ietf.org/arch/browse/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, 18 Dec 2015 15:27:36 -0000

--001a1140168a07145c05272dc773
Content-Type: text/plain; charset=UTF-8

Hi,

In the IEEE 802.11 MAC standard, if a node finds the medium idle for a
duration >= DIFS, it directly accesses the channel. Otherwise, if the
medium is busy, it waits for the medium to be idle for DIFS, then starts
backoff counter and transmits
when the counter reaches zero.

I understand that in case of a retransmission of a packet (for which no ACK
was received), the direct access is NOT allowed, i.e. it waits for the
medium to be idle for DIFS, then starts backoff counter (with a doubled
contention window) and transmits when the counter reaches zero.

Could you please confirm if my understanding is correct?


Regards,
Debarshi Kumar Sanyal

--001a1140168a07145c05272dc773
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div><div>Hi,<br><br></div>In the IEEE 802.11 MAC standard=
, if a node finds the medium idle for a duration &gt;=3D DIFS, it directly =
accesses the channel. Otherwise, if the medium is busy, it waits for the me=
dium to be idle for DIFS, then starts backoff counter and transmits <br>whe=
n the counter reaches zero.<br></div><br>I understand that in case of a ret=
ransmission of a packet (for which no ACK was received), the direct access =
is NOT allowed, i.e. it waits for the medium to be idle for DIFS, then star=
ts backoff counter (with a doubled contention window) and transmits when th=
e counter reaches zero.<br><br><div><div><div>Could you please confirm if m=
y understanding is correct?<br></div><div><br><br clear=3D"all"><div><div c=
lass=3D"gmail_signature"><div dir=3D"ltr"><font color=3D"#0000ff" face=3D"t=
ahoma, sans-serif">Regards,</font><div><font color=3D"#0000ff" face=3D"taho=
ma, sans-serif">Debarshi Kumar Sanyal<br></font></div></div></div></div>
</div></div></div></div>

--001a1140168a07145c05272dc773--


From nobody Tue Dec 22 06:42:31 2015
Return-Path: <internet-drafts@ietf.org>
X-Original-To: manet@ietf.org
Delivered-To: manet@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 777831A047A; Tue, 22 Dec 2015 06:42:30 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.11.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20151222144230.11733.27133.idtracker@ietfa.amsl.com>
Date: Tue, 22 Dec 2015 06:42:30 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/WXTNT-P9gmM8ZbS_tHAsGpYT8fE>
Cc: manet@ietf.org
Subject: [manet] I-D Action: draft-ietf-manet-rfc5444-usage-01.txt
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.15
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: <https://mailarchive.ietf.org/arch/browse/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: Tue, 22 Dec 2015 14:42:30 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
 This draft is a work item of the Mobile Ad-hoc Networks Working Group of the IETF.

        Title           : Rules For Designing Protocols Using the RFC 5444 Generalized Packet/ Message Format
        Authors         : Thomas Clausen
                          Christopher Dearlove
                          Ulrich Herberg
                          Henning Rogge
	Filename        : draft-ietf-manet-rfc5444-usage-01.txt
	Pages           : 19
	Date            : 2015-12-22

Abstract:
   This document updates the generalized MANET packet/message format,
   specified in RFC 5444, by providing rules and recommendations for how
   protocols can use that packet/message format.  In particular, the
   mandatory rules prohibit a number of uses of RFC 5444 that have been
   suggested in various proposals, and which would have led to
   interoperability problems, to the impediment of protocol extension
   development, and to an inability to use generic RFC 5444 parsers.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-manet-rfc5444-usage/

There's also a htmlized version available at:
https://tools.ietf.org/html/draft-ietf-manet-rfc5444-usage-01

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-manet-rfc5444-usage-01


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Tue Dec 22 06:51:17 2015
Return-Path: <chris.dearlove@baesystems.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 DE4B21A1A00 for <manet@ietfa.amsl.com>; Tue, 22 Dec 2015 06:51:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.103
X-Spam-Level: 
X-Spam-Status: No, score=-4.103 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RCVD_IN_DNSWL_HI=-5, RDNS_NONE=0.793] 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 j1h0bNPeJOrl for <manet@ietfa.amsl.com>; Tue, 22 Dec 2015 06:51:12 -0800 (PST)
Received: from ukmta2.baesystems.com (unknown [20.133.0.56]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5B90B1A19FE for <manet@ietf.org>; Tue, 22 Dec 2015 06:51:12 -0800 (PST)
X-IronPort-AV: E=Sophos;i="5.20,464,1444690800"; d="scan'208";a="24366588"
Received: from unknown (HELO baemasmds017.greenlnk.net) ([10.15.207.104]) by ukmta2.baesystems.com with ESMTP; 22 Dec 2015 14:51:10 +0000
X-IronPort-AV: E=Sophos;i="5.20,464,1444690800"; d="scan'208";a="125019593"
Received: from glkxh0005v.greenlnk.net ([10.109.2.36]) by baemasmds017.greenlnk.net with ESMTP; 22 Dec 2015 14:51:10 +0000
Received: from GLKXM0002V.GREENLNK.net ([169.254.5.123]) by GLKXH0005V.GREENLNK.net ([10.109.2.36]) with mapi id 14.03.0248.002; Tue, 22 Dec 2015 14:51:10 +0000
From: "Dearlove, Christopher (UK)" <chris.dearlove@baesystems.com>
To: "manet@ietf.org" <manet@ietf.org>
Thread-Topic: [manet] I-D Action: draft-ietf-manet-rfc5444-usage-01.txt
Thread-Index: AQHRPMcxMfrY01tNYUCXraZ5j2+EVp7XFScA
Date: Tue, 22 Dec 2015 14:51:05 +0000
Message-ID: <B31EEDDDB8ED7E4A93FDF12A4EECD30D880AE409@GLKXM0002V.GREENLNK.net>
References: <20151222144230.11733.27133.idtracker@ietfa.amsl.com>
In-Reply-To: <20151222144230.11733.27133.idtracker@ietfa.amsl.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.109.62.6]
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/gdXHs7_WS7fn7anlS_j62dQINCI>
Subject: Re: [manet] I-D Action: draft-ietf-manet-rfc5444-usage-01.txt
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: <https://mailarchive.ietf.org/arch/browse/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: Tue, 22 Dec 2015 14:51:16 -0000

A quick note to say this mostly (a) cleans up quite a few things that often=
 shouldn't have been there, (b) adds a few details in some places (most sig=
nificantly discussing TLV efficiency better) and (c) stops the draft expiri=
ng.

In the new year the authors, plus of course any input from the WG, will con=
sider if there are any other areas we should add to this draft, or whether =
we should go ahead and try to publish this basically as it is (corrections =
and clarifications included of course).

And if you see this in time, Happy Christmas and New Year. Otherwise hope i=
t was good in hindsight.

Christopher


-----Original Message-----
From: manet [mailto:manet-bounces@ietf.org] On Behalf Of internet-drafts@ie=
tf.org
Sent: 22 December 2015 14:43
To: i-d-announce@ietf.org
Cc: manet@ietf.org
Subject: [manet] I-D Action: draft-ietf-manet-rfc5444-usage-01.txt

----------------------! WARNING ! ---------------------- This message origi=
nates from outside our organisation, either from an external partner or fro=
m the internet.
Consider carefully whether you should click on any links, open any attachme=
nts or reply.
Follow the 'Report Suspicious Emails' link on IT matters for instructions o=
n reporting suspicious email messages.
--------------------------------------------------------

*** WARNING ***
EXTERNAL EMAIL -- This message originates from outside our organization.


A New Internet-Draft is available from the on-line Internet-Drafts director=
ies.
 This draft is a work item of the Mobile Ad-hoc Networks Working Group of t=
he IETF.

        Title           : Rules For Designing Protocols Using the RFC 5444 =
Generalized Packet/ Message Format
        Authors         : Thomas Clausen
                          Christopher Dearlove
                          Ulrich Herberg
                          Henning Rogge
	Filename        : draft-ietf-manet-rfc5444-usage-01.txt
	Pages           : 19
	Date            : 2015-12-22

Abstract:
   This document updates the generalized MANET packet/message format,
   specified in RFC 5444, by providing rules and recommendations for how
   protocols can use that packet/message format.  In particular, the
   mandatory rules prohibit a number of uses of RFC 5444 that have been
   suggested in various proposals, and which would have led to
   interoperability problems, to the impediment of protocol extension
   development, and to an inability to use generic RFC 5444 parsers.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-manet-rfc5444-usage/

There's also a htmlized version available at:
https://tools.ietf.org/html/draft-ietf-manet-rfc5444-usage-01

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-manet-rfc5444-usage-01


Please note that it may take a couple of minutes from the time of submissio=
n until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

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


From nobody Mon Dec 28 21:29:26 2015
Return-Path: <wwwrun@rfc-editor.org>
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 CC2341A1A82; Mon, 28 Dec 2015 21:29:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.912
X-Spam-Level: 
X-Spam-Status: No, score=-106.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] 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 tAscWup0rUoB; Mon, 28 Dec 2015 21:29:24 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) by ietfa.amsl.com (Postfix) with ESMTP id CB6031A1A7F; Mon, 28 Dec 2015 21:29:23 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id B882D180016; Mon, 28 Dec 2015 21:28:53 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20151229052853.B882D180016@rfc-editor.org>
Date: Mon, 28 Dec 2015 21:28:53 -0800 (PST)
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/kqNOMu8gfDrzCBOSZ4OpyZ02-UM>
Cc: drafts-update-ref@iana.org, manet@ietf.org, rfc-editor@rfc-editor.org
Subject: [manet] RFC 7722 on Multi-Topology Extension for the Optimized Link State Routing Protocol Version 2 (OLSRv2)
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: <https://mailarchive.ietf.org/arch/browse/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: Tue, 29 Dec 2015 05:29:26 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 7722

        Title:      Multi-Topology Extension for the Optimized 
                    Link State Routing Protocol Version 2 (OLSRv2) 
        Author:     C. Dearlove, T. Clausen
        Status:     Experimental
        Stream:     IETF
        Date:       December 2015
        Mailbox:    chris.dearlove@baesystems.com, 
                    T.Clausen@computer.org
        Pages:      23
        Characters: 52375
        Updates:    RFC 7188, RFC 7631

        I-D Tag:    draft-ietf-manet-olsrv2-multitopology-07.txt

        URL:        https://www.rfc-editor.org/info/rfc7722

        DOI:        http://dx.doi.org/10.17487/RFC7722

This specification describes an extension to the Optimized Link State
Routing Protocol version 2 (OLSRv2) to support multiple routing
topologies, while retaining interoperability with OLSRv2 routers that
do not implement this extension.

This specification updates RFCs 7188 and 7631 by modifying and
extending TLV registries and descriptions.

This document is a product of the Mobile Ad-hoc Networks Working Group of the IETF.


EXPERIMENTAL: This memo defines an Experimental Protocol for the
Internet community.  It does not specify an Internet standard of any
kind. Discussion and suggestions for improvement are requested.
Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/rfc.html

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC



From nobody Tue Dec 29 00:46:14 2015
Return-Path: <john.dowdell.ietf@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 E76081A6F11 for <manet@ietfa.amsl.com>; Tue, 29 Dec 2015 00:46:13 -0800 (PST)
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 kar5FNLurQlW for <manet@ietfa.amsl.com>; Tue, 29 Dec 2015 00:46:12 -0800 (PST)
Received: from mail-wm0-x22f.google.com (mail-wm0-x22f.google.com [IPv6:2a00:1450:400c:c09::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 890F61A6F10 for <manet@ietf.org>; Tue, 29 Dec 2015 00:46:11 -0800 (PST)
Received: by mail-wm0-x22f.google.com with SMTP id u188so4097788wmu.1 for <manet@ietf.org>; Tue, 29 Dec 2015 00:46:11 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:mime-version:to:from:subject:date:in-reply-to:references :content-type; bh=2OlTLuDdy7PKDf4SmAasXupeGc34Fiip+oh4ZFfPjJk=; b=sAWPKgumc9EN4zDWDEpFwXDVyvVyZjIgrxpsW8jQTdoG5isQqnpkbU38nSamTdVBX4 nGVIMIZ6GvXDkC0xj7nJvsyUoOWd0rPt/6Pjia5lHY4ZQHBf5+nWEicCcaJ14KCfZH0S zYNYBHgfx8xL681Oh0OdbH9/ytPg8a7rx901r0jWcL8Nf/y0a9eiBUnKBSjikmpW7lab a8nndD327J1qv9uup8eaUdZb9ODBOmwU/tQhP+6Xxzj0muPhH7hm1tPI8ARgqKHCi5c4 iK+hHrCEOkzqR0DgkVkyt4ddBXl/tnXA/DM6bkIT6hNWAiUxOWRugqRxb2Fe6NzH7cTT XPSQ==
X-Received: by 10.194.92.4 with SMTP id ci4mr74915984wjb.175.1451378770129; Tue, 29 Dec 2015 00:46:10 -0800 (PST)
Received: from [192.168.1.66] (host86-164-153-73.range86-164.btcentralplus.com. [86.164.153.73]) by smtp.gmail.com with ESMTPSA id e198sm76607wmd.0.2015.12.29.00.46.08 for <manet@ietf.org> (version=TLSv1/SSLv3 cipher=OTHER); Tue, 29 Dec 2015 00:46:09 -0800 (PST)
Message-ID: <56824851.cf821c0a.e2c36.0684@mx.google.com>
MIME-Version: 1.0
To: "manet@ietf.org" <manet@ietf.org>
From: John Dowdell <john.dowdell.ietf@gmail.com>
Date: Tue, 29 Dec 2015 08:45:11 +0000
In-Reply-To: <20151229052853.B882D180016@rfc-editor.org>
References: <20151229052853.B882D180016@rfc-editor.org>
Content-Type: multipart/alternative; boundary="_1B96B8A1-8458-4E64-BA27-50BB236984B7_"
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/SHSQJSsrNLTehUFe52GBHjSeP3c>
Subject: Re: [manet] RFC 7722 on Multi-Topology Extension for the Optimized LinkState Routing Protocol Version 2 (OLSRv2)
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: <https://mailarchive.ietf.org/arch/browse/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: Tue, 29 Dec 2015 08:46:14 -0000

--_1B96B8A1-8458-4E64-BA27-50BB236984B7_
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="utf-8"

Congratulations to Chris and Thomas!

Regards
John

-----Original Message-----
From: "rfc-editor@rfc-editor.org" <rfc-editor@rfc-editor.org>
Sent: =E2=80=8E29/=E2=80=8E12/=E2=80=8E2015 05:30
To: "ietf-announce@ietf.org" <ietf-announce@ietf.org>; "rfc-dist@rfc-editor=
.org" <rfc-dist@rfc-editor.org>
Cc: "drafts-update-ref@iana.org" <drafts-update-ref@iana.org>; "manet@ietf.=
org" <manet@ietf.org>; "rfc-editor@rfc-editor.org" <rfc-editor@rfc-editor.o=
rg>
Subject: [manet] RFC 7722 on Multi-Topology Extension for the Optimized Lin=
kState Routing Protocol Version 2 (OLSRv2)

A new Request for Comments is now available in online RFC libraries.

       =20
        RFC 7722

        Title:      Multi-Topology Extension for the Optimized=20
                    Link State Routing Protocol Version 2 (OLSRv2)=20
        Author:     C. Dearlove, T. Clausen
        Status:     Experimental
        Stream:     IETF
        Date:       December 2015
        Mailbox:    chris.dearlove@baesystems.com,=20
                    T.Clausen@computer.org
        Pages:      23
        Characters: 52375
        Updates:    RFC 7188, RFC 7631

        I-D Tag:    draft-ietf-manet-olsrv2-multitopology-07.txt

        URL:        https://www.rfc-editor.org/info/rfc7722

        DOI:        http://dx.doi.org/10.17487/RFC7722

This specification describes an extension to the Optimized Link State
Routing Protocol version 2 (OLSRv2) to support multiple routing
topologies, while retaining interoperability with OLSRv2 routers that
do not implement this extension.

This specification updates RFCs 7188 and 7631 by modifying and
extending TLV registries and descriptions.

This document is a product of the Mobile Ad-hoc Networks Working Group of t=
he IETF.


EXPERIMENTAL: This memo defines an Experimental Protocol for the
Internet community.  It does not specify an Internet standard of any
kind. Discussion and suggestions for improvement are requested.
Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/rfc.html

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC


_______________________________________________
manet mailing list
manet@ietf.org
https://www.ietf.org/mailman/listinfo/manet

--_1B96B8A1-8458-4E64-BA27-50BB236984B7_
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html; charset="utf-8"

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; charset=
=3Dutf-8"></head><body><div><div style=3D"font-family: Calibri,sans-serif; =
font-size: 11pt;">Congratulations to Chris and Thomas!<br><br>Regards<br>Jo=
hn</div></div><div dir=3D"ltr"><hr><span style=3D"font-family: Calibri,sans=
-serif; font-size: 11pt; font-weight: bold;">From: </span><span style=3D"fo=
nt-family: Calibri,sans-serif; font-size: 11pt;"><a href=3D"mailto:rfc-edit=
or@rfc-editor.org">rfc-editor@rfc-editor.org</a></span><br><span style=3D"f=
ont-family: Calibri,sans-serif; font-size: 11pt; font-weight: bold;">Sent: =
</span><span style=3D"font-family: Calibri,sans-serif; font-size: 11pt;">=
=E2=80=8E29/=E2=80=8E12/=E2=80=8E2015 05:30</span><br><span style=3D"font-f=
amily: Calibri,sans-serif; font-size: 11pt; font-weight: bold;">To: </span>=
<span style=3D"font-family: Calibri,sans-serif; font-size: 11pt;"><a href=
=3D"mailto:ietf-announce@ietf.org">ietf-announce@ietf.org</a>; <a href=3D"m=
ailto:rfc-dist@rfc-editor.org">rfc-dist@rfc-editor.org</a></span><br><span =
style=3D"font-family: Calibri,sans-serif; font-size: 11pt; font-weight: bol=
d;">Cc: </span><span style=3D"font-family: Calibri,sans-serif; font-size: 1=
1pt;"><a href=3D"mailto:drafts-update-ref@iana.org">drafts-update-ref@iana.=
org</a>; <a href=3D"mailto:manet@ietf.org">manet@ietf.org</a>; <a href=3D"m=
ailto:rfc-editor@rfc-editor.org">rfc-editor@rfc-editor.org</a></span><br><s=
pan style=3D"font-family: Calibri,sans-serif; font-size: 11pt; font-weight:=
 bold;">Subject: </span><span style=3D"font-family: Calibri,sans-serif; fon=
t-size: 11pt;">[manet] RFC 7722 on Multi-Topology Extension for the Optimiz=
ed LinkState Routing Protocol Version 2 (OLSRv2)</span><br><br></div>A new =
Request for Comments is now available in online RFC libraries.<br><br>&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp; RFC 7722<br><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Title:=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Multi-Topology Extension for the Optimized <=
br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Link State Routing Protocol Vers=
ion 2 (OLSRv2) <br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Author:&nbsp;=
&nbsp;&nbsp;&nbsp; C. Dearlove, T. Clausen<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp; Status:&nbsp;&nbsp;&nbsp;&nbsp; Experimental<br>&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Stream:&nbsp;&nbsp;&nbsp;&nbsp; IETF<br>&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Date:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp; December 2015<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Mailbox:&n=
bsp;&nbsp;&nbsp; chris.dearlove@baesystems.com, <br>&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp; T.Clausen@computer.org<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp; Pages:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 23<br>&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp; Characters: 52375<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp; Updates:&nbsp;&nbsp;&nbsp; RFC 7188, RFC 7631<br><br>&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; I-D Tag:&nbsp;&nbsp;&nbsp; draft-ietf-manet=
-olsrv2-multitopology-07.txt<br><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; URL:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; https://www.rfc-editor.o=
rg/info/rfc7722<br><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; DOI:&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; http://dx.doi.org/10.17487/RFC7722<br=
><br>This specification describes an extension to the Optimized Link State<=
br>Routing Protocol version 2 (OLSRv2) to support multiple routing<br>topol=
ogies, while retaining interoperability with OLSRv2 routers that<br>do not =
implement this extension.<br><br>This specification updates RFCs 7188 and 7=
631 by modifying and<br>extending TLV registries and descriptions.<br><br>T=
his document is a product of the Mobile Ad-hoc Networks Working Group of th=
e IETF.<br><br><br>EXPERIMENTAL: This memo defines an Experimental Protocol=
 for the<br>Internet community.&nbsp; It does not specify an Internet stand=
ard of any<br>kind. Discussion and suggestions for improvement are requeste=
d.<br>Distribution of this memo is unlimited.<br><br>This announcement is s=
ent to the IETF-Announce and rfc-dist lists.<br>To subscribe or unsubscribe=
, see<br>&nbsp; https://www.ietf.org/mailman/listinfo/ietf-announce<br>&nbs=
p; https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist<br><br>For sear=
ching the RFC series, see https://www.rfc-editor.org/search<br>For download=
ing RFCs, see https://www.rfc-editor.org/rfc.html<br><br>Requests for speci=
al distribution should be addressed to either the<br>author of the RFC in q=
uestion, or to rfc-editor@rfc-editor.org.&nbsp; Unless<br>specifically note=
d otherwise on the RFC itself, all RFCs are for<br>unlimited distribution.<=
br><br><br>The RFC Editor Team<br>Association Management Solutions, LLC<br>=
<br><br>_______________________________________________<br>manet mailing li=
st<br>manet@ietf.org<br>https://www.ietf.org/mailman/listinfo/manet<br></bo=
dy></html>=

--_1B96B8A1-8458-4E64-BA27-50BB236984B7_--

