Re: [manet-dlep-rg] Mandatory processing TLVs by routers

Teco Boot <teco@inf-net.nl> Tue, 12 November 2013 18:17 UTC

Return-Path: <teco@inf-net.nl>
X-Original-To: manet-dlep-rg@ietfa.amsl.com
Delivered-To: manet-dlep-rg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D172911E811B for <manet-dlep-rg@ietfa.amsl.com>; Tue, 12 Nov 2013 10:17:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.135
X-Spam-Level:
X-Spam-Status: No, score=-3.135 tagged_above=-999 required=5 tests=[AWL=-0.136, BAYES_00=-2.599, J_CHICKENPOX_44=0.6, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pSfbIpFo0wRy for <manet-dlep-rg@ietfa.amsl.com>; Tue, 12 Nov 2013 10:17:42 -0800 (PST)
Received: from mail-ea0-f174.google.com (mail-ea0-f174.google.com [209.85.215.174]) by ietfa.amsl.com (Postfix) with ESMTP id 195F411E810A for <manet-dlep-rg@ietf.org>; Tue, 12 Nov 2013 10:17:41 -0800 (PST)
Received: by mail-ea0-f174.google.com with SMTP id n15so3032980ead.5 for <manet-dlep-rg@ietf.org>; Tue, 12 Nov 2013 10:17:40 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:content-type:mime-version:subject:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=xVzz9g23HXMYZ6q9bo2VWARJs/MTEu3OzlwbXaiZQrY=; b=mAexJm3w2N6Kc82NmgeBqD/5Rxy8RUcgX3a6Lb8ZX6BQbawFRS46OLzoGXqTcHeQkT PIoR/MNgYSv5l8PkpbRXbboIpUShflN4kEuZiYxzqrkIwoDzhJgda94dpvhFu7MK8Mpi R+cgVwG6UJj6PjHvYhTnVS9P6S5WnAI+Z4b1gQI/hkQkiXCIv9dBB6wZkU024jlYvh0S +bg2XVv0jmDgwk3TETmLRooMU7WMSTtsMwg3F80Cfgk/xMvH40gprPQf7PcHJimqKumh GOdin7SZ/aeokSdGujLZgm6XOXO360CmKelB4w5MmJtReyBq51c6Fx6/o/hf9CGlLesn kUXw==
X-Gm-Message-State: ALoCoQmrotxLG7IbgewaYQf5OPH8uIXA5IaFH4RcSLnN7LJgeNF1hEm9BTRGUBGVI65G6fvl9vZE
X-Received: by 10.15.94.201 with SMTP id bb49mr43739412eeb.23.1384280260816; Tue, 12 Nov 2013 10:17:40 -0800 (PST)
Received: from [10.175.173.29] (524A14A4.cm-4-3a.dynamic.ziggo.nl. [82.74.20.164]) by mx.google.com with ESMTPSA id m54sm70360028eex.2.2013.11.12.10.17.39 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 12 Nov 2013 10:17:39 -0800 (PST)
Content-Type: text/plain; charset="windows-1252"
Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1816\))
From: Teco Boot <teco@inf-net.nl>
In-Reply-To: <14CC4A97-CF43-4F30-89ED-CDDA336F94A3@cisco.com>
Date: Tue, 12 Nov 2013 19:17:38 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <2E2BEE1A-4BA4-4C07-9484-693B1646B5AD@inf-net.nl>
References: <72FB622921C13746AD6349E70A8D9F307D9192F7@EXC-MBX03.tsn.tno.nl> <CAK=bVC85XAXR3Zkwq+JwELF-dvgrKwbowWCvwvnjeVn7VStnbw@mail.gmail.com> <72FB622921C13746AD6349E70A8D9F307D9193CD@EXC-MBX03.tsn.tno.nl> <5A8A5085482DA84995F4E70F5093AB50268E6C@XCH-BLV-503.nw.nos.boeing.com> <B2BA430A-F4E6-4DED-A7BB-7282A22802B7@inf-net.nl> <D02397F1-9D1B-4B36-81D0-4585ACDBA34A@gmail.com> <5D184300-2D97-4EC1-8D91-76D4A79B2BDA@inf-net.nl> <DDAE98C5-520E-4F8F-9F9B-2AB9A15A70EF@cisco.com> <F5164D41-0C8F-4E23-B2F8-F7CE4843131C@inf-net.nl> <349D2FB7-896C-47AD-9815-9131FEBBCB45@cisco.com> <806ecf54-7e1e-46f4-94ee-0704c2acc284@SUCNPTEXC01.COM.AD.UK.DS.CORP> <B177F831FB91F242972D0C35F6A0733106FB043A@SUCNPTEXM01.com.ad.uk.ds.corp> <A483DEC1-04C8-4DB0-8DF3-41A35F166179@inf-net.nl> <14CC4A97-CF43-4F30-89ED-CDDA336F94A3@cisco.com>
To: Stan Ratliff <sratliff@cisco.com>
X-Mailer: Apple Mail (2.1816)
Cc: "DLEP Research Group (manet-dlep-rg@ietf.org)" <manet-dlep-rg@ietf.org>, "Taylor, Rick" <Rick.Taylor@cassidian.com>
Subject: Re: [manet-dlep-rg] Mandatory processing TLVs by routers
X-BeenThere: manet-dlep-rg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: DLEP Radio Group <manet-dlep-rg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet-dlep-rg>, <mailto:manet-dlep-rg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet-dlep-rg>
List-Post: <mailto:manet-dlep-rg@ietf.org>
List-Help: <mailto:manet-dlep-rg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet-dlep-rg>, <mailto:manet-dlep-rg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Nov 2013 18:17:46 -0000

