Re: [alto] ALTO deployment considerations and map calculation draft

"Scharf, Michael (Michael)" <michael.scharf@alcatel-lucent.com> Wed, 28 October 2015 15:55 UTC

From: "Scharf, Michael (Michael)" <michael.scharf@alcatel-lucent.com>
To: "Gurbani, Vijay K (Vijay)" <vijay.gurbani@alcatel-lucent.com>, Hans Seidel <hseidel@benocs.com>
Thread-Topic: ALTO deployment considerations and map calculation draft
Thread-Index: AQHREZc/cG9U5vnlZUO0Kz7CvrxRdJ6BDNwg
Date: Wed, 28 Oct 2015 15:55:00 +0000
Message-ID: <655C07320163294895BBADA28372AF5D485323D9@FR712WXCHMBA15.zeu.alcatel-lucent.com>
References: <5630ECD6.9030101@bell-labs.com>
In-Reply-To: <5630ECD6.9030101@bell-labs.com>
Accept-Language: de-DE, en-US
Content-Language: de-DE
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/alto/x7RPEMTmwQS2V769Mqa3geTCC-I>
Cc: IETF ALTO <alto@ietf.org>
Subject: Re: [alto] ALTO deployment considerations and map calculation draft
Precedence: list

Well, draft-ietf-alto-deployments is not *my* draft - I just volunteered a long time ago to help the WG completing it.

I could see value in including draft-seidel-alto-map-calculation, even if we are post WGLC. Personally, I'd also be open to add another author/editor.

But I am interested in completing draft-ietf-alto-deployments soon, i.e., not further delaying it by several IETF meetings.

Michael


> -----Original Message-----
> From: Vijay K. Gurbani [mailto:vkg@bell-labs.com]
> Sent: Wednesday, October 28, 2015 4:42 PM
> To: Scharf, Michael (Michael); Hans Seidel
> Cc: IETF ALTO
> Subject: ALTO deployment considerations and map calculation draft
> 
> Michael, Hans: Pursuant to our virtual meeting yesterday, I have been
> thinking whether Hans' draft [1] has any input that can go into
> Michael's deployment draft [2]?
> 
> Can I kindly request the authors to inform the working group if there
> is any beneficial overlap from [1] that we may take into [2]?  I
> realize that [2] has been through WGLC so I am not expecting
> large-scale changes in it.  But if there is any deployment-related
> experience from [1] that can be put into [2], we should do our due
> diligence and make sure that we reflect that experience.
> 
> Thanks!
> 
> [1] http://datatracker.ietf.org/doc/draft-seidel-alto-map-calculation/
> [2] http://datatracker.ietf.org/doc/draft-ietf-alto-deployments/
> 
> - vijay
> --
> Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent
> 1960 Lucent Lane, Rm. 9C-533, Naperville, Illinois 60563 (USA)
> Email: vkg@{bell-labs.com,acm.org} / vijay.gurbani@alcatel-lucent.com
> Web: http://ect.bell-labs.com/who/vkg/  | Calendar: http://goo.gl/x3Ogq

[alto] ALTO deployment considerations and map cal… Vijay K. Gurbani
Re: [alto] ALTO deployment considerations and map… Scharf, Michael (Michael)
Re: [alto] ALTO deployment considerations and map… Y. Richard Yang
Re: [alto] ALTO deployment considerations and map… Vijay K. Gurbani
Re: [alto] ALTO deployment considerations and map… Vijay K. Gurbani
Re: [alto] ALTO deployment considerations and map… Vijay K. Gurbani