Vijay K. Gurbani | 4 Dec 22:21 2014

IETF 91 minutes (draft) posted

Folks: The minutes for the Honolulu ALTO WG meeting have been posted.

Please see http://www.ietf.org/proceedings/91/minutes/minutes-91-alto
and let Enrico, Jan and I know of any discrepancies.

Cheers,

- vijay
--

-- 
Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent
1960 Lucent Lane, Rm. 9C-533, Naperville, Illinois 60563 (USA)
Email: vkg <at> {bell-labs.com,acm.org} / vijay.gurbani <at> alcatel-lucent.com
Web: http://ect.bell-labs.com/who/vkg/  | Calendar: http://goo.gl/x3Ogq

邓灵莉/Lingli Deng | 21 Nov 03:28 2014

FW: New Version Notification for draft-deng-alto-p2p-ext-05.txt

Hi all,

We've uploaded a new revision on endpoint property extension draft.
The technical content in this revision is not changed and consistent with the slides we presented last
week, and all the changes are editorial. 
For those not present last week or familiar with our draft, please refer to the slides:
http://www.ietf.org/proceedings/91/slides/slides-91-alto-7.pdf 

Due to the time limit, we was not able to solicit feedback from the group as we would wanted.
Any review and comments from the list would be highly appreciated.

Lingli&Haibin&Sebastian&Richard&Qin

> -----Original Message-----
> From: internet-drafts <at> ietf.org [mailto:internet-drafts <at> ietf.org]
> Sent: Friday, November 21, 2014 10:19 AM
> To: Haibin Song; Qin Wu; Wenson Wu; Richard Yang; Haibin Song; Deng Lingli;
> Sebastian Kiesel; Yang Yang; Lingli Deng; Sebastian Kiesel
> Subject: New Version Notification for draft-deng-alto-p2p-ext-05.txt
> 
> 
> A new version of I-D, draft-deng-alto-p2p-ext-05.txt
> has been successfully submitted by Lingli Deng and posted to the
> IETF repository.
> 
> Name:		draft-deng-alto-p2p-ext
> Revision:	05
> Title:		Extended End Point Properties for Application-Layer Traffic
> Optimization
> Document date:	2014-11-17
(Continue reading)

Huseyin ABACI | 16 Nov 20:13 2014
Picon

Call for eBook Chapters on Sustainable Computing

Call for eBook Chapters on "Sustainable Computing"

We apologise if you get multiple copies of this message.

Please forward this message to your colleagues that might be interested.


Deadlines
Proposal Submission Deadline: 15 December 2014
Notification of Acceptance: 30 January 2015
Full Chapter Submission: 1 May 2015
Review Results Returned: 31 August 2015
Final Chapter Submission: 9 October 2015

Book Chapters for
Sustainable Computing

Proposal Submission
1-2 pages including abstract, chapter objectives and chapter outline, in Microsoft Word or Adobe PDF format. Submit to huseyin.abaci <at> adu.edu.tr and c.peoples <at> ulster.ac.uk with the subject title “Sustainable Computing - Chapter Proposal" before 15 December 2014.

eBook Editors
Editor-in-Chief
Huseyin Abaci Ph.D., Assistant Professor in the Department of Computer Engineering at Adnan Menderes University, Aydın, Turkey
Email: huseyin.abaci <at> adu.edu.tr  

Co-Editor
Cathryn Peoples Ph.D., Teaching Fellow in the Faculty of Computing and Engineering at the University of Ulster, Coleraine, Northern Ireland, United Kingdom.  
Email: c.peoples <at> ulster.ac.uk

Description of the eBook on "Sustainable Computing"
Improvements in the operation of Information and Communication Technology (ICT) allows and encourages the provision of more effective and efficient facilities and services, such as bandwidth-intensive Video-on-Demand (VoD), Voice over Internet Protocol (VoIP), cloud computing, online multi-player gaming, and file sharing. These activities, however, come at the cost of higher energy consumption. Global warming and energy dependence are major international concerns today, not just for our government agencies, but also for the utilities that provide critical infrastructures for our digital economy.

This eBook will focus on the achievement of energy efficient computing, investigating energy efficient technologies and techniques in data centres, clouds, and more general wired/wireless networks. Of specific interest are the development of efficient data collection methods, algorithms and optimisation techniques which achieve energy reduction.

eBook Topics
Topics of interests include but are not limited to the following:

•        Energy efficiency methods for sustainable ICT
•        Energy efficiency in datacentres
•        Energy efficiency in cloud networks
•        Energy efficiency in wired metro-core networks
•        Energy efficiency in wireless networks
•        Energy efficiency in customer premises equipment
•        Energy efficiency in network devices
•        Energy efficiency in optical networks
•        Energy efficient topology/protocols/applications
•        Energy efficiency in integrated circuits and other computer components.
•        Test bed setup to investigate proposed energy efficient network solutions.