Op 12 nov. 2013, om 18:58 heeft Stan Ratliff (sratliff) <sratliff@cisco.com> het volgende geschreven:

> 
> DLEP peers MUST terminate a session (or note an error and declare a message malformed) if any MANDATORY TLVs are *missing* from a message. 

Yes.


> As to the specific metrics case: 
> 
> Assume that a modem has delivered the 4 MANDATORY TLVs during DLEP peer session initialization. 
> Now assume that a "Destination Update" is presented to the router containing a "new" (unannounced) metric TLV.
> 
> What is the router to do?

This is not about TLVs it doesn't 'understand' but about invalid operation of the peer.

First, the router issues a bug record in vendors tracking system ;-)
Then, it makes the exception. That’s why it is a SHOULD.


Teco
 


> 
> Stan
> 
> On Nov 12, 2013, at 10:32 AM, Teco Boot <teco@inf-net.nl>
> wrote:
> 
>> 
>> Op 12 nov. 2013, om 13:51 heeft Taylor, Rick <Rick.Taylor@cassidian.com> het volgende geschreven:
>> 
>>> My understanding of mandatory metrics was:
>>> 
>>> Modems:  MUST advertise support (by giving default values in Initialize message at least) for MDRT,MDRR,CDRT,CDRR, RLQ and Latency (TBD)
>>> 
>>> Routers:  MUST NOT terminate a connection on receipt of any of these TLVs because they do not 'understand' them.
>> 
>> Router SHOULD NOT terminate a connection on receipt of any TLVs it doesn't 'understand'.
>> 
>> Teco
>> 
>> 
>>> Whether the router does anything with any of these metrics is the router's business.
>>> 
>>> Rick Taylor
>>> 
>>>> -----Original Message-----
>>>> From: manet-dlep-rg-bounces@ietf.org [mailto:manet-dlep-rg-
>>>> bounces@ietf.org] On Behalf Of Teco Boot
>>>> Sent: 11 November 2013 18:17
>>>> To: Stan Ratliff
>>>> Cc: DLEP Research Group (manet-dlep-rg@ietf.org)
>>>> Subject: Re: [manet-dlep-rg] Mandatory processing TLVs by routers
>>>> 
>>>> 
>>>> Op 11 nov. 2013, om 18:44 heeft Stan Ratliff (sratliff)
>>>> <sratliff@cisco.com> het volgende geschreven:
>>>> 
>>>>> 
>>>>> On Nov 11, 2013, at 11:00 AM, Teco Boot <teco@inf-net.nl> wrote:
>>>>> 
>>>>>> Was Re: [manet-dlep-rg] notes DLEP meeting @ IETF88
>>>>>> 
>>>>>> I'll split of threads, unless one prefer mail storms without clear
>>>> subjects.
>>>>>> 
>>>>>> Op 11 nov. 2013, om 01:55 heeft Stan Ratliff (sratliff)
>>>> <sratliff@cisco.com> het volgende geschreven:
>>>>>> 
>>>>>>> Item 1 and 2 seem contradictory to me. Metric values are reported via
>>>> TLVs. If a given metric TLV is MANDATORY, then the router MUST process it
>>>> (at least, the router MUST NOT generate an error because it exists).
>>>>>> 
>>>>>> This is about:
>>>>>> 
>>>>>>>>>>> 1. There are no metric TLVs it is MANDATORY for the Router to
>>>> process.
>>>>>>>>>>> 2. The modem MUST report MDRT, MDRR, CDRT, and CDRR in the Peer
>>>> Discovery message, and make a best effort to accurately report these
>>>> metrics subsequently.
>>>>>> 
>>>>>> Item 2 is the first one to read, then item 1 follows. Routers may
>>>> ignore all TLVs, and for example only use Neighbor Up and Neighbor Down.
>>>>> 
>>>>> 
>>>>> Oh, well.... naturally. When looking at an enumerated list, I *SHOULD
>>>> HAVE* had the general sense to read the second item first.... silly me.
>>>>> 
>>>>> On another topic, to say that I disagree with "... Routers may ignore all
>>>> TLVs..." would be an understatement. That's why TLVs are classified as
>>>> MANDATORY or OPTIONAL. Routers (or modems, for that matter) are free to
>>>> ignore OPTIONAL TLVs. But to mandate that something exist in a message,
>>>> but then say "but you can ignore it"? Doesn't make any sense to me.
>>>> 
>>>> Why do you care? It is perfectly fine you use these mandatory TLV's. Let
>>>> others do their thing.
>>>> 
>>>> Teco
>>>> 
>>>> 
>>>> _______________________________________________
>>>> manet-dlep-rg mailing list
>>>> manet-dlep-rg@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/manet-dlep-rg
>>> The information contained within this e-mail and any files attached to this e-mail is private and in addition may include commercially sensitive information. The contents of this e-mail are for the intended recipient only and therefore if you wish to disclose the information contained within this e-mail or attached files, please contact the sender prior to any such disclosure. If you are not the intended recipient, any disclosure, copying or distribution is prohibited. Please also contact the sender and inform them of the error and delete the e-mail, including any attached files from your system. Cassidian Limited, Registered Office : Quadrant House, Celtic Springs, Coedkernew, Newport, NP10 8FZ Company No: 04191036 http://www.cassidian.com
>> 
>