IETF Logo Mail Archive

Re: [Idr] AD Review of draft-ietf-idr-ix-bgp-route-server-09

"Alvaro Retana (aretana)" <aretana@cisco.com> Wed, 01 June 2016 18:17 UTC

Return-Path: <aretana@cisco.com>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D374112D1C2; Wed, 1 Jun 2016 11:17:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.947
X-Spam-Level:
X-Spam-Status: No, score=-15.947 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_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.426, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
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 eG9QOIe1Ieo1; Wed, 1 Jun 2016 11:17:14 -0700 (PDT)
Received: from alln-iport-3.cisco.com (alln-iport-3.cisco.com [173.37.142.90]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2371912D0A8; Wed, 1 Jun 2016 11:17:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1340; q=dns/txt; s=iport; t=1464805034; x=1466014634; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=L9ac8X+peQc/W1Cw/Y45+LRRe82eipYWwIN/NAPFTfs=; b=JSWQ+5oPtTGL5reztL/ELWD6KzALaV2s+OpxWXWWi1kOudSZUwoCuj03 TiFOsTtNrlqFAyNj0hrINPZNNb0eDlPXMvEFewhko3zY0TGWu0XHPs32R lmmLMh571fC83s8gbq4So47Np+V7930yLmQshSbqaSfBR8ClwKN8gMPNS Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0ASAgDCJU9X/5tdJa1dgz2BUwa6FgENgXqGEQKBMjgUAQEBAQEBAWUnhEYBAQQ6PxACAQgYHhAyJQIEDgWIL8FHAQEBAQEBAQEBAQEBAQEBAQEBH4YnhE2EKoVwAQSTN4UAAY4fgWmNM4YziRgBHgEBQoNtbok4fwEBAQ
X-IronPort-AV: E=Sophos;i="5.26,402,1459814400"; d="scan'208";a="279826101"
Received: from rcdn-core-4.cisco.com ([173.37.93.155]) by alln-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 01 Jun 2016 18:17:13 +0000
Received: from XCH-ALN-001.cisco.com (xch-aln-001.cisco.com [173.36.7.11]) by rcdn-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id u51IHD8P027202 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 1 Jun 2016 18:17:13 GMT
Received: from xch-aln-002.cisco.com (173.36.7.12) by XCH-ALN-001.cisco.com (173.36.7.11) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Wed, 1 Jun 2016 13:17:12 -0500
Received: from xch-aln-002.cisco.com ([173.36.7.12]) by XCH-ALN-002.cisco.com ([173.36.7.12]) with mapi id 15.00.1104.009; Wed, 1 Jun 2016 13:17:12 -0500
From: "Alvaro Retana (aretana)" <aretana@cisco.com>
To: Nick Hilliard <nick@inex.ie>
Thread-Topic: AD Review of draft-ietf-idr-ix-bgp-route-server-09
Thread-Index: AQHRNFCzHRdSwT+uvUK1lt056oVbCA==
Date: Wed, 01 Jun 2016 18:17:12 +0000
Message-ID: <D3749E53.12A346%aretana@cisco.com>
References: <D29085C4.EFB5A%aretana@cisco.com> <5723E3B4.4090103@foobar.org> <D36A0E05.1277AB%aretana@cisco.com> <574EF89D.6080206@inex.ie>
In-Reply-To: <574EF89D.6080206@inex.ie>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.6.2.160219
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.117.15.4]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <F83F9C994AB4984E8606190766CC18F9@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/idr/8JeLjYqqoBNY2bN-0h5Hadnw9s4>
Cc: "idr-chairs@ietf.org" <idr-chairs@ietf.org>, "idr@ietf.org" <idr@ietf.org>, "shares@ndzh.com" <shares@ndzh.com>, "draft-ietf-idr-ix-bgp-route-server@ietf.org" <draft-ietf-idr-ix-bgp-route-server@ietf.org>
Subject: Re: [Idr] AD Review of draft-ietf-idr-ix-bgp-route-server-09
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Jun 2016 18:17:16 -0000

On 6/1/16, 11:00 AM, "Nick Hilliard" <nick@inex.ie> wrote:

Nick:

Hi!

>Alvaro Retana (aretana) wrote:
>>>We deliberately steered clear of dealing with operational issues in this
>>>draft because its focus was on the bgp protocol. Several of the comments
>>>you make below are probably more relevant to
>>>draft-ietf-grow-ix-bgp-route-server-operations. We've marked them as
>>>such.
>>Does that mean that you will update
>>draft-ietf-grow-ix-bgp-route-server-operations, or what?  Just wondering.
>>It would be nice to have a reference from this document to
>>draft-ietf-grow-ix-bgp-route-server-operations.
>
>We thought about it and the bgp-route-server-operations operations draft
>references the bgp-route-server draft, but not the other way around.
>This was done because bgp-route-server is standards track and
>bgp-route-server-operations is informational.  Also, it stops the
>chicken and egg problem.

Those are not problems.  Standards track documents point at Informational
documents all the time, as long as the reference is not Normative, then
it's ok.  In this case, I think it would be beneficial to tell people
reading draft-ietf-idr-ix-bgp-route-server that there are operational
considerations (as an informational reference) somewhere else.

I'll leave it up to you.

Thanks!

Alvaro.

v2.23.0 | Report a Bug | By Email