IETF Logo Mail Archive

Re: [nmrg] Last Call: draft-irtf-nmrg-location-ipfix-05

"Romascanu, Dan (Dan)" <dromasca@avaya.com> Tue, 01 March 2016 19:02 UTC

Return-Path: <dromasca@avaya.com>
X-Original-To: nmrg@ietfa.amsl.com
Delivered-To: nmrg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C6BDD1B3FED for <nmrg@ietfa.amsl.com>; Tue, 1 Mar 2016 11:02:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.906
X-Spam-Level:
X-Spam-Status: No, score=-6.906 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.006] 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 2vvIwaBnjPAe for <nmrg@ietfa.amsl.com>; Tue, 1 Mar 2016 11:02:50 -0800 (PST)
Received: from de307622-de-outbound.net.avaya.com (de307622-de-outbound.net.avaya.com [198.152.71.100]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D0A821B3FEA for <nmrg@irtf.org>; Tue, 1 Mar 2016 11:02:49 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A2D0AQCrv9RW/xUHmMZeGQEBAQEPAQEBAYJfK1JtBrpmAQ2BZyGFcgKBOzgUAQEBAQEBAWQnhEEBAQEBAxIoPwwEAgEIDQQEAQELFAkHMhQJCAIEAQ0FCBqHfQENpkmZLQEBAQEBAQEBAQEBAQEBAQEBAQEBAREEhhOEOYQ1gyuBDwWXDAGFWIlnhESDGYQfgRqFc4hXHgEBQoNkaodFAX0BAQE
X-IPAS-Result: A2D0AQCrv9RW/xUHmMZeGQEBAQEPAQEBAYJfK1JtBrpmAQ2BZyGFcgKBOzgUAQEBAQEBAWQnhEEBAQEBAxIoPwwEAgEIDQQEAQELFAkHMhQJCAIEAQ0FCBqHfQENpkmZLQEBAQEBAQEBAQEBAQEBAQEBAQEBAREEhhOEOYQ1gyuBDwWXDAGFWIlnhESDGYQfgRqFc4hXHgEBQoNkaodFAX0BAQE
X-IronPort-AV: E=Sophos;i="5.22,521,1449550800"; d="scan'208";a="144877407"
Received: from unknown (HELO co300216-co-erhwest-exch.avaya.com) ([198.152.7.21]) by de307622-de-outbound.net.avaya.com with ESMTP; 01 Mar 2016 14:02:46 -0500
X-OutboundMail_SMTP: 1
Received: from unknown (HELO AZ-FFEXHC02.global.avaya.com) ([135.64.58.12]) by co300216-co-erhwest-out.avaya.com with ESMTP/TLS/AES256-SHA; 01 Mar 2016 14:02:45 -0500
Received: from AZ-FFEXMB04.global.avaya.com ([fe80::6db7:b0af:8480:c126]) by AZ-FFEXHC02.global.avaya.com ([135.64.58.12]) with mapi id 14.03.0174.001; Tue, 1 Mar 2016 20:02:43 +0100
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: Lisandro Zambenedetti Granville <granville@inf.ufrgs.br>, Network Management Research Group <nmrg@irtf.org>
Thread-Topic: [nmrg] Last Call: draft-irtf-nmrg-location-ipfix-05
Thread-Index: AQHRaBhOeRqWDUUQsUimjQ0pvJb6Np9FB81A
Date: Tue, 01 Mar 2016 19:02:42 +0000
Message-ID: <9904FB1B0159DA42B0B887B7FA8119CA6BF739CD@AZ-FFEXMB04.global.avaya.com>
References: <59831908-3640-4C64-B6DF-C430F8278927@inf.ufrgs.br>
In-Reply-To: <59831908-3640-4C64-B6DF-C430F8278927@inf.ufrgs.br>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [135.64.58.47]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/nmrg/Q-uxQlGeteAtJ4exvFLTk_9F9bw>
Cc: "iana-prot-param-comment@iana.org" <iana-prot-param-comment@iana.org>
Subject: Re: [nmrg] Last Call: draft-irtf-nmrg-location-ipfix-05
X-BeenThere: nmrg@irtf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Network Management Research Group discussion list <nmrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/nmrg>, <mailto:nmrg-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/nmrg/>
List-Post: <mailto:nmrg@irtf.org>
List-Help: <mailto:nmrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/nmrg>, <mailto:nmrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Mar 2016 19:02:55 -0000

Hi, 

I have a comment related to the IANA Considerations section. First, it refers [4119] which is not listed in the references. Second it is not clear what is required from IANA. Is this actually adding a new column to the registry defined in RFC 4119, section 6.1? This should be clearly explained, and this is an update to RFC 4119. There is one more problem however. The registry is extensible according to a first come - first served policy, allowing for new methods for determining location to be added. How will the new numeric values be picked. Probably the next available integer - but this also needs to be explained. 

I hope this helps. 

Regards,

Dan
 

> -----Original Message-----
> From: nmrg [mailto:nmrg-bounces@irtf.org] On Behalf Of Lisandro
> Zambenedetti Granville
> Sent: Monday, February 15, 2016 7:43 PM
> To: Network Management Research Group
> Subject: [nmrg] Last Call: draft-irtf-nmrg-location-ipfix-05
> 
> Dear NMRG
> 
> This message is to start a two week last call (LC) on the following NMRG
> document, on incorporating location information in IP flow-based
> monitoring:
> 
> . draft-irtf-nmrg-location-ipfix-05
>  https://datatracker.ietf.org/doc/draft-irtf-nmrg-location-ipfix/
> 
> Please review the documents and provide your feedback in this two week
> window. This last calls ends in Mar. 1st.
> 
> Lisandro and Laurent

v2.23.0 | Report a Bug | By Email