Chapter Submission Procedure
Authors are invited to submit a 1-2 page chapter proposal before 15 December 2015. Authors of accepted proposals will be notified by 30 January 2015, and will be sent guidelines for preparation of the full chapter (between 5,000 and 12,000 words in length). Full chapters should be submitted by 1 May 2015 and will be reviewed on a double-blind review basis. Contributors may also be requested to serve as reviewers for this eBook.

Publisher
This book will be published by Bentham Science Publisher and is expected to be released before the end of December 2015.

Inquiries
If you have any inquiries about this call, please contact us at huseyin.abaci <at> adu.edu.tr or c.peoples <at> ulster.ac.uk.
<div><div><div><div tabindex="0" role="button" class="_rp_N3 ms-font-weight-regular ms-font-color-neutralDark rpHighlightAllClass rpHighlightBodyClass"><div class="rps_d721"><div><div><div data-mce-style="font-family: times new roman,new york,times,serif; font-size: 12pt; color: #000000;">
<div><span data-mce-style="font-size: xx-large;">Call for eBook Chapters on "Sustainable Computing"</span></div>
<div><br></div>
<div>We apologise if you get multiple copies of this message.</div>
<div><br></div>
<div>Please forward this message to your colleagues that might be interested.</div>
<div><br></div>
<div>
<br><span data-mce-style="font-size: x-large;">Deadlines</span><br> Proposal Submission Deadline: 15 December 2014<br> Notification of Acceptance: 30 January 2015<br> Full Chapter Submission: 1 May 2015<br> Review Results Returned: 31 August 2015<br> Final Chapter Submission: 9 October 2015</div>
<div><br></div>
<div>
<span data-mce-style="font-size: x-large;">Book Chapters for</span> <br> Sustainable Computing</div>
<div><br></div>
<div>
<span data-mce-style="font-size: x-large;">Proposal Submission</span> <br> 1-2 pages including abstract, chapter objectives and chapter outline, in Microsoft Word or Adobe PDF format. Submit to huseyin.abaci <at> adu.edu.tr and c.peoples <at> ulster.ac.uk with the subject title &ldquo;Sustainable Computing - Chapter Proposal" before 15 December 2014.</div>
<div><br></div>
<div>
<span data-mce-style="font-size: x-large;">eBook Editors</span><br>Editor-in-Chief <br> Huseyin Abaci Ph.D., Assistant Professor in the Department of Computer Engineering at Adnan Menderes University, Ayd&#305;n, Turkey<br> Email: huseyin.abaci <at> adu.edu.tr &nbsp;</div>
<div><br></div>
<div>Co-Editor<br> Cathryn Peoples Ph.D., Teaching Fellow in the Faculty of Computing and Engineering at the University of Ulster, Coleraine, Northern Ireland, United Kingdom. &nbsp;<br> Email: c.peoples <at> ulster.ac.uk</div>
<div><br></div>
<div>
<span data-mce-style="font-size: x-large; color: #000000;">Description of the eBook on "Sustainable Computing"</span><br> Improvements in the operation of Information and Communication Technology (ICT) allows and encourages the provision of more effective and efficient facilities and services, such as bandwidth-intensive Video-on-Demand (VoD), Voice over Internet Protocol (VoIP), cloud computing, online multi-player gaming, and file sharing. These activities, however, come at the cost of higher energy consumption. Global warming and energy dependence are major international concerns today, not just for our government agencies, but also for the utilities that provide critical infrastructures for our digital economy.</div>
<div><br></div>
<div>This eBook will focus on the achievement of energy efficient computing, investigating energy efficient technologies and techniques in data centres, clouds, and more general wired/wireless networks. Of specific interest are the development of efficient data collection methods, algorithms and optimisation techniques which achieve energy reduction.</div>
<div><br></div>
<div>
<span data-mce-style="font-size: x-large;">eBook Topics</span><br>Topics of interests include but are not limited to the following:</div>
<div><br></div>
<div>&bull;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Energy efficiency methods for sustainable ICT<br> &bull;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Energy efficiency in datacentres<br> &bull;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Energy efficiency in cloud networks<br> &bull;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Energy efficiency in wired metro-core networks<br> &bull;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Energy efficiency in wireless networks<br> &bull;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Energy efficiency in customer premises equipment <br> &bull;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Energy efficiency in network devices<br> &bull;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Energy efficiency in optical networks <br> &bull;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Energy efficient topology/protocols/applications<br> &bull;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Energy efficiency in integrated circuits and other computer components.<br> &bull;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Test bed setup to investigate proposed energy efficient network solutions.</div>
<div><br></div>
<div>
<span data-mce-style="font-size: x-large;">Chapter Submission Procedure</span><br> Authors are invited to submit a 1-2 page chapter proposal before 15 December 2015. Authors of accepted proposals will be notified by 30 January 2015, and will be sent guidelines for preparation of the full chapter (between 5,000 and 12,000 words in length). Full chapters should be submitted by 1 May 2015 and will be reviewed on a double-blind review basis. Contributors may also be requested to serve as reviewers for this eBook.</div>
<div><br></div>
<div>
<span data-mce-style="font-size: x-large;">Publisher</span><br> This book will be published by Bentham Science Publisher and is expected to be released before the end of December 2015.</div>
<div><br></div>
<div>
<span data-mce-style="font-size: x-large;">Inquiries</span><br> If you have any inquiries about this call, please contact us at huseyin.abaci <at> adu.edu.tr or c.peoples <at> ulster.ac.uk.</div>
</div></div></div></div></div></div></div></div>
Y. Richard Yang | 14 Nov 02:07 2014
Picon

ALTO YANG and topology discussions slides

Dear all,

We have spent some efforts on both applying YANG to ALTO and the ALTO topology extension. Quite some contents are made in the last few days, and hence the drafts are obsolete. Instead, please refer to the slides (https://datatracker.ietf.org/meeting/91/materials.html#wg-alto), which are more updated. We sure want to hear your feedback during the session today.

Cheers,

Richard
<div><div dir="ltr">Dear all,<div><br></div>
<div>We have spent some efforts on both applying YANG to ALTO and the ALTO topology extension. Quite some contents are made in the last few days, and hence the drafts are obsolete. Instead, please refer to the slides (<a href="https://datatracker.ietf.org/meeting/91/materials.html#wg-alto">https://datatracker.ietf.org/meeting/91/materials.html#wg-alto</a>), which are more updated. We sure want to hear your feedback during the session today.
</div>
<div><br></div>
<div>Cheers,</div>
<div><br></div>
<div>Richard</div>
</div></div>
Vijay K. Gurbani | 12 Nov 16:01 2014

Updated agenda, note taker and jabber scribe

Folks: The ALTO agenda has been updated.  Please take a look at it as
some slots have been moved around.

http://www.ietf.org/proceedings/91/agenda/agenda-91-alto

Also, if a couple of folks will like to volunteer to be note takers,
that will help.  A jabber scribe will be needed as well.  Please get in
touch with the co-chairs to express your interest in either of the
roles.  That will save some time.

Cheers,

- vijay
--

-- 
Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent
1960 Lucent Lane, Rm. 9C-533, Naperville, Illinois 60563 (USA)
Email: vkg <at> {bell-labs.com,acm.org} / vijay.gurbani <at> alcatel-lucent.com
Web: http://ect.bell-labs.com/who/vkg/  | Calendar: http://goo.gl/x3Ogq

RANDRIAMASY, SABINE (SABINE | 11 Nov 19:35 2014

ALTO Cost calendars in wireless access networks

Hi Uwe,

 

I see that your draft http://tools.ietf.org/id/draft-rauschenbach-alto-wireless-access-00.txt will be presented in the next ALTO WG session.

 

Given that your draft poses the need for a calendar in its following sections 3.2.1.  Cost calendar to extend battery life for background tasks and section 3.2.2.  Cost calendar to optimize application sessions, you may want to look at http://tools.ietf.org/id/draft-randriamasy-alto-cost-calendar-02.txt, that proposes ALTO cost calendars and will be presented during the ALTO WG session as well, as it would be interesting to see how this proposal may meet your expectations.

 

Best regards,

Sabine

 

<div>
<div class="WordSection1">
<p class="MsoNormal">Hi Uwe,<p></p></p>
<p class="MsoNormal"><p>&nbsp;</p></p>
<p class="MsoNormal">I see that your draft <a href="http://tools.ietf.org/id/draft-rauschenbach-alto-wireless-access-00.txt">
http://tools.ietf.org/id/draft-rauschenbach-alto-wireless-access-00.txt</a> will be presented in the next ALTO WG session.
<p></p></p>
<p class="MsoNormal"><p>&nbsp;</p></p>
<p class="MsoNormal">Given that your draft poses the need for a calendar in its following sections 3.2.1.&nbsp; Cost calendar to extend battery life for background tasks and section 3.2.2.&nbsp; Cost calendar to optimize application sessions, you may want to look at
<a href="http://tools.ietf.org/id/draft-randriamasy-alto-cost-calendar-02.txt">http://tools.ietf.org/id/draft-randriamasy-alto-cost-calendar-02.txt</a>, that proposes ALTO cost calendars and will be presented during the ALTO WG session as well, as it would
 be interesting to see how this proposal may meet your expectations. <p></p></p>
<p class="MsoNormal"><p>&nbsp;</p></p>
<p class="MsoNormal">Best regards,<p></p></p>
<p class="MsoNormal">Sabine<p></p></p>
<p class="MsoNormal"><p>&nbsp;</p></p>
</div>
</div>
Y. Richard Yang | 7 Nov 21:28 2014
Picon

ALTO topology design issues

Dear all,

As we are preparing for the slides on a potential ALTO topology extension (node-link graph), we have a few design choices that can benefit from some discussions in the WG list.

1. path vector vs flow

Starting from -03, the document introduced the concept of a path vector mode as a generic mechanism to provide topology/routing information. Upon writing the slides, however, we found that to handle multi-path routing (e.g., ECMP), we will need a simple flow routing concept, where path vector is a special case. Any comments on extending to this direction will be appreciated.

2. property graph as a node-graph foundation

Another design choice, when introducing node-link graph, is  
(1) adding network nodes in the network map, and hence we have a single place for all network nodes, and PID properties can provide properties for all such nodes; or
(2) separate PIDs (endpoint user groups) from network nodes. This may be conceptually cleaner. Then it implies two types of links, which will be captured by property graphs.

If you have any comments on this aspect, please share your opinions.

3. Subgraph selection API

How to provide a generic mechanism to allow an ALTO client to select a subgraph is still not clear--it will depend on the use cases. So far, the first selection service is the expander of a given set of src/dst PIDs: the expander is the union of path vectors (or flows, if we consider multi-path). If you have any opinions on this aspect, please let us know.

Cheers,

Richard

---------- Forwarded message ----------
From: <internet-drafts <at> ietf.org>
Date: Mon, Oct 27, 2014 at 7:41 PM
Subject: New Version Notification for draft-yang-alto-topology-05.txt
To: Greg Bernstein <gregb <at> grotto-networking.com>, Michael Scharf <michael.scharf <at> alcatel-lucent.com>, Wendy Roome <w.roome <at> alcatel-lucent.com>, Young Lee <leeyoung <at> huawei.com>, "Y. Richard Yang" <yry <at> cs.yale.edu>



A new version of I-D, draft-yang-alto-topology-05.txt
has been successfully submitted by Y. Richard Yang and posted to the
IETF repository.

Name:           draft-yang-alto-topology
Revision:       05
Title:          ALTO Topology Extensions
Document date:  2014-10-27
Group:          Individual Submission
Pages:          18
URL:            http://www.ietf.org/internet-drafts/draft-yang-alto-topology-05.txt
Status:         https://datatracker.ietf.org/doc/draft-yang-alto-topology/
Htmlized:       http://tools.ietf.org/html/draft-yang-alto-topology-05
Diff:           http://www.ietf.org/rfcdiff?url2=draft-yang-alto-topology-05

Abstract:
   The Application-Layer Traffic Optimization (ALTO) Service has defined
   network and cost maps to provide basic network information.  In this
   document, we discuss designs to provide abstracted graph
   representations of network topology.  We start with a basic
   application use case of multi-flow scheduling using ALTO.  We show
   that ALTO cost maps alone cannot provide sufficient information.  We
   then define one key, generic component to address the issues:
   introducing path vectors in cost maps.  We specify two approaches to
   complement path vectors and achieve a complete design: an approach
   using opaque network elements and another using a graph (node-link)
   representation.


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.

The IETF Secretariat
<div><div dir="ltr">Dear all,<div><br></div>
<div>As we are preparing for the slides on a potential ALTO topology extension (node-link graph), we have a few design choices that can benefit from some discussions in the WG list.</div>
<div><br></div>
<div>1. path vector vs flow</div>
<div><br></div>
<div>Starting from -03, the document introduced the concept of a path vector mode as a generic mechanism to provide topology/routing information. Upon writing the slides, however, we found that to handle multi-path routing (e.g., ECMP), we will need a simple flow routing concept, where path vector is a special case. Any comments on extending to this direction will be appreciated.</div>
<div><br></div>
<div>2. property graph as a node-graph foundation</div>
<div><br></div>
<div>Another design choice, when introducing node-link graph, is &nbsp;</div>
<div>(1) adding network nodes in the network map, and hence we have a single place for all network nodes, and PID properties can provide properties for all such nodes; or</div>
<div>(2) separate PIDs (endpoint user groups) from network nodes. This may be conceptually cleaner. Then it implies two types of links, which will be captured by property graphs.</div>
<div><br></div>
<div>If you have any comments on this aspect, please share your opinions.</div>
<div><br></div>
<div>3. Subgraph selection API</div>
<div><br></div>
<div>How to provide a generic mechanism to allow an ALTO client to select a subgraph is still not clear--it will depend on the use cases. So far, the first selection service is the expander of a given set of src/dst PIDs: the expander is the union of path vectors (or flows, if we consider multi-path). If you have any opinions on this aspect, please let us know.</div>
<div><br></div>
<div>Cheers,</div>
<div><br></div>
<div>Richard</div>
<div>
<br><div class="gmail_quote">---------- Forwarded message ----------<br>From:  <span dir="ltr">&lt;<a href="mailto:internet-drafts <at> ietf.org">internet-drafts <at> ietf.org</a>&gt;</span><br>Date: Mon, Oct 27, 2014 at 7:41 PM<br>Subject: New Version Notification for draft-yang-alto-topology-05.txt<br>To: Greg Bernstein &lt;<a href="mailto:gregb <at> grotto-networking.com">gregb <at> grotto-networking.com</a>&gt;, Michael Scharf &lt;<a href="mailto:michael.scharf <at> alcatel-lucent.com">michael.scharf <at> alcatel-lucent.com</a>&gt;, Wendy Roome &lt;<a href="mailto:w.roome <at> alcatel-lucent.com">w.roome <at> alcatel-lucent.com</a>&gt;, Young Lee &lt;<a href="mailto:leeyoung <at> huawei.com">leeyoung <at> huawei.com</a>&gt;, "Y. Richard Yang" &lt;<a href="mailto:yry <at> cs.yale.edu">yry <at> cs.yale.edu</a>&gt;<br><br><br><br>
A new version of I-D, draft-yang-alto-topology-05.txt<br>
has been successfully submitted by Y. Richard Yang and posted to the<br>
IETF repository.<br><br>
Name:&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;draft-yang-alto-topology<br>
Revision:&nbsp; &nbsp; &nbsp; &nbsp;05<br>
Title:&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; ALTO Topology Extensions<br>
Document date:&nbsp; 2014-10-27<br>
Group:&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Individual Submission<br>
Pages:&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 18<br>
URL:&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; <a href="http://www.ietf.org/internet-drafts/draft-yang-alto-topology-05.txt" target="_blank">http://www.ietf.org/internet-drafts/draft-yang-alto-topology-05.txt</a><br>
Status:&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;<a href="https://datatracker.ietf.org/doc/draft-yang-alto-topology/" target="_blank">https://datatracker.ietf.org/doc/draft-yang-alto-topology/</a><br>
Htmlized:&nbsp; &nbsp; &nbsp; &nbsp;<a href="http://tools.ietf.org/html/draft-yang-alto-topology-05" target="_blank">http://tools.ietf.org/html/draft-yang-alto-topology-05</a><br>
Diff:&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;<a href="http://www.ietf.org/rfcdiff?url2=draft-yang-alto-topology-05" target="_blank">http://www.ietf.org/rfcdiff?url2=draft-yang-alto-topology-05</a><br><br>
Abstract:<br>
&nbsp; &nbsp;The Application-Layer Traffic Optimization (ALTO) Service has defined<br>
&nbsp; &nbsp;network and cost maps to provide basic network information.&nbsp; In this<br>
&nbsp; &nbsp;document, we discuss designs to provide abstracted graph<br>
&nbsp; &nbsp;representations of network topology.&nbsp; We start with a basic<br>
&nbsp; &nbsp;application use case of multi-flow scheduling using ALTO.&nbsp; We show<br>
&nbsp; &nbsp;that ALTO cost maps alone cannot provide sufficient information.&nbsp; We<br>
&nbsp; &nbsp;then define one key, generic component to address the issues:<br>
&nbsp; &nbsp;introducing path vectors in cost maps.&nbsp; We specify two approaches to<br>
&nbsp; &nbsp;complement path vectors and achieve a complete design: an approach<br>
&nbsp; &nbsp;using opaque network elements and another using a graph (node-link)<br>
&nbsp; &nbsp;representation.<br><br><br>
Please note that it may take a couple of minutes from the time of submission<br>
until the htmlized version and diff are available at <a href="http://tools.ietf.org" target="_blank">tools.ietf.org</a>.<br><br>
The IETF Secretariat<br>
</div>
</div>
</div></div>
RANDRIAMASY, SABINE (SABINE | 28 Oct 18:03 2014

Updates on Multi-Cost ALTO

Hi all,

 

A new version of the Multi-Cost ALTO draft by Wendy Roome and myself  is available at

http://tools.ietf.org/id/draft-randriamasy-alto-multi-cost-09.txt

The revision relates to discussions in Toronto and before on the possibility to request Cost Values on a set C1 of Cost Types with  AND/OR constraints on a different set C2 of cost types.  

The draft  proposes a light way to do it:

-it introduces a member “testable cost-types” in the IRD capabilities of the Filtered Multi-Cost Map and Endpoint Multi-Cost Map

- it adapts the constraints syntax rules accordingly.

The draft provides related transaction examples and refers to previous work that dealt with requests on cost-types with AND-constraints on different cost-types, see draft-lee-alto-app-net-info-exchange.   

Feedback on this proposal is more than welcome,

Thanks,

 

Sabine and Wendy

 

 

<div>
<div class="WordSection1">
<p class="MsoNormal">Hi all,<p></p></p>
<p class="MsoNormal"><p>&nbsp;</p></p>
<p class="MsoNormal">A new version of the Multi-Cost ALTO draft by Wendy Roome and myself &nbsp;is available at
<p></p></p>
<p class="MsoNormal"><a href="http://tools.ietf.org/id/draft-randriamasy-alto-multi-cost-09.txt">http://tools.ietf.org/id/draft-randriamasy-alto-multi-cost-09.txt</a>
<p></p></p>
<p class="MsoNormal">The revision relates to discussions in Toronto and before on the possibility to request Cost Values on a set C1 of Cost Types with &nbsp;AND/OR constraints on a different set C2 of cost types. &nbsp;<p></p></p>
<p class="MsoNormal">The draft &nbsp;proposes a light way to do it: <p></p></p>
<p class="MsoNormal">-it introduces a member &ldquo;testable cost-types&rdquo; in the IRD capabilities of the Filtered Multi-Cost Map and Endpoint Multi-Cost Map<p></p></p>
<p class="MsoNormal">- it adapts the constraints syntax rules accordingly. <p></p></p>
<p class="MsoNormal">The draft provides related transaction examples and refers to previous work that dealt with requests on cost-types with AND-constraints on different cost-types, see
<a href="http://tools.ietf.org/html/draft-lee-alto-app-net-info-exchange">draft-lee-alto-app-net-info-exchange</a>. &nbsp;&nbsp;<p></p></p>
<table class="MsoNormalTable" border="0" cellpadding="0"><tr>
<td></td>
<td></td>
</tr></table>
<p class="MsoNormal">Feedback on this proposal is more than welcome,<p></p></p>
<p class="MsoNormal">Thanks,<p></p></p>
<p class="MsoNormal"><p>&nbsp;</p></p>
<p class="MsoNormal">Sabine and Wendy<p></p></p>
<p class="MsoNormal"><p>&nbsp;</p></p>
<p class="MsoNormal"><p>&nbsp;</p></p>
</div>
</div>
Y. Richard Yang | 27 Oct 17:38 2014
Picon

Fwd: New Version Notification for draft-shi-alto-yang-json-00.txt

Hi all,

Related with the previous email. This document looks at not only ALTO but other protocols that use JSON objects in message body. We look at if one may use YANG to specify it (note, only the message body). It turns out ALTO JSON objects cannot be generated from a YANG specification. The main issue, as already discussed in some previous email messages appeared in both ALTO/netmod, is key-value store. 

Any comments are appreciated, again!

Richard

---------- Forwarded message ----------
From: <internet-drafts <at> ietf.org>
Date: Mon, Oct 27, 2014 at 11:31 AM
Subject: New Version Notification for draft-shi-alto-yang-json-00.txt
To: "Y. Richard Yang" <yang.r.yang <at> gmail.com>, Xiao Shi <xiao.shi <at> yale.edu>



A new version of I-D, draft-shi-alto-yang-json-00.txt
has been successfully submitted by Xiao Shi and posted to the
IETF repository.

Name:           draft-shi-alto-yang-json
Revision:       00
Title:          Modeling JSON Messages Using YANG
Document date:  2014-10-27
Group:          Individual Submission
Pages:          23
URL:            http://www.ietf.org/internet-drafts/draft-shi-alto-yang-json-00.txt
Status:         https://datatracker.ietf.org/doc/draft-shi-alto-yang-json/
Htmlized:       http://tools.ietf.org/html/draft-shi-alto-yang-json-00


Abstract:
   JavaScript Object Notation (JSON) has been a popular choice as the
   message encoding for many network protocols.  Meanwhile, there are
   broad interests in the networking community to use the YANG data
   modeling language [RFC6020] to define data store and protocol
   messages, so that one can use YANG related tools such as the
   OpenDayLight Controller.  Although YANG itself is XML based, there
   have been efforts to model JSON content using YANG
   [draft-ietf-netmod-yang-json-01]

   This document explores the conditions under which the messages of a
   JSON based protocol can have a syntactically equivalent and hence
   interoperable YANG model.  In particular, this document shows that
   any JSON protocol message with stand-alone non-object JSON values,
   certain JSON arrays of elements of mixed types, or non-keyword keys
   in key-value pairs cannot have a syntactically equivalent YANG model.
   It also applies these conditions to the ALTO and CDNi protocol
   messages as examples.




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.

The IETF Secretariat




--
Richard
<div><div dir="ltr">
<span>Hi all,</span><div><br></div>
<div>Related with the previous email. This document looks at not only ALTO but other protocols that use JSON objects in message body. We look at if one may use YANG to specify it (note, only the message body). It turns out ALTO JSON objects cannot be generated from a YANG specification. The main issue, as already discussed in some previous email messages appeared in both ALTO/netmod, is key-value store.&nbsp;</div>
<div><br></div>
<div>Any comments are appreciated, again!</div>
<div><br></div>
<div>Richard</div>
<div><br></div>
<div class="gmail_quote">---------- Forwarded message ----------<br>From:  <span dir="ltr">&lt;<a href="mailto:internet-drafts <at> ietf.org">internet-drafts <at> ietf.org</a>&gt;</span><br>Date: Mon, Oct 27, 2014 at 11:31 AM<br>Subject: New Version Notification for draft-shi-alto-yang-json-00.txt<br>To: "Y. Richard Yang" &lt;<a href="mailto:yang.r.yang <at> gmail.com">yang.r.yang <at> gmail.com</a>&gt;, Xiao Shi &lt;<a href="mailto:xiao.shi <at> yale.edu">xiao.shi <at> yale.edu</a>&gt;<br><br><br><br>
A new version of I-D, draft-shi-alto-yang-json-00.txt<br>
has been successfully submitted by Xiao Shi and posted to the<br>
IETF repository.<br><br>
Name:&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;draft-shi-alto-yang-json<br>
Revision:&nbsp; &nbsp; &nbsp; &nbsp;00<br>
Title:&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Modeling JSON Messages Using YANG<br>
Document date:&nbsp; 2014-10-27<br>
Group:&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Individual Submission<br>
Pages:&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 23<br>
URL:&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; <a href="http://www.ietf.org/internet-drafts/draft-shi-alto-yang-json-00.txt" target="_blank">http://www.ietf.org/internet-drafts/draft-shi-alto-yang-json-00.txt</a><br>
Status:&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;<a href="https://datatracker.ietf.org/doc/draft-shi-alto-yang-json/" target="_blank">https://datatracker.ietf.org/doc/draft-shi-alto-yang-json/</a><br>
Htmlized:&nbsp; &nbsp; &nbsp; &nbsp;<a href="http://tools.ietf.org/html/draft-shi-alto-yang-json-00" target="_blank">http://tools.ietf.org/html/draft-shi-alto-yang-json-00</a><br><br><br>
Abstract:<br>
&nbsp; &nbsp;JavaScript Object Notation (JSON) has been a popular choice as the<br>
&nbsp; &nbsp;message encoding for many network protocols.&nbsp; Meanwhile, there are<br>
&nbsp; &nbsp;broad interests in the networking community to use the YANG data<br>
&nbsp; &nbsp;modeling language [RFC6020] to define data store and protocol<br>
&nbsp; &nbsp;messages, so that one can use YANG related tools such as the<br>
&nbsp; &nbsp;OpenDayLight Controller.&nbsp; Although YANG itself is XML based, there<br>
&nbsp; &nbsp;have been efforts to model JSON content using YANG<br>
&nbsp; &nbsp;[draft-ietf-netmod-yang-json-01]<br><br>
&nbsp; &nbsp;This document explores the conditions under which the messages of a<br>
&nbsp; &nbsp;JSON based protocol can have a syntactically equivalent and hence<br>
&nbsp; &nbsp;interoperable YANG model.&nbsp; In particular, this document shows that<br>
&nbsp; &nbsp;any JSON protocol message with stand-alone non-object JSON values,<br>
&nbsp; &nbsp;certain JSON arrays of elements of mixed types, or non-keyword keys<br>
&nbsp; &nbsp;in key-value pairs cannot have a syntactically equivalent YANG model.<br>
&nbsp; &nbsp;It also applies these conditions to the ALTO and CDNi protocol<br>
&nbsp; &nbsp;messages as examples.<br><br><br><br><br>
Please note that it may take a couple of minutes from the time of submission<br>
until the htmlized version and diff are available at <a href="http://tools.ietf.org" target="_blank">tools.ietf.org</a>.<br><br>
The IETF Secretariat<br><br>
</div>
<br><br clear="all"><div><br></div>-- <br>Richard
</div></div>
Y. Richard Yang | 27 Oct 17:32 2014
Picon

Fwd: New Version Notification for draft-shi-alto-yang-model-00.txt

Hi all,

In a setting of providing ALTO into ODL, we started to specify ALTO services defined in RFC7285 using YANG. It turns to be a quite interesting experience. Below is an draft specifying our approaches and first two models. The third model, in the context of considering NETCONF/RESTCONF, is slightly more complex and we will post in a next revision.

Any comments are appreciated!

Richard


---------- Forwarded message ----------
From: <internet-drafts <at> ietf.org>
Date: Mon, Oct 27, 2014 at 12:11 PM
Subject: New Version Notification for draft-shi-alto-yang-model-00.txt
To: Michael Scharf <michael.scharf <at> alcatel-lucent.com>, "Y. Richard Yang" <yang.r.yang <at> gmail.com>, Xiao Shi <xiao.shi <at> yale.edu>



A new version of I-D, draft-shi-alto-yang-model-00.txt
has been successfully submitted by Xiao Shi and posted to the
IETF repository.

Name:           draft-shi-alto-yang-model
Revision:       00
Title:          A YANG Data Model for Base ALTO Data and Services
Document date:  2014-10-27
Group:          Individual Submission
Pages:          66
URL:            http://www.ietf.org/internet-drafts/draft-shi-alto-yang-model-00.txt
Status:         https://datatracker.ietf.org/doc/draft-shi-alto-yang-model/
Htmlized:       http://tools.ietf.org/html/draft-shi-alto-yang-model-00


Abstract:
   The Application-Layer Traffic Optimization (ALTO) protocol [RFC7285]
   defines a set of network information services, including the network-
   map service, the cost-map service, the filtered map services, the
   endpoint property service, and the endpoint cost service.  A meta
   service, called the information resource directory (IRD) service,
   allows an ALTO server to provide ALTO clients with meta information
   (e.g., the access URI) about each resource and service it provides.
   [RFC7285] uses a RESTful design and encodes client request parameters
   and server responses using JSON.  One may consider that most of these
   services are based on data maintained at an ALTO server.  Hence, in
   this document, we explore how one may use the data modeling language
   YANG [RFC6020] to specify the services defined in [RFC7285].  We
   first define two YANG models for RPC specification and data instance
   description of of ALTO services.  We then discuss the "standard
   operations" defined in NETCONF/RESTCONF to evaluate potential
   integration.




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.

The IETF Secretariat




--
Richard
<div><div dir="ltr">Hi all,<div><br></div>
<div>In a setting of providing ALTO into ODL, we started to specify ALTO services defined in RFC7285 using YANG. It turns to be a quite interesting experience. Below is an draft specifying our approaches and first two models. The third model, in the context of considering NETCONF/RESTCONF, is slightly more complex and we will post in a next revision.</div>
<div><br></div>
<div>Any comments are appreciated!</div>
<div><br></div>
<div>Richard</div>
<div><br></div>
<div>
<br><div class="gmail_quote">---------- Forwarded message ----------<br>From:  <span dir="ltr">&lt;<a href="mailto:internet-drafts <at> ietf.org">internet-drafts <at> ietf.org</a>&gt;</span><br>Date: Mon, Oct 27, 2014 at 12:11 PM<br>Subject: New Version Notification for draft-shi-alto-yang-model-00.txt<br>To: Michael Scharf &lt;<a href="mailto:michael.scharf <at> alcatel-lucent.com">michael.scharf <at> alcatel-lucent.com</a>&gt;, "Y. Richard Yang" &lt;<a href="mailto:yang.r.yang <at> gmail.com">yang.r.yang <at> gmail.com</a>&gt;, Xiao Shi &lt;<a href="mailto:xiao.shi <at> yale.edu">xiao.shi <at> yale.edu</a>&gt;<br><br><br><br>
A new version of I-D, draft-shi-alto-yang-model-00.txt<br>
has been successfully submitted by Xiao Shi and posted to the<br>
IETF repository.<br><br>
Name:&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;draft-shi-alto-yang-model<br>
Revision:&nbsp; &nbsp; &nbsp; &nbsp;00<br>
Title:&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; A YANG Data Model for Base ALTO Data and Services<br>
Document date:&nbsp; 2014-10-27<br>
Group:&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Individual Submission<br>
Pages:&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 66<br>
URL:&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; <a href="http://www.ietf.org/internet-drafts/draft-shi-alto-yang-model-00.txt" target="_blank">http://www.ietf.org/internet-drafts/draft-shi-alto-yang-model-00.txt</a><br>
Status:&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;<a href="https://datatracker.ietf.org/doc/draft-shi-alto-yang-model/" target="_blank">https://datatracker.ietf.org/doc/draft-shi-alto-yang-model/</a><br>
Htmlized:&nbsp; &nbsp; &nbsp; &nbsp;<a href="http://tools.ietf.org/html/draft-shi-alto-yang-model-00" target="_blank">http://tools.ietf.org/html/draft-shi-alto-yang-model-00</a><br><br><br>
Abstract:<br>
&nbsp; &nbsp;The Application-Layer Traffic Optimization (ALTO) protocol [RFC7285]<br>
&nbsp; &nbsp;defines a set of network information services, including the network-<br>
&nbsp; &nbsp;map service, the cost-map service, the filtered map services, the<br>
&nbsp; &nbsp;endpoint property service, and the endpoint cost service.&nbsp; A meta<br>
&nbsp; &nbsp;service, called the information resource directory (IRD) service,<br>
&nbsp; &nbsp;allows an ALTO server to provide ALTO clients with meta information<br>
&nbsp; &nbsp;(e.g., the access URI) about each resource and service it provides.<br>
&nbsp; &nbsp;[RFC7285] uses a RESTful design and encodes client request parameters<br>
&nbsp; &nbsp;and server responses using JSON.&nbsp; One may consider that most of these<br>
&nbsp; &nbsp;services are based on data maintained at an ALTO server.&nbsp; Hence, in<br>
&nbsp; &nbsp;this document, we explore how one may use the data modeling language<br>
&nbsp; &nbsp;YANG [RFC6020] to specify the services defined in [RFC7285].&nbsp; We<br>
&nbsp; &nbsp;first define two YANG models for RPC specification and data instance<br>
&nbsp; &nbsp;description of of ALTO services.&nbsp; We then discuss the "standard<br>
&nbsp; &nbsp;operations" defined in NETCONF/RESTCONF to evaluate potential<br>
&nbsp; &nbsp;integration.<br><br><br><br><br>
Please note that it may take a couple of minutes from the time of submission<br>
until the htmlized version and diff are available at <a href="http://tools.ietf.org" target="_blank">tools.ietf.org</a>.<br><br>
The IETF Secretariat<br><br>
</div>
<br><br clear="all"><div><br></div>-- <br>Richard
</div>
</div></div>
Vijay K. Gurbani | 28 Oct 14:47 2014

Draft agenda posted

Folks: A draft agenda for ALTO meeting in HI has been posted.

Please see https://datatracker.ietf.org/meeting/91/agenda/alto/

Let the chairs know of any changes.

Meeting materials (slides) are due on November 9, 2014.  Please
convert your slides to PDF and email them to the chairs.

Thanks,

- vijay
--

-- 
Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent
1960 Lucent Lane, Rm. 9C-533, Naperville, Illinois 60563 (USA)
Email: vkg <at> {bell-labs.com,acm.org} / vijay.gurbani <at> alcatel-lucent.com
Web: http://ect.bell-labs.com/who/vkg/  | Calendar: http://goo.gl/x3Ogq


Gmane