IETF Logo Mail Archive

Re: [alto] Call for adoption: Adopting graph representation format deliverables

"Scharf, Michael (Nokia - DE)" <michael.scharf@nokia.com> Tue, 02 August 2016 09:04 UTC

Return-Path: <michael.scharf@nokia.com>
X-Original-To: alto@ietfa.amsl.com
Delivered-To: alto@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 355DC12D181; Tue, 2 Aug 2016 02:04:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.921
X-Spam-Level:
X-Spam-Status: No, score=-6.921 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 VuAade5jGciE; Tue, 2 Aug 2016 02:04:47 -0700 (PDT)
Received: from smtp-fr.alcatel-lucent.com (fr-hpida-esg-02.alcatel-lucent.com [135.245.210.21]) (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 E9F7E128E19; Tue, 2 Aug 2016 02:04:46 -0700 (PDT)
Received: from fr712umx4.dmz.alcatel-lucent.com (unknown [135.245.210.45]) by Websense Email Security Gateway with ESMTPS id 8B586A0E49738; Tue, 2 Aug 2016 09:04:43 +0000 (GMT)
Received: from fr712usmtp2.zeu.alcatel-lucent.com (fr712usmtp2.zeu.alcatel-lucent.com [135.239.2.42]) by fr712umx4.dmz.alcatel-lucent.com (GMO-o) with ESMTP id u7294hsP004199 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 2 Aug 2016 09:04:44 GMT
Received: from FR712WXCHHUB03.zeu.alcatel-lucent.com (fr712wxchhub03.zeu.alcatel-lucent.com [135.239.2.74]) by fr712usmtp2.zeu.alcatel-lucent.com (GMO) with ESMTP id u7294af3005710 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 2 Aug 2016 11:04:43 +0200
Received: from FR712WXCHMBA15.zeu.alcatel-lucent.com ([169.254.7.159]) by FR712WXCHHUB03.zeu.alcatel-lucent.com ([135.239.2.74]) with mapi id 14.03.0195.001; Tue, 2 Aug 2016 11:04:37 +0200
From: "Scharf, Michael (Nokia - DE)" <michael.scharf@nokia.com>
To: "Gurbani, Vijay (Nokia - US)" <vijay.gurbani@nokia-bell-labs.com>, IETF ALTO <alto@ietf.org>
Thread-Topic: Call for adoption: Adopting graph representation format deliverables
Thread-Index: AQHR7DzzD/+eX6kVBkq2U13+/rtSI6A1XvQQ
Date: Tue, 02 Aug 2016 09:04:37 +0000
Message-ID: <655C07320163294895BBADA28372AF5D4898B829@FR712WXCHMBA15.zeu.alcatel-lucent.com>
References: <7da1ee78-9756-8ca6-860a-9ecd795792a6@nokia-bell-labs.com>
In-Reply-To: <7da1ee78-9756-8ca6-860a-9ecd795792a6@nokia-bell-labs.com>
Accept-Language: de-DE, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [135.239.27.39]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/alto/8U42mRrnu6PLVdrgWSSFfIeglFQ>
Cc: "draft-gao-alto-routing-state-abstraction@tools.ietf.org" <draft-gao-alto-routing-state-abstraction@tools.ietf.org>, "draft-yang-alto-path-vector@ietf.org" <draft-yang-alto-path-vector@ietf.org>
Subject: Re: [alto] Call for adoption: Adopting graph representation format deliverables
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "Application-Layer Traffic Optimization \(alto\) WG mailing list" <alto.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/alto>, <mailto:alto-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/alto/>
List-Post: <mailto:alto@ietf.org>
List-Help: <mailto:alto-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/alto>, <mailto:alto-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Aug 2016 09:04:49 -0000

I think the path vector format is a valuable addition to ALTO. Sorry, I have not followed the routing state abstraction recently but looking at the document right now I find the current wording rather difficult to read. For instance, it lacks intuitive engineering examples. But clarity could possibly be improved after WG adoption.

Michael  


-----Original Message-----
From: Vijay K. Gurbani [mailto:vijay.gurbani@nokia-bell-labs.com] 
Sent: Monday, August 01, 2016 11:38 PM
To: IETF ALTO
Cc: draft-gao-alto-routing-state-abstraction@tools.ietf.org; draft-yang-alto-path-vector@ietf.org
Subject: Call for adoption: Adopting graph representation format deliverables

Folks: As the (draft) minutes [1] of IETF 96 reflect, there was general consensus on adoption of path vector and routing state abstraction documents towards the charter deliverable of graph representation formats in ALTO.

The chairs will like to start a call for adoption of the two documents
--- https://tools.ietf.org/html/draft-yang-alto-path-vector-03 and
https://tools.ietf.org/html/draft-gao-alto-routing-state-abstraction-03
--- as deliverables towards the charter item.

Note that there remains some ambiguity (in the chair's mind) on whether, once adopted, these will proceed as two drafts or whether they will be merged in one.  The authors of these drafts are urged to provide clarity on the evolution of these documents.

The call for adoption runs for two weeks, from Mon Aug 1, 2016 to Mon Aug 15, 2016.  This will be a good time to comment on the list and inform the working group of any issues with adopting these items, or whether the working group was remiss in considering other documents.
Please post to the list.  (Even a simple "I support these documents towards charter deliverable" is a good indication.)

Thanks,

[1] https://www.ietf.org/proceedings/96/minutes/minutes-96-alto

- vijay
--
Vijay K. Gurbani, Bell Laboratories, Nokia Networks
1960 Lucent Lane, Rm. 9C-533, Naperville, Illinois 60563 (USA)
Email: vkg@bell-labs.com / vijay.gurbani@nokia-bell-labs.com
Web: http://ect.bell-labs.com/who/vkg/  | Calendar: http://goo.gl/x3Ogq

v2.23.0 | Report a Bug | By Email