
From vkg@bell-labs.com  Thu Nov  1 05:44:17 2012
Return-Path: <vkg@bell-labs.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 48E8021F8A56 for <alto@ietfa.amsl.com>; Thu,  1 Nov 2012 05:44:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level: 
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id l0fGGG3XZ8Fx for <alto@ietfa.amsl.com>; Thu,  1 Nov 2012 05:44:16 -0700 (PDT)
Received: from ihemail1.lucent.com (ihemail1.lucent.com [135.245.0.33]) by ietfa.amsl.com (Postfix) with ESMTP id 9CD1721F8778 for <alto@ietf.org>; Thu,  1 Nov 2012 05:44:15 -0700 (PDT)
Received: from usnavsmail1.ndc.alcatel-lucent.com (usnavsmail1.ndc.alcatel-lucent.com [135.3.39.9]) by ihemail1.lucent.com (8.13.8/IER-o) with ESMTP id qA1CiEjf001031 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <alto@ietf.org>; Thu, 1 Nov 2012 07:44:15 -0500 (CDT)
Received: from umail.lucent.com (umail-ce2.ndc.lucent.com [135.3.40.63]) by usnavsmail1.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id qA1CiDdj017804 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <alto@ietf.org>; Thu, 1 Nov 2012 07:44:14 -0500
Received: from shoonya.ih.lucent.com (shoonya.ih.lucent.com [135.185.237.229]) by umail.lucent.com (8.13.8/TPES) with ESMTP id qA1CiDVo009576 for <alto@ietf.org>; Thu, 1 Nov 2012 07:44:13 -0500 (CDT)
Message-ID: <50926EE3.2070804@bell-labs.com>
Date: Thu, 01 Nov 2012 07:45:23 -0500
From: "Vijay K. Gurbani" <vkg@bell-labs.com>
Organization: Bell Laboratories, Alcatel-Lucent
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:13.0) Gecko/20120605 Thunderbird/13.0
MIME-Version: 1.0
To: alto <alto@ietf.org>
References: <20121101031318.29487.88368.idtracker@ietfa.amsl.com>
In-Reply-To: <20121101031318.29487.88368.idtracker@ietfa.amsl.com>
X-Forwarded-Message-Id: <20121101031318.29487.88368.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.33
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.9
Subject: [alto] Fwd: Help the NomCom: Community Feedback
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Thu, 01 Nov 2012 12:44:17 -0000

Folks: Please help provide community feedback to NomCom in evaluating
candidates for open positions.  Please see email below for more
instructions.

Thank you.


-------- Original Message --------
Subject: Help the NomCom: Community Feedback
Date: Wed, 31 Oct 2012 20:13:18 -0700
From: NomCom Chair <nomcom-chair@ietf.org>
To: Working Group Chairs <wgchairs@ietf.org>

The IETF Nominations Committee (NomCom) continues to seek input from
the IETF Community. The NomCom would greatly appreciate any help you
could provide in making members of your working group aware of ways in
which they can provide valuable feedback to the NomCom.

In order to ensure that your input is received in time to be useful, the
NomCom needs to receive community feedback on or before Sunday, November 4.

The final list of candidates (as per RFC 5680) that the NomCom is
considering for open positions can be found at:
https://www.ietf.org/group/nomcom/2012/input/

The NomCom will be holding office hours during IETF 85, Monday-
Thursday from 1:00pm to 3:00pm in Room 305. The NomCom welcomes
comments on specific individuals, as well as general feedback related to
any of the positions that NomCom is considering.

Note: A list of leadership positions that the NomCom is considering can be
found at: https://www.ietf.org/group/nomcom/2012/

If the NomCom office hours are inconvenient for you or if you cannot
attend IETF 85, the NomCom is happy to take community input via email
to nomcom12@ietf.org. Additionally, the NomCom is happy to arrange a
meeting outside of office hours, just send us email and we can set
something up.

Comments on specific candidates can also be provided to the NomCom
via the web feedback tool:
https://www.ietf.org/group/nomcom/2012/input/

Thank you for your help,
- Matt Lepinski
   nomcom-chair@ietf.org

- 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/




From vkg@bell-labs.com  Thu Nov  1 06:44:24 2012
Return-Path: <vkg@bell-labs.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 6C58021F8E71 for <alto@ietfa.amsl.com>; Thu,  1 Nov 2012 06:44:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -108.599
X-Spam-Level: 
X-Spam-Status: No, score=-108.599 tagged_above=-999 required=5 tests=[AWL=-2.000, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hhJGRu0NDffO for <alto@ietfa.amsl.com>; Thu,  1 Nov 2012 06:44:23 -0700 (PDT)
Received: from ihemail4.lucent.com (ihemail4.lucent.com [135.245.0.39]) by ietfa.amsl.com (Postfix) with ESMTP id AC0BC21F8E70 for <alto@ietf.org>; Thu,  1 Nov 2012 06:44:23 -0700 (PDT)
Received: from usnavsmail4.ndc.alcatel-lucent.com (usnavsmail4.ndc.alcatel-lucent.com [135.3.39.12]) by ihemail4.lucent.com (8.13.8/IER-o) with ESMTP id qA1DiJSP001148 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <alto@ietf.org>; Thu, 1 Nov 2012 08:44:19 -0500 (CDT)
Received: from umail.lucent.com (umail-ce2.ndc.lucent.com [135.3.40.63]) by usnavsmail4.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id qA1DiJ8U000907 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <alto@ietf.org>; Thu, 1 Nov 2012 08:44:19 -0500
Received: from shoonya.ih.lucent.com (shoonya.ih.lucent.com [135.185.237.229]) by umail.lucent.com (8.13.8/TPES) with ESMTP id qA1DiI31016369 for <alto@ietf.org>; Thu, 1 Nov 2012 08:44:18 -0500 (CDT)
Message-ID: <50927CF8.6090608@bell-labs.com>
Date: Thu, 01 Nov 2012 08:45:28 -0500
From: "Vijay K. Gurbani" <vkg@bell-labs.com>
Organization: Bell Laboratories, Alcatel-Lucent
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:13.0) Gecko/20120605 Thunderbird/13.0
MIME-Version: 1.0
To: alto <alto@ietf.org>
References: <CANTg3aDLgxhon1gXQfwJEDxH1oMeYfzAxPEApwMeWsK1g+SNbg@mail.gmail.com>
In-Reply-To: <CANTg3aDLgxhon1gXQfwJEDxH1oMeYfzAxPEApwMeWsK1g+SNbg@mail.gmail.com>
X-Forwarded-Message-Id: <CANTg3aDLgxhon1gXQfwJEDxH1oMeYfzAxPEApwMeWsK1g+SNbg@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.39
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.12
Subject: [alto] Fwd: Re: [85all] NomCom: Office Hours in Atlanta
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Thu, 01 Nov 2012 13:44:24 -0000

-------- Original Message --------
Subject: Re: [85all] NomCom: Office Hours in Atlanta
Date: Thu, 1 Nov 2012 08:22:48 -0400
From: Matthew Lepinski <mlepinski.ietf@gmail.com>
To: 85all@ietf.org

I apologize for a minor error in the message below.

In order to ensure that your input is useful to the NomCom, please
send us your feedback on or before Sunday, November 11.
(i.e., NOT November 4 as incorrectly indicated in the email below)

- Matt Lepinski
   nomcom-chair@ietf.org

On Wed, Oct 31, 2012 at 11:09 PM, Matthew Lepinski
<mlepinski.ietf@gmail.com> wrote:
> The IETF Nominations Committee (NomCom) continues to seek input from
> the IETF Community.
>
> The final list of candidates (as per RFC 5680) that the NomCom is
> considering for open positions can be found at:
> https://www.ietf.org/group/nomcom/2012/input/
>
> The NomCom will be holding office hours during IETF 85, Monday-
> Thursday from 1:00pm to 3:00pm in Room 305. The NomCom welcomes
> comments on specific individuals, as well as general feedback related to
> any of the positions that NomCom is considering.
>
> Note: A list of leadership positions that the NomCom is considering can be
> found at: https://www.ietf.org/group/nomcom/2012/
>
> If the NomCom office hours are inconvenient for you or if you cannot
> attend IETF 85, the NomCom is happy to take community input via email
> to nomcom12@ietf.org. Additionally, the NomCom is happy to arrange a
> meeting outside of office hours, just send us email and we can set
> something up.
>
> Comments on specific candidates can also be provided to the NomCom
> via the web feedback tool:
> https://www.ietf.org/group/nomcom/2012/input/
>
> In order to ensure that your input is received in time to be useful, please
> provide your input on or before Sunday, November 4.
>
> Thank you for your help,
> - Matt Lepinski
>   nomcom-chair@ietf.org
_______________________________________________
85all mailing list
85all@ietf.org
https://www.ietf.org/mailman/listinfo/85all

- 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/




From vkg@bell-labs.com  Mon Nov  5 09:29:54 2012
Return-Path: <vkg@bell-labs.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 1D41521F88C0 for <alto@ietfa.amsl.com>; Mon,  5 Nov 2012 09:29:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level: 
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TDH-V+kwxVBE for <alto@ietfa.amsl.com>; Mon,  5 Nov 2012 09:29:53 -0800 (PST)
Received: from ihemail1.lucent.com (ihemail1.lucent.com [135.245.0.33]) by ietfa.amsl.com (Postfix) with ESMTP id 6A00421F8503 for <alto@ietf.org>; Mon,  5 Nov 2012 09:29:53 -0800 (PST)
Received: from usnavsmail4.ndc.alcatel-lucent.com (usnavsmail4.ndc.alcatel-lucent.com [135.3.39.12]) by ihemail1.lucent.com (8.13.8/IER-o) with ESMTP id qA5HTqfo004927 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <alto@ietf.org>; Mon, 5 Nov 2012 11:29:52 -0600 (CST)
Received: from umail.lucent.com (umail-ce2.ndc.lucent.com [135.3.40.63]) by usnavsmail4.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id qA5HTpls000630 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <alto@ietf.org>; Mon, 5 Nov 2012 11:29:52 -0600
Received: from shoonya.ih.lucent.com (vkg.lra.lucent.com [135.244.3.42]) by umail.lucent.com (8.13.8/TPES) with ESMTP id qA5HTpQi018973 for <alto@ietf.org>; Mon, 5 Nov 2012 11:29:51 -0600 (CST)
Message-ID: <5097F7D7.1030409@bell-labs.com>
Date: Mon, 05 Nov 2012 11:31:03 -0600
From: "Vijay K. Gurbani" <vkg@bell-labs.com>
Organization: Bell Laboratories, Alcatel-Lucent
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:13.0) Gecko/20120605 Thunderbird/13.0
MIME-Version: 1.0
To: alto <alto@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.33
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.12
Subject: [alto] 2nd ALTO Interoperability reminder
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Mon, 05 Nov 2012 17:29:54 -0000

Folks: This is a reminder for the 2nd ALTO interoperability event
today evening.  The logistics are:

   Room: 211
   Date: Mon, Nov-5-2012
   Time: 20:00:00
   Internet-Draft:
       http://www.ietf.org/id/draft-gurbani-alto-interop-cases-02.txt

We will host a Skype session for remote participants.  Those of you
planning to participate remotely, please send Enrico and me your
Skype IDs.

Thanks,

- 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/


From vkg@bell-labs.com  Mon Nov  5 16:41:40 2012
Return-Path: <vkg@bell-labs.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 21E1721F8458 for <alto@ietfa.amsl.com>; Mon,  5 Nov 2012 16:41:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -108.599
X-Spam-Level: 
X-Spam-Status: No, score=-108.599 tagged_above=-999 required=5 tests=[AWL=-2.000, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6w3Cj1ou8LJ0 for <alto@ietfa.amsl.com>; Mon,  5 Nov 2012 16:41:36 -0800 (PST)
Received: from ihemail3.lucent.com (ihemail3.lucent.com [135.245.0.37]) by ietfa.amsl.com (Postfix) with ESMTP id 40CDF21F8514 for <alto@ietf.org>; Mon,  5 Nov 2012 16:41:36 -0800 (PST)
Received: from usnavsmail3.ndc.alcatel-lucent.com (usnavsmail3.ndc.alcatel-lucent.com [135.3.39.11]) by ihemail3.lucent.com (8.13.8/IER-o) with ESMTP id qA60fYFI028712 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <alto@ietf.org>; Mon, 5 Nov 2012 18:41:34 -0600 (CST)
Received: from umail.lucent.com (umail-ce2.ndc.lucent.com [135.3.40.63]) by usnavsmail3.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id qA60fXWU011462 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <alto@ietf.org>; Mon, 5 Nov 2012 18:41:34 -0600
Received: from shoonya.ih.lucent.com (vkg.lra.lucent.com [135.244.3.172]) by umail.lucent.com (8.13.8/TPES) with ESMTP id qA60fWrG006789 for <alto@ietf.org>; Mon, 5 Nov 2012 18:41:33 -0600 (CST)
Message-ID: <50985D05.1010102@bell-labs.com>
Date: Mon, 05 Nov 2012 18:42:45 -0600
From: "Vijay K. Gurbani" <vkg@bell-labs.com>
Organization: Bell Laboratories, Alcatel-Lucent
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:13.0) Gecko/20120605 Thunderbird/13.0
MIME-Version: 1.0
To: alto <alto@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.37
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.11
Subject: [alto] Interoperability pairings
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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, 06 Nov 2012 00:41:40 -0000

Folks: By my count, we have 4 servers and 2 clients that will be
part of the ALTO interoperability.

Assume that we have servers S1, S2, S3, S4 and clients C1 and C2, I
propose that we divide our time in 1/2 hour slots to ensure that all
of the pairings are tested within 2 hours (+/- 1/2 hour or so).

Thus we have the following pairings:

8:15-8:45        8:45-9:15        9:15-9:45        9:45-10:15
S1-C1            S3-C1            S1-C2            S3-C2
S2-C2            S4-C2            S2-C1            S4-C1

If anyone has an alternative idea to proceed, please let me and
Enrico know.

At the end of the interoperability tests, can each pair please report
the following to the chairs:

Total tests attempted:
Total tests passed successfully:

Thanks,

- 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/


From yang.r.yang@gmail.com  Mon Nov  5 20:29:46 2012
Return-Path: <yang.r.yang@gmail.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 3AC3711E80E0 for <alto@ietfa.amsl.com>; Mon,  5 Nov 2012 20:29:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.31
X-Spam-Level: 
X-Spam-Status: No, score=-1.31 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, SARE_HTML_USL_OBFU=1.666]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JDnrN9BoMuXs for <alto@ietfa.amsl.com>; Mon,  5 Nov 2012 20:29:45 -0800 (PST)
Received: from mail-ob0-f172.google.com (mail-ob0-f172.google.com [209.85.214.172]) by ietfa.amsl.com (Postfix) with ESMTP id 64B7F11E80DE for <alto@ietf.org>; Mon,  5 Nov 2012 20:29:45 -0800 (PST)
Received: by mail-ob0-f172.google.com with SMTP id v19so24006obq.31 for <alto@ietf.org>; Mon, 05 Nov 2012 20:29:45 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=FQD6PMHqFb685FjIGasigF0ijTekINClrycNmVm9bqE=; b=XHJURI86BCcfBuBaI7bJwh70Fv1uAFGiYMXAtUPmKnfJwDU3pPbGWmwJtS8OMsZEmk YNjS5MGhn3vD/0MKTDtxoe60Bsz/dQ/qGJsk3AzpC3qmsdCtHo0irWl4YZKbCGEhEZBz ytfiV59URK05k6XDxchd4IVm1S+68X703wKa4SDiB1sqK54Jip/4qXCIMiGj9lNRVTSf JTWT9T5VM97kEkKNrGAAgaUwXjrpTvdgAFQitavg88PiWETG47WM+hoEcjoXmkTcmrvo /F9hH+ltsFVhMT3SQsUNSjUaS9nO5d5aG10qvPNc+PKMMxtE6f3fK9GGlu2ZYAaNCMGy 8AnA==
MIME-Version: 1.0
Received: by 10.182.177.100 with SMTP id cp4mr9889059obc.71.1352176184978; Mon, 05 Nov 2012 20:29:44 -0800 (PST)
Sender: yang.r.yang@gmail.com
Received: by 10.76.155.162 with HTTP; Mon, 5 Nov 2012 20:29:44 -0800 (PST)
In-Reply-To: <50985D05.1010102@bell-labs.com>
References: <50985D05.1010102@bell-labs.com>
Date: Mon, 5 Nov 2012 23:29:44 -0500
X-Google-Sender-Auth: pN3O-ewXcVrHyHn1Ge3A6n8_8Tg
Message-ID: <CANUuoLqkwU1t73ExUOvtHQ1jwSD3UegM4MRWNKCuoUkUjoUdUA@mail.gmail.com>
From: "Y. Richard Yang" <yry@cs.yale.edu>
To: "Vijay K. Gurbani" <vkg@bell-labs.com>
Content-Type: multipart/alternative; boundary=e89a8f838d9f2dee4b04cdcc0d61
Cc: alto <alto@ietf.org>
Subject: Re: [alto] Interoperability pairings
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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, 06 Nov 2012 04:29:46 -0000

--e89a8f838d9f2dee4b04cdcc0d61
Content-Type: text/plain; charset=ISO-8859-1

Hi Vijay,

I think we know the issue of the extra numbers before and after the json
return: the server used chunked encoding:

HTTP/1.1 200 OK
Transfer-Encoding: chunked
Content-Type: application/alto-endpointprop+json
Date: Tue, 06 Nov 2012 04:33:56 GMT

82
{
"meta" : {},
"data" : {
"map-vtag" : "1352176329",
"map" : {
"ipv4:192.168.1.23" : {
"pid" : "mypid2"
}
}
}
}
0

A client supporting chunked encoding will remove those number and a client
(e.g., nc) does not will keep them. The examples in the current spec all
use content length. Do we want to say something here or not?

Richard


On Mon, Nov 5, 2012 at 7:42 PM, Vijay K. Gurbani <vkg@bell-labs.com> wrote:

> Folks: By my count, we have 4 servers and 2 clients that will be
> part of the ALTO interoperability.
>
> Assume that we have servers S1, S2, S3, S4 and clients C1 and C2, I
> propose that we divide our time in 1/2 hour slots to ensure that all
> of the pairings are tested within 2 hours (+/- 1/2 hour or so).
>
> Thus we have the following pairings:
>
> 8:15-8:45        8:45-9:15        9:15-9:45        9:45-10:15
> S1-C1            S3-C1            S1-C2            S3-C2
> S2-C2            S4-C2            S2-C1            S4-C1
>
> If anyone has an alternative idea to proceed, please let me and
> Enrico know.
>
> At the end of the interoperability tests, can each pair please report
> the following to the chairs:
>
> Total tests attempted:
> Total tests passed successfully:
>
> Thanks,
>
> - 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<vijay.gurbani@alcatel-lucent.com>
> Web:   http://ect.bell-labs.com/who/**vkg/<http://ect.bell-labs.com/who/vkg/>
>
> ______________________________**_________________
> alto mailing list
> alto@ietf.org
> https://www.ietf.org/mailman/**listinfo/alto<https://www.ietf.org/mailman/listinfo/alto>
>

--e89a8f838d9f2dee4b04cdcc0d61
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi Vijay,<div><br></div><div>I think we know the issue of the extra numbers=
 before and after the json return: the server used chunked encoding:</div><=
div><br><div>HTTP/1.1 200 OK</div><div>Transfer-Encoding: chunked</div><div=
>
Content-Type: application/alto-endpointprop+json</div><div>Date: Tue, 06 No=
v 2012 04:33:56 GMT</div><div><br></div><div>82</div><div>{</div><div><span=
 class=3D"Apple-tab-span" style=3D"white-space:pre">	</span>&quot;meta&quot=
; : {},</div>
<div><span class=3D"Apple-tab-span" style=3D"white-space:pre">	</span>&quot=
;data&quot; : {</div><div><span class=3D"Apple-tab-span" style=3D"white-spa=
ce:pre">		</span>&quot;map-vtag&quot; : &quot;1352176329&quot;,</div><div><=
span class=3D"Apple-tab-span" style=3D"white-space:pre">		</span>&quot;map&=
quot; : {</div>
<div><span class=3D"Apple-tab-span" style=3D"white-space:pre">			</span>&qu=
ot;ipv4:192.168.1.23&quot; : {</div><div><span class=3D"Apple-tab-span" sty=
le=3D"white-space:pre">				</span>&quot;pid&quot; : &quot;mypid2&quot;</div=
><div>
<span class=3D"Apple-tab-span" style=3D"white-space:pre">			</span>}</div><=
div><span class=3D"Apple-tab-span" style=3D"white-space:pre">		</span>}</di=
v><div><span class=3D"Apple-tab-span" style=3D"white-space:pre">	</span>}</=
div><div>
}</div><div>0</div><div><br></div><div>A client supporting chunked encoding=
 will remove those number and a client (e.g., nc) does not will keep them. =
The examples in the current spec all use content length. Do we want to say =
something here or not?</div>
<div><br></div><div>Richard</div><div><br></div><div><br></div><div class=
=3D"gmail_quote">On Mon, Nov 5, 2012 at 7:42 PM, Vijay K. Gurbani <span dir=
=3D"ltr">&lt;<a href=3D"mailto:vkg@bell-labs.com" target=3D"_blank">vkg@bel=
l-labs.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">Folks: By my count, we have 4 servers and 2 =
clients that will be<br>
part of the ALTO interoperability.<br>
<br>
Assume that we have servers S1, S2, S3, S4 and clients C1 and C2, I<br>
propose that we divide our time in 1/2 hour slots to ensure that all<br>
of the pairings are tested within 2 hours (+/- 1/2 hour or so).<br>
<br>
Thus we have the following pairings:<br>
<br>
8:15-8:45 =A0 =A0 =A0 =A08:45-9:15 =A0 =A0 =A0 =A09:15-9:45 =A0 =A0 =A0 =A0=
9:45-10:15<br>
S1-C1 =A0 =A0 =A0 =A0 =A0 =A0S3-C1 =A0 =A0 =A0 =A0 =A0 =A0S1-C2 =A0 =A0 =A0=
 =A0 =A0 =A0S3-C2<br>
S2-C2 =A0 =A0 =A0 =A0 =A0 =A0S4-C2 =A0 =A0 =A0 =A0 =A0 =A0S2-C1 =A0 =A0 =A0=
 =A0 =A0 =A0S4-C1<br>
<br>
If anyone has an alternative idea to proceed, please let me and<br>
Enrico know.<br>
<br>
At the end of the interoperability tests, can each pair please report<br>
the following to the chairs:<br>
<br>
Total tests attempted:<br>
Total tests passed successfully:<br>
<br>
Thanks,<br>
<br>
- vijay<span class=3D"HOEnZb"><font color=3D"#888888"><br>
-- <br>
Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent<br>
1960 Lucent Lane, Rm. 9C-533, Naperville, Illinois 60563 (USA)<br>
Email: vkg@{<a href=3D"http://bell-labs.com" target=3D"_blank">bell-labs.co=
m</a>,<a href=3D"http://acm.org" target=3D"_blank">acm.org</a>} / <a href=
=3D"mailto:vijay.gurbani@alcatel-lucent.com" target=3D"_blank">vijay.gurban=
i@alcatel-lucent.<u></u>com</a><br>

Web: =A0 <a href=3D"http://ect.bell-labs.com/who/vkg/" target=3D"_blank">ht=
tp://ect.bell-labs.com/who/<u></u>vkg/</a><br>
<br>
______________________________<u></u>_________________<br>
alto mailing list<br>
<a href=3D"mailto:alto@ietf.org" target=3D"_blank">alto@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/alto" target=3D"_blank">ht=
tps://www.ietf.org/mailman/<u></u>listinfo/alto</a><br>
</font></span></blockquote></div><br></div>

--e89a8f838d9f2dee4b04cdcc0d61--

From vkg@bell-labs.com  Tue Nov  6 07:15:56 2012
Return-Path: <vkg@bell-labs.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 2BC3821F8996 for <alto@ietfa.amsl.com>; Tue,  6 Nov 2012 07:15:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.599
X-Spam-Level: 
X-Spam-Status: No, score=-109.599 tagged_above=-999 required=5 tests=[AWL=1.000, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6tdOwYc2RguG for <alto@ietfa.amsl.com>; Tue,  6 Nov 2012 07:15:55 -0800 (PST)
Received: from ihemail1.lucent.com (ihemail1.lucent.com [135.245.0.33]) by ietfa.amsl.com (Postfix) with ESMTP id 731BA21F8837 for <alto@ietf.org>; Tue,  6 Nov 2012 07:15:55 -0800 (PST)
Received: from usnavsmail2.ndc.alcatel-lucent.com (usnavsmail2.ndc.alcatel-lucent.com [135.3.39.10]) by ihemail1.lucent.com (8.13.8/IER-o) with ESMTP id qA6FFrqe027501 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Tue, 6 Nov 2012 09:15:54 -0600 (CST)
Received: from umail.lucent.com (umail-ce2.ndc.lucent.com [135.3.40.63]) by usnavsmail2.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id qA6FFro5029227 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 6 Nov 2012 09:15:53 -0600
Received: from shoonya.ih.lucent.com ([135.244.41.173]) by umail.lucent.com (8.13.8/TPES) with ESMTP id qA6FFpWP016457; Tue, 6 Nov 2012 09:15:51 -0600 (CST)
Message-ID: <509929A9.3020509@bell-labs.com>
Date: Tue, 06 Nov 2012 09:15:53 -0600
From: "Vijay K. Gurbani" <vkg@bell-labs.com>
Organization: Bell Laboratories, Alcatel-Lucent
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:13.0) Gecko/20120605 Thunderbird/13.0
MIME-Version: 1.0
To: "Y. Richard Yang" <yry@cs.yale.edu>
References: <50985D05.1010102@bell-labs.com> <CANUuoLqkwU1t73ExUOvtHQ1jwSD3UegM4MRWNKCuoUkUjoUdUA@mail.gmail.com>
In-Reply-To: <CANUuoLqkwU1t73ExUOvtHQ1jwSD3UegM4MRWNKCuoUkUjoUdUA@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.33
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.10
Cc: alto <alto@ietf.org>
Subject: Re: [alto] Interoperability pairings
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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, 06 Nov 2012 15:15:56 -0000

On 11/05/2012 10:29 PM, Y. Richard Yang wrote:
> Hi Vijay,
>
> I think we know the issue of the extra numbers before and after the
> json return: the server used chunked encoding:
[...]
> A client supporting chunked encoding will remove those number and a
> client (e.g., nc) does not will keep them.

Richard: OK, that explains the numbers in nc output.

> The examples in the current spec all use content length. Do we want
> to say something here or not?

I am leaning to no primarily because rfc2616 makes it mandatory to
receive and decode the chunked transfer encoding.  Since nc is not
rfc2616 compliant, but we require ALTO clients to be (section 6.3 of
the ALTO protocol), I think we do not need to specify anything more.

Thanks,

- 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/



From richard.alimi@gmail.com  Tue Nov  6 08:53:46 2012
Return-Path: <richard.alimi@gmail.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 7BE1E21F859F for <alto@ietfa.amsl.com>; Tue,  6 Nov 2012 08:53:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.31
X-Spam-Level: 
X-Spam-Status: No, score=-1.31 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, SARE_HTML_USL_OBFU=1.666]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jrtFmO3ZjLIh for <alto@ietfa.amsl.com>; Tue,  6 Nov 2012 08:53:45 -0800 (PST)
Received: from mail-vc0-f172.google.com (mail-vc0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id 8C5A721F859A for <alto@ietf.org>; Tue,  6 Nov 2012 08:53:45 -0800 (PST)
Received: by mail-vc0-f172.google.com with SMTP id fl11so650370vcb.31 for <alto@ietf.org>; Tue, 06 Nov 2012 08:53:45 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type; bh=VheL0B0yCOk4kUQnKgNPre4Ow+C0QBYYDHolXA30X5A=; b=LR3TwpfWvJlOcyt3Pe9NvSORgbHOCE7dA8TyhGyHajhuemOireJxjg7VfgX60XlrOx xAhXxTDJMwudyQsNs48tjPtyLBgNEPkybaCnTqF4IKhj6Y4wD3C7lhmJlBw0xx8UtIol tIDLYErDdobTPQ4PUL8yZ7ZyrfvwQWJMSTUMLjaB/Zm2QOLroIohCuEtdIalsubuRFFw NbczqG5jHEgrCtMr1pw2V69DnJGh5+QNPFCKCxfvv6/9s3/0NE5ukW1pw+2Ml0q5hA1A Xrd0tcJgD+FNRhBZgnvtk8hqa1HiO1xMdNYCqcq8C32PiCPMYZfobmKxYVSivxcAzGre RdPg==
Received: by 10.52.27.106 with SMTP id s10mr1336100vdg.12.1352220825050; Tue, 06 Nov 2012 08:53:45 -0800 (PST)
MIME-Version: 1.0
Sender: richard.alimi@gmail.com
Received: by 10.58.198.44 with HTTP; Tue, 6 Nov 2012 08:53:24 -0800 (PST)
In-Reply-To: <509929A9.3020509@bell-labs.com>
References: <50985D05.1010102@bell-labs.com> <CANUuoLqkwU1t73ExUOvtHQ1jwSD3UegM4MRWNKCuoUkUjoUdUA@mail.gmail.com> <509929A9.3020509@bell-labs.com>
From: Richard Alimi <rich@velvetsea.net>
Date: Tue, 6 Nov 2012 08:53:24 -0800
X-Google-Sender-Auth: VYEvswEMpmdrf-si97amli41lOA
Message-ID: <CA+cvDaZKRTHqxGem3woEuo5wzQf1sJD5QNks8TtM5Hpwf3jsyg@mail.gmail.com>
To: "Vijay K. Gurbani" <vkg@bell-labs.com>
Content-Type: multipart/alternative; boundary=20cf307cfe6eef5f7d04cdd6716a
Cc: alto <alto@ietf.org>
Subject: Re: [alto] Interoperability pairings
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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, 06 Nov 2012 16:53:46 -0000

--20cf307cfe6eef5f7d04cdd6716a
Content-Type: text/plain; charset=ISO-8859-1

On Tue, Nov 6, 2012 at 7:15 AM, Vijay K. Gurbani <vkg@bell-labs.com> wrote:

> On 11/05/2012 10:29 PM, Y. Richard Yang wrote:
>
>> Hi Vijay,
>>
>> I think we know the issue of the extra numbers before and after the
>> json return: the server used chunked encoding:
>>
> [...]
>
>  A client supporting chunked encoding will remove those number and a
>> client (e.g., nc) does not will keep them.
>>
>
> Richard: OK, that explains the numbers in nc output.
>
>
>  The examples in the current spec all use content length. Do we want
>> to say something here or not?
>>
>
> I am leaning to no primarily because rfc2616 makes it mandatory to
> receive and decode the chunked transfer encoding.  Since nc is not
> rfc2616 compliant, but we require ALTO clients to be (section 6.3 of
> the ALTO protocol), I think we do not need to specify anything more.
>
>
FWIW, I believe in an earlier version of the draft we were more explicit
and specified that clients must support chunked encoding.  The guidance we
received at that point was to not reiterate details from the rfc2616.

Rich


>
> Thanks,
>
> - 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<vijay.gurbani@alcatel-lucent.com>
> Web:   http://ect.bell-labs.com/who/**vkg/<http://ect.bell-labs.com/who/vkg/>
>
>
> ______________________________**_________________
> alto mailing list
> alto@ietf.org
> https://www.ietf.org/mailman/**listinfo/alto<https://www.ietf.org/mailman/listinfo/alto>
>

--20cf307cfe6eef5f7d04cdd6716a
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<br><div class=3D"gmail_extra"><div class=3D"gmail_quote">On Tue, Nov 6, 20=
12 at 7:15 AM, Vijay K. Gurbani <span dir=3D"ltr">&lt;<a href=3D"mailto:vkg=
@bell-labs.com" target=3D"_blank">vkg@bell-labs.com</a>&gt;</span> wrote:<b=
r><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:=
1px #ccc solid;padding-left:1ex">

<div class=3D"im">On 11/05/2012 10:29 PM, Y. Richard Yang wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
Hi Vijay,<br>
<br>
I think we know the issue of the extra numbers before and after the<br>
json return: the server used chunked encoding:<br>
</blockquote></div>
[...]<div class=3D"im"><br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
A client supporting chunked encoding will remove those number and a<br>
client (e.g., nc) does not will keep them.<br>
</blockquote>
<br></div>
Richard: OK, that explains the numbers in nc output.<div class=3D"im"><br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
The examples in the current spec all use content length. Do we want<br>
to say something here or not?<br>
</blockquote>
<br></div>
I am leaning to no primarily because rfc2616 makes it mandatory to<br>
receive and decode the chunked transfer encoding. =A0Since nc is not<br>
rfc2616 compliant, but we require ALTO clients to be (section 6.3 of<br>
the ALTO protocol), I think we do not need to specify anything more.<div cl=
ass=3D"HOEnZb"><div class=3D"h5"><br></div></div></blockquote><div><br></di=
v><div>FWIW, I believe in an earlier version of the draft we were more expl=
icit and specified that clients must support chunked encoding. =A0The guida=
nce we received at that point was to not reiterate details from the rfc2616=
.</div>

<div><br></div><div>Rich</div><div>=A0</div><blockquote class=3D"gmail_quot=
e" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">=
<div class=3D"HOEnZb"><div class=3D"h5">
<br>
Thanks,<br>
<br>
- vijay<br>
-- <br>
Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent<br>
1960 Lucent Lane, Rm. 9C-533, Naperville, Illinois 60563 (USA)<br>
Email: vkg@{<a href=3D"http://bell-labs.com" target=3D"_blank">bell-labs.co=
m</a>,<a href=3D"http://acm.org" target=3D"_blank">acm.org</a>} / <a href=
=3D"mailto:vijay.gurbani@alcatel-lucent.com" target=3D"_blank">vijay.gurban=
i@alcatel-lucent.<u></u>com</a><br>


Web: =A0 <a href=3D"http://ect.bell-labs.com/who/vkg/" target=3D"_blank">ht=
tp://ect.bell-labs.com/who/<u></u>vkg/</a><br>
<br>
<br>
______________________________<u></u>_________________<br>
alto mailing list<br>
<a href=3D"mailto:alto@ietf.org" target=3D"_blank">alto@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/alto" target=3D"_blank">ht=
tps://www.ietf.org/mailman/<u></u>listinfo/alto</a><br>
</div></div></blockquote></div><br></div>

--20cf307cfe6eef5f7d04cdd6716a--

From yang.r.yang@gmail.com  Tue Nov  6 09:46:50 2012
Return-Path: <yang.r.yang@gmail.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 EF52421F87F2 for <alto@ietfa.amsl.com>; Tue,  6 Nov 2012 09:46:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.31
X-Spam-Level: 
X-Spam-Status: No, score=-1.31 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, SARE_HTML_USL_OBFU=1.666]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 56eLqcJqcKw0 for <alto@ietfa.amsl.com>; Tue,  6 Nov 2012 09:46:44 -0800 (PST)
Received: from mail-ob0-f172.google.com (mail-ob0-f172.google.com [209.85.214.172]) by ietfa.amsl.com (Postfix) with ESMTP id 8722221F893C for <alto@ietf.org>; Tue,  6 Nov 2012 09:46:43 -0800 (PST)
Received: by mail-ob0-f172.google.com with SMTP id v19so772023obq.31 for <alto@ietf.org>; Tue, 06 Nov 2012 09:46:43 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=8KgFGZcVo/QnyIamLm0P4jufX8WWHbMAqrjS/e59aUQ=; b=sqs7WYeHNuCwXjOdi/TUOPmbHY40oqFYrxDgylZi3aQFKZedDmHzOVPNAFU68s6MLH za3oRbV1HDIkjoUk5Z0OkvQigQKb3OCjc7/NhQ3YdFfcofCwqYDmRalIId8sk4mgFLUO k+Wvj+Ae16Pmmg0rOPFjRZ90Fk5clicD0oncvo91RWiKPL/NPVMmJgaBDJWN1D+yQ/IM VUvcCNp/r1ywXGQE9rget2YeK3+aFvGwRrbNLfLiNAArnpY3r7GylWI63CbrFGZvXQNg 7OqK7QcxdQ/B9ZieVXjIu3dY+Th0ECX9f2r6YOLchBdmIYxsGEPoCS/2ZiC/zNvZ54oW saig==
MIME-Version: 1.0
Received: by 10.182.177.100 with SMTP id cp4mr1479037obc.71.1352224002998; Tue, 06 Nov 2012 09:46:42 -0800 (PST)
Sender: yang.r.yang@gmail.com
Received: by 10.76.155.162 with HTTP; Tue, 6 Nov 2012 09:46:42 -0800 (PST)
In-Reply-To: <CA+cvDaZKRTHqxGem3woEuo5wzQf1sJD5QNks8TtM5Hpwf3jsyg@mail.gmail.com>
References: <50985D05.1010102@bell-labs.com> <CANUuoLqkwU1t73ExUOvtHQ1jwSD3UegM4MRWNKCuoUkUjoUdUA@mail.gmail.com> <509929A9.3020509@bell-labs.com> <CA+cvDaZKRTHqxGem3woEuo5wzQf1sJD5QNks8TtM5Hpwf3jsyg@mail.gmail.com>
Date: Tue, 6 Nov 2012 12:46:42 -0500
X-Google-Sender-Auth: 3d3_gSovHmVGG9j-jWi1UgckMDs
Message-ID: <CANUuoLoONwM+O7pes9pfTqfYute_VAm+boTx8KeS2EfuXt2cWw@mail.gmail.com>
From: "Y. Richard Yang" <yry@cs.yale.edu>
To: Richard Alimi <rich@velvetsea.net>
Content-Type: multipart/alternative; boundary=e89a8f838d9f5b008704cdd72f61
Cc: alto <alto@ietf.org>
Subject: Re: [alto] Interoperability pairings
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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, 06 Nov 2012 17:46:50 -0000

--e89a8f838d9f5b008704cdd72f61
Content-Type: text/plain; charset=ISO-8859-1

Hi Rich, Vijay,

No action makes sense to me. From this experience, I may suggest that we
add a suggestive sentence about
potential issues of not handling chunked encoding, just for the benefit of
readers. What do you know?

Richard

On Tue, Nov 6, 2012 at 11:53 AM, Richard Alimi <rich@velvetsea.net> wrote:

>
> On Tue, Nov 6, 2012 at 7:15 AM, Vijay K. Gurbani <vkg@bell-labs.com>wrote:
>
>> On 11/05/2012 10:29 PM, Y. Richard Yang wrote:
>>
>>> Hi Vijay,
>>>
>>> I think we know the issue of the extra numbers before and after the
>>> json return: the server used chunked encoding:
>>>
>> [...]
>>
>>  A client supporting chunked encoding will remove those number and a
>>> client (e.g., nc) does not will keep them.
>>>
>>
>> Richard: OK, that explains the numbers in nc output.
>>
>>
>>  The examples in the current spec all use content length. Do we want
>>> to say something here or not?
>>>
>>
>> I am leaning to no primarily because rfc2616 makes it mandatory to
>> receive and decode the chunked transfer encoding.  Since nc is not
>> rfc2616 compliant, but we require ALTO clients to be (section 6.3 of
>> the ALTO protocol), I think we do not need to specify anything more.
>>
>>
> FWIW, I believe in an earlier version of the draft we were more explicit
> and specified that clients must support chunked encoding.  The guidance we
> received at that point was to not reiterate details from the rfc2616.
>
> Rich
>
>
>>
>> Thanks,
>>
>> - 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<vijay.gurbani@alcatel-lucent.com>
>> Web:   http://ect.bell-labs.com/who/**vkg/<http://ect.bell-labs.com/who/vkg/>
>>
>>
>> ______________________________**_________________
>> alto mailing list
>> alto@ietf.org
>> https://www.ietf.org/mailman/**listinfo/alto<https://www.ietf.org/mailman/listinfo/alto>
>>
>
>

--e89a8f838d9f5b008704cdd72f61
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi Rich, Vijay,<div><br></div><div>No action makes sense to me. From this e=
xperience, I may suggest that we add a suggestive sentence about=A0</div><d=
iv>potential issues of not handling chunked encoding, just for the benefit =
of readers. What do you know?</div>
<div><br></div><div>Richard<br><br><div class=3D"gmail_quote">On Tue, Nov 6=
, 2012 at 11:53 AM, Richard Alimi <span dir=3D"ltr">&lt;<a href=3D"mailto:r=
ich@velvetsea.net" target=3D"_blank">rich@velvetsea.net</a>&gt;</span> wrot=
e:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><br><div class=3D"gmail_extra"><div class=3D=
"gmail_quote"><div class=3D"im">On Tue, Nov 6, 2012 at 7:15 AM, Vijay K. Gu=
rbani <span dir=3D"ltr">&lt;<a href=3D"mailto:vkg@bell-labs.com" target=3D"=
_blank">vkg@bell-labs.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">

<div>On 11/05/2012 10:29 PM, Y. Richard Yang wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
Hi Vijay,<br>
<br>
I think we know the issue of the extra numbers before and after the<br>
json return: the server used chunked encoding:<br>
</blockquote></div>
[...]<div><br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
A client supporting chunked encoding will remove those number and a<br>
client (e.g., nc) does not will keep them.<br>
</blockquote>
<br></div>
Richard: OK, that explains the numbers in nc output.<div><br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
The examples in the current spec all use content length. Do we want<br>
to say something here or not?<br>
</blockquote>
<br></div>
I am leaning to no primarily because rfc2616 makes it mandatory to<br>
receive and decode the chunked transfer encoding. =A0Since nc is not<br>
rfc2616 compliant, but we require ALTO clients to be (section 6.3 of<br>
the ALTO protocol), I think we do not need to specify anything more.<div><d=
iv><br></div></div></blockquote><div><br></div></div><div>FWIW, I believe i=
n an earlier version of the draft we were more explicit and specified that =
clients must support chunked encoding. =A0The guidance we received at that =
point was to not reiterate details from the rfc2616.</div>


<div><br></div><div>Rich</div><div>=A0</div><blockquote class=3D"gmail_quot=
e" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">=
<div><div><div class=3D"im">
<br>
Thanks,<br>
<br>
- vijay<br>
-- <br>
Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent<br>
1960 Lucent Lane, Rm. 9C-533, Naperville, Illinois 60563 (USA)<br>
Email: vkg@{<a href=3D"http://bell-labs.com" target=3D"_blank">bell-labs.co=
m</a>,<a href=3D"http://acm.org" target=3D"_blank">acm.org</a>} / <a href=
=3D"mailto:vijay.gurbani@alcatel-lucent.com" target=3D"_blank">vijay.gurban=
i@alcatel-lucent.<u></u>com</a><br>



Web: =A0 <a href=3D"http://ect.bell-labs.com/who/vkg/" target=3D"_blank">ht=
tp://ect.bell-labs.com/who/<u></u>vkg/</a><br>
<br>
<br></div><div class=3D"im">
______________________________<u></u>_________________<br>
alto mailing list<br>
<a href=3D"mailto:alto@ietf.org" target=3D"_blank">alto@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/alto" target=3D"_blank">ht=
tps://www.ietf.org/mailman/<u></u>listinfo/alto</a><br>
</div></div></div></blockquote></div><br></div>
</blockquote></div><br></div>

--e89a8f838d9f5b008704cdd72f61--

From junchang.wang@yale.edu  Tue Nov  6 11:11:51 2012
Return-Path: <junchang.wang@yale.edu>
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 CCDF621F84E0 for <alto@ietfa.amsl.com>; Tue,  6 Nov 2012 11:11:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.31
X-Spam-Level: 
X-Spam-Status: No, score=-1.31 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, SARE_HTML_USL_OBFU=1.666]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AwxvQTrClCDZ for <alto@ietfa.amsl.com>; Tue,  6 Nov 2012 11:11:51 -0800 (PST)
Received: from mail-wi0-f178.google.com (mail-wi0-f178.google.com [209.85.212.178]) by ietfa.amsl.com (Postfix) with ESMTP id 944D421F8626 for <alto@ietf.org>; Tue,  6 Nov 2012 11:11:49 -0800 (PST)
Received: by mail-wi0-f178.google.com with SMTP id hr7so657343wib.13 for <alto@ietf.org>; Tue, 06 Nov 2012 11:11:49 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yale.edu; s=googleprd; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=B3ivVrcIcsY8uvcKcZvDkSygWH/yVMgZBE+dW8DlHA0=; b=KkL49UGTDqAaoN92RiU/buQjYliZ5gvluisO1c21T6fUITRqRKdxXyomtY/mSXbSJB dBtyn4mbJkgg3P2t1abggoJowJoAZRJyxRM4rMpFyJVsZBusWprB7TEWVsywywSCSaBP MUczBuofC0nVGvVZgeK+2tMioUGFBTouQfURM=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:x-gm-message-state; bh=B3ivVrcIcsY8uvcKcZvDkSygWH/yVMgZBE+dW8DlHA0=; b=OKqtHfF1fF/T6UHqtxWjvX0U5+7yPOBo9LzjnLAXQxfs/Apzc+EbwV70QCeL3fGE4p deJzA6DFBv9gbjfDJ3cECAffZyxgcpQOdqMTu5NE92y20iwC/Zepshrs4CJjrsReGKLI MdZ4qwUEmt8JLffHHyr5hYqYO2pUsD21Ldcf8hEFXVBDswNOMZiR1Ed8FMzkLG5g0fsG RgheMIw2KUe3Fv4I79eMQlkSXX9fSv/8Syy68Xo1tGREkxEZsOQBly6gu4NvmAhDkToO ruFFuBL5N/abALWSTc29biye0u8nHaig/ppIi17wQlOveMHmZ9bqex4xL19+qHA0Ouk/ 0sgA==
MIME-Version: 1.0
Received: by 10.216.139.137 with SMTP id c9mr955652wej.54.1352229108678; Tue, 06 Nov 2012 11:11:48 -0800 (PST)
Received: by 10.194.104.3 with HTTP; Tue, 6 Nov 2012 11:11:48 -0800 (PST)
In-Reply-To: <CANUuoLoONwM+O7pes9pfTqfYute_VAm+boTx8KeS2EfuXt2cWw@mail.gmail.com>
References: <50985D05.1010102@bell-labs.com> <CANUuoLqkwU1t73ExUOvtHQ1jwSD3UegM4MRWNKCuoUkUjoUdUA@mail.gmail.com> <509929A9.3020509@bell-labs.com> <CA+cvDaZKRTHqxGem3woEuo5wzQf1sJD5QNks8TtM5Hpwf3jsyg@mail.gmail.com> <CANUuoLoONwM+O7pes9pfTqfYute_VAm+boTx8KeS2EfuXt2cWw@mail.gmail.com>
Date: Tue, 6 Nov 2012 14:11:48 -0500
Message-ID: <CAErQho5WSAvie8cDg+Eur=dP+TU0_mJ71Pv=VtoraiCHnsRFWA@mail.gmail.com>
From: "Junchang(Jason) Wang" <junchang.wang@yale.edu>
To: "Y. Richard Yang" <yry@cs.yale.edu>, Richard Alimi <rich@velvetsea.net>, alto <alto@ietf.org>, "Vijay K. Gurbani" <vkg@bell-labs.com>
Content-Type: multipart/alternative; boundary=001636c5bd89ad802804cdd85f2c
X-Gm-Message-State: ALoCoQkdub40/uSTz3NLwXZthT7Z29VC7x0rnBQkwXYk5XzI5UEX+eFvJydKXEObl+RUYe1Et/5m
Subject: Re: [alto] Interoperability pairings
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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, 06 Nov 2012 19:11:51 -0000

--001636c5bd89ad802804cdd85f2c
Content-Type: text/plain; charset=ISO-8859-1

Dear all,

Or adding a single sentence about potential issues of clients which aren't
rfc2616 compliant in Section 6.3 would benefit readers a lot.

Thanks.

--Jason

On Tue, Nov 6, 2012 at 12:46 PM, Y. Richard Yang <yry@cs.yale.edu> wrote:

> Hi Rich, Vijay,
>
> No action makes sense to me. From this experience, I may suggest that we
> add a suggestive sentence about
> potential issues of not handling chunked encoding, just for the benefit of
> readers. What do you know?
>
> Richard
>
>
> On Tue, Nov 6, 2012 at 11:53 AM, Richard Alimi <rich@velvetsea.net> wrote:
>
>>
>> On Tue, Nov 6, 2012 at 7:15 AM, Vijay K. Gurbani <vkg@bell-labs.com>wrote:
>>
>>> On 11/05/2012 10:29 PM, Y. Richard Yang wrote:
>>>
>>>> Hi Vijay,
>>>>
>>>> I think we know the issue of the extra numbers before and after the
>>>> json return: the server used chunked encoding:
>>>>
>>> [...]
>>>
>>>  A client supporting chunked encoding will remove those number and a
>>>> client (e.g., nc) does not will keep them.
>>>>
>>>
>>> Richard: OK, that explains the numbers in nc output.
>>>
>>>
>>>  The examples in the current spec all use content length. Do we want
>>>> to say something here or not?
>>>>
>>>
>>> I am leaning to no primarily because rfc2616 makes it mandatory to
>>> receive and decode the chunked transfer encoding.  Since nc is not
>>> rfc2616 compliant, but we require ALTO clients to be (section 6.3 of
>>> the ALTO protocol), I think we do not need to specify anything more.
>>>
>>>
>> FWIW, I believe in an earlier version of the draft we were more explicit
>> and specified that clients must support chunked encoding.  The guidance we
>> received at that point was to not reiterate details from the rfc2616.
>>
>> Rich
>>
>>
>>>
>>> Thanks,
>>>
>>> - 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<vijay.gurbani@alcatel-lucent.com>
>>> Web:   http://ect.bell-labs.com/who/**vkg/<http://ect.bell-labs.com/who/vkg/>
>>>
>>>
>>> ______________________________**_________________
>>> alto mailing list
>>> alto@ietf.org
>>> https://www.ietf.org/mailman/**listinfo/alto<https://www.ietf.org/mailman/listinfo/alto>
>>>
>>
>>
>
> _______________________________________________
> alto mailing list
> alto@ietf.org
> https://www.ietf.org/mailman/listinfo/alto
>
>

--001636c5bd89ad802804cdd85f2c
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Dear all,<div><br></div><div>Or adding a single sentence about potential is=
sues of clients which aren&#39;t rfc2616 compliant in Section 6.3 would ben=
efit readers a lot.</div><div><br></div><div>Thanks.</div><div><br></div>
<div>--Jason<br><br><div class=3D"gmail_quote">On Tue, Nov 6, 2012 at 12:46=
 PM, Y. Richard Yang <span dir=3D"ltr">&lt;<a href=3D"mailto:yry@cs.yale.ed=
u" target=3D"_blank">yry@cs.yale.edu</a>&gt;</span> wrote:<br><blockquote c=
lass=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;=
padding-left:1ex">
Hi Rich, Vijay,<div><br></div><div>No action makes sense to me. From this e=
xperience, I may suggest that we add a suggestive sentence about=A0</div><d=
iv>potential issues of not handling chunked encoding, just for the benefit =
of readers. What do you know?</div>
<span class=3D"HOEnZb"><font color=3D"#888888">
<div><br></div></font></span><div><span class=3D"HOEnZb"><font color=3D"#88=
8888">Richard</font></span><div><div class=3D"h5"><br><br><div class=3D"gma=
il_quote">On Tue, Nov 6, 2012 at 11:53 AM, Richard Alimi <span dir=3D"ltr">=
&lt;<a href=3D"mailto:rich@velvetsea.net" target=3D"_blank">rich@velvetsea.=
net</a>&gt;</span> wrote:<br>

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><br><div class=3D"gmail_extra"><div class=3D=
"gmail_quote"><div>On Tue, Nov 6, 2012 at 7:15 AM, Vijay K. Gurbani <span d=
ir=3D"ltr">&lt;<a href=3D"mailto:vkg@bell-labs.com" target=3D"_blank">vkg@b=
ell-labs.com</a>&gt;</span> wrote:<br>

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">

<div>On 11/05/2012 10:29 PM, Y. Richard Yang wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
Hi Vijay,<br>
<br>
I think we know the issue of the extra numbers before and after the<br>
json return: the server used chunked encoding:<br>
</blockquote></div>
[...]<div><br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
A client supporting chunked encoding will remove those number and a<br>
client (e.g., nc) does not will keep them.<br>
</blockquote>
<br></div>
Richard: OK, that explains the numbers in nc output.<div><br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
The examples in the current spec all use content length. Do we want<br>
to say something here or not?<br>
</blockquote>
<br></div>
I am leaning to no primarily because rfc2616 makes it mandatory to<br>
receive and decode the chunked transfer encoding. =A0Since nc is not<br>
rfc2616 compliant, but we require ALTO clients to be (section 6.3 of<br>
the ALTO protocol), I think we do not need to specify anything more.<div><d=
iv><br></div></div></blockquote><div><br></div></div><div>FWIW, I believe i=
n an earlier version of the draft we were more explicit and specified that =
clients must support chunked encoding. =A0The guidance we received at that =
point was to not reiterate details from the rfc2616.</div>



<div><br></div><div>Rich</div><div>=A0</div><blockquote class=3D"gmail_quot=
e" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">=
<div><div><div>
<br>
Thanks,<br>
<br>
- vijay<br>
-- <br>
Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent<br>
1960 Lucent Lane, Rm. 9C-533, Naperville, Illinois 60563 (USA)<br>
Email: vkg@{<a href=3D"http://bell-labs.com" target=3D"_blank">bell-labs.co=
m</a>,<a href=3D"http://acm.org" target=3D"_blank">acm.org</a>} / <a href=
=3D"mailto:vijay.gurbani@alcatel-lucent.com" target=3D"_blank">vijay.gurban=
i@alcatel-lucent.<u></u>com</a><br>




Web: =A0 <a href=3D"http://ect.bell-labs.com/who/vkg/" target=3D"_blank">ht=
tp://ect.bell-labs.com/who/<u></u>vkg/</a><br>
<br>
<br></div><div>
______________________________<u></u>_________________<br>
alto mailing list<br>
<a href=3D"mailto:alto@ietf.org" target=3D"_blank">alto@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/alto" target=3D"_blank">ht=
tps://www.ietf.org/mailman/<u></u>listinfo/alto</a><br>
</div></div></div></blockquote></div><br></div>
</blockquote></div><br></div></div></div>
<br>_______________________________________________<br>
alto mailing list<br>
<a href=3D"mailto:alto@ietf.org">alto@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/alto" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/alto</a><br>
<br></blockquote></div><br></div>

--001636c5bd89ad802804cdd85f2c--

From vkg@bell-labs.com  Tue Nov  6 11:14:40 2012
Return-Path: <vkg@bell-labs.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 1B11921F8B31 for <alto@ietfa.amsl.com>; Tue,  6 Nov 2012 11:14:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -107.932
X-Spam-Level: 
X-Spam-Status: No, score=-107.932 tagged_above=-999 required=5 tests=[AWL=-1.333, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zN98hLTuyTUg for <alto@ietfa.amsl.com>; Tue,  6 Nov 2012 11:14:29 -0800 (PST)
Received: from ihemail3.lucent.com (ihemail3.lucent.com [135.245.0.37]) by ietfa.amsl.com (Postfix) with ESMTP id 58E5E21F8929 for <alto@ietf.org>; Tue,  6 Nov 2012 11:14:29 -0800 (PST)
Received: from usnavsmail3.ndc.alcatel-lucent.com (usnavsmail3.ndc.alcatel-lucent.com [135.3.39.11]) by ihemail3.lucent.com (8.13.8/IER-o) with ESMTP id qA6JEM5A016589 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Tue, 6 Nov 2012 13:14:23 -0600 (CST)
Received: from umail.lucent.com (umail-ce2.ndc.lucent.com [135.3.40.63]) by usnavsmail3.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id qA6JELb4008363 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 6 Nov 2012 13:14:22 -0600
Received: from shoonya.ih.lucent.com (vkg.lra.lucent.com [135.244.9.123]) by umail.lucent.com (8.13.8/TPES) with ESMTP id qA6JELbq010304; Tue, 6 Nov 2012 13:14:21 -0600 (CST)
Message-ID: <509961D6.3070007@bell-labs.com>
Date: Tue, 06 Nov 2012 13:15:34 -0600
From: "Vijay K. Gurbani" <vkg@bell-labs.com>
Organization: Bell Laboratories, Alcatel-Lucent
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:13.0) Gecko/20120605 Thunderbird/13.0
MIME-Version: 1.0
To: "Y. Richard Yang" <yry@cs.yale.edu>
References: <50985D05.1010102@bell-labs.com> <CANUuoLqkwU1t73ExUOvtHQ1jwSD3UegM4MRWNKCuoUkUjoUdUA@mail.gmail.com> <509929A9.3020509@bell-labs.com> <CA+cvDaZKRTHqxGem3woEuo5wzQf1sJD5QNks8TtM5Hpwf3jsyg@mail.gmail.com> <CANUuoLoONwM+O7pes9pfTqfYute_VAm+boTx8KeS2EfuXt2cWw@mail.gmail.com>
In-Reply-To: <CANUuoLoONwM+O7pes9pfTqfYute_VAm+boTx8KeS2EfuXt2cWw@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.37
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.11
Cc: alto <alto@ietf.org>
Subject: Re: [alto] Interoperability pairings
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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, 06 Nov 2012 19:14:40 -0000

On 11/06/2012 11:46 AM, Y. Richard Yang wrote:
> Hi Rich, Vijay,
>
> No action makes sense to me. From this experience, I may suggest that we
> add a suggestive sentence about
> potential issues of not handling chunked encoding, just for the benefit
> of readers. What do you know?

Richard: I am rather conflicted on what to do.  Clearly, nc is not a
RFC2616 client, and just as clearly, any RFC2616 client will support
chunked encoding.

I also realize that we spent some time at the bakeoff looking at the
byte count prefix in nc(1) but not correlating it immediately with the
"Transfer-Encoding: chunked" header, so saying something seems
appropriate.

In the end, I think I will chalk this upto us being tired and cranky
late at night.

But, if the editor team of the protocol document can find a place to
exhort implementations to pay attention to transfer encodings applied
to message bodies without reiterating rfc2616, then please proceed.  I
tried to spend some time thinking how to do this, but could not arrive
at a reasonable set of words.  So alas, I cannot contribute any text
to get you started ...

Thanks,

- 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/



From vkg@bell-labs.com  Tue Nov  6 11:19:16 2012
Return-Path: <vkg@bell-labs.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 87F7021F8A8C for <alto@ietfa.amsl.com>; Tue,  6 Nov 2012 11:19:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.599
X-Spam-Level: 
X-Spam-Status: No, score=-109.599 tagged_above=-999 required=5 tests=[AWL=1.000, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2DLF2dYLSnC9 for <alto@ietfa.amsl.com>; Tue,  6 Nov 2012 11:19:15 -0800 (PST)
Received: from ihemail2.lucent.com (ihemail2.lucent.com [135.245.0.35]) by ietfa.amsl.com (Postfix) with ESMTP id 92ABD21F8772 for <alto@ietf.org>; Tue,  6 Nov 2012 11:19:15 -0800 (PST)
Received: from usnavsmail2.ndc.alcatel-lucent.com (usnavsmail2.ndc.alcatel-lucent.com [135.3.39.10]) by ihemail2.lucent.com (8.13.8/IER-o) with ESMTP id qA6JJElK017657 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Tue, 6 Nov 2012 13:19:14 -0600 (CST)
Received: from umail.lucent.com (umail-ce2.ndc.lucent.com [135.3.40.63]) by usnavsmail2.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id qA6JJDMb027859 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 6 Nov 2012 13:19:14 -0600
Received: from shoonya.ih.lucent.com (vkg.lra.lucent.com [135.244.9.123]) by umail.lucent.com (8.13.8/TPES) with ESMTP id qA6JJDMh014921; Tue, 6 Nov 2012 13:19:13 -0600 (CST)
Message-ID: <509962F9.2040807@bell-labs.com>
Date: Tue, 06 Nov 2012 13:20:25 -0600
From: "Vijay K. Gurbani" <vkg@bell-labs.com>
Organization: Bell Laboratories, Alcatel-Lucent
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:13.0) Gecko/20120605 Thunderbird/13.0
MIME-Version: 1.0
To: "Junchang(Jason) Wang" <junchang.wang@yale.edu>
References: <50985D05.1010102@bell-labs.com> <CANUuoLqkwU1t73ExUOvtHQ1jwSD3UegM4MRWNKCuoUkUjoUdUA@mail.gmail.com> <509929A9.3020509@bell-labs.com> <CA+cvDaZKRTHqxGem3woEuo5wzQf1sJD5QNks8TtM5Hpwf3jsyg@mail.gmail.com> <CANUuoLoONwM+O7pes9pfTqfYute_VAm+boTx8KeS2EfuXt2cWw@mail.gmail.com> <CAErQho5WSAvie8cDg+Eur=dP+TU0_mJ71Pv=VtoraiCHnsRFWA@mail.gmail.com>
In-Reply-To: <CAErQho5WSAvie8cDg+Eur=dP+TU0_mJ71Pv=VtoraiCHnsRFWA@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.35
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.10
Cc: alto <alto@ietf.org>
Subject: Re: [alto] Interoperability pairings
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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, 06 Nov 2012 19:19:16 -0000

On 11/06/2012 01:11 PM, Junchang(Jason) Wang wrote:
> Dear all,
>
> Or adding a single sentence about potential issues of clients which
> aren't rfc2616 compliant in Section 6.3 would benefit readers a lot.

Jason: The problem with is why stop at the specific example of Content-
Encoding?  A client that isn't compliant will rfc2616 can potentially
do anything it wants and fail in a spectacular way, or worse, cause the
ALTO server to fail in a spectacular way.

I think Section 6.3 takes a reasonable stand that ALTO clients and
servers MUST be compliant with rfc2616.  Hedging our bets and saying
that clients MAY be partially compatible opens up a larger can of
worms, unfortunately.

Thanks,

- 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/



From junchang.wang@yale.edu  Tue Nov  6 11:22:42 2012
Return-Path: <junchang.wang@yale.edu>
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 0E32F21F8B0C for <alto@ietfa.amsl.com>; Tue,  6 Nov 2012 11:22:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.143
X-Spam-Level: 
X-Spam-Status: No, score=-2.143 tagged_above=-999 required=5 tests=[AWL=0.833,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Mng1H7GE86Fr for <alto@ietfa.amsl.com>; Tue,  6 Nov 2012 11:22:40 -0800 (PST)
Received: from mail-wi0-f172.google.com (mail-wi0-f172.google.com [209.85.212.172]) by ietfa.amsl.com (Postfix) with ESMTP id 70DD621F84E8 for <alto@ietf.org>; Tue,  6 Nov 2012 11:22:40 -0800 (PST)
Received: by mail-wi0-f172.google.com with SMTP id hq12so3818140wib.13 for <alto@ietf.org>; Tue, 06 Nov 2012 11:22:39 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yale.edu; s=googleprd; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=elFIgm8YDyj8kOU60vu37Ir7bdGxecwHTSRmBbAp7jc=; b=mOEhX/6npxA917CqJW1RXd0+Hio6DRCtQvx/9jiPilnErMUkoSJKSNCaXrD80CoSzm OZOUNtCNYrvX4VOBCmtnOFxEc9yQ30J++0jSiSj0FDIPaqRpa9dQpTbWDtfGLIanZMit oFIo2m/8IuiPJAQvlIPJYtFFXbRycA5iq3XO8=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:x-gm-message-state; bh=elFIgm8YDyj8kOU60vu37Ir7bdGxecwHTSRmBbAp7jc=; b=bkp9zDEzLN/EsXENQD0lZYAZhzusqzUzQfcs8Kju2Zx7pL3nJGiG2Z1Y1KKPydaCWd VKV6GIbhNyRrsRJ81t94pnBIxktXh7hrHokEEQFTpHZJc9mg9itIhYnANty9JKOv6dlW lJsgan1JDDyaMsg+wCWQQWHM4Vyr7bbO6dlMSJyqrkWLquyBTp9KIqMi5lET5Tu2dtIi CJm3Ckm2yRAWDJ4L2UP6gi1BzLFpnILQ3myyaFJjTEHUwQqKc1dNoZruvAikueufxSRL 3aTCZW9BtkKmjb3uwE16DOnITMZ3kAgAS/EKEvz0EJPGn+Cn+3i1cmdPCfOLihJArjg5 gjog==
MIME-Version: 1.0
Received: by 10.216.139.137 with SMTP id c9mr965766wej.54.1352229759262; Tue, 06 Nov 2012 11:22:39 -0800 (PST)
Received: by 10.194.104.3 with HTTP; Tue, 6 Nov 2012 11:22:39 -0800 (PST)
In-Reply-To: <CANUuoLpaOa91assUwcpq=Fcc_db7fSVEWY4BWFqL8SZmCJatHA@mail.gmail.com>
References: <CAMMTW_+x6s+WTuzXM_QNTr5pmVX7eVdwp0cYyX1cjx+MRaPkdQ@mail.gmail.com> <CANUuoLpaOa91assUwcpq=Fcc_db7fSVEWY4BWFqL8SZmCJatHA@mail.gmail.com>
Date: Tue, 6 Nov 2012 14:22:39 -0500
Message-ID: <CAErQho5EmRf_GY_jyMxeRfejqzx5LoaYdmsb5Vbg5-vQHfOb8A@mail.gmail.com>
From: "Junchang(Jason) Wang" <junchang.wang@yale.edu>
To: "Y. Richard Yang" <yry@cs.yale.edu>, Vijay Gurbani <vijay.gurbani@gmail.com>, hongqiang.liu@yale.edu, Enrico Marocco <enrico.marocco@telecomitalia.it>
Content-Type: multipart/alternative; boundary=001636c5bd89749f2c04cdd88640
X-Gm-Message-State: ALoCoQn+2CJxB2cWz27ecjc6H+oqrsKUpPFP9emti2L0iprbRGRdJC3xOS9r4so52Gax33FpGs9V
Cc: alto <alto@ietf.org>
Subject: Re: [alto] Constraints results in E_SYNTAX
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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, 06 Nov 2012 19:22:42 -0000

--001636c5bd89749f2c04cdd88640
Content-Type: text/plain; charset=ISO-8859-1

Dear Vijay,

Last night, Richard and me together compared your script (simply
returned E_SYNTAX) and ours (worked correctly) line by line for at least 10
minutes, and finally figured out there's a extra 's' in your script
which inured the problem.

I wonder whether it's reasonable that servers return error code
(say E_SYNTAX) PLUS some clues (say, a piece of the string that incurs the
problem). I think that benefits clients a lot.


Thanks.

--Jason


On Mon, Nov 5, 2012 at 11:54 PM, Y. Richard Yang <yry@cs.yale.edu> wrote:

> Hi Vijay,
>
> On Mon, Nov 5, 2012 at 9:35 PM, Vijay Gurbani <vijay.gurbani@gmail.com>wrote:
>
>> Here is the request:
>> POST /endpoints/costs HTTP/1.1
>>
>
> costs -> cost according to spec?
>
> Richard
>
>
>> Accept: application/alto-endpointcost+json,application/alto-error+json
>> Content-Type: application/alto-endpointcostparams+json
>> Content-Length: 488
>>
>> {
>>    "constraints": ["le 5", "ge 4"],
>>    "cost-mode": "numerical",
>>    "cost-type": "routingcost",
>>    "endpoints": {
>>       "dsts": [
>>         "ipv4:10.0.0.0",
>>         "ipv4:15.0.0.0",
>>         "ipv4:192.168.11.0",
>>         "ipv4:192.168.10.0",
>>         "ipv4:128.0.0.0",
>>         "ipv4:130.0.0.0",
>>         "ipv4:0.0.0.0",
>>         "ipv4:132.0.0.0",
>>         "ipv4:135.0.0.0"
>>       ],
>>       "srcs": [
>>         "ipv4:10.0.0.0",
>>         "ipv4:192.168.11.0",
>>         "ipv4:192.168.10.0"
>>       ]
>>    }
>> }
>>
>> and response:
>> cat Test-ECS-3.txt | nc p4p-1.cs.yale.edu 6671
>> HTTP/1.1 400 Bad Request
>> Content-Length: 24
>> Content-Type: application/alto-error+json
>> Date: Tue, 06 Nov 2012 02:47:18 GMT
>>
>> {
>>         "code" : "E_SYNTAX"
>> }
>>
>
>

--001636c5bd89749f2c04cdd88640
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Dear Vijay,<div><br></div><div>Last night, Richard and me together compared=
 your script (simply returned=A0E_SYNTAX) and ours (worked correctly) line =
by line for at least 10 minutes, and=A0finally=A0figured out there&#39;s a =
extra &#39;s&#39; in your script which=A0inured=A0the problem.</div>
<div><br></div><div>I wonder whether it&#39;s=A0reasonable that servers ret=
urn error code (say=A0E_SYNTAX) PLUS some clues (say, a piece of the string=
 that incurs the problem). I think that benefits clients a lot.</div><div><=
br>
</div><div><br></div><div>Thanks.</div><div><br></div><div>--Jason</div><di=
v>=A0</div><div><br><div class=3D"gmail_quote">On Mon, Nov 5, 2012 at 11:54=
 PM, Y. Richard Yang <span dir=3D"ltr">&lt;<a href=3D"mailto:yry@cs.yale.ed=
u" target=3D"_blank">yry@cs.yale.edu</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">Hi Vijay,<br><br><div class=3D"gmail_quote">=
<div class=3D"im">On Mon, Nov 5, 2012 at 9:35 PM, Vijay Gurbani <span dir=
=3D"ltr">&lt;<a href=3D"mailto:vijay.gurbani@gmail.com" target=3D"_blank">v=
ijay.gurbani@gmail.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
Here is the request:<br>
POST /endpoints/costs HTTP/1.1<br></blockquote><div><br></div></div><div>co=
sts -&gt; cost according to spec?</div><span class=3D"HOEnZb"><font color=
=3D"#888888"><div><br></div><div>Richard</div></font></span><div><div class=
=3D"h5">
<div>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;=
border-left:1px #ccc solid;padding-left:1ex">

Accept: application/alto-endpointcost+json,application/alto-error+json<br>
Content-Type: application/alto-endpointcostparams+json<br>
Content-Length: 488<br>
<br>
{<br>
=A0 =A0&quot;constraints&quot;: [&quot;le 5&quot;, &quot;ge 4&quot;],<br>
=A0 =A0&quot;cost-mode&quot;: &quot;numerical&quot;,<br>
=A0 =A0&quot;cost-type&quot;: &quot;routingcost&quot;,<br>
=A0 =A0&quot;endpoints&quot;: {<br>
=A0 =A0 =A0 &quot;dsts&quot;: [<br>
=A0 =A0 =A0 =A0 &quot;ipv4:10.0.0.0&quot;,<br>
=A0 =A0 =A0 =A0 &quot;ipv4:15.0.0.0&quot;,<br>
=A0 =A0 =A0 =A0 &quot;ipv4:192.168.11.0&quot;,<br>
=A0 =A0 =A0 =A0 &quot;ipv4:192.168.10.0&quot;,<br>
=A0 =A0 =A0 =A0 &quot;ipv4:128.0.0.0&quot;,<br>
=A0 =A0 =A0 =A0 &quot;ipv4:130.0.0.0&quot;,<br>
=A0 =A0 =A0 =A0 &quot;ipv4:0.0.0.0&quot;,<br>
=A0 =A0 =A0 =A0 &quot;ipv4:132.0.0.0&quot;,<br>
=A0 =A0 =A0 =A0 &quot;ipv4:135.0.0.0&quot;<br>
=A0 =A0 =A0 ],<br>
=A0 =A0 =A0 &quot;srcs&quot;: [<br>
=A0 =A0 =A0 =A0 &quot;ipv4:10.0.0.0&quot;,<br>
=A0 =A0 =A0 =A0 &quot;ipv4:192.168.11.0&quot;,<br>
=A0 =A0 =A0 =A0 &quot;ipv4:192.168.10.0&quot;<br>
=A0 =A0 =A0 ]<br>
=A0 =A0}<br>
}<br>
<br>
and response:<br>
cat Test-ECS-3.txt | nc <a href=3D"http://p4p-1.cs.yale.edu" target=3D"_bla=
nk">p4p-1.cs.yale.edu</a> 6671<br>
HTTP/1.1 400 Bad Request<br>
Content-Length: 24<br>
Content-Type: application/alto-error+json<br>
Date: Tue, 06 Nov 2012 02:47:18 GMT<br>
<br>
{<br>
=A0 =A0 =A0 =A0 &quot;code&quot; : &quot;E_SYNTAX&quot;<br>
}<br>
</blockquote></div></div></div><br>
</blockquote></div><br></div>

--001636c5bd89749f2c04cdd88640--

From ben@niven-jenkins.co.uk  Tue Nov  6 11:44:27 2012
Return-Path: <ben@niven-jenkins.co.uk>
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 E5C7521F88EF for <alto@ietfa.amsl.com>; Tue,  6 Nov 2012 11:44:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.449
X-Spam-Level: 
X-Spam-Status: No, score=-102.449 tagged_above=-999 required=5 tests=[AWL=0.150, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mXsrT43lnzgQ for <alto@ietfa.amsl.com>; Tue,  6 Nov 2012 11:44:27 -0800 (PST)
Received: from mailex.mailcore.me (mailex.mailcore.me [94.136.40.61]) by ietfa.amsl.com (Postfix) with ESMTP id C24B721F8D7A for <alto@ietf.org>; Tue,  6 Nov 2012 11:44:26 -0800 (PST)
Received: from dhcp-1123.meeting.ietf.org ([130.129.17.35]) by mail11.atlas.pipex.net with esmtpa (Exim 4.71) (envelope-from <ben@niven-jenkins.co.uk>) id 1TVp4T-0004jM-7H; Tue, 06 Nov 2012 19:44:25 +0000
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: text/plain; charset=us-ascii
From: Ben Niven-Jenkins <ben@niven-jenkins.co.uk>
In-Reply-To: <509961D6.3070007@bell-labs.com>
Date: Tue, 6 Nov 2012 19:44:21 +0000
Content-Transfer-Encoding: quoted-printable
Message-Id: <DC1B5F6E-C1BF-4D3F-A61C-8E16728CD5D2@niven-jenkins.co.uk>
References: <50985D05.1010102@bell-labs.com> <CANUuoLqkwU1t73ExUOvtHQ1jwSD3UegM4MRWNKCuoUkUjoUdUA@mail.gmail.com> <509929A9.3020509@bell-labs.com> <CA+cvDaZKRTHqxGem3woEuo5wzQf1sJD5QNks8TtM5Hpwf3jsyg@mail.gmail.com> <CANUuoLoONwM+O7pes9pfTqfYute_VAm+boTx8KeS2EfuXt2cWw@mail.gmail.com> <509961D6.3070007@bell-labs.com>
To: Vijay K. Gurbani <vkg@bell-labs.com>
X-Mailer: Apple Mail (2.1085)
X-Mailcore-Auth: 9600544
X-Mailcore-Domain: 172912
Cc: alto <alto@ietf.org>
Subject: Re: [alto] Interoperability pairings
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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, 06 Nov 2012 19:44:28 -0000

Vijay, Richard,

On 6 Nov 2012, at 19:15, Vijay K. Gurbani wrote:

> On 11/06/2012 11:46 AM, Y. Richard Yang wrote:
>> Hi Rich, Vijay,
>>=20
>> No action makes sense to me. =46rom this experience, I may suggest =
that we
>> add a suggestive sentence about
>> potential issues of not handling chunked encoding, just for the =
benefit
>> of readers. What do you know?
>=20
> Richard: I am rather conflicted on what to do.  Clearly, nc is not a
> RFC2616 client, and just as clearly, any RFC2616 client will support
> chunked encoding.
>=20
> I also realize that we spent some time at the bakeoff looking at the
> byte count prefix in nc(1) but not correlating it immediately with the
> "Transfer-Encoding: chunked" header, so saying something seems
> appropriate.

IMO there is no need to say anything. RFCs are about interoperability. =
The ALTO protocol spec states that RFC2616 compliance is a MUST, =
therefore the specification should not make accommodation for =
interoperability with clients that do not conform to RFC2616.

I think doing anything else would lead to re-iterating the whole of =
RFC2616.

Ben

>=20
> In the end, I think I will chalk this upto us being tired and cranky
> late at night.
>=20
> But, if the editor team of the protocol document can find a place to
> exhort implementations to pay attention to transfer encodings applied
> to message bodies without reiterating rfc2616, then please proceed.  I
> tried to spend some time thinking how to do this, but could not arrive
> at a reasonable set of words.  So alas, I cannot contribute any text
> to get you started ...
>=20
> Thanks,
>=20
> - vijay
> --=20
> 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/
>=20
>=20
> _______________________________________________
> alto mailing list
> alto@ietf.org
> https://www.ietf.org/mailman/listinfo/alto


From ben@niven-jenkins.co.uk  Tue Nov  6 11:47:56 2012
Return-Path: <ben@niven-jenkins.co.uk>
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 286E521F8A78 for <alto@ietfa.amsl.com>; Tue,  6 Nov 2012 11:47:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.499
X-Spam-Level: 
X-Spam-Status: No, score=-102.499 tagged_above=-999 required=5 tests=[AWL=0.100, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id U8vTc5qmkMvK for <alto@ietfa.amsl.com>; Tue,  6 Nov 2012 11:47:55 -0800 (PST)
Received: from mailex.mailcore.me (mailex.mailcore.me [94.136.40.62]) by ietfa.amsl.com (Postfix) with ESMTP id 7EFBA21F8A5C for <alto@ietf.org>; Tue,  6 Nov 2012 11:47:55 -0800 (PST)
Received: from dhcp-1123.meeting.ietf.org ([130.129.17.35]) by mail5.atlas.pipex.net with esmtpa (Exim 4.71) (envelope-from <ben@niven-jenkins.co.uk>) id 1TVp7q-0007Dl-AA; Tue, 06 Nov 2012 19:47:54 +0000
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: text/plain; charset=us-ascii
From: Ben Niven-Jenkins <ben@niven-jenkins.co.uk>
In-Reply-To: <509962F9.2040807@bell-labs.com>
Date: Tue, 6 Nov 2012 19:47:52 +0000
Content-Transfer-Encoding: quoted-printable
Message-Id: <23E4A407-26B6-4440-9803-86F3FCD4DC5F@niven-jenkins.co.uk>
References: <50985D05.1010102@bell-labs.com> <CANUuoLqkwU1t73ExUOvtHQ1jwSD3UegM4MRWNKCuoUkUjoUdUA@mail.gmail.com> <509929A9.3020509@bell-labs.com> <CA+cvDaZKRTHqxGem3woEuo5wzQf1sJD5QNks8TtM5Hpwf3jsyg@mail.gmail.com> <CANUuoLoONwM+O7pes9pfTqfYute_VAm+boTx8KeS2EfuXt2cWw@mail.gmail.com> <CAErQho5WSAvie8cDg+Eur=dP+TU0_mJ71Pv=VtoraiCHnsRFWA@mail.gmail.com> <509962F9.2040807@bell-labs.com>
To: Vijay K. Gurbani <vkg@bell-labs.com>
X-Mailer: Apple Mail (2.1085)
X-Mailcore-Auth: 9600544
X-Mailcore-Domain: 172912
Cc: alto <alto@ietf.org>
Subject: Re: [alto] Interoperability pairings
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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, 06 Nov 2012 19:47:56 -0000

On 6 Nov 2012, at 19:20, Vijay K. Gurbani wrote:

> On 11/06/2012 01:11 PM, Junchang(Jason) Wang wrote:
>> Dear all,
>>=20
>> Or adding a single sentence about potential issues of clients which
>> aren't rfc2616 compliant in Section 6.3 would benefit readers a lot.
>=20
> Jason: The problem with is why stop at the specific example of =
Content-
> Encoding?  A client that isn't compliant will rfc2616 can potentially
> do anything it wants and fail in a spectacular way, or worse, cause =
the
> ALTO server to fail in a spectacular way.
>=20
> I think Section 6.3 takes a reasonable stand that ALTO clients and
> servers MUST be compliant with rfc2616.  Hedging our bets and saying
> that clients MAY be partially compatible opens up a larger can of
> worms, unfortunately.

+1 the ALTO protocol spec is clear - to implement ALTO you need to be =
RFC2616 compliant. If someone wants to implement an ALTO client that =
isn't RFC2616 compliant then they are on their own and interoperability =
isn't guaranteed.

Ben

>=20
> Thanks,
>=20
> - vijay
> --=20
> 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/
>=20
>=20
> _______________________________________________
> alto mailing list
> alto@ietf.org
> https://www.ietf.org/mailman/listinfo/alto


From yang.r.yang@gmail.com  Tue Nov  6 12:04:02 2012
Return-Path: <yang.r.yang@gmail.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 1E6D621F8AD3 for <alto@ietfa.amsl.com>; Tue,  6 Nov 2012 12:04:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.143
X-Spam-Level: 
X-Spam-Status: No, score=-2.143 tagged_above=-999 required=5 tests=[AWL=0.833,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZHF7-0DcZtpy for <alto@ietfa.amsl.com>; Tue,  6 Nov 2012 12:04:01 -0800 (PST)
Received: from mail-oa0-f44.google.com (mail-oa0-f44.google.com [209.85.219.44]) by ietfa.amsl.com (Postfix) with ESMTP id 6480621F8AE6 for <alto@ietf.org>; Tue,  6 Nov 2012 12:03:56 -0800 (PST)
Received: by mail-oa0-f44.google.com with SMTP id n5so950939oag.31 for <alto@ietf.org>; Tue, 06 Nov 2012 12:03:55 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=7aYjaqxM9OGCsgW2BvUutGgrvi1t/g4AdFQFhY+4uUU=; b=XR7/jwuzF4pnOWyirIKKQLmzAxepQyotrv3az0oWGAKuv+bm83FyJGUpAnMvPB1eqz 1BUID5Lk1cT67TcDIL11HlcfzUeAh2jt+GocvdJ/Do+GwtF8LOXuBneUCmdScPc9AlBZ DLogUimVIZZ3gYfI9glb5mbtGsn/RLIrQHCbxGVmFUOV5qpOea1xJVcdpLnfExw/lXk2 S8L4SifeQldM0DB5nT82omolqPH9XRnh7tH+VdoJWwj6PlPAiS3Xzkaja8ctZffjVvaZ SLvzdRvYX1QBDUZTbQGWISOIbI8vIvuu4uPeu8Ta6S36N3IFT6RUGPa3CLekGgpmsGJj xkJg==
MIME-Version: 1.0
Received: by 10.60.32.135 with SMTP id j7mr1724919oei.132.1352232235850; Tue, 06 Nov 2012 12:03:55 -0800 (PST)
Sender: yang.r.yang@gmail.com
Received: by 10.76.155.162 with HTTP; Tue, 6 Nov 2012 12:03:55 -0800 (PST)
In-Reply-To: <23E4A407-26B6-4440-9803-86F3FCD4DC5F@niven-jenkins.co.uk>
References: <50985D05.1010102@bell-labs.com> <CANUuoLqkwU1t73ExUOvtHQ1jwSD3UegM4MRWNKCuoUkUjoUdUA@mail.gmail.com> <509929A9.3020509@bell-labs.com> <CA+cvDaZKRTHqxGem3woEuo5wzQf1sJD5QNks8TtM5Hpwf3jsyg@mail.gmail.com> <CANUuoLoONwM+O7pes9pfTqfYute_VAm+boTx8KeS2EfuXt2cWw@mail.gmail.com> <CAErQho5WSAvie8cDg+Eur=dP+TU0_mJ71Pv=VtoraiCHnsRFWA@mail.gmail.com> <509962F9.2040807@bell-labs.com> <23E4A407-26B6-4440-9803-86F3FCD4DC5F@niven-jenkins.co.uk>
Date: Tue, 6 Nov 2012 15:03:55 -0500
X-Google-Sender-Auth: 3HRelCA8NT9CLyWXeMjZbA8jnDE
Message-ID: <CANUuoLpnNi_LDT4YoJ=Wbe5+Q7C2AAXfVWDnmrK441Em2vcCpw@mail.gmail.com>
From: "Y. Richard Yang" <yry@cs.yale.edu>
To: Ben Niven-Jenkins <ben@niven-jenkins.co.uk>
Content-Type: multipart/alternative; boundary=e89a8fb1f826125abb04cdd91a75
Cc: alto <alto@ietf.org>
Subject: Re: [alto] Interoperability pairings
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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, 06 Nov 2012 20:04:02 -0000

--e89a8fb1f826125abb04cdd91a75
Content-Type: text/plain; charset=ISO-8859-1

On Tue, Nov 6, 2012 at 2:47 PM, Ben Niven-Jenkins
<ben@niven-jenkins.co.uk>wrote:

>
> On 6 Nov 2012, at 19:20, Vijay K. Gurbani wrote:
>
> > On 11/06/2012 01:11 PM, Junchang(Jason) Wang wrote:
> >> Dear all,
> >>
> >> Or adding a single sentence about potential issues of clients which
> >> aren't rfc2616 compliant in Section 6.3 would benefit readers a lot.
> >
> > Jason: The problem with is why stop at the specific example of Content-
> > Encoding?  A client that isn't compliant will rfc2616 can potentially
> > do anything it wants and fail in a spectacular way, or worse, cause the
> > ALTO server to fail in a spectacular way.
> >
> > I think Section 6.3 takes a reasonable stand that ALTO clients and
> > servers MUST be compliant with rfc2616.  Hedging our bets and saying
> > that clients MAY be partially compatible opens up a larger can of
> > worms, unfortunately.
>
> +1 the ALTO protocol spec is clear - to implement ALTO you need to be
> RFC2616 compliant. If someone wants to implement an ALTO client that isn't
> RFC2616 compliant then they are on their own and interoperability isn't
> guaranteed.
>
>
Thanks for the opinions, VIjay, Ben. We then proceed with the current
writing, without singling out some potential issues.

Vijay: if you have some write up on (experiences from) interop, chunked
coding might be listed as a potential source issue.

Thanks!

Richard



> Ben
>
> >
> > Thanks,
> >
> > - 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/
> >
> >
> > _______________________________________________
> > alto mailing list
> > alto@ietf.org
> > https://www.ietf.org/mailman/listinfo/alto
>
> _______________________________________________
> alto mailing list
> alto@ietf.org
> https://www.ietf.org/mailman/listinfo/alto
>

--e89a8fb1f826125abb04cdd91a75
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Tue, Nov 6, 2012 at 2:47 PM, Ben Niven-Jenkins <span dir=3D"ltr">&lt;<a =
href=3D"mailto:ben@niven-jenkins.co.uk" target=3D"_blank">ben@niven-jenkins=
.co.uk</a>&gt;</span> wrote:<br><div class=3D"gmail_quote"><blockquote clas=
s=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;pad=
ding-left:1ex">
<div class=3D"im"><br>
On 6 Nov 2012, at 19:20, Vijay K. Gurbani wrote:<br>
<br>
&gt; On 11/06/2012 01:11 PM, Junchang(Jason) Wang wrote:<br>
&gt;&gt; Dear all,<br>
&gt;&gt;<br>
&gt;&gt; Or adding a single sentence about potential issues of clients whic=
h<br>
&gt;&gt; aren&#39;t rfc2616 compliant in Section 6.3 would benefit readers =
a lot.<br>
&gt;<br>
&gt; Jason: The problem with is why stop at the specific example of Content=
-<br>
&gt; Encoding? =A0A client that isn&#39;t compliant will rfc2616 can potent=
ially<br>
&gt; do anything it wants and fail in a spectacular way, or worse, cause th=
e<br>
&gt; ALTO server to fail in a spectacular way.<br>
&gt;<br>
&gt; I think Section 6.3 takes a reasonable stand that ALTO clients and<br>
&gt; servers MUST be compliant with rfc2616. =A0Hedging our bets and saying=
<br>
&gt; that clients MAY be partially compatible opens up a larger can of<br>
&gt; worms, unfortunately.<br>
<br>
</div>+1 the ALTO protocol spec is clear - to implement ALTO you need to be=
 RFC2616 compliant. If someone wants to implement an ALTO client that isn&#=
39;t RFC2616 compliant then they are on their own and interoperability isn&=
#39;t guaranteed.<br>

<span class=3D"HOEnZb"><font color=3D"#888888"><br></font></span></blockquo=
te><div><br></div><div>Thanks for the opinions, VIjay, Ben. We then proceed=
 with the current writing, without singling out some potential issues.=A0</=
div>
<div><br></div><div>Vijay: if you have some write up on (experiences from) =
interop, chunked coding might be listed as a potential source issue.</div><=
div><br></div><div>Thanks!</div><div><br></div><div>Richard</div><div><br>
</div><div>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0=
 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=3D"HOEnZb"><=
font color=3D"#888888">
Ben<br>
</font></span><div class=3D"im HOEnZb"><br>
&gt;<br>
&gt; Thanks,<br>
&gt;<br>
&gt; - vijay<br>
&gt; --<br>
&gt; Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent<br>
&gt; 1960 Lucent Lane, Rm. 9C-533, Naperville, Illinois 60563 (USA)<br>
&gt; Email: vkg@{<a href=3D"http://bell-labs.com" target=3D"_blank">bell-la=
bs.com</a>,<a href=3D"http://acm.org" target=3D"_blank">acm.org</a>} / <a h=
ref=3D"mailto:vijay.gurbani@alcatel-lucent.com">vijay.gurbani@alcatel-lucen=
t.com</a><br>

&gt; Web: =A0 <a href=3D"http://ect.bell-labs.com/who/vkg/" target=3D"_blan=
k">http://ect.bell-labs.com/who/vkg/</a><br>
&gt;<br>
&gt;<br>
</div><div class=3D"HOEnZb"><div class=3D"h5">&gt; ________________________=
_______________________<br>
&gt; alto mailing list<br>
&gt; <a href=3D"mailto:alto@ietf.org">alto@ietf.org</a><br>
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/alto" target=3D"_blan=
k">https://www.ietf.org/mailman/listinfo/alto</a><br>
<br>
_______________________________________________<br>
alto mailing list<br>
<a href=3D"mailto:alto@ietf.org">alto@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/alto" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/alto</a><br>
</div></div></blockquote></div><br>

--e89a8fb1f826125abb04cdd91a75--

From yang.r.yang@gmail.com  Tue Nov  6 12:14:42 2012
Return-Path: <yang.r.yang@gmail.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 A9E0B21F8A8C for <alto@ietfa.amsl.com>; Tue,  6 Nov 2012 12:14:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.421
X-Spam-Level: 
X-Spam-Status: No, score=-2.421 tagged_above=-999 required=5 tests=[AWL=0.555,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dsGo5dp2q5Ii for <alto@ietfa.amsl.com>; Tue,  6 Nov 2012 12:14:42 -0800 (PST)
Received: from mail-ob0-f172.google.com (mail-ob0-f172.google.com [209.85.214.172]) by ietfa.amsl.com (Postfix) with ESMTP id A3D3D21F8496 for <alto@ietf.org>; Tue,  6 Nov 2012 12:14:41 -0800 (PST)
Received: by mail-ob0-f172.google.com with SMTP id v19so934443obq.31 for <alto@ietf.org>; Tue, 06 Nov 2012 12:14:41 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=C5LUqMUYqS+h0/xP1iJ1SlC6Ax66U762bnUp/HgaCh4=; b=FqG95PDktEcvXmvciUaVcVunSXs1+HeDEEF8CJ9bEN2mtyGHG8Wp2EN+3usTSg6mfm qZFHaAzwKwoqHgQriIKzZo49aJT3dGQm0SuIhoDBkTf5iMhvB9BNDYtDhktgAycwu83Q pcoVo1i+KoPbgZMKFesYFEDHOpZMPz9nYFzsD14bHhTfzHnD9/MucFKdVxs4q8elwZHR fbeCCX22nDK2+qpPrsGtfEKurFE1tSoURfOI3mmmNGRgKDEVYdvKK7seg7O+QHGAZHRR KGmXhDLZoBD0IGyXSMDM1QrdX2ikP+Rs/84DPOHxvLU21DXleTS46IxAp/Yu479IK0lz i92A==
MIME-Version: 1.0
Received: by 10.60.169.20 with SMTP id aa20mr1853580oec.105.1352232881171; Tue, 06 Nov 2012 12:14:41 -0800 (PST)
Sender: yang.r.yang@gmail.com
Received: by 10.76.155.162 with HTTP; Tue, 6 Nov 2012 12:14:41 -0800 (PST)
In-Reply-To: <CAErQho5EmRf_GY_jyMxeRfejqzx5LoaYdmsb5Vbg5-vQHfOb8A@mail.gmail.com>
References: <CAMMTW_+x6s+WTuzXM_QNTr5pmVX7eVdwp0cYyX1cjx+MRaPkdQ@mail.gmail.com> <CANUuoLpaOa91assUwcpq=Fcc_db7fSVEWY4BWFqL8SZmCJatHA@mail.gmail.com> <CAErQho5EmRf_GY_jyMxeRfejqzx5LoaYdmsb5Vbg5-vQHfOb8A@mail.gmail.com>
Date: Tue, 6 Nov 2012 15:14:41 -0500
X-Google-Sender-Auth: jgLriAy_PRjKpCT75nlqV94mosk
Message-ID: <CANUuoLoansbm=7AXW2f8As7Sp5rcQsM56QG2Ob_1-3tiUVBZiQ@mail.gmail.com>
From: "Y. Richard Yang" <yry@cs.yale.edu>
To: "Junchang(Jason) Wang" <junchang.wang@yale.edu>
Content-Type: multipart/alternative; boundary=bcaec54d49a6892ca004cdd940f7
Cc: Vijay Gurbani <vijay.gurbani@gmail.com>, hongqiang.liu@yale.edu, alto <alto@ietf.org>
Subject: Re: [alto] Constraints results in E_SYNTAX
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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, 06 Nov 2012 20:14:42 -0000

--bcaec54d49a6892ca004cdd940f7
Content-Type: text/plain; charset=ISO-8859-1

Hi Jason,

On Tue, Nov 6, 2012 at 2:22 PM, Junchang(Jason) Wang <junchang.wang@yale.edu
> wrote:

>
> I wonder whether it's reasonable that servers return error code
> (say E_SYNTAX) PLUS some clues (say, a piece of the string that incurs the
> problem). I think that benefits clients a lot.
>
>
Adding a string then opens the issue of multi-language support, which can
become a problem.

Regarding the specific test case, I would imagine that a more specific
error is an error code indicating that the client has required a URL that
is not exposed by the Information Directory (due to a typo in the current
case). In the current spec, this is shown as a general ALTO code E_SYNTAX
and HTTP status code 400 (Bad Request). I can imagine that the HTTP error
code could be 404 (Not Found) in this case to be more informative, instead
of the current 400.

Richard


>
> Thanks.
>
> --Jason
>
>
> On Mon, Nov 5, 2012 at 11:54 PM, Y. Richard Yang <yry@cs.yale.edu> wrote:
>
>> Hi Vijay,
>>
>> On Mon, Nov 5, 2012 at 9:35 PM, Vijay Gurbani <vijay.gurbani@gmail.com>wrote:
>>
>>> Here is the request:
>>> POST /endpoints/costs HTTP/1.1
>>>
>>
>> costs -> cost according to spec?
>>
>> Richard
>>
>>
>>> Accept: application/alto-endpointcost+json,application/alto-error+json
>>> Content-Type: application/alto-endpointcostparams+json
>>> Content-Length: 488
>>>
>>> {
>>>    "constraints": ["le 5", "ge 4"],
>>>    "cost-mode": "numerical",
>>>    "cost-type": "routingcost",
>>>    "endpoints": {
>>>       "dsts": [
>>>         "ipv4:10.0.0.0",
>>>         "ipv4:15.0.0.0",
>>>         "ipv4:192.168.11.0",
>>>         "ipv4:192.168.10.0",
>>>         "ipv4:128.0.0.0",
>>>         "ipv4:130.0.0.0",
>>>         "ipv4:0.0.0.0",
>>>         "ipv4:132.0.0.0",
>>>         "ipv4:135.0.0.0"
>>>       ],
>>>       "srcs": [
>>>         "ipv4:10.0.0.0",
>>>         "ipv4:192.168.11.0",
>>>         "ipv4:192.168.10.0"
>>>       ]
>>>    }
>>> }
>>>
>>> and response:
>>> cat Test-ECS-3.txt | nc p4p-1.cs.yale.edu 6671
>>> HTTP/1.1 400 Bad Request
>>> Content-Length: 24
>>> Content-Type: application/alto-error+json
>>> Date: Tue, 06 Nov 2012 02:47:18 GMT
>>>
>>> {
>>>         "code" : "E_SYNTAX"
>>> }
>>>
>>
>>
>

--bcaec54d49a6892ca004cdd940f7
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi Jason,<br><br><div class=3D"gmail_quote">On Tue, Nov 6, 2012 at 2:22 PM,=
 Junchang(Jason) Wang <span dir=3D"ltr">&lt;<a href=3D"mailto:junchang.wang=
@yale.edu" target=3D"_blank">junchang.wang@yale.edu</a>&gt;</span> wrote:<b=
r><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:=
1px #ccc solid;padding-left:1ex">
<div><br></div><div>I wonder whether it&#39;s=A0reasonable that servers ret=
urn error code (say=A0E_SYNTAX) PLUS some clues (say, a piece of the string=
 that incurs the problem). I think that benefits clients a lot.</div><div><=
br>
</div></blockquote><div><br></div><div>Adding a string then opens the issue=
 of multi-language support, which can become a problem.=A0</div><div><br></=
div><div>Regarding the specific test case, I would imagine that a more spec=
ific error is an error code indicating that the client has required a URL t=
hat is not exposed by the Information Directory (due to a typo in the curre=
nt case). In the current spec, this is shown as a general ALTO code E_SYNTA=
X and HTTP status code 400 (Bad Request). I can imagine that the HTTP error=
 code could be 404 (Not Found) in this case to be more informative, instead=
 of the current 400.=A0</div>
<div><br></div><div>Richard</div><div>=A0</div><blockquote class=3D"gmail_q=
uote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1e=
x"><div>
</div><div><br></div><div>Thanks.</div><span class=3D"HOEnZb"><font color=
=3D"#888888"><div><br></div><div>--Jason</div></font></span><div class=3D"H=
OEnZb"><div class=3D"h5"><div>=A0</div><div><br><div class=3D"gmail_quote">=
On Mon, Nov 5, 2012 at 11:54 PM, Y. Richard Yang <span dir=3D"ltr">&lt;<a h=
ref=3D"mailto:yry@cs.yale.edu" target=3D"_blank">yry@cs.yale.edu</a>&gt;</s=
pan> wrote:<br>

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">Hi Vijay,<br><br><div class=3D"gmail_quote">=
<div>On Mon, Nov 5, 2012 at 9:35 PM, Vijay Gurbani <span dir=3D"ltr">&lt;<a=
 href=3D"mailto:vijay.gurbani@gmail.com" target=3D"_blank">vijay.gurbani@gm=
ail.com</a>&gt;</span> wrote:<br>

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
Here is the request:<br>
POST /endpoints/costs HTTP/1.1<br></blockquote><div><br></div></div><div>co=
sts -&gt; cost according to spec?</div><span><font color=3D"#888888"><div><=
br></div><div>Richard</div></font></span><div><div>
<div>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;=
border-left:1px #ccc solid;padding-left:1ex">

Accept: application/alto-endpointcost+json,application/alto-error+json<br>
Content-Type: application/alto-endpointcostparams+json<br>
Content-Length: 488<br>
<br>
{<br>
=A0 =A0&quot;constraints&quot;: [&quot;le 5&quot;, &quot;ge 4&quot;],<br>
=A0 =A0&quot;cost-mode&quot;: &quot;numerical&quot;,<br>
=A0 =A0&quot;cost-type&quot;: &quot;routingcost&quot;,<br>
=A0 =A0&quot;endpoints&quot;: {<br>
=A0 =A0 =A0 &quot;dsts&quot;: [<br>
=A0 =A0 =A0 =A0 &quot;ipv4:10.0.0.0&quot;,<br>
=A0 =A0 =A0 =A0 &quot;ipv4:15.0.0.0&quot;,<br>
=A0 =A0 =A0 =A0 &quot;ipv4:192.168.11.0&quot;,<br>
=A0 =A0 =A0 =A0 &quot;ipv4:192.168.10.0&quot;,<br>
=A0 =A0 =A0 =A0 &quot;ipv4:128.0.0.0&quot;,<br>
=A0 =A0 =A0 =A0 &quot;ipv4:130.0.0.0&quot;,<br>
=A0 =A0 =A0 =A0 &quot;ipv4:0.0.0.0&quot;,<br>
=A0 =A0 =A0 =A0 &quot;ipv4:132.0.0.0&quot;,<br>
=A0 =A0 =A0 =A0 &quot;ipv4:135.0.0.0&quot;<br>
=A0 =A0 =A0 ],<br>
=A0 =A0 =A0 &quot;srcs&quot;: [<br>
=A0 =A0 =A0 =A0 &quot;ipv4:10.0.0.0&quot;,<br>
=A0 =A0 =A0 =A0 &quot;ipv4:192.168.11.0&quot;,<br>
=A0 =A0 =A0 =A0 &quot;ipv4:192.168.10.0&quot;<br>
=A0 =A0 =A0 ]<br>
=A0 =A0}<br>
}<br>
<br>
and response:<br>
cat Test-ECS-3.txt | nc <a href=3D"http://p4p-1.cs.yale.edu" target=3D"_bla=
nk">p4p-1.cs.yale.edu</a> 6671<br>
HTTP/1.1 400 Bad Request<br>
Content-Length: 24<br>
Content-Type: application/alto-error+json<br>
Date: Tue, 06 Nov 2012 02:47:18 GMT<br>
<br>
{<br>
=A0 =A0 =A0 =A0 &quot;code&quot; : &quot;E_SYNTAX&quot;<br>
}<br>
</blockquote></div></div></div><br>
</blockquote></div><br></div>
</div></div></blockquote></div><br>

--bcaec54d49a6892ca004cdd940f7--

From vkg@bell-labs.com  Tue Nov  6 13:46:19 2012
Return-Path: <vkg@bell-labs.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 9283A21F8A44 for <alto@ietfa.amsl.com>; Tue,  6 Nov 2012 13:46:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.799
X-Spam-Level: 
X-Spam-Status: No, score=-109.799 tagged_above=-999 required=5 tests=[AWL=0.800, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uniQk9FK8IGy for <alto@ietfa.amsl.com>; Tue,  6 Nov 2012 13:46:18 -0800 (PST)
Received: from ihemail2.lucent.com (ihemail2.lucent.com [135.245.0.35]) by ietfa.amsl.com (Postfix) with ESMTP id AC48E21F8A4D for <alto@ietf.org>; Tue,  6 Nov 2012 13:46:18 -0800 (PST)
Received: from usnavsmail3.ndc.alcatel-lucent.com (usnavsmail3.ndc.alcatel-lucent.com [135.3.39.11]) by ihemail2.lucent.com (8.13.8/IER-o) with ESMTP id qA6LkGm7002133 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Tue, 6 Nov 2012 15:46:17 -0600 (CST)
Received: from umail.lucent.com (umail-ce2.ndc.lucent.com [135.3.40.63]) by usnavsmail3.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id qA6LkGnI016320 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 6 Nov 2012 15:46:16 -0600
Received: from shoonya.ih.lucent.com (vkg.lra.lucent.com [135.244.9.90]) by umail.lucent.com (8.13.8/TPES) with ESMTP id qA6LkFST012049; Tue, 6 Nov 2012 15:46:15 -0600 (CST)
Message-ID: <50998571.4080501@bell-labs.com>
Date: Tue, 06 Nov 2012 15:47:29 -0600
From: "Vijay K. Gurbani" <vkg@bell-labs.com>
Organization: Bell Laboratories, Alcatel-Lucent
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:13.0) Gecko/20120605 Thunderbird/13.0
MIME-Version: 1.0
To: "Junchang(Jason) Wang" <junchang.wang@yale.edu>
References: <CAMMTW_+x6s+WTuzXM_QNTr5pmVX7eVdwp0cYyX1cjx+MRaPkdQ@mail.gmail.com> <CANUuoLpaOa91assUwcpq=Fcc_db7fSVEWY4BWFqL8SZmCJatHA@mail.gmail.com> <CAErQho5EmRf_GY_jyMxeRfejqzx5LoaYdmsb5Vbg5-vQHfOb8A@mail.gmail.com>
In-Reply-To: <CAErQho5EmRf_GY_jyMxeRfejqzx5LoaYdmsb5Vbg5-vQHfOb8A@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.35
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.11
Cc: hongqiang.liu@yale.edu, alto <alto@ietf.org>
Subject: Re: [alto] Constraints results in E_SYNTAX
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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, 06 Nov 2012 21:46:19 -0000

On 11/06/2012 01:22 PM, Junchang(Jason) Wang wrote:
> Last night, Richard and me together compared your script (simply
> returned E_SYNTAX) and ours (worked correctly) line by line for at least
> 10 minutes, and finally figured out there's a extra 's' in your script
> which inured the problem.

Jason: Right, I discovered that later as well.

> I wonder whether it's reasonable that servers return error code
> (say E_SYNTAX) PLUS some clues (say, a piece of the string that incurs
> the problem). I think that benefits clients a lot.

That is always a good option, but the best place to put this would
have been in definition of ErrorResourceEntity (c.f. Section 6.5.2
of the ALTO protocol document).  I think it is too late to add it
now, but more importantly, I don't think we absolutely need this
functionality.  HTTP is rich enough to provide for richer error
responses without us introducing mechanisms in ALTO.

As Richard mentions, a more appropriate HTTP status code to return
in this particular case would have been a 404, not 400.  It is
the R-URI that was the problem here.

But there are other mechanisms to inform the client of the nature of the
error without necessarily nailing it down in the ALTO protocol
specification.  A couple of that come to mind are:

1) Use a more descriptive Reason-Phrase.  For instance, consider Test-
  JSON-ERR-1 from draft-gurbani-alto-interop-cases-02.  In that test
  case, the server returns a "400 Bad Request".  There is nothing to
  stop the server returning "400 Mismatched braces in entity-body".
  The Reason-Phrase is there for consumption of humans, so the more
  descriptive it is, the better.

2) Use multi-part MIME.  One part is the normal
  "application/alto-error+json" and the other part could be
  "text/plain" that describes the error in more detail.

Thanks,

- 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/



From vkg@bell-labs.com  Tue Nov  6 13:49:57 2012
Return-Path: <vkg@bell-labs.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 ED8A921F8BFA for <alto@ietfa.amsl.com>; Tue,  6 Nov 2012 13:49:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -107.932
X-Spam-Level: 
X-Spam-Status: No, score=-107.932 tagged_above=-999 required=5 tests=[AWL=-1.333, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id u0uUwBlMkejP for <alto@ietfa.amsl.com>; Tue,  6 Nov 2012 13:49:56 -0800 (PST)
Received: from ihemail3.lucent.com (ihemail3.lucent.com [135.245.0.37]) by ietfa.amsl.com (Postfix) with ESMTP id B199E21F8B5F for <alto@ietf.org>; Tue,  6 Nov 2012 13:49:55 -0800 (PST)
Received: from usnavsmail4.ndc.alcatel-lucent.com (usnavsmail4.ndc.alcatel-lucent.com [135.3.39.12]) by ihemail3.lucent.com (8.13.8/IER-o) with ESMTP id qA6LnrO8006199 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Tue, 6 Nov 2012 15:49:54 -0600 (CST)
Received: from umail.lucent.com (umail-ce2.ndc.lucent.com [135.3.40.63]) by usnavsmail4.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id qA6Lnrgt012207 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 6 Nov 2012 15:49:53 -0600
Received: from shoonya.ih.lucent.com (vkg.lra.lucent.com [135.244.9.90]) by umail.lucent.com (8.13.8/TPES) with ESMTP id qA6LnqLO023243; Tue, 6 Nov 2012 15:49:53 -0600 (CST)
Message-ID: <5099864A.4070701@bell-labs.com>
Date: Tue, 06 Nov 2012 15:51:06 -0600
From: "Vijay K. Gurbani" <vkg@bell-labs.com>
Organization: Bell Laboratories, Alcatel-Lucent
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:13.0) Gecko/20120605 Thunderbird/13.0
MIME-Version: 1.0
To: "Y. Richard Yang" <yry@cs.yale.edu>
References: <50985D05.1010102@bell-labs.com> <CANUuoLqkwU1t73ExUOvtHQ1jwSD3UegM4MRWNKCuoUkUjoUdUA@mail.gmail.com> <509929A9.3020509@bell-labs.com> <CA+cvDaZKRTHqxGem3woEuo5wzQf1sJD5QNks8TtM5Hpwf3jsyg@mail.gmail.com> <CANUuoLoONwM+O7pes9pfTqfYute_VAm+boTx8KeS2EfuXt2cWw@mail.gmail.com> <CAErQho5WSAvie8cDg+Eur=dP+TU0_mJ71Pv=VtoraiCHnsRFWA@mail.gmail.com> <509962F9.2040807@bell-labs.com> <23E4A407-26B6-4440-9803-86F3FCD4DC5F@niven-jenkins.co.uk> <CANUuoLpnNi_LDT4YoJ=Wbe5+Q7C2AAXfVWDnmrK441Em2vcCpw@mail.gmail.com>
In-Reply-To: <CANUuoLpnNi_LDT4YoJ=Wbe5+Q7C2AAXfVWDnmrK441Em2vcCpw@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.37
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.12
Cc: alto <alto@ietf.org>
Subject: Re: [alto] Interoperability pairings
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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, 06 Nov 2012 21:49:57 -0000

On 11/06/2012 02:03 PM, Y. Richard Yang wrote:
> Thanks for the opinions, VIjay, Ben. We then proceed with the current
> writing, without singling out some potential issues.
>
> Vijay: if you have some write up on (experiences from) interop, chunked
> coding might be listed as a potential source issue.

Richard: Yes, I will do so.  One place where we can document such
"gotchas" is as part of draft-gurbani-alto-interop-cases.

The rub is that we should, then, insure that the draft gets published
instead of simply expiring.  But at least it will distill some known
issues that implementors can be wary of.

Thanks,

- 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/



From junchang.wang@yale.edu  Tue Nov  6 17:53:37 2012
Return-Path: <junchang.wang@yale.edu>
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 3456321F8708 for <alto@ietfa.amsl.com>; Tue,  6 Nov 2012 17:53:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.976
X-Spam-Level: 
X-Spam-Status: No, score=-2.976 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vjouhiRzgK1L for <alto@ietfa.amsl.com>; Tue,  6 Nov 2012 17:53:36 -0800 (PST)
Received: from mail-wg0-f44.google.com (mail-wg0-f44.google.com [74.125.82.44]) by ietfa.amsl.com (Postfix) with ESMTP id 14FB021F85E8 for <alto@ietf.org>; Tue,  6 Nov 2012 17:53:35 -0800 (PST)
Received: by mail-wg0-f44.google.com with SMTP id dr13so502854wgb.13 for <alto@ietf.org>; Tue, 06 Nov 2012 17:53:35 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yale.edu; s=googleprd; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=+KG7RjvoBEu+eBzjba/EE5Am7f3Q2/MViFxevH1W5tU=; b=Uyge7K/m9Ls2xe13+wNa8qXWRNYKKT3CxX+S1elFocQf2BdBvoRaV/kufoYxsQJnDa F3xJUktp33rZlt2QHXXzEf2veT10BuTBUTfNiIWMTNcXWfyo3tGLp+wZb/yPhsQyLGqB g27CaBs1pV6xPgDTAvHUgyF8zfdLLtCgxhgXY=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:x-gm-message-state; bh=+KG7RjvoBEu+eBzjba/EE5Am7f3Q2/MViFxevH1W5tU=; b=V9ahKNgkivj5RU4OOeT2SOlXaz/ipb37icCJn74sU16+8i4K9EjT7aX8bNIoG5DxM8 HQVYUbZYTxFC2AwWHBPbYP57yatyWzmCwA1vgOe6l2Y864ft1BUTIO3MdVGjVmeYnjRv D1U9ttU+YZqbV9b3vYJYv0htdNmibHIjATivJ3ywFrdsuPzS7zoTAkcXzyVVrtSa45rT 4bZKVa7zs3/2F+zM7/bkG7YAUgTaJaSrDytrtkyXjxyfadgzuAMCYA959/KCW4JVRbZ5 1cRo3XdbiPYn2tGsvifNLmjQiQm/veh6SCgic+cuC3hIavBT3ZEGRflesu9NyH+lcyx4 kpvw==
MIME-Version: 1.0
Received: by 10.216.142.139 with SMTP id i11mr1353411wej.19.1352253214935; Tue, 06 Nov 2012 17:53:34 -0800 (PST)
Received: by 10.194.104.3 with HTTP; Tue, 6 Nov 2012 17:53:34 -0800 (PST)
In-Reply-To: <50998571.4080501@bell-labs.com>
References: <CAMMTW_+x6s+WTuzXM_QNTr5pmVX7eVdwp0cYyX1cjx+MRaPkdQ@mail.gmail.com> <CANUuoLpaOa91assUwcpq=Fcc_db7fSVEWY4BWFqL8SZmCJatHA@mail.gmail.com> <CAErQho5EmRf_GY_jyMxeRfejqzx5LoaYdmsb5Vbg5-vQHfOb8A@mail.gmail.com> <50998571.4080501@bell-labs.com>
Date: Tue, 6 Nov 2012 20:53:34 -0500
Message-ID: <CAErQho5d4B-5cB=d+=20XwPK2rEkwzAjeG344kHKJCXc54yPug@mail.gmail.com>
From: "Junchang(Jason) Wang" <junchang.wang@yale.edu>
To: "Vijay K. Gurbani" <vkg@bell-labs.com>
Content-Type: multipart/alternative; boundary=0016e6d9a3b285c9a904cdddfc52
X-Gm-Message-State: ALoCoQnEk94haIIPooqzr04B/+jjGESjPeZJFRM53EvHD/br0jxd5FLpThK34gZgzf5EN01ot+FA
Cc: hongqiang.liu@yale.edu, alto <alto@ietf.org>
Subject: Re: [alto] Constraints results in E_SYNTAX
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Wed, 07 Nov 2012 01:53:37 -0000

--0016e6d9a3b285c9a904cdddfc52
Content-Type: text/plain; charset=ISO-8859-1

Learned a lot from this conversation. Thanks all.

(see below)

On Tue, Nov 6, 2012 at 4:47 PM, Vijay K. Gurbani <vkg@bell-labs.com> wrote:

>
> 2) Use multi-part MIME.  One part is the normal
>  "application/alto-error+json" and the other part could be
>  "text/plain" that describes the error in more detail.
>


We can try to implement this in our ALTO server. But whether it's better to
mention that in some documents so that clients can follow? In other words,
clients should be aware of error description part. Is that right?

Thanks.

--Jason

--0016e6d9a3b285c9a904cdddfc52
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div><br></div>Learned a lot from this conversation. Thanks all.=A0<div><br=
></div><div>(see below)<br><br><div class=3D"gmail_quote">On Tue, Nov 6, 20=
12 at 4:47 PM, Vijay K. Gurbani <span dir=3D"ltr">&lt;<a href=3D"mailto:vkg=
@bell-labs.com" target=3D"_blank">vkg@bell-labs.com</a>&gt;</span> wrote:<b=
r>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div class=3D"im"><br></div>
2) Use multi-part MIME. =A0One part is the normal<br>
=A0&quot;application/alto-error+json&quot; and the other part could be<br>
=A0&quot;text/plain&quot; that describes the error in more detail.<br></blo=
ckquote><div>=A0</div><div><br></div><div>We can try to implement this in o=
ur ALTO server. But whether it&#39;s better to mention that in some documen=
ts so that clients can follow? In other words, clients should be aware of e=
rror description part. Is that right?</div>
<div><br></div><div>Thanks.</div><div><br></div><div>--Jason</div></div></d=
iv>

--0016e6d9a3b285c9a904cdddfc52--

From vkg@bell-labs.com  Tue Nov  6 18:59:43 2012
Return-Path: <vkg@bell-labs.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 9E3BB21F8BAC for <alto@ietfa.amsl.com>; Tue,  6 Nov 2012 18:59:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.742
X-Spam-Level: 
X-Spam-Status: No, score=-109.742 tagged_above=-999 required=5 tests=[AWL=0.857, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fzpvWOR0roby for <alto@ietfa.amsl.com>; Tue,  6 Nov 2012 18:59:42 -0800 (PST)
Received: from ihemail2.lucent.com (ihemail2.lucent.com [135.245.0.35]) by ietfa.amsl.com (Postfix) with ESMTP id 08FD221F8BAB for <alto@ietf.org>; Tue,  6 Nov 2012 18:59:38 -0800 (PST)
Received: from usnavsmail4.ndc.alcatel-lucent.com (usnavsmail4.ndc.alcatel-lucent.com [135.3.39.12]) by ihemail2.lucent.com (8.13.8/IER-o) with ESMTP id qA72xQdd019916 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Tue, 6 Nov 2012 20:59:26 -0600 (CST)
Received: from umail.lucent.com (umail-ce2.ndc.lucent.com [135.3.40.63]) by usnavsmail4.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id qA72xPsB004703 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 6 Nov 2012 20:59:26 -0600
Received: from shoonya.ih.lucent.com (vkg.lra.lucent.com [135.244.3.194]) by umail.lucent.com (8.13.8/TPES) with ESMTP id qA72xObu014098; Tue, 6 Nov 2012 20:59:25 -0600 (CST)
Message-ID: <5099CED5.4080008@bell-labs.com>
Date: Tue, 06 Nov 2012 21:00:37 -0600
From: "Vijay K. Gurbani" <vkg@bell-labs.com>
Organization: Bell Laboratories, Alcatel-Lucent
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:13.0) Gecko/20120605 Thunderbird/13.0
MIME-Version: 1.0
To: "Junchang(Jason) Wang" <junchang.wang@yale.edu>
References: <CAMMTW_+x6s+WTuzXM_QNTr5pmVX7eVdwp0cYyX1cjx+MRaPkdQ@mail.gmail.com> <CANUuoLpaOa91assUwcpq=Fcc_db7fSVEWY4BWFqL8SZmCJatHA@mail.gmail.com> <CAErQho5EmRf_GY_jyMxeRfejqzx5LoaYdmsb5Vbg5-vQHfOb8A@mail.gmail.com> <50998571.4080501@bell-labs.com> <CAErQho5d4B-5cB=d+=20XwPK2rEkwzAjeG344kHKJCXc54yPug@mail.gmail.com>
In-Reply-To: <CAErQho5d4B-5cB=d+=20XwPK2rEkwzAjeG344kHKJCXc54yPug@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.35
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.12
Cc: hongqiang.liu@yale.edu, alto <alto@ietf.org>
Subject: Re: [alto] Constraints results in E_SYNTAX
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Wed, 07 Nov 2012 02:59:43 -0000

On 11/06/2012 07:53 PM, Junchang(Jason) Wang wrote:
> On Tue, Nov 6, 2012 at 4:47 PM, Vijay K. Gurbani <vkg@bell-labs.com
> <mailto:vkg@bell-labs.com>> wrote:
>
>
>     2) Use multi-part MIME.  One part is the normal
>       "application/alto-error+json" and the other part could be
>       "text/plain" that describes the error in more detail.
>
> We can try to implement this in our ALTO server. But whether it's better
> to mention that in some documents so that clients can follow? In other
> words, clients should be aware of error description part. Is that right?

Yes, at least aware enough that they decode the multipart MIME and
render the "text/plain" for human consumption.  But even if they do
not, the problem is apparent when one uses a packet sniffer (tcpdump,
wireshark, etc.) to look at the traffic.

 From the ease of use perspective, using the Reason-Phrase is probably
the way to go.

We could probably have an "Implementer's Guide" section in draft-
gurbani-alto-interop-cases where we provide relevant information.
Probably best to put it there instead of the protocol document.

Thanks,

- 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/



From junchang.wang@yale.edu  Wed Nov  7 08:13:39 2012
Return-Path: <junchang.wang@yale.edu>
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 8E28321F8C08 for <alto@ietfa.amsl.com>; Wed,  7 Nov 2012 08:13:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.976
X-Spam-Level: 
X-Spam-Status: No, score=-2.976 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZMj8tYPHPswf for <alto@ietfa.amsl.com>; Wed,  7 Nov 2012 08:13:38 -0800 (PST)
Received: from mail-wg0-f44.google.com (mail-wg0-f44.google.com [74.125.82.44]) by ietfa.amsl.com (Postfix) with ESMTP id 5881321F8BF7 for <alto@ietf.org>; Wed,  7 Nov 2012 08:13:37 -0800 (PST)
Received: by mail-wg0-f44.google.com with SMTP id dr13so806643wgb.13 for <alto@ietf.org>; Wed, 07 Nov 2012 08:13:27 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yale.edu; s=googleprd; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=KxHuW+r1vqfKCDl1ocTisGuoO35AMjmLd4sPDllg5aY=; b=vKvrqx5hhzHA9CZE0h+RpNJHVkGxmAEFsEVu+a+Xwg5vwPkI494Fs1MLEvWQhZj5QH 3KlFQNzTriTpzQuYiavVeZHqoz3hgPXZxmu1ZMozzBuUw2Y9qiJwlNfx+8EgFe6nR9B9 6Ti54h3LpCTkz1XoYeWwLAwhgu71ZAiszbrXg=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:x-gm-message-state; bh=KxHuW+r1vqfKCDl1ocTisGuoO35AMjmLd4sPDllg5aY=; b=XVYkHkbNhmixs3DR3YkhsYTeb9CHPLvxXNgoqtRmCWF6WaZ9G0MmbEiZ3W2Spwr9in F8qZDy9D5DBnpIiH/IJgzo/HiapgJF8x95YULjGUdvWhzwV6rW98Q7bMo2M3Fq04NltN sUBtgqGFVbCXQfLdLvGFs/I60VWgz0oh7SFkkOag/fuadD/zCxhfRkI/aSUDZGXSGjm3 /T49znnuR8EBik+uNJt5WkT7yOba1B/MlwArnPI5ArV7KBDowoV0dfN0QO3TXmczz0Ue pphdWafH/gmrKVamT/dVsRc9vTCdtNlDaSEwSfDm2kVJTjC0hzE+oZ/jC+AbRvnpl/+Q PH2g==
MIME-Version: 1.0
Received: by 10.181.11.167 with SMTP id ej7mr8592677wid.11.1352304807365; Wed, 07 Nov 2012 08:13:27 -0800 (PST)
Received: by 10.194.104.3 with HTTP; Wed, 7 Nov 2012 08:13:27 -0800 (PST)
In-Reply-To: <5099CED5.4080008@bell-labs.com>
References: <CAMMTW_+x6s+WTuzXM_QNTr5pmVX7eVdwp0cYyX1cjx+MRaPkdQ@mail.gmail.com> <CANUuoLpaOa91assUwcpq=Fcc_db7fSVEWY4BWFqL8SZmCJatHA@mail.gmail.com> <CAErQho5EmRf_GY_jyMxeRfejqzx5LoaYdmsb5Vbg5-vQHfOb8A@mail.gmail.com> <50998571.4080501@bell-labs.com> <CAErQho5d4B-5cB=d+=20XwPK2rEkwzAjeG344kHKJCXc54yPug@mail.gmail.com> <5099CED5.4080008@bell-labs.com>
Date: Wed, 7 Nov 2012 11:13:27 -0500
Message-ID: <CAErQho5NV3+h1EpHcXgnHhHen1M2A2YLY_dA8Dzpq3JdEZyZOw@mail.gmail.com>
From: "Junchang(Jason) Wang" <junchang.wang@yale.edu>
To: "Vijay K. Gurbani" <vkg@bell-labs.com>
Content-Type: multipart/alternative; boundary=f46d043c80f2abcb6204cde9fffb
X-Gm-Message-State: ALoCoQmCX+O0v7JkUJQhNcAqpWfPTVKgsKHlxNP3c4ySjXWkuBOcH7hVYxLNqE+AlUoY5Ws5iimU
Cc: hongqiang.liu@yale.edu, alto <alto@ietf.org>
Subject: Re: [alto] Constraints results in E_SYNTAX
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Wed, 07 Nov 2012 16:13:39 -0000

--f46d043c80f2abcb6204cde9fffb
Content-Type: text/plain; charset=ISO-8859-1

On Tue, Nov 6, 2012 at 10:00 PM, Vijay K. Gurbani <vkg@bell-labs.com> wrote:

> On 11/06/2012 07:53 PM, Junchang(Jason) Wang wrote:
>
>> On Tue, Nov 6, 2012 at 4:47 PM, Vijay K. Gurbani <vkg@bell-labs.com
>> <mailto:vkg@bell-labs.com>> wrote:
>>
>>
>>     2) Use multi-part MIME.  One part is the normal
>>       "application/alto-error+json" and the other part could be
>>       "text/plain" that describes the error in more detail.
>>
>> We can try to implement this in our ALTO server. But whether it's better
>> to mention that in some documents so that clients can follow? In other
>> words, clients should be aware of error description part. Is that right?
>>
>
> Yes, at least aware enough that they decode the multipart MIME and
> render the "text/plain" for human consumption.  But even if they do
> not, the problem is apparent when one uses a packet sniffer (tcpdump,
> wireshark, etc.) to look at the traffic.
>
> From the ease of use perspective, using the Reason-Phrase is probably
> the way to go.
>
> We could probably have an "Implementer's Guide" section in draft-
> gurbani-alto-interop-cases where we provide relevant information.
> Probably best to put it there instead of the protocol document.
>
>
Hi Vijay,

Sounds great. I can implement the Reason-Phrase schema in our ALTO server
soon and deploy it on p4p-1.cs.yale.edu for test.


Thanks.

--Jason

--f46d043c80f2abcb6204cde9fffb
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<br><br><div class=3D"gmail_quote">On Tue, Nov 6, 2012 at 10:00 PM, Vijay K=
. Gurbani <span dir=3D"ltr">&lt;<a href=3D"mailto:vkg@bell-labs.com" target=
=3D"_blank">vkg@bell-labs.com</a>&gt;</span> wrote:<br><blockquote class=3D=
"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding=
-left:1ex">

<div>On 11/06/2012 07:53 PM, Junchang(Jason) Wang wrote:<br>
</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-l=
eft:1px #ccc solid;padding-left:1ex"><div>
On Tue, Nov 6, 2012 at 4:47 PM, Vijay K. Gurbani &lt;<a href=3D"mailto:vkg@=
bell-labs.com" target=3D"_blank">vkg@bell-labs.com</a><br></div><div>
&lt;mailto:<a href=3D"mailto:vkg@bell-labs.com" target=3D"_blank">vkg@bell-=
labs.com</a>&gt;&gt; wrote:<br>
<br>
<br>
=A0 =A0 2) Use multi-part MIME. =A0One part is the normal<br>
=A0 =A0 =A0 &quot;application/alto-error+json&quot; and the other part coul=
d be<br>
=A0 =A0 =A0 &quot;text/plain&quot; that describes the error in more detail.=
<br>
<br>
We can try to implement this in our ALTO server. But whether it&#39;s bette=
r<br>
to mention that in some documents so that clients can follow? In other<br>
words, clients should be aware of error description part. Is that right?<br=
>
</div></blockquote>
<br>
Yes, at least aware enough that they decode the multipart MIME and<br>
render the &quot;text/plain&quot; for human consumption. =A0But even if the=
y do<br>
not, the problem is apparent when one uses a packet sniffer (tcpdump,<br>
wireshark, etc.) to look at the traffic.<br>
<br>
>From the ease of use perspective, using the Reason-Phrase is probably<br>
the way to go.<br>
<br>
We could probably have an &quot;Implementer&#39;s Guide&quot; section in dr=
aft-<br>
gurbani-alto-interop-cases where we provide relevant information.<br>
Probably best to put it there instead of the protocol document.<div><div><b=
r></div></div></blockquote><div><br></div><div>Hi Vijay,</div><div><br></di=
v><div>Sounds great. I can implement the=A0Reason-Phrase schema in our ALTO=
 server soon and deploy it on <a href=3D"http://p4p-1.cs.yale.edu" target=
=3D"_blank">p4p-1.cs.yale.edu</a> for test.</div>

<div><br></div><div><br></div><div>Thanks.</div><div><br></div><div>--Jason=
</div></div>

--f46d043c80f2abcb6204cde9fffb--

From richard.alimi@gmail.com  Wed Nov  7 11:39:32 2012
Return-Path: <richard.alimi@gmail.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 089BD21F8C77 for <alto@ietfa.amsl.com>; Wed,  7 Nov 2012 11:39:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.31
X-Spam-Level: 
X-Spam-Status: No, score=-1.31 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, SARE_HTML_USL_OBFU=1.666]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8-1+We-gamzI for <alto@ietfa.amsl.com>; Wed,  7 Nov 2012 11:39:24 -0800 (PST)
Received: from mail-vb0-f44.google.com (mail-vb0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id 575BF21F8C67 for <alto@ietf.org>; Wed,  7 Nov 2012 11:39:24 -0800 (PST)
Received: by mail-vb0-f44.google.com with SMTP id fc26so2158458vbb.31 for <alto@ietf.org>; Wed, 07 Nov 2012 11:39:23 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type; bh=M/PzZj8wGeOmMnK+IsADEg6NH18fNcPF1kyrjJN3jJY=; b=zRCxuDHjXMfN9sf6BhAfAKVO7k6ZyXwgayxlX1VvjbKP6FiHlz6pEUU3YOf913vEtW PFB7U+S79xJEabESBrcqFVnWfQ0C9e5/XxmoRz/vjODRoYiQ0AHhyNmik1ioepMgqzGl naZFC0ywkhQxMMTQ/cLGWzFUNImvJgDlxCU7+/wxyP825PcXjDPgNOHjhboVhmzjmjRo 7sGZ09N+/1eT2yR8L4Nas5VvS+xjsrOq7pAdkxjPxzQ09PkSlXcEvaL0f6egBYu5Hjup yaYce3Vrs9LbpHdEyDY3wqy4q4w85Q/dNcrRDTeVuzqSPBMx+PcHs7Y1eKRVYuuiQbHx 0cQQ==
Received: by 10.52.74.6 with SMTP id p6mr4412830vdv.124.1352317163445; Wed, 07 Nov 2012 11:39:23 -0800 (PST)
MIME-Version: 1.0
Sender: richard.alimi@gmail.com
Received: by 10.58.198.44 with HTTP; Wed, 7 Nov 2012 11:39:03 -0800 (PST)
In-Reply-To: <50998571.4080501@bell-labs.com>
References: <CAMMTW_+x6s+WTuzXM_QNTr5pmVX7eVdwp0cYyX1cjx+MRaPkdQ@mail.gmail.com> <CANUuoLpaOa91assUwcpq=Fcc_db7fSVEWY4BWFqL8SZmCJatHA@mail.gmail.com> <CAErQho5EmRf_GY_jyMxeRfejqzx5LoaYdmsb5Vbg5-vQHfOb8A@mail.gmail.com> <50998571.4080501@bell-labs.com>
From: Richard Alimi <rich@velvetsea.net>
Date: Wed, 7 Nov 2012 11:39:03 -0800
X-Google-Sender-Auth: Vu2jysqsj5iqNsW0Eu0OTBX48bE
Message-ID: <CA+cvDaazN81M5zCgXtZU6PMCSXXQOyNZRBL0BU8-YGsvBPb5Qg@mail.gmail.com>
To: "Vijay K. Gurbani" <vkg@bell-labs.com>
Content-Type: multipart/alternative; boundary=20cf3071ca70269e0404cdece06e
Cc: Harry Liu <hongqiang.liu@yale.edu>, alto <alto@ietf.org>
Subject: Re: [alto] Constraints results in E_SYNTAX
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Wed, 07 Nov 2012 19:39:32 -0000

--20cf3071ca70269e0404cdece06e
Content-Type: text/plain; charset=ISO-8859-1

On Tue, Nov 6, 2012 at 1:47 PM, Vijay K. Gurbani <vkg@bell-labs.com> wrote:

> On 11/06/2012 01:22 PM, Junchang(Jason) Wang wrote:
>
>> Last night, Richard and me together compared your script (simply
>> returned E_SYNTAX) and ours (worked correctly) line by line for at least
>> 10 minutes, and finally figured out there's a extra 's' in your script
>> which inured the problem.
>>
>
> Jason: Right, I discovered that later as well.
>
>
>  I wonder whether it's reasonable that servers return error code
>> (say E_SYNTAX) PLUS some clues (say, a piece of the string that incurs
>> the problem). I think that benefits clients a lot.
>>
>
> That is always a good option, but the best place to put this would
> have been in definition of ErrorResourceEntity (c.f. Section 6.5.2
> of the ALTO protocol document).  I think it is too late to add it
> now,


The ALTO protocol used to have a reason that was free-form text.  Ted
Hardie suggested in his review that we drop this to avoid multi-language
issues (as Richard Yang pointed out).  We then removed the reason field.


> but more importantly, I don't think we absolutely need this
> functionality.  HTTP is rich enough to provide for richer error
> responses without us introducing mechanisms in ALTO.
>
> As Richard mentions, a more appropriate HTTP status code to return
> in this particular case would have been a 404, not 400.  It is
> the R-URI that was the problem here.
>
> But there are other mechanisms to inform the client of the nature of the
> error without necessarily nailing it down in the ALTO protocol
> specification.  A couple of that come to mind are:
>
> 1) Use a more descriptive Reason-Phrase.  For instance, consider Test-
>  JSON-ERR-1 from draft-gurbani-alto-interop-**cases-02.  In that test
>  case, the server returns a "400 Bad Request".  There is nothing to
>  stop the server returning "400 Mismatched braces in entity-body".
>  The Reason-Phrase is there for consumption of humans, so the more
>  descriptive it is, the better.
>
> 2) Use multi-part MIME.  One part is the normal
>  "application/alto-error+json" and the other part could be
>  "text/plain" that describes the error in more detail.
>
> Thanks,
>
> - 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<vijay.gurbani@alcatel-lucent.com>
> Web:   http://ect.bell-labs.com/who/**vkg/<http://ect.bell-labs.com/who/vkg/>
>
>
> ______________________________**_________________
> alto mailing list
> alto@ietf.org
> https://www.ietf.org/mailman/**listinfo/alto<https://www.ietf.org/mailman/listinfo/alto>
>

--20cf3071ca70269e0404cdece06e
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<br><div class=3D"gmail_extra"><div class=3D"gmail_quote">On Tue, Nov 6, 20=
12 at 1:47 PM, Vijay K. Gurbani <span dir=3D"ltr">&lt;<a href=3D"mailto:vkg=
@bell-labs.com" target=3D"_blank">vkg@bell-labs.com</a>&gt;</span> wrote:<b=
r><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:=
1px #ccc solid;padding-left:1ex">

<div class=3D"im">On 11/06/2012 01:22 PM, Junchang(Jason) Wang wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
Last night, Richard and me together compared your script (simply<br>
returned E_SYNTAX) and ours (worked correctly) line by line for at least<br=
>
10 minutes, and finally figured out there&#39;s a extra &#39;s&#39; in your=
 script<br>
which inured the problem.<br>
</blockquote>
<br></div>
Jason: Right, I discovered that later as well.<div class=3D"im"><br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
I wonder whether it&#39;s reasonable that servers return error code<br>
(say E_SYNTAX) PLUS some clues (say, a piece of the string that incurs<br>
the problem). I think that benefits clients a lot.<br>
</blockquote>
<br></div>
That is always a good option, but the best place to put this would<br>
have been in definition of ErrorResourceEntity (c.f. Section 6.5.2<br>
of the ALTO protocol document). =A0I think it is too late to add it<br>
now,</blockquote><div><br></div><div>The ALTO protocol used to have a reaso=
n that was free-form text. =A0Ted Hardie suggested in his review that we dr=
op this to avoid multi-language issues (as Richard Yang pointed out). =A0We=
 then removed the reason field.</div>

<div>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;=
border-left:1px #ccc solid;padding-left:1ex"> but more importantly, I don&#=
39;t think we absolutely need this<br>
functionality. =A0HTTP is rich enough to provide for richer error<br>
responses without us introducing mechanisms in ALTO.<br>
<br>
As Richard mentions, a more appropriate HTTP status code to return<br>
in this particular case would have been a 404, not 400. =A0It is<br>
the R-URI that was the problem here.<br>
<br>
But there are other mechanisms to inform the client of the nature of the<br=
>
error without necessarily nailing it down in the ALTO protocol<br>
specification. =A0A couple of that come to mind are:<br>
<br>
1) Use a more descriptive Reason-Phrase. =A0For instance, consider Test-<br=
>
=A0JSON-ERR-1 from draft-gurbani-alto-interop-<u></u>cases-02. =A0In that t=
est<br>
=A0case, the server returns a &quot;400 Bad Request&quot;. =A0There is noth=
ing to<br>
=A0stop the server returning &quot;400 Mismatched braces in entity-body&quo=
t;.<br>
=A0The Reason-Phrase is there for consumption of humans, so the more<br>
=A0descriptive it is, the better.<br>
<br>
2) Use multi-part MIME. =A0One part is the normal<br>
=A0&quot;application/alto-error+json&quot; and the other part could be<br>
=A0&quot;text/plain&quot; that describes the error in more detail.<br>
<br>
Thanks,<br>
<br>
- vijay<span class=3D"HOEnZb"><font color=3D"#888888"><br>
-- <br>
Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent<br>
1960 Lucent Lane, Rm. 9C-533, Naperville, Illinois 60563 (USA)<br>
Email: vkg@{<a href=3D"http://bell-labs.com" target=3D"_blank">bell-labs.co=
m</a>,<a href=3D"http://acm.org" target=3D"_blank">acm.org</a>} / <a href=
=3D"mailto:vijay.gurbani@alcatel-lucent.com" target=3D"_blank">vijay.gurban=
i@alcatel-lucent.<u></u>com</a><br>


Web: =A0 <a href=3D"http://ect.bell-labs.com/who/vkg/" target=3D"_blank">ht=
tp://ect.bell-labs.com/who/<u></u>vkg/</a><br>
<br>
<br>
______________________________<u></u>_________________<br>
alto mailing list<br>
<a href=3D"mailto:alto@ietf.org" target=3D"_blank">alto@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/alto" target=3D"_blank">ht=
tps://www.ietf.org/mailman/<u></u>listinfo/alto</a><br>
</font></span></blockquote></div><br></div>

--20cf3071ca70269e0404cdece06e--

From ben@niven-jenkins.co.uk  Wed Nov  7 12:06:39 2012
Return-Path: <ben@niven-jenkins.co.uk>
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 891E221F8CE2 for <alto@ietfa.amsl.com>; Wed,  7 Nov 2012 12:06:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.539
X-Spam-Level: 
X-Spam-Status: No, score=-102.539 tagged_above=-999 required=5 tests=[AWL=0.060, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 69OCMcW8Td5F for <alto@ietfa.amsl.com>; Wed,  7 Nov 2012 12:06:39 -0800 (PST)
Received: from mailex.mailcore.me (mailex.mailcore.me [94.136.40.61]) by ietfa.amsl.com (Postfix) with ESMTP id D86E321F8CDB for <alto@ietf.org>; Wed,  7 Nov 2012 12:06:38 -0800 (PST)
Received: from dhcp-1123.meeting.ietf.org ([130.129.17.35]) by mail6.atlas.pipex.net with esmtpa (Exim 4.71) (envelope-from <ben@niven-jenkins.co.uk>) id 1TWBtV-0006US-DD for alto@ietf.org; Wed, 07 Nov 2012 20:06:37 +0000
From: Ben Niven-Jenkins <ben@niven-jenkins.co.uk>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Date: Wed, 7 Nov 2012 20:06:35 +0000
Message-Id: <ADD18858-3A25-4DA2-A59E-D3BCE0936744@niven-jenkins.co.uk>
To: alto <alto@ietf.org>
Mime-Version: 1.0 (Apple Message framework v1085)
X-Mailer: Apple Mail (2.1085)
X-Mailcore-Auth: 9600544
X-Mailcore-Domain: 172912
Subject: [alto] ALTO error responses & HTTP's Accept header
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Wed, 07 Nov 2012 20:06:39 -0000

Colleagues,

During the ALTO WG session today, a question was raised against the ALTO =
protocol spec about what should the behaviour be when an error occurs =
but the client included an Accept: header in its request but =
application/alto-error+json was not included in the Accept header.

RFC2616 states:
   If an Accept-Encoding field is present in a request, and if the
   server cannot send a response which is acceptable according to the
   Accept-Encoding header, then the server SHOULD send an error response
   with the 406 (Not Acceptable) status code.

However, draft-ietf-httpbis-p2-semantics (which is currently in WG LC =
and will obsolete RFC2616 when published) states:
   If an Accept header field is
   present in a request and none of the available representations for
   the response have a media type that is listed as acceptable, the
   origin server MAY either honor the Accept header field by sending a
   406 (Not Acceptable) response or disregard the Accept header field by
   treating the response as if it is not subject to content negotiation.=20=


Which confirms what I said at the mic that in the case being considered =
the ALTO server is allowed to return a response with a Content-Type of =
application/alto-error+json if an ALTO error occurs and the client has =
included an Accept header in its request but not included =
application/alto-error+json in the Accept header.

Ben


From diego@tid.es  Wed Nov  7 12:29:27 2012
Return-Path: <diego@tid.es>
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 97F8E21F8B6E for <alto@ietfa.amsl.com>; Wed,  7 Nov 2012 12:29:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.452
X-Spam-Level: 
X-Spam-Status: No, score=-5.452 tagged_above=-999 required=5 tests=[AWL=-0.343, BAYES_05=-1.11, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CXRLBxS5jjKA for <alto@ietfa.amsl.com>; Wed,  7 Nov 2012 12:29:26 -0800 (PST)
Received: from tidos.tid.es (tidos.tid.es [195.235.93.44]) by ietfa.amsl.com (Postfix) with ESMTP id 90E2621F8A26 for <alto@ietf.org>; Wed,  7 Nov 2012 12:29:24 -0800 (PST)
Received: from sbrightmailg01.hi.inet (sbrightmailg01.hi.inet [10.95.64.104]) by tid.hi.inet (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0MD400BP4WWXR5@tid.hi.inet> for alto@ietf.org; Wed, 07 Nov 2012 21:29:21 +0100 (MET)
Received: from tid (tid.hi.inet [10.95.64.10])	by sbrightmailg01.hi.inet (Symantec Messaging Gateway) with SMTP id 7F.A4.03143.1A4CA905; Wed, 07 Nov 2012 21:29:21 +0100 (CET)
Received: from correo.tid.es (mailhost.hi.inet [10.95.64.100]) by tid.hi.inet (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPS id <0MD400BP1WWWR5@tid.hi.inet> for alto@ietf.org; Wed, 07 Nov 2012 21:29:20 +0100 (MET)
Received: from EX10-MB2-MAD.hi.inet ([169.254.2.64]) by ex10-htcas4-mad.hi.inet ([::1]) with mapi id 14.02.0318.004; Wed, 07 Nov 2012 21:29:20 +0100
Date: Wed, 07 Nov 2012 20:29:20 +0000
From: "Diego R. Lopez" <diego@tid.es>
X-Originating-IP: [10.95.64.115]
To: "alto@ietf.org" <alto@ietf.org>
Message-id: <E6D8B95470ED0845B3376F61DCAB1A0452AD8F3F@EX10-MB2-MAD.hi.inet>
MIME-version: 1.0
Content-type: multipart/alternative; boundary="Boundary_(ID_CiDtgdMeBjIEzt8Gj8kIgA)"
Content-language: en-US
Accept-Language: en-US
Thread-topic: [apps-discuss] Simple Web Discovery (SWD) Enabling Hosted Deployments
Thread-index: AQHNvSaQj1l3dqGb+EuDplkgTnvJfw==
X-AuditID: 0a5f4068-b7f746d000000c47-32-509ac4a1d0b2
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrPKsWRmVeSWpSXmKPExsXCFe/ApbvwyKwAgz27OSwebt/L6sDosWTJ T6YAxigum5TUnMyy1CJ9uwSujAWd95kL3s9hrGib9oexgfFwF2MXIyeHhICJxPPda9ggbDGJ C/fWA9lcHEICGxgltnefZYRwvjNKLPn4iAXCmcYo0f3wAlgLi4CqRPfLrWCj2IDsR82/2UFs YYFQiUdrdzNBjFWQ+HPuMQuILSKgLPFh0xewOK+At8SkdTtYIWxBiR+T74HVMAvkSmzt2cgI YYtLNLfeBIszAp33/dQaJog5oRIHzj1j7mLkALL1JO50GUKsEpBYsuc8M4QtKvHy8T+w8UIC LhLnn/cwTmAUmYVk2ywk22Yh2QZhG0i8PzefGcLWlli28DWUrS+x8ctZqHoziYaWn6zIahYw cqxiFCtOKspMzyjJTczMSTcw1MvI1MvMSy3ZxAiJsYwdjMt3qhxiFOBgVOLh5ZCZFSDEmlhW XJl7iFGSg0lJlNdvF1CILyk/pTIjsTgjvqg0J7X4EKMEB7OSCO/PNUA53pTEyqrUonyYlAwH h5IEr91hoJRgUWp6akVaZg4wkcCkmTg4Qdp5gNptQGp4iwsSc4sz0yHypxhVOa78m/uQUYgl Lz8vVUqcVxKkSACkKKM0D27OK0ZxoIOFectAsjzAVAg34RXQcCag4cXXZoAML0lESEk1MLK7 cTr9qH3VMS/nRINLjpMi85NXl097d+i7Hi54z1FVtVeDO57T6bbseVk7ddP0X0u6dOLsVlwQ KF2zdjqP1LLZnKJ/lp54tcUwuNNd4m/FjNbiSQdXFp2eZ/bW+ePfx3KLv12QmsdedXSegn7j xCKBq+zxj3Rv3beZ/UxsfWbv8+ub2DI+CiqxFGckGmoxFxUnAgAct9fmQgMAAA==
References: <1e8757a8-659a-42d2-9708-309f4b8de076@email.android.com>
Subject: [alto] Fwd: [apps-discuss] Simple Web Discovery (SWD) Enabling Hosted	Deployments
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Wed, 07 Nov 2012 20:29:27 -0000

--Boundary_(ID_CiDtgdMeBjIEzt8Gj8kIgA)
Content-type: text/plain; charset=Windows-1252
Content-transfer-encoding: quoted-printable

Hi,

This is the recent proposal being orginated inside the OpenIDConnect commun=
ity I mentioned at the mike that
could be useful for not requiring an U-NAPTR lookup.

I think it is worth considering as an alternative way for ALTO server disco=
very, since it provides a
simple and  coherent interface (based on HTTP GET) for this purpose.

Be goode,

Begin forwarded message:

From: "Paul E. Jones" <paulej@packetizer.com<mailto:paulej@packetizer.com>>
Subject: [apps-discuss] Fwd: FW: Simple Web Discovery (SWD) Enabling Hosted=
 Deployments
Date: 5 November 2012 08:44:11.000 EST
To: <apps-discuss@ietf.org<mailto:apps-discuss@ietf.org>>

FYI

________________________________
From: Mike Jones <Michael.Jones@microsoft.com<mailto:Michael.Jones@microsof=
t.com>>
Sent: Mon Nov 05 07:55:14 EST 2012
To: "Paul E. Jones" <paulej@packetizer.com<mailto:paulej@packetizer.com>>
Subject: FW: Simple Web Discovery (SWD) Enabling Hosted Deployments

Paul, could you do me a favor and forward this note to the apps-discuss lis=
t so people have context on why I updated SWD?  For some reason, the list d=
oesn=92t appear to be accepting my message.

                                                            Thanks,
                                                            -- Mike

From: Mike Jones
Sent: Sunday, November 04, 2012 9:21 PM
To: apps-discuss@ietf.org<mailto:apps-discuss@ietf.org>
Subject: Simple Web Discovery (SWD) Enabling Hosted Deployments

I=92ve updated the Simple Web Discovery (SWD)<http://tools.ietf.org/html/dr=
aft-jones-simple-web-discovery> specification to incorporate a means of per=
forming discovery on domains for which it may not be possible to create a .=
well-known endpoint.  This can often be the case for hosted domains, where =
it is common for e-mail to be provided but no web server.  This solution wa=
s developed in discussions by the OpenID Connect<http://openid.net/connect/=
> working group.

This draft is being published now to facilitate discussions of the need to =
enable discovery for hosted domains and possible solutions for doing so at =
the IETF Applications Area working group meeting at IETF 85 in Atlanta<http=
://www.ietf.org/meeting/85/>.

The updated specification is available at:

=B7        http://tools.ietf.org/html/draft-jones-simple-web-discovery-04

Changes made were:
=B7        Specified that the SWD server for a domain may be located at the=
 simple-web-discovery subdomain of the domain and that SWD clients must fir=
st try the endpoint at the domain and then the endpoint at the subdomain.
=B7        Removed the SWD_service_redirect response, since redirection can=
 be accomplished by pointing the simple-web-discovery subdomain to a differ=
ent location than the domain's host.
=B7        Removed mailto: from examples in favor of bare e-mail address sy=
ntax.
=B7        Specified that SWD servers may also be run on ports other than 4=
43, provided they use TLS on those ports.

An HTML formatted version is available at:

=B7        http://self-issued.info/docs/draft-jones-simple-web-discovery-04=
.html

(This notice was also posted to http://self-issued.info/?p=3D891.)

                                                            -- Mike

_______________________________________________
apps-discuss mailing list
apps-discuss@ietf.org<mailto:apps-discuss@ietf.org>
https://www.ietf.org/mailman/listinfo/apps-discuss


--
"Esta vez no fallaremos, Doctor Infierno"

Dr Diego R. Lopez
Telefonica I+D
http://people.tid.es/diego.lopez/

e-mail: diego@tid.es
Tel:    +34 913 129 041
Mobile: +34 682 051 091
-----------------------------------------


________________________________

Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nu=
estra pol=EDtica de env=EDo y recepci=F3n de correo electr=F3nico en el enl=
ace situado m=E1s abajo.
This message is intended exclusively for its addressee. We only send and re=
ceive email on the basis of the terms set out at:
http://www.tid.es/ES/PAGINAS/disclaimer.aspx

--Boundary_(ID_CiDtgdMeBjIEzt8Gj8kIgA)
Content-id: <A3D6AA696FCC35439840FED06EBF8B86@hi.inet>
Content-type: text/html; charset=Windows-1252
Content-transfer-encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
</head>
<body style=3D"word-wrap:break-word">
Hi,
<div><br>
</div>
<div>This is the recent proposal being orginated inside the OpenIDConnect c=
ommunity I mentioned at the mike that</div>
<div>could be useful for not requiring an U-NAPTR lookup.</div>
<div><br>
</div>
<div>I think it is worth considering&nbsp;as an alternative way for ALTO se=
rver discovery, since it provides a&nbsp;</div>
<div>simple and &nbsp;coherent interface (based&nbsp;on HTTP GET) for this =
purpose.</div>
<div>
<div><br>
</div>
<div>Be goode,</div>
<div><br>
<div>Begin forwarded message:</div>
<br class=3D"Apple-interchange-newline">
<blockquote type=3D"cite">
<div style=3D"margin-top:0px; margin-right:0px; margin-bottom:0px; margin-l=
eft:0px">
<span style=3D"font-family:'Helvetica'; font-size:medium"><b>From: </b></sp=
an><span style=3D"font-family:'Helvetica'; font-size:medium">&quot;Paul E. =
Jones&quot; &lt;<a href=3D"mailto:paulej@packetizer.com">paulej@packetizer.=
com</a>&gt;<br>
</span></div>
<div style=3D"margin-top:0px; margin-right:0px; margin-bottom:0px; margin-l=
eft:0px">
<span style=3D"font-family:'Helvetica'; font-size:medium"><b>Subject: </b><=
/span><span style=3D"font-family:'Helvetica'; font-size:medium"><b>[apps-di=
scuss] Fwd: FW: Simple Web Discovery (SWD) Enabling Hosted Deployments</b><=
br>
</span></div>
<div style=3D"margin-top:0px; margin-right:0px; margin-bottom:0px; margin-l=
eft:0px">
<span style=3D"font-family:'Helvetica'; font-size:medium"><b>Date: </b></sp=
an><span style=3D"font-family:'Helvetica'; font-size:medium">5 November 201=
2 08:44:11.000 EST<br>
</span></div>
<div style=3D"margin-top:0px; margin-right:0px; margin-bottom:0px; margin-l=
eft:0px">
<span style=3D"font-family:'Helvetica'; font-size:medium"><b>To: </b></span=
><span style=3D"font-family:'Helvetica'; font-size:medium">&lt;<a href=3D"m=
ailto:apps-discuss@ietf.org">apps-discuss@ietf.org</a>&gt;<br>
</span></div>
<br>
<div>
<div>FYI<br>
<br>
<div style=3D"font-size:10.0pt; font-family:&quot;Tahoma&quot;,&quot;sans-s=
erif&quot;; padding:3.0pt 0in 0in 0in">
<hr style=3D"border:none; border-top:solid #B5C4DF 1.0pt">
<b>From:</b> Mike Jones &lt;<a href=3D"mailto:Michael.Jones@microsoft.com">=
Michael.Jones@microsoft.com</a>&gt;<br>
<b>Sent:</b> Mon Nov 05 07:55:14 EST 2012<br>
<b>To:</b> &quot;Paul E. Jones&quot; &lt;<a href=3D"mailto:paulej@packetize=
r.com">paulej@packetizer.com</a>&gt;<br>
<b>Subject:</b> FW: Simple Web Discovery (SWD) Enabling Hosted Deployments<=
br>
</div>
<br>
<style>
<!--
@font-face
	{font-family:Wingdings}
@font-face
	{font-family:Wingdings}
@font-face
	{font-family:Calibri}
@font-face
	{font-family:Tahoma}
@font-face
	{font-family:Verdana}
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin-top:0in;
	margin-right:0in;
	margin-bottom:10.0pt;
	margin-left:0in;
	line-height:115%;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif"}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline}
tt
	{font-family:"Courier New";
	color:#003366}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{margin-top:0in;
	margin-right:0in;
	margin-bottom:10.0pt;
	margin-left:.5in;
	line-height:115%;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif"}
span.EmailStyle19
	{font-family:"Calibri","sans-serif";
	color:windowtext}
span.EmailStyle20
	{font-family:"Calibri","sans-serif";
	color:#1F497D}
.MsoChpDefault
	{font-size:10.0pt}
@page WordSection1
	{margin:1.0in 1.0in 1.0in 1.0in}
div.WordSection1
	{}
ol
	{margin-bottom:0in}
ul
	{margin-bottom:0in}
-->
</style>
<div lang=3D"EN-US">
<div class=3D"WordSection1">
<p class=3D"MsoNormal" style=3D"margin-bottom:0in; margin-bottom:.0001pt"><=
span style=3D"color:#1F497D">Paul, could you do me a favor and forward this=
 note to the apps-discuss list so people have context on why I updated SWD?=
&nbsp; For some reason, the list doesn=92t appear
 to be accepting my message.</span></p>
<p class=3D"MsoNormal" style=3D"margin-bottom:0in; margin-bottom:.0001pt"><=
span style=3D"color:#1F497D">&nbsp;</span></p>
<p class=3D"MsoNormal" style=3D"margin-bottom:0in; margin-bottom:.0001pt"><=
span style=3D"color:#1F497D">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; Thanks,</span></p>
<p class=3D"MsoNormal" style=3D"margin-bottom:0in; margin-bottom:.0001pt"><=
span style=3D"color:#1F497D">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp; -- Mike</span></p>
<p class=3D"MsoNormal" style=3D"margin-bottom:0in; margin-bottom:.0001pt"><=
span style=3D"color:#1F497D">&nbsp;</span></p>
<div>
<div style=3D"border-right-style:none; border-bottom-style:none; border-lef=
t-style:none; border-width:initial; border-color:initial; border-top-style:=
solid; border-top-color:rgb(181,196,223); border-top-width:1pt; padding-top=
:3pt; padding-right:0in; padding-bottom:0in; padding-left:0in; position:sta=
tic; z-index:auto">
<p class=3D"MsoNormal" style=3D"margin-bottom:0in; margin-bottom:.0001pt; l=
ine-height:normal">
<b><span style=3D"font-size:10.0pt; font-family:&quot;Tahoma&quot;,&quot;sa=
ns-serif&quot;">From:</span></b><span style=3D"font-size:10.0pt; font-famil=
y:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Mike Jones
<br>
<b>Sent:</b> Sunday, November 04, 2012 9:21 PM<br>
<b>To:</b> <a href=3D"mailto:apps-discuss@ietf.org">apps-discuss@ietf.org</=
a><br>
<b>Subject:</b> Simple Web Discovery (SWD) Enabling Hosted Deployments</spa=
n></p>
</div>
</div>
<p class=3D"MsoNormal">&nbsp;</p>
<p class=3D"MsoNormal" style=3D"margin-bottom:0in; margin-bottom:.0001pt">I=
=92ve updated the
<a href=3D"http://tools.ietf.org/html/draft-jones-simple-web-discovery">Sim=
ple Web Discovery (SWD)</a> specification to incorporate a means of perform=
ing discovery on domains for which it may not be possible to create a .well=
-known endpoint.&nbsp; This can often be
 the case for hosted domains, where it is common for e-mail to be provided =
but no web server.&nbsp; This solution was developed in discussions by the
<a href=3D"http://openid.net/connect/">OpenID Connect</a> working group.</p=
>
<p class=3D"MsoNormal" style=3D"margin-bottom:0in; margin-bottom:.0001pt">&=
nbsp;</p>
<p class=3D"MsoNormal" style=3D"margin-bottom:0in; margin-bottom:.0001pt">T=
his draft is being published now to facilitate discussions of the need to e=
nable discovery for hosted domains and possible solutions for doing so at t=
he IETF Applications Area working group
 meeting at <a href=3D"http://www.ietf.org/meeting/85/">IETF 85 in Atlanta<=
/a>.</p>
<p class=3D"MsoNormal" style=3D"margin-bottom:0in; margin-bottom:.0001pt">&=
nbsp;</p>
<p class=3D"MsoNormal" style=3D"margin-bottom:0in; margin-bottom:.0001pt">T=
he updated specification is available at:</p>
<p class=3D"MsoListParagraph" style=3D"margin-bottom:0in; margin-bottom:.00=
01pt; text-indent:-.25in">
<span style=3D"font-family:Symbol"><span style=3D"">=B7<span style=3D"font:=
7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;
</span></span></span><a href=3D"http://tools.ietf.org/html/draft-jones-simp=
le-web-discovery-04">http://tools.ietf.org/html/draft-jones-simple-web-disc=
overy-04</a></p>
<p class=3D"MsoNormal" style=3D"margin-bottom:0in; margin-bottom:.0001pt">&=
nbsp;</p>
<p class=3D"MsoNormal" style=3D"margin-bottom:0in; margin-bottom:.0001pt">C=
hanges made were:</p>
<p class=3D"MsoNormal" style=3D"margin-right:0in; margin-bottom:0in; margin=
-left:.25in; margin-bottom:.0001pt; text-indent:0in; line-height:normal">
<span lang=3D"EN" style=3D"font-size:10.0pt; font-family:Symbol; color:blac=
k"><span style=3D"">=B7<span style=3D"font:7.0pt &quot;Times New Roman&quot=
;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><span lang=3D"EN" style=3D"font-family:&quot;Verdana&q=
uot;,&quot;sans-serif&quot;; color:black">Specified that the SWD server for=
 a domain may be located at the
</span><span lang=3D"EN" style=3D"font-family:&quot;Courier New&quot;; colo=
r:#003366">simple-web-discovery</span><span lang=3D"EN" style=3D"font-famil=
y:&quot;Verdana&quot;,&quot;sans-serif&quot;; color:black"> subdomain of th=
e domain and that SWD clients must first try the endpoint at the domain
 and then the endpoint at the subdomain. </span></p>
<p class=3D"MsoNormal" style=3D"margin-right:0in; margin-bottom:0in; margin=
-left:.25in; margin-bottom:.0001pt; text-indent:0in; line-height:normal">
<span lang=3D"EN" style=3D"font-size:10.0pt; font-family:Symbol; color:blac=
k"><span style=3D"">=B7<span style=3D"font:7.0pt &quot;Times New Roman&quot=
;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><span lang=3D"EN" style=3D"font-family:&quot;Verdana&q=
uot;,&quot;sans-serif&quot;; color:black">Removed the
</span><span lang=3D"EN" style=3D"font-family:&quot;Courier New&quot;; colo=
r:#003366">SWD_service_redirect</span><span lang=3D"EN" style=3D"font-famil=
y:&quot;Verdana&quot;,&quot;sans-serif&quot;; color:black"> response, since=
 redirection can be accomplished by pointing the
</span><span lang=3D"EN" style=3D"font-family:&quot;Courier New&quot;; colo=
r:#003366">simple-web-discovery</span><span lang=3D"EN" style=3D"font-famil=
y:&quot;Verdana&quot;,&quot;sans-serif&quot;; color:black"> subdomain to a =
different location than the domain's host.
</span></p>
<p class=3D"MsoNormal" style=3D"margin-right:0in; margin-bottom:0in; margin=
-left:.25in; margin-bottom:.0001pt; text-indent:0in; line-height:normal">
<span lang=3D"EN" style=3D"font-size:10.0pt; font-family:Symbol; color:blac=
k"><span style=3D"">=B7<span style=3D"font:7.0pt &quot;Times New Roman&quot=
;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><span lang=3D"EN" style=3D"font-family:&quot;Verdana&q=
uot;,&quot;sans-serif&quot;; color:black">Removed
</span><span lang=3D"EN" style=3D"font-family:&quot;Courier New&quot;; colo=
r:#003366">mailto:</span><span lang=3D"EN" style=3D"font-family:&quot;Verda=
na&quot;,&quot;sans-serif&quot;; color:black"> from examples in favor of ba=
re e-mail address syntax.
</span></p>
<p class=3D"MsoNormal" style=3D"margin-right:0in; margin-bottom:0in; margin=
-left:.25in; margin-bottom:.0001pt; text-indent:0in; line-height:normal">
<span lang=3D"EN" style=3D"font-size:10.0pt; font-family:Symbol; color:blac=
k"><span style=3D"">=B7<span style=3D"font:7.0pt &quot;Times New Roman&quot=
;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><span lang=3D"EN" style=3D"font-family:&quot;Verdana&q=
uot;,&quot;sans-serif&quot;; color:black">Specified that SWD servers may al=
so be run on ports other than 443, provided they use TLS on those ports.</s=
pan></p>
<p class=3D"MsoNormal" style=3D"margin-bottom:0in; margin-bottom:.0001pt">&=
nbsp;</p>
<p class=3D"MsoNormal" style=3D"margin-bottom:0in; margin-bottom:.0001pt">A=
n HTML formatted version is available at:</p>
<p class=3D"MsoListParagraph" style=3D"margin-bottom:0in; margin-bottom:.00=
01pt; text-indent:-.25in">
<span style=3D"font-family:Symbol"><span style=3D"">=B7<span style=3D"font:=
7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;
</span></span></span><a href=3D"http://self-issued.info/docs/draft-jones-si=
mple-web-discovery-04.html">http://self-issued.info/docs/draft-jones-simple=
-web-discovery-04.html</a></p>
<p class=3D"MsoNormal" style=3D"margin-bottom:0in; margin-bottom:.0001pt">&=
nbsp;</p>
<p class=3D"MsoNormal" style=3D"margin-bottom:0in; margin-bottom:.0001pt">(=
This notice was also posted to
<a href=3D"http://self-issued.info/?p=3D891">http://self-issued.info/?p=3D8=
91</a>.)</p>
<p class=3D"MsoNormal" style=3D"margin-bottom:0in; margin-bottom:.0001pt">&=
nbsp;</p>
<p class=3D"MsoNormal" style=3D"margin-bottom:0in; margin-bottom:.0001pt">&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -- Mike</p>
<p class=3D"MsoNormal" style=3D"margin-bottom:0in; margin-bottom:.0001pt">&=
nbsp;</p>
</div>
</div>
</div>
</div>
_______________________________________________<br>
apps-discuss mailing list<br>
<a href=3D"mailto:apps-discuss@ietf.org">apps-discuss@ietf.org</a><br>
https://www.ietf.org/mailman/listinfo/apps-discuss<br>
</blockquote>
</div>
<br>
<div><span class=3D"Apple-style-span" style=3D"border-collapse:separate; co=
lor:rgb(0,0,0); font-family:Helvetica; font-style:normal; font-variant:norm=
al; font-weight:normal; letter-spacing:normal; line-height:normal; orphans:=
2; text-indent:0px; text-transform:none; white-space:normal; widows:2; word=
-spacing:0px; font-size:medium"><span class=3D"Apple-style-span" style=3D"b=
order-collapse:separate; color:rgb(0,0,0); font-family:Helvetica; font-styl=
e:normal; font-variant:normal; font-weight:normal; letter-spacing:normal; l=
ine-height:normal; orphans:2; text-indent:0px; text-transform:none; white-s=
pace:normal; widows:2; word-spacing:0px; font-size:medium">
<div style=3D"word-wrap:break-word"><span class=3D"Apple-style-span" style=
=3D"border-collapse:separate; color:rgb(0,0,0); font-family:Helvetica; font=
-style:normal; font-variant:normal; font-weight:normal; letter-spacing:norm=
al; line-height:normal; orphans:2; text-indent:0px; text-transform:none; wh=
ite-space:normal; widows:2; word-spacing:0px; font-size:medium">
<div style=3D"word-wrap:break-word"><br>
--<br>
&quot;Esta vez no fallaremos, Doctor Infierno&quot;<br>
<br>
Dr Diego R. Lopez<br>
Telefonica I&#43;D</div>
<div style=3D"word-wrap:break-word"><a href=3D"http://people.tid.es/diego.l=
opez/">http://people.tid.es/diego.lopez/</a><br>
<br>
e-mail: diego@tid.es<br>
Tel: &nbsp; &nbsp;&#43;34 913 129 041<br>
Mobile: &#43;34 682 051 091<br>
-----------------------------------------</div>
</span></div>
</span></span></div>
<br>
</div>
<br>
<hr>
<font face=3D"Arial" color=3D"Gray" size=3D"1"><br>
Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nu=
estra pol=EDtica de env=EDo y recepci=F3n de correo electr=F3nico en el enl=
ace situado m=E1s abajo.<br>
This message is intended exclusively for its addressee. We only send and re=
ceive email on the basis of the terms set out at:<br>
http://www.tid.es/ES/PAGINAS/disclaimer.aspx<br>
</font>
</body>
</html>

--Boundary_(ID_CiDtgdMeBjIEzt8Gj8kIgA)--

From michael.scharf@alcatel-lucent.com  Wed Nov  7 12:50:39 2012
Return-Path: <michael.scharf@alcatel-lucent.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 5BE3621F8C3E for <alto@ietfa.amsl.com>; Wed,  7 Nov 2012 12:50:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.482
X-Spam-Level: 
X-Spam-Status: No, score=-9.482 tagged_above=-999 required=5 tests=[AWL=0.766,  BAYES_00=-2.599, HELO_EQ_FR=0.35, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JUqnfrn7BVu6 for <alto@ietfa.amsl.com>; Wed,  7 Nov 2012 12:50:38 -0800 (PST)
Received: from smail3.alcatel.fr (smail3.alcatel.fr [64.208.49.56]) by ietfa.amsl.com (Postfix) with ESMTP id C978321F8C27 for <alto@ietf.org>; Wed,  7 Nov 2012 12:50:37 -0800 (PST)
Received: from FRMRSSXCHHUB01.dc-m.alcatel-lucent.com (FRMRSSXCHHUB01.dc-m.alcatel-lucent.com [135.120.45.61]) by smail3.alcatel.fr (8.14.3/8.14.3/ICT) with ESMTP id qA7KoO4a007674 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Wed, 7 Nov 2012 21:50:25 +0100
Received: from FRMRSSXCHMBSE3.dc-m.alcatel-lucent.com ([135.120.45.56]) by FRMRSSXCHHUB01.dc-m.alcatel-lucent.com ([135.120.45.61]) with mapi; Wed, 7 Nov 2012 21:50:24 +0100
From: "Scharf, Michael (Michael)" <michael.scharf@alcatel-lucent.com>
To: "Diego R. Lopez" <diego@tid.es>, "alto@ietf.org" <alto@ietf.org>
Date: Wed, 7 Nov 2012 21:50:24 +0100
Thread-Topic: [alto] Fwd: [apps-discuss] Simple Web Discovery (SWD) Enabling Hosted	Deployments
Thread-Index: AQHNvSaQj1l3dqGb+EuDplkgTnvJf5fe1YPd
Message-ID: <2A886F9088894347A3BE0CC5B7A85F3E9AA0F3999B@FRMRSSXCHMBSE3.dc-m.alcatel-lucent.com>
References: <1e8757a8-659a-42d2-9708-309f4b8de076@email.android.com>, <E6D8B95470ED0845B3376F61DCAB1A0452AD8F3F@EX10-MB2-MAD.hi.inet>
In-Reply-To: <E6D8B95470ED0845B3376F61DCAB1A0452AD8F3F@EX10-MB2-MAD.hi.inet>
Accept-Language: de-DE, en-US
Content-Language: de-DE
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: de-DE, en-US
Content-Type: multipart/alternative; boundary="_000_2A886F9088894347A3BE0CC5B7A85F3E9AA0F3999BFRMRSSXCHMBSE_"
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.69 on 155.132.188.83
Subject: Re: [alto] Fwd: [apps-discuss] Simple Web Discovery (SWD) Enabling	Hosted	Deployments
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Wed, 07 Nov 2012 20:50:39 -0000

--_000_2A886F9088894347A3BE0CC5B7A85F3E9AA0F3999BFRMRSSXCHMBSE_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

Hi all,

After briefly scanning through draft-jones-simple-web-discovery, which seem=
s to be an individual draft, I wonder how the ALTO service would be registe=
red in this solution. The text states: "The definition of URIs used to iden=
tify principals and services are outside the scope of this specification." =
If such issues are not clear as of now, it is unclear to me whether this is=
 indeed a mature technology.

At first sight, compared to that, the U-NAPTR lookup is a well-understood m=
echanism used by other IETF protocols with similar requirements like ALTO.

Michael




________________________________
Von: alto-bounces@ietf.org [alto-bounces@ietf.org] im Auftrag von Diego R. =
Lopez [diego@tid.es]
Gesendet: Mittwoch, 7. November 2012 21:29
An: alto@ietf.org
Betreff: [alto] Fwd: [apps-discuss] Simple Web Discovery (SWD) Enabling Hos=
ted Deployments

Hi,

This is the recent proposal being orginated inside the OpenIDConnect commun=
ity I mentioned at the mike that
could be useful for not requiring an U-NAPTR lookup.

I think it is worth considering as an alternative way for ALTO server disco=
very, since it provides a
simple and  coherent interface (based on HTTP GET) for this purpose.

Be goode,

Begin forwarded message:

From: "Paul E. Jones" <paulej@packetizer.com<mailto:paulej@packetizer.com>>
Subject: [apps-discuss] Fwd: FW: Simple Web Discovery (SWD) Enabling Hosted=
 Deployments
Date: 5 November 2012 08:44:11.000 EST
To: <apps-discuss@ietf.org<mailto:apps-discuss@ietf.org>>

FYI

________________________________
From: Mike Jones <Michael.Jones@microsoft.com<mailto:Michael.Jones@microsof=
t.com>>
Sent: Mon Nov 05 07:55:14 EST 2012
To: "Paul E. Jones" <paulej@packetizer.com<mailto:paulej@packetizer.com>>
Subject: FW: Simple Web Discovery (SWD) Enabling Hosted Deployments

Paul, could you do me a favor and forward this note to the apps-discuss lis=
t so people have context on why I updated SWD?  For some reason, the list d=
oesn=92t appear to be accepting my message.

                                                            Thanks,
                                                            -- Mike

From: Mike Jones
Sent: Sunday, November 04, 2012 9:21 PM
To: apps-discuss@ietf.org<mailto:apps-discuss@ietf.org>
Subject: Simple Web Discovery (SWD) Enabling Hosted Deployments

I=92ve updated the Simple Web Discovery (SWD)<http://tools.ietf.org/html/dr=
aft-jones-simple-web-discovery> specification to incorporate a means of per=
forming discovery on domains for which it may not be possible to create a .=
well-known endpoint.  This can often be the case for hosted domains, where =
it is common for e-mail to be provided but no web server.  This solution wa=
s developed in discussions by the OpenID Connect<http://openid.net/connect/=
> working group.

This draft is being published now to facilitate discussions of the need to =
enable discovery for hosted domains and possible solutions for doing so at =
the IETF Applications Area working group meeting at IETF 85 in Atlanta<http=
://www.ietf.org/meeting/85/>.

The updated specification is available at:

=95        http://tools.ietf.org/html/draft-jones-simple-web-discovery-04

Changes made were:
=95        Specified that the SWD server for a domain may be located at the=
 simple-web-discovery subdomain of the domain and that SWD clients must fir=
st try the endpoint at the domain and then the endpoint at the subdomain.
=95        Removed the SWD_service_redirect response, since redirection can=
 be accomplished by pointing the simple-web-discovery subdomain to a differ=
ent location than the domain's host.
=95        Removed mailto: from examples in favor of bare e-mail address sy=
ntax.
=95        Specified that SWD servers may also be run on ports other than 4=
43, provided they use TLS on those ports.

An HTML formatted version is available at:

=95        http://self-issued.info/docs/draft-jones-simple-web-discovery-04=
.html

(This notice was also posted to http://self-issued.info/?p=3D891.)

                                                            -- Mike

_______________________________________________
apps-discuss mailing list
apps-discuss@ietf.org<mailto:apps-discuss@ietf.org>
https://www.ietf.org/mailman/listinfo/apps-discuss


--
"Esta vez no fallaremos, Doctor Infierno"

Dr Diego R. Lopez
Telefonica I+D
http://people.tid.es/diego.lopez/

e-mail: diego@tid.es
Tel:    +34 913 129 041
Mobile: +34 682 051 091
-----------------------------------------


________________________________

Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nu=
estra pol=EDtica de env=EDo y recepci=F3n de correo electr=F3nico en el enl=
ace situado m=E1s abajo.
This message is intended exclusively for its addressee. We only send and re=
ceive email on the basis of the terms set out at:
http://www.tid.es/ES/PAGINAS/disclaimer.aspx

--_000_2A886F9088894347A3BE0CC5B7A85F3E9AA0F3999BFRMRSSXCHMBSE_
Content-Type: text/html; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

<html dir=3D"ltr"><head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
<meta content=3D"MSHTML 6.00.6000.17114" name=3D"GENERATOR">
<style id=3D"owaTempEditStyle"></style><style title=3D"owaParaStyle"><!--P =
{
	MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px
}
--></style>
</head>
<body style=3D"WORD-WRAP: break-word" ocsi=3D"x">
<div style=3D"FONT-SIZE: x-small; COLOR: #000000; DIRECTION: ltr; FONT-FAMI=
LY: Tahoma">
<div>Hi all,</div>
<div><font face=3D"tahoma"></font>&nbsp;</div>
<div><font face=3D"tahoma">After briefly scanning through draft-jones-simpl=
e-web-discovery, which seems to be an individual draft,</font><font face=3D=
"tahoma">&nbsp;I wonder how&nbsp;the ALTO service&nbsp;would be registered =
in this solution. The text states: &quot;The definition
 of URIs used to identify principals and services are outside the scope of =
this specification.&quot; If such issues are not clear as of now, it is unc=
lear to me whether this is indeed a mature technology.</font></div>
<div dir=3D"ltr"><font face=3D"tahoma"></font>&nbsp;</div>
<div dir=3D"ltr"><font face=3D"tahoma">At first sight, compared to that, th=
e U-NAPTR lookup is a well-understood&nbsp;mechanism used by other IETF pro=
tocols with similar requirements like ALTO.</font></div>
<div dir=3D"ltr"><font face=3D"tahoma"></font>&nbsp;</div>
<div dir=3D"ltr"><font face=3D"tahoma">Michael</font></div>
<div dir=3D"ltr"><font face=3D"tahoma"></font>&nbsp;</div>
<div dir=3D"ltr"><font face=3D"tahoma"></font>&nbsp;</div>
<div dir=3D"ltr"><font face=3D"tahoma"></font>&nbsp;</div>
<div dir=3D"ltr"><font face=3D"tahoma"></font>&nbsp;</div>
<div id=3D"divRpF977929" style=3D"DIRECTION: ltr">
<hr tabindex=3D"-1">
<font face=3D"Tahoma" color=3D"#000000" size=3D"2"><b>Von:</b> alto-bounces=
@ietf.org [alto-bounces@ietf.org] im Auftrag von Diego R. Lopez [diego@tid.=
es]<br>
<b>Gesendet:</b> Mittwoch, 7. November 2012 21:29<br>
<b>An:</b> alto@ietf.org<br>
<b>Betreff:</b> [alto] Fwd: [apps-discuss] Simple Web Discovery (SWD) Enabl=
ing Hosted Deployments<br>
</font><br>
</div>
<div></div>
<div>Hi,
<div><br>
</div>
<div>This is the recent proposal being orginated inside the OpenIDConnect c=
ommunity I mentioned at the mike that</div>
<div>could be useful for not requiring an U-NAPTR lookup.</div>
<div><br>
</div>
<div>I think it is worth considering&nbsp;as an alternative way for ALTO se=
rver discovery, since it provides a&nbsp;</div>
<div>simple and &nbsp;coherent interface (based&nbsp;on HTTP GET) for this =
purpose.</div>
<div>
<div><br>
</div>
<div>Be goode,</div>
<div><br>
<div>Begin forwarded message:</div>
<br class=3D"Apple-interchange-newline">
<blockquote type=3D"cite">
<div style=3D"MARGIN: 0px"><span style=3D"FONT-SIZE: medium; FONT-FAMILY: '=
Helvetica'"><b>From:
</b></span><span style=3D"FONT-SIZE: medium; FONT-FAMILY: 'Helvetica'">&quo=
t;Paul E. Jones&quot; &lt;<a href=3D"mailto:paulej@packetizer.com">paulej@p=
acketizer.com</a>&gt;<br>
</span></div>
<div style=3D"MARGIN: 0px"><span style=3D"FONT-SIZE: medium; FONT-FAMILY: '=
Helvetica'"><b>Subject:
</b></span><span style=3D"FONT-SIZE: medium; FONT-FAMILY: 'Helvetica'"><b>[=
apps-discuss] Fwd: FW: Simple Web Discovery (SWD) Enabling Hosted Deploymen=
ts</b><br>
</span></div>
<div style=3D"MARGIN: 0px"><span style=3D"FONT-SIZE: medium; FONT-FAMILY: '=
Helvetica'"><b>Date:
</b></span><span style=3D"FONT-SIZE: medium; FONT-FAMILY: 'Helvetica'">5 No=
vember 2012 08:44:11.000 EST<br>
</span></div>
<div style=3D"MARGIN: 0px"><span style=3D"FONT-SIZE: medium; FONT-FAMILY: '=
Helvetica'"><b>To:
</b></span><span style=3D"FONT-SIZE: medium; FONT-FAMILY: 'Helvetica'">&lt;=
<a href=3D"mailto:apps-discuss@ietf.org">apps-discuss@ietf.org</a>&gt;<br>
</span></div>
<br>
<div>
<div>FYI<br>
<br>
<div style=3D"PADDING-RIGHT: 0in; PADDING-LEFT: 0in; FONT-SIZE: 10pt; PADDI=
NG-BOTTOM: 0in; PADDING-TOP: 3pt; FONT-FAMILY: 'Tahoma','sans-serif'">
<hr style=3D"BORDER-RIGHT: medium none; BORDER-TOP: #b5c4df 1pt solid; BORD=
ER-LEFT: medium none; BORDER-BOTTOM: medium none">
<b>From:</b> Mike Jones &lt;<a href=3D"mailto:Michael.Jones@microsoft.com">=
Michael.Jones@microsoft.com</a>&gt;<br>
<b>Sent:</b> Mon Nov 05 07:55:14 EST 2012<br>
<b>To:</b> &quot;Paul E. Jones&quot; &lt;<a href=3D"mailto:paulej@packetize=
r.com">paulej@packetizer.com</a>&gt;<br>
<b>Subject:</b> FW: Simple Web Discovery (SWD) Enabling Hosted Deployments<=
br>
</div>
<br>
<style>@font-face {
	font-family: Wingdings;
}
@font-face {
	font-family: Wingdings;
}
@font-face {
	font-family: Calibri;
}
@font-face {
	font-family: Tahoma;
}
@font-face {
	font-family: Verdana;
}
@page WordSection1 {margin: 1.0in 1.0in 1.0in 1.0in; }
P.MsoNormal {
	FONT-SIZE: 11pt; MARGIN: 0in 0in 10pt; LINE-HEIGHT: 115%; FONT-FAMILY: "Ca=
libri","sans-serif"
}
LI.MsoNormal {
	FONT-SIZE: 11pt; MARGIN: 0in 0in 10pt; LINE-HEIGHT: 115%; FONT-FAMILY: "Ca=
libri","sans-serif"
}
DIV.MsoNormal {
	FONT-SIZE: 11pt; MARGIN: 0in 0in 10pt; LINE-HEIGHT: 115%; FONT-FAMILY: "Ca=
libri","sans-serif"
}
A:link {
	COLOR: blue; TEXT-DECORATION: underline
}
SPAN.MsoHyperlink {
	COLOR: blue; TEXT-DECORATION: underline
}
A:visited {
	COLOR: purple; TEXT-DECORATION: underline
}
SPAN.MsoHyperlinkFollowed {
	COLOR: purple; TEXT-DECORATION: underline
}
TT {
	COLOR: #003366; FONT-FAMILY: "Courier New"
}
P.MsoListParagraph {
	FONT-SIZE: 11pt; MARGIN: 0in 0in 10pt 0.5in; LINE-HEIGHT: 115%; FONT-FAMIL=
Y: "Calibri","sans-serif"
}
LI.MsoListParagraph {
	FONT-SIZE: 11pt; MARGIN: 0in 0in 10pt 0.5in; LINE-HEIGHT: 115%; FONT-FAMIL=
Y: "Calibri","sans-serif"
}
DIV.MsoListParagraph {
	FONT-SIZE: 11pt; MARGIN: 0in 0in 10pt 0.5in; LINE-HEIGHT: 115%; FONT-FAMIL=
Y: "Calibri","sans-serif"
}
SPAN.EmailStyle19 {
	COLOR: windowtext; FONT-FAMILY: "Calibri","sans-serif"
}
SPAN.EmailStyle20 {
	COLOR: #1f497d; FONT-FAMILY: "Calibri","sans-serif"
}
.MsoChpDefault {
	FONT-SIZE: 10pt
}
OL {
	MARGIN-BOTTOM: 0in
}
UL {
	MARGIN-BOTTOM: 0in
}
</style>
<div lang=3D"EN-US">
<div class=3D"WordSection1">
<p class=3D"MsoNormal" style=3D"MARGIN-BOTTOM: 0pt"><span style=3D"COLOR: #=
1f497d">Paul, could you do me a favor and forward this note to the apps-dis=
cuss list so people have context on why I updated SWD?&nbsp; For some reaso=
n, the list doesn=92t appear to be accepting
 my message.</span></p>
<p class=3D"MsoNormal" style=3D"MARGIN-BOTTOM: 0pt"><span style=3D"COLOR: #=
1f497d"></span>&nbsp;</p>
<p class=3D"MsoNormal" style=3D"MARGIN-BOTTOM: 0pt"><span style=3D"COLOR: #=
1f497d">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Thanks,</span></p=
>
<p class=3D"MsoNormal" style=3D"MARGIN-BOTTOM: 0pt"><span style=3D"COLOR: #=
1f497d">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -- Mike</spa=
n></p>
<p class=3D"MsoNormal" style=3D"MARGIN-BOTTOM: 0pt"><span style=3D"COLOR: #=
1f497d"></span>&nbsp;</p>
<div>
<div style=3D"PADDING-RIGHT: 0in; BORDER-TOP: rgb(181,196,223) 1pt solid; P=
ADDING-LEFT: 0in; PADDING-BOTTOM: 0in; PADDING-TOP: 3pt; BORDER-RIGHT-STYLE=
: none; BORDER-LEFT-STYLE: none; POSITION: static; BORDER-BOTTOM-STYLE: non=
e">
<p class=3D"MsoNormal" style=3D"MARGIN-BOTTOM: 0pt; LINE-HEIGHT: normal"><b=
><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma','sans-serif'">From:<=
/span></b><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma','sans-serif=
'"> Mike Jones
<br>
<b>Sent:</b> Sunday, November 04, 2012 9:21 PM<br>
<b>To:</b> <a href=3D"mailto:apps-discuss@ietf.org">apps-discuss@ietf.org</=
a><br>
<b>Subject:</b> Simple Web Discovery (SWD) Enabling Hosted Deployments</spa=
n></p>
</div>
</div>
<p class=3D"MsoNormal">&nbsp;</p>
<p class=3D"MsoNormal" style=3D"MARGIN-BOTTOM: 0pt">I=92ve updated the <a h=
ref=3D"http://tools.ietf.org/html/draft-jones-simple-web-discovery" target=
=3D"_blank">
Simple Web Discovery (SWD)</a> specification to incorporate a means of perf=
orming discovery on domains for which it may not be possible to create a .w=
ell-known endpoint.&nbsp; This can often be the case for hosted domains, wh=
ere it is common for e-mail to be provided
 but no web server.&nbsp; This solution was developed in discussions by the=
 <a href=3D"http://openid.net/connect/" target=3D"_blank">
OpenID Connect</a> working group.</p>
<p class=3D"MsoNormal" style=3D"MARGIN-BOTTOM: 0pt">&nbsp;</p>
<p class=3D"MsoNormal" style=3D"MARGIN-BOTTOM: 0pt">This draft is being pub=
lished now to facilitate discussions of the need to enable discovery for ho=
sted domains and possible solutions for doing so at the IETF Applications A=
rea working group meeting at
<a href=3D"http://www.ietf.org/meeting/85/" target=3D"_blank">IETF 85 in At=
lanta</a>.</p>
<p class=3D"MsoNormal" style=3D"MARGIN-BOTTOM: 0pt">&nbsp;</p>
<p class=3D"MsoNormal" style=3D"MARGIN-BOTTOM: 0pt">The updated specificati=
on is available at:</p>
<p class=3D"MsoListParagraph" style=3D"MARGIN-BOTTOM: 0pt; TEXT-INDENT: -0.=
25in"><span style=3D"FONT-FAMILY: Symbol"><span>=B7<span style=3D"FONT: 7pt=
 'Times New Roman'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><a href=3D"http://tools.ietf.org/html/draft-jones-simp=
le-web-discovery-04" target=3D"_blank">http://tools.ietf.org/html/draft-jon=
es-simple-web-discovery-04</a></p>
<p class=3D"MsoNormal" style=3D"MARGIN-BOTTOM: 0pt">&nbsp;</p>
<p class=3D"MsoNormal" style=3D"MARGIN-BOTTOM: 0pt">Changes made were:</p>
<p class=3D"MsoNormal" style=3D"MARGIN-BOTTOM: 0pt; MARGIN-LEFT: 0.25in; TE=
XT-INDENT: 0in; LINE-HEIGHT: normal; MARGIN-RIGHT: 0in">
<span lang=3D"EN" style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Symb=
ol"><span>=B7<span style=3D"FONT: 7pt 'Times New Roman'">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><span lang=3D"EN" style=3D"COLOR: black; FONT-FAMILY: =
'Verdana','sans-serif'">Specified that the SWD server for a domain may be l=
ocated at the
</span><span lang=3D"EN" style=3D"COLOR: #003366; FONT-FAMILY: 'Courier New=
'">simple-web-discovery</span><span lang=3D"EN" style=3D"COLOR: black; FONT=
-FAMILY: 'Verdana','sans-serif'"> subdomain of the domain and that SWD clie=
nts must first try the endpoint at the domain
 and then the endpoint at the subdomain. </span></p>
<p class=3D"MsoNormal" style=3D"MARGIN-BOTTOM: 0pt; MARGIN-LEFT: 0.25in; TE=
XT-INDENT: 0in; LINE-HEIGHT: normal; MARGIN-RIGHT: 0in">
<span lang=3D"EN" style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Symb=
ol"><span>=B7<span style=3D"FONT: 7pt 'Times New Roman'">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><span lang=3D"EN" style=3D"COLOR: black; FONT-FAMILY: =
'Verdana','sans-serif'">Removed the
</span><span lang=3D"EN" style=3D"COLOR: #003366; FONT-FAMILY: 'Courier New=
'">SWD_service_redirect</span><span lang=3D"EN" style=3D"COLOR: black; FONT=
-FAMILY: 'Verdana','sans-serif'"> response, since redirection can be accomp=
lished by pointing the
</span><span lang=3D"EN" style=3D"COLOR: #003366; FONT-FAMILY: 'Courier New=
'">simple-web-discovery</span><span lang=3D"EN" style=3D"COLOR: black; FONT=
-FAMILY: 'Verdana','sans-serif'"> subdomain to a different location than th=
e domain's host.
</span></p>
<p class=3D"MsoNormal" style=3D"MARGIN-BOTTOM: 0pt; MARGIN-LEFT: 0.25in; TE=
XT-INDENT: 0in; LINE-HEIGHT: normal; MARGIN-RIGHT: 0in">
<span lang=3D"EN" style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Symb=
ol"><span>=B7<span style=3D"FONT: 7pt 'Times New Roman'">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><span lang=3D"EN" style=3D"COLOR: black; FONT-FAMILY: =
'Verdana','sans-serif'">Removed
</span><span lang=3D"EN" style=3D"COLOR: #003366; FONT-FAMILY: 'Courier New=
'">mailto:</span><span lang=3D"EN" style=3D"COLOR: black; FONT-FAMILY: 'Ver=
dana','sans-serif'"> from examples in favor of bare e-mail address syntax.
</span></p>
<p class=3D"MsoNormal" style=3D"MARGIN-BOTTOM: 0pt; MARGIN-LEFT: 0.25in; TE=
XT-INDENT: 0in; LINE-HEIGHT: normal; MARGIN-RIGHT: 0in">
<span lang=3D"EN" style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Symb=
ol"><span>=B7<span style=3D"FONT: 7pt 'Times New Roman'">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><span lang=3D"EN" style=3D"COLOR: black; FONT-FAMILY: =
'Verdana','sans-serif'">Specified that SWD servers may also be run on ports=
 other than 443, provided they use TLS on those ports.</span></p>
<p class=3D"MsoNormal" style=3D"MARGIN-BOTTOM: 0pt">&nbsp;</p>
<p class=3D"MsoNormal" style=3D"MARGIN-BOTTOM: 0pt">An HTML formatted versi=
on is available at:</p>
<p class=3D"MsoListParagraph" style=3D"MARGIN-BOTTOM: 0pt; TEXT-INDENT: -0.=
25in"><span style=3D"FONT-FAMILY: Symbol"><span>=B7<span style=3D"FONT: 7pt=
 'Times New Roman'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><a href=3D"http://self-issued.info/docs/draft-jones-si=
mple-web-discovery-04.html" target=3D"_blank">http://self-issued.info/docs/=
draft-jones-simple-web-discovery-04.html</a></p>
<p class=3D"MsoNormal" style=3D"MARGIN-BOTTOM: 0pt">&nbsp;</p>
<p class=3D"MsoNormal" style=3D"MARGIN-BOTTOM: 0pt">(This notice was also p=
osted to <a href=3D"http://self-issued.info/?p=3D891" target=3D"_blank">
http://self-issued.info/?p=3D891</a>.)</p>
<p class=3D"MsoNormal" style=3D"MARGIN-BOTTOM: 0pt">&nbsp;</p>
<p class=3D"MsoNormal" style=3D"MARGIN-BOTTOM: 0pt">&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -- Mike</p>
<p class=3D"MsoNormal" style=3D"MARGIN-BOTTOM: 0pt">&nbsp;</p>
</div>
</div>
</div>
</div>
_______________________________________________<br>
apps-discuss mailing list<br>
<a href=3D"mailto:apps-discuss@ietf.org">apps-discuss@ietf.org</a><br>
https://www.ietf.org/mailman/listinfo/apps-discuss<br>
</blockquote>
</div>
<br>
<div><span class=3D"Apple-style-span" style=3D"WORD-SPACING: 0px; FONT: med=
ium Helvetica; TEXT-TRANSFORM: none; COLOR: rgb(0,0,0); TEXT-INDENT: 0px; W=
HITE-SPACE: normal; LETTER-SPACING: normal; BORDER-COLLAPSE: separate; orph=
ans: 2; widows: 2"><span class=3D"Apple-style-span" style=3D"WORD-SPACING: =
0px; FONT: medium Helvetica; TEXT-TRANSFORM: none; COLOR: rgb(0,0,0); TEXT-=
INDENT: 0px; WHITE-SPACE: normal; LETTER-SPACING: normal; BORDER-COLLAPSE: =
separate; orphans: 2; widows: 2">
<div style=3D"WORD-WRAP: break-word"><span class=3D"Apple-style-span" style=
=3D"WORD-SPACING: 0px; FONT: medium Helvetica; TEXT-TRANSFORM: none; COLOR:=
 rgb(0,0,0); TEXT-INDENT: 0px; WHITE-SPACE: normal; LETTER-SPACING: normal;=
 BORDER-COLLAPSE: separate; orphans: 2; widows: 2">
<div style=3D"WORD-WRAP: break-word"><br>
--<br>
&quot;Esta vez no fallaremos, Doctor Infierno&quot;<br>
<br>
Dr Diego R. Lopez<br>
Telefonica I&#43;D</div>
<div style=3D"WORD-WRAP: break-word"><a href=3D"http://people.tid.es/diego.=
lopez/" target=3D"_blank">http://people.tid.es/diego.lopez/</a><br>
<br>
e-mail: diego@tid.es<br>
Tel: &nbsp; &nbsp;&#43;34 913 129 041<br>
Mobile: &#43;34 682 051 091<br>
-----------------------------------------</div>
</span></div>
</span></span></div>
<br>
</div>
<br>
<hr>
<font face=3D"Arial" color=3D"gray" size=3D"1"><br>
Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nu=
estra pol=EDtica de env=EDo y recepci=F3n de correo electr=F3nico en el enl=
ace situado m=E1s abajo.<br>
This message is intended exclusively for its addressee. We only send and re=
ceive email on the basis of the terms set out at:<br>
http://www.tid.es/ES/PAGINAS/disclaimer.aspx<br>
</font></div>
</div>
</body>
</html>

--_000_2A886F9088894347A3BE0CC5B7A85F3E9AA0F3999BFRMRSSXCHMBSE_--

From w.roome@alcatel-lucent.com  Wed Nov  7 13:19:01 2012
Return-Path: <w.roome@alcatel-lucent.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 2446B21F8C2B for <alto@ietfa.amsl.com>; Wed,  7 Nov 2012 13:19:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EmMx1f+kI8wU for <alto@ietfa.amsl.com>; Wed,  7 Nov 2012 13:19:00 -0800 (PST)
Received: from ihemail3.lucent.com (ihemail3.lucent.com [135.245.0.37]) by ietfa.amsl.com (Postfix) with ESMTP id 95AB621F8C5B for <alto@ietf.org>; Wed,  7 Nov 2012 13:19:00 -0800 (PST)
Received: from usnavsmail2.ndc.alcatel-lucent.com (usnavsmail2.ndc.alcatel-lucent.com [135.3.39.10]) by ihemail3.lucent.com (8.13.8/IER-o) with ESMTP id qA7LIxM8029797 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <alto@ietf.org>; Wed, 7 Nov 2012 15:19:00 -0600 (CST)
Received: from umail.lucent.com (umail-ce2.ndc.lucent.com [135.3.40.63]) by usnavsmail2.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id qA7LIxw2032655 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <alto@ietf.org>; Wed, 7 Nov 2012 15:18:59 -0600
Received: from [135.222.152.198] (wdr-i7mbp.mh.lucent.com [135.222.152.198]) by umail.lucent.com (8.13.8/TPES) with ESMTP id qA7LIujL017998 for <alto@ietf.org>; Wed, 7 Nov 2012 15:18:58 -0600 (CST)
User-Agent: Microsoft-MacOutlook/14.2.4.120824
Date: Wed, 07 Nov 2012 16:19:24 -0500
From: Bill Roome <w.roome@alcatel-lucent.com>
To: <alto@ietf.org>
Message-ID: <CCC038CF.11088%w.roome@alcatel-lucent.com>
Thread-Topic: [alto] Constraints results in E_SYNTAX
In-Reply-To: <mailman.135.1352318425.18836.alto@ietf.org>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.37
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.10
Subject: Re: [alto] Constraints results in E_SYNTAX
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Wed, 07 Nov 2012 21:19:01 -0000

>Message: 4
>Date: Wed, 7 Nov 2012 11:39:03 -0800
>From: Richard Alimi <rich@velvetsea.net>
>..........
>
>The ALTO protocol used to have a reason that was free-form text.  Ted
>Hardie suggested in his review that we drop this to avoid multi-language
>issues (as Richard Yang pointed out).  We then removed the reason field.

I wondered why the reason field was removed! However, that begs the
question of whether a generic "Something's Wrong!" error code is better
than a detailed description in a language that the ALTO user might not
understand.

I suggest restoring the "reason" string. If nothing else, a client
implementer can send it to the ALTO service provider and ask them to
translate it.

	- Bill Roome 



From richard.alimi@gmail.com  Wed Nov  7 14:55:54 2012
Return-Path: <richard.alimi@gmail.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 7E17521F8582 for <alto@ietfa.amsl.com>; Wed,  7 Nov 2012 14:55:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.976
X-Spam-Level: 
X-Spam-Status: No, score=-2.976 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CNSRdCqjcJdx for <alto@ietfa.amsl.com>; Wed,  7 Nov 2012 14:55:50 -0800 (PST)
Received: from mail-wg0-f44.google.com (mail-wg0-f44.google.com [74.125.82.44]) by ietfa.amsl.com (Postfix) with ESMTP id 22FC221F853B for <alto@ietf.org>; Wed,  7 Nov 2012 14:55:49 -0800 (PST)
Received: by mail-wg0-f44.google.com with SMTP id dr13so984539wgb.13 for <alto@ietf.org>; Wed, 07 Nov 2012 14:55:49 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type; bh=jfff4T0WBOd1gkLzNZv+4AgBAcyygvRFKiYgUMzQkAo=; b=03PksrBFYJGisQoin3Hv1l9HyGRdA3NYF0hlypcwGEcoZUGyUQH7ueQO63ZFApeX/1 ewlUsPRsLhjL1radZjZ7e20/ja6IByiF/9fgbbVKkISIFYIxoVu3w+9jgxyKzVkxJxmC evabOrmNdwyUk/tEKIMeYrMRQWCgJxIvpb2+mPHQMwsNG+yiTAb++SIxx3oFBZiJ6tiX ou4PkUwwFdZwFJWE38vL9ugbLyq9Hhmjq0vqEHoHFz5qAn/1WvyCoaKa4lCNrX9cjX8I KIve49nO501QPPONf6ViRjL8Pzhj7sFAKyZUDWkQGHEQjH1at5c4hUzPJ/maP6bPoACd ygqA==
Received: by 10.180.79.37 with SMTP id g5mr27319104wix.7.1352328949191; Wed, 07 Nov 2012 14:55:49 -0800 (PST)
MIME-Version: 1.0
Sender: richard.alimi@gmail.com
Received: by 10.180.5.3 with HTTP; Wed, 7 Nov 2012 14:55:27 -0800 (PST)
In-Reply-To: <CCC038CF.11088%w.roome@alcatel-lucent.com>
References: <mailman.135.1352318425.18836.alto@ietf.org> <CCC038CF.11088%w.roome@alcatel-lucent.com>
From: Richard Alimi <rich@velvetsea.net>
Date: Wed, 7 Nov 2012 14:55:27 -0800
X-Google-Sender-Auth: OmcqRqvyg90KNEzw58catXA1fug
Message-ID: <CA+cvDaYDsV+Asz8gs0ujBMV3Li8G5U-CrtMDkZuCbATEsXbxkA@mail.gmail.com>
To: Bill Roome <w.roome@alcatel-lucent.com>
Content-Type: multipart/alternative; boundary=f46d044306b0a2d59e04cdef9e6b
Cc: "alto@ietf.org" <alto@ietf.org>
Subject: Re: [alto] Constraints results in E_SYNTAX
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Wed, 07 Nov 2012 22:55:54 -0000

--f46d044306b0a2d59e04cdef9e6b
Content-Type: text/plain; charset=ISO-8859-1

On Wed, Nov 7, 2012 at 1:19 PM, Bill Roome <w.roome@alcatel-lucent.com>wrote:

>
> >Message: 4
> >Date: Wed, 7 Nov 2012 11:39:03 -0800
> >From: Richard Alimi <rich@velvetsea.net>
> >..........
> >
> >The ALTO protocol used to have a reason that was free-form text.  Ted
> >Hardie suggested in his review that we drop this to avoid multi-language
> >issues (as Richard Yang pointed out).  We then removed the reason field.
>
> I wondered why the reason field was removed! However, that begs the
> question of whether a generic "Something's Wrong!" error code is better
> than a detailed description in a language that the ALTO user might not
> understand.
>
> I suggest restoring the "reason" string. If nothing else, a client
> implementer can send it to the ALTO service provider and ask them to
> translate it.
>

I'll leave this up to the WG.  I'd prefer to not go back and forth with
this.  I personally have no strong feelings one way or the other.

Rich


>
>         - Bill Roome
>
>
> _______________________________________________
> alto mailing list
> alto@ietf.org
> https://www.ietf.org/mailman/listinfo/alto
>

--f46d044306b0a2d59e04cdef9e6b
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div class=3D"gmail_extra"><div class=3D"gmail_quote">On Wed, Nov 7, 2012 a=
t 1:19 PM, Bill Roome <span dir=3D"ltr">&lt;<a href=3D"mailto:w.roome@alcat=
el-lucent.com" target=3D"_blank">w.roome@alcatel-lucent.com</a>&gt;</span> =
wrote:<br>

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><br>
&gt;Message: 4<br>
&gt;Date: Wed, 7 Nov 2012 11:39:03 -0800<br>
&gt;From: Richard Alimi &lt;<a href=3D"mailto:rich@velvetsea.net">rich@velv=
etsea.net</a>&gt;<br>
&gt;..........<br>
<div class=3D"im">&gt;<br>
&gt;The ALTO protocol used to have a reason that was free-form text. =A0Ted=
<br>
&gt;Hardie suggested in his review that we drop this to avoid multi-languag=
e<br>
&gt;issues (as Richard Yang pointed out). =A0We then removed the reason fie=
ld.<br>
<br>
</div>I wondered why the reason field was removed! However, that begs the<b=
r>
question of whether a generic &quot;Something&#39;s Wrong!&quot; error code=
 is better<br>
than a detailed description in a language that the ALTO user might not<br>
understand.<br>
<br>
I suggest restoring the &quot;reason&quot; string. If nothing else, a clien=
t<br>
implementer can send it to the ALTO service provider and ask them to<br>
translate it.<br></blockquote><div><br></div><div>I&#39;ll leave this up to=
 the WG. =A0I&#39;d prefer to not go back and forth with this. =A0I persona=
lly have no strong feelings one way or the other.</div><div><br></div><div>

Rich</div><div>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0=
 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
=A0 =A0 =A0 =A0 - Bill Roome<br>
</font></span><div class=3D"HOEnZb"><div class=3D"h5"><br>
<br>
_______________________________________________<br>
alto mailing list<br>
<a href=3D"mailto:alto@ietf.org">alto@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/alto" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/alto</a><br>
</div></div></blockquote></div><br></div>

--f46d044306b0a2d59e04cdef9e6b--

From diego@tid.es  Fri Nov  9 10:18:11 2012
Return-Path: <diego@tid.es>
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 3F19621F85C3 for <alto@ietfa.amsl.com>; Fri,  9 Nov 2012 10:18:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.32
X-Spam-Level: 
X-Spam-Status: No, score=-6.32 tagged_above=-999 required=5 tests=[AWL=0.279,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nR4LeggSovLs for <alto@ietfa.amsl.com>; Fri,  9 Nov 2012 10:18:10 -0800 (PST)
Received: from tidos.tid.es (tidos.tid.es [195.235.93.44]) by ietfa.amsl.com (Postfix) with ESMTP id 3C90821F85BB for <alto@ietf.org>; Fri,  9 Nov 2012 10:18:10 -0800 (PST)
Received: from sbrightmailg01.hi.inet (sbrightmailg01.hi.inet [10.95.64.104]) by tid.hi.inet (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0MD800EWLG684O@tid.hi.inet> for alto@ietf.org; Fri, 09 Nov 2012 19:18:08 +0100 (MET)
Received: from tid (tid.hi.inet [10.95.64.10])	by sbrightmailg01.hi.inet (Symantec Messaging Gateway) with SMTP id 57.6B.03143.0E84D905; Fri, 09 Nov 2012 19:18:08 +0100 (CET)
Received: from correo.tid.es (mailhost.hi.inet [10.95.64.100]) by tid.hi.inet (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPS id <0MD800EWHG684O@tid.hi.inet> for alto@ietf.org; Fri, 09 Nov 2012 19:18:08 +0100 (MET)
Received: from EX10-MB2-MAD.hi.inet ([169.254.2.64]) by EX10-HTCAS6-MAD.hi.inet ([fe80::e1e3:e2fc:beda:deb9%15]) with mapi id 14.02.0318.004; Fri, 09 Nov 2012 19:18:08 +0100
Date: Fri, 09 Nov 2012 18:18:08 +0000
From: "Diego R. Lopez" <diego@tid.es>
In-reply-to: <2A886F9088894347A3BE0CC5B7A85F3E9AA0F3999B@FRMRSSXCHMBSE3.dc-m.alcatel-lucent.com>
X-Originating-IP: [10.95.64.115]
To: "Scharf, Michael (Michael)" <michael.scharf@alcatel-lucent.com>
Message-id: <E6D8B95470ED0845B3376F61DCAB1A0452AE0EB0@EX10-MB2-MAD.hi.inet>
Content-id: <5C21EA96097DC74BB25894F2AA7E09E4@hi.inet>
MIME-version: 1.0
Content-type: text/plain; charset=Windows-1252
Content-language: en-US
Content-transfer-encoding: quoted-printable
Accept-Language: en-US, es-ES
Thread-topic: [alto] [apps-discuss] Simple Web Discovery (SWD) Enabling	Hosted Deployments
Thread-index: AQHNvqaRADfxHISJBE2aQ8YJfrM/WA==
X-AuditID: 0a5f4068-b7f746d000000c47-20-509d48e0ba12
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrFKsWRmVeSWpSXmKPExsXCFe/ApfvAY26AQdc+M4uH2/eyOjB6LFny kymAMYrLJiU1J7MstUjfLoEro//jF7aCR3wVDdPfsDQw/ubuYuTkkBAwkfi2ZTIzhC0mceHe erYuRi4OIYENjBIXp3xlhXC+M0rMureRCcLZyCjR+XQdE0gLi4CqxLYLd1lAbDYg+1Hzb3YQ W1ggWuLujI9gNZwCSRJ/T82DWqEg8efcY7B6EQFniV+rm8DizALKEudW3GQFsXkFvCVa+n+x Q8TNJJ4f/ckIEReU+DH5HgtEXE/i45/bjBC2uERz602ouLbEk3cXwOYwCshKvJs/nxViV4zE 5/YTQPUcQLaexPNmOYhzBCSW7DkPdZqoxMvH/6AevsMoMe93F+sEoL+RnDELyRmzkJwxC8kZ s5CcsYCRdRWjWHFSUWZ6RkluYmZOuoGhXkamXmZeaskmRkjkZexgXL5T5RCjAAejEg9vgeWc ACHWxLLiytxDjJIcTEqivOsd5wYI8SXlp1RmJBZnxBeV5qQWH2KU4GBWEuGdzASU401JrKxK LcqHSclwcChJ8PIAk4SQYFFqempFWmYOML3ApJk4OEHaeYDaJUFqeIsLEnOLM9Mh8qcYVTka exY9ZBRiycvPS5US59UDKRIAKcoozYOb84pRHOhgYYgsDzBBwk14BTScCWh445E5IMNLEhFS Ug2MHOLn/uiVbMqXYJz+7EHpbYUPh63XT2ad1S6RXKT7+5X7CffcmMqcvXHnq3nm2YbpfDM7 8fZ0Gt/fTc2GrsmHJshYPbY7e/jH4WdOzhqpO3X/rdOZ4LKaO+n+1ZusD6ONK5/ecNdZvYNT 7upK75n787vPXcgtU2YRvzlnxwGnjQm8009wXDnMp8RSnJFoqMVcVJwIABerF2dNAwAA
References: <1e8757a8-659a-42d2-9708-309f4b8de076@email.android.com> <E6D8B95470ED0845B3376F61DCAB1A0452AD8F3F@EX10-MB2-MAD.hi.inet> <2A886F9088894347A3BE0CC5B7A85F3E9AA0F3999B@FRMRSSXCHMBSE3.dc-m.alcatel-lucent.com>
Cc: "alto@ietf.org" <alto@ietf.org>
Subject: Re: [alto] [apps-discuss] Simple Web Discovery (SWD) Enabling	Hosted	Deployments
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Fri, 09 Nov 2012 18:18:11 -0000

Hi,

As I understand it, the proposal does not intend to keep a registry of the
URIs used for discovery (it is a parameter for a query using HTTP GET) and,
therefore, ALTO could mandate its own URI, in the same way the U-NAPTR
lookup defines the string to be queried.

The requirements on external registrations are essentially the same in both
cases (none, I think). My point is that an ALTO client would have to rely
only in queries aligned with the rest of the transport protocol, i.e.
plain HTTP(S), and not be required to include support for specific DNS
queries.

Be goode,

On 7 Nov 2012, at 15:50 , Scharf, Michael (Michael) wrote:
> After briefly scanning through draft-jones-simple-web-discovery, which se=
ems to be an individual draft, I wonder how the ALTO service would be regis=
tered in this solution. The text states: "The definition of URIs used to id=
entify principals and services are outside the scope of this specification.=
" If such issues are not clear as of now, it is unclear to me whether this =
is indeed a mature technology.
>
> At first sight, compared to that, the U-NAPTR lookup is a well-understood=
 mechanism used by other IETF protocols with similar requirements like ALTO=
.
>
> Michael
>
--
"Esta vez no fallaremos, Doctor Infierno"

Dr Diego R. Lopez
Telefonica I+D
http://people.tid.es/diego.lopez/

e-mail: diego@tid.es
Tel:    +34 913 129 041
Mobile: +34 682 051 091
-----------------------------------------


________________________________

Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nu=
estra pol=EDtica de env=EDo y recepci=F3n de correo electr=F3nico en el enl=
ace situado m=E1s abajo.
This message is intended exclusively for its addressee. We only send and re=
ceive email on the basis of the terms set out at:
http://www.tid.es/ES/PAGINAS/disclaimer.aspx

From michael.scharf@alcatel-lucent.com  Fri Nov  9 11:54:01 2012
Return-Path: <michael.scharf@alcatel-lucent.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 EC61A21F867E for <alto@ietfa.amsl.com>; Fri,  9 Nov 2012 11:54:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.564
X-Spam-Level: 
X-Spam-Status: No, score=-7.564 tagged_above=-999 required=5 tests=[AWL=-1.315, BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZeT3nhdA9MyO for <alto@ietfa.amsl.com>; Fri,  9 Nov 2012 11:54:01 -0800 (PST)
Received: from smail2.alcatel.fr (smail2.alcatel.fr [62.23.212.57]) by ietfa.amsl.com (Postfix) with ESMTP id F37B921F8675 for <alto@ietf.org>; Fri,  9 Nov 2012 11:54:00 -0800 (PST)
Received: from FRMRSSXCHHUB01.dc-m.alcatel-lucent.com (FRMRSSXCHHUB01.dc-m.alcatel-lucent.com [135.120.45.61]) by smail2.alcatel.fr (8.14.3/8.14.3/ICT) with ESMTP id qA9JrhZA009142 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Fri, 9 Nov 2012 20:53:59 +0100
Received: from FRMRSSXCHMBSE3.dc-m.alcatel-lucent.com ([135.120.45.56]) by FRMRSSXCHHUB01.dc-m.alcatel-lucent.com ([135.120.45.61]) with mapi; Fri, 9 Nov 2012 20:53:50 +0100
From: "Scharf, Michael (Michael)" <michael.scharf@alcatel-lucent.com>
To: "Diego R. Lopez" <diego@tid.es>
Date: Fri, 9 Nov 2012 20:53:49 +0100
Thread-Topic: [alto] [apps-discuss] Simple Web Discovery (SWD) Enabling Hosted	Deployments
Thread-Index: AQHNvqaRADfxHISJBE2aQ8YJfrM/WJfh1Ieg
Message-ID: <2A886F9088894347A3BE0CC5B7A85F3E9AA0F0A840@FRMRSSXCHMBSE3.dc-m.alcatel-lucent.com>
References: <1e8757a8-659a-42d2-9708-309f4b8de076@email.android.com> <E6D8B95470ED0845B3376F61DCAB1A0452AD8F3F@EX10-MB2-MAD.hi.inet> <2A886F9088894347A3BE0CC5B7A85F3E9AA0F3999B@FRMRSSXCHMBSE3.dc-m.alcatel-lucent.com> <E6D8B95470ED0845B3376F61DCAB1A0452AE0EB0@EX10-MB2-MAD.hi.inet>
In-Reply-To: <E6D8B95470ED0845B3376F61DCAB1A0452AE0EB0@EX10-MB2-MAD.hi.inet>
Accept-Language: de-DE, en-US
Content-Language: de-DE
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: de-DE, en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.69 on 155.132.188.80
Cc: "alto@ietf.org" <alto@ietf.org>
Subject: Re: [alto] [apps-discuss] Simple Web Discovery (SWD) Enabling	Hosted	Deployments
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Fri, 09 Nov 2012 19:54:02 -0000

Diego,

> As I understand it, the proposal does not intend to keep a=20
> registry of the URIs used for discovery (it is a parameter=20
> for a query using HTTP GET) and, therefore, ALTO could=20
> mandate its own URI, in the same way the U-NAPTR lookup=20
> defines the string to be queried.
>=20
> The requirements on external registrations are essentially=20
> the same in both cases (none, I think).

U-NAPTR application service tags are registered with IANA, and that is what=
 the current ALTO discovery draft does.

I wonder how and where ALTO would register its URI if it were using draft-j=
ones-simple-web-discovery for discovery. Probably in new IANA registry?

Such questions would probably have to be sorted out elsewhere in the IETF b=
efore ALTO discovery could rely on draft-jones-simple-web-discovery.

> My point is that an=20
> ALTO client would have to rely only in queries aligned with=20
> the rest of the transport protocol, i.e.
> plain HTTP(S), and not be required to include support for=20
> specific DNS queries.

I don't really understand your argument regarding the client. The ALTO clie=
nt has to perform DNS queries anyway, i. e., DNS is not a new protocol on t=
he client side.

However, my impression is that draft-jones-simple-web-discovery could resul=
t in quite some complexity on the server side. My understanding of the prop=
osal is that, if applied to ALTO, an access network provider would have to =
run a Web server for each access network domain names announced in the DHCP=
 option according to RFC 5986. I could imagine that this results in quite s=
ome operational issues for an ISP:

- Today, an operator might not run Web servers for domain names such as "ds=
l.westcoast.myisp.net", i. e., this might require a new server infrastructu=
re. Compared to that, the DNS infrastructure already exists and just has to=
 be extended by entries.

- There may be synchronization issues, e. g. in case of domain mame renumbe=
ring, because different databases have to be kept in sync. Right now, for A=
LTO discovery to work well, an ISP may have to keep DHCP and DNS in sync, w=
hich are both well-established network services. With draft-jones-simple-we=
b-discovery, a third Web infrastructure has to be taken into account.

- I could imagine that load balancing mechanisms and strategies for DNS cou=
ld be quite different from Web load balancing, also taking into account HTT=
P proxies etc. ALTO discovery requires that a topologically close server is=
 discovered. The DNS infrastructure is a network service and thus somehow l=
inked to topology, unlike a Web platform.

Right now, all the points are speculation. It might be doable to engineer a=
n ALTO discovery solution based on draft-jones-simple-web-discovery, if it =
becomes an IETF standard. But, as of now, I don't really understand what th=
e benefit would be for ALTO.

Michael

From sebi@gw01.ehlo.wurstkaes.de  Fri Nov  9 13:01:01 2012
Return-Path: <sebi@gw01.ehlo.wurstkaes.de>
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 8ED3E21F85F3 for <alto@ietfa.amsl.com>; Fri,  9 Nov 2012 13:01:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fjxbCiywL5XT for <alto@ietfa.amsl.com>; Fri,  9 Nov 2012 13:01:01 -0800 (PST)
Received: from gw01.ehlo.wurstkaes.de (gw01.ehlo.wurstkaes.de [IPv6:2a02:a00:e000:116::41]) by ietfa.amsl.com (Postfix) with ESMTP id 0756B21F85F0 for <alto@ietf.org>; Fri,  9 Nov 2012 13:01:00 -0800 (PST)
Received: from sebi by gw01.ehlo.wurstkaes.de with local (Exim 4.72) (envelope-from <sebi@gw01.ehlo.wurstkaes.de>) id 1TWvgw-0000Ek-Ju; Fri, 09 Nov 2012 22:00:42 +0100
Date: Fri, 9 Nov 2012 22:00:42 +0100
From: Sebastian Kiesel <ietf-alto@skiesel.de>
To: "Diego R. Lopez" <diego@tid.es>
Message-ID: <20121109210042.GK3249@gw01.ehlo.wurstkaes.de>
References: <1e8757a8-659a-42d2-9708-309f4b8de076@email.android.com> <E6D8B95470ED0845B3376F61DCAB1A0452AD8F3F@EX10-MB2-MAD.hi.inet> <2A886F9088894347A3BE0CC5B7A85F3E9AA0F3999B@FRMRSSXCHMBSE3.dc-m.alcatel-lucent.com> <E6D8B95470ED0845B3376F61DCAB1A0452AE0EB0@EX10-MB2-MAD.hi.inet>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <E6D8B95470ED0845B3376F61DCAB1A0452AE0EB0@EX10-MB2-MAD.hi.inet>
Accept-Languages: en, de
Organization: my personal mail account
User-Agent: Mutt/1.5.20 (2009-06-14)
Cc: "alto@ietf.org" <alto@ietf.org>
Subject: Re: [alto] [apps-discuss] Simple Web Discovery (SWD) Enabling	Hosted	Deployments
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Fri, 09 Nov 2012 21:01:01 -0000

On Fri, Nov 09, 2012 at 06:18:08PM +0000, Diego R. Lopez wrote:
...
>  My point is that an ALTO client would have to rely
> only in queries aligned with the rest of the transport protocol, i.e.
> plain HTTP(S), and not be required to include support for specific DNS
> queries.

I think we could even do that within the ALTO protocol, see
http://tools.ietf.org/id/draft-kiesel-alto-alto4alto-00.txt but I also
believe that in a multi-domain scenario this inter-ALTO-server mesh
structure would be much more cumbersome than relying on DNS, and a DNS
resolver stub is anyway included in virtually every networked device.

just my 2 cents
S.

From ietf@meetecho.com  Sat Nov 10 12:15:46 2012
Return-Path: <ietf@meetecho.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 65D1E21F8507 for <alto@ietfa.amsl.com>; Sat, 10 Nov 2012 12:15:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.719
X-Spam-Level: 
X-Spam-Status: No, score=-0.719 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 73q+1g9imCzW for <alto@ietfa.amsl.com>; Sat, 10 Nov 2012 12:15:46 -0800 (PST)
Received: from smtpdg9.aruba.it (smtpdg9.aruba.it [62.149.158.239]) by ietfa.amsl.com (Postfix) with ESMTP id BBF3B21F8530 for <alto@ietf.org>; Sat, 10 Nov 2012 12:15:45 -0800 (PST)
Received: from [192.168.0.4] ([151.77.98.23]) by smtpcmd03.ad.aruba.it with bizsmtp id MwFh1k00J0WGHKK01wFj2F; Sat, 10 Nov 2012 21:15:43 +0100
Message-ID: <509EB5E9.2010500@meetecho.com>
Date: Sat, 10 Nov 2012 21:15:37 +0100
From: Meetecho IETF support <ietf@meetecho.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: "alto@ietf.org" <alto@ietf.org>
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [alto] Meetecho session recording
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Sat, 10 Nov 2012 20:15:46 -0000

Dear all,

the full recording (synchronized video, audio, slides and jabber room)
of this WG session at IETF-85 is available.

You can watch it by accessing the following URL:
http://www.meetecho.com/ietf85/recordings

For the chair(s): please feel free to put the link to the recording in 
the minutes, if you think this might be useful.

In case of problems with the playout, just drop an e-mail to 
ietf-team@meetecho.com.

Cheers,
the Meetecho team

-- 
Meetecho s.r.l.
Web Conferencing and Collaboration Tools
www.meetecho.com

From diego@tid.es  Mon Nov 12 06:13:02 2012
Return-Path: <diego@tid.es>
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 3252D21F85B4 for <alto@ietfa.amsl.com>; Mon, 12 Nov 2012 06:13:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.055
X-Spam-Level: 
X-Spam-Status: No, score=-5.055 tagged_above=-999 required=5 tests=[AWL=-1.056, BAYES_50=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TMNEnJk7RKw3 for <alto@ietfa.amsl.com>; Mon, 12 Nov 2012 06:13:01 -0800 (PST)
Received: from correo-bck.tid.es (correo-bck.tid.es [195.235.93.200]) by ietfa.amsl.com (Postfix) with ESMTP id 1B79821F8568 for <alto@ietf.org>; Mon, 12 Nov 2012 06:13:00 -0800 (PST)
Received: from sbrightmailg02.hi.inet (Sbrightmailg02.hi.inet [10.95.78.105]) by tid.hi.inet (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0MDD00AODOTI9J@tid.hi.inet> for alto@ietf.org; Mon, 12 Nov 2012 15:12:58 +0100 (MET)
Received: from vanvan (vanvan.hi.inet [10.95.78.49])	by sbrightmailg02.hi.inet (Symantec Messaging Gateway) with SMTP id F3.FF.05494.AE301A05; Mon, 12 Nov 2012 15:12:58 +0100 (CET)
Received: from correo.tid.es (mailhost.hi.inet [10.95.64.100]) by tid.hi.inet (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPS id <0MDD00AOWOTM9J@tid.hi.inet> for alto@ietf.org; Mon, 12 Nov 2012 15:12:58 +0100 (MET)
Received: from EX10-MB2-MAD.hi.inet ([169.254.2.64]) by ex10-htcas3-mad.hi.inet ([::1]) with mapi id 14.02.0318.004; Mon, 12 Nov 2012 15:12:41 +0100
Date: Mon, 12 Nov 2012 14:12:57 +0000
From: "Diego R. Lopez" <diego@tid.es>
In-reply-to: <2A886F9088894347A3BE0CC5B7A85F3E9AA0F0A840@FRMRSSXCHMBSE3.dc-m.alcatel-lucent.com>
X-Originating-IP: [10.95.64.115]
To: "Scharf, Michael (Michael)" <michael.scharf@alcatel-lucent.com>
Message-id: <E6D8B95470ED0845B3376F61DCAB1A0452AE54E3@EX10-MB2-MAD.hi.inet>
Content-id: <949DD50B5349414891B1DA2F693CC525@hi.inet>
MIME-version: 1.0
Content-type: text/plain; charset=utf-8
Content-language: en-US
Content-transfer-encoding: base64
Accept-Language: en-US
Thread-topic: [alto] [apps-discuss] Simple Web Discovery (SWD) Enabling	Hosted Deployments
Thread-index: AQHNvqaRADfxHISJBE2aQ8YJfrM/WJfh1IeggARdBwA=
X-AuditID: 0a5f4e69-b7fc06d000001576-9b-50a103ea370c
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrOKsWRmVeSWpSXmKPExsXCFe9nqPuKeWGAQdMELYuH2/eyOjB6LFny kymAMYrLJiU1J7MstUjfLoErY86ZQ4wFD4wqLr+czNbAuMOwi5GDQ0LARKJtS00XIyeQKSZx 4d56NhBbSGAbo0TjoqAuRi4g+zujxMT3u5kgnGmMEjtXvWUBqWIRUJW4/+YuO4jNBmQ/av4N ZgsLREvcnfGRCcTmFEiS6GhsZYHYoCDx59xjMFtEwFni1+omZhCbWUBZ4tyKm6wgNq+At8Sn C/vYIeJmQEfsYYeIC0r8mHyPBeRoZgF1iSlTciFKxCWaW2+yQNiKEtMWNTCC2IxAz3w/tYYJ YlWMxOf2E4wQtpXE1T1vWCHOEZBYsuc8M4QtKvHy8T9WiB+/MEm0Xn/ANIFRYhaSM2YhOWMW whmzkJwxC8kZCxhZVzGKFScVZaZnlOQmZuakGxjpZWTqZeallmxihMRc5g7G5TtVDjEKcDAq 8fDuuLsgQIg1say4MvcQoyQHk5IoLz/TwgAhvqT8lMqMxOKM+KLSnNTiQ4wSHMxKIry/Qcp5 UxIrq1KL8mFSMhwcShK8/sD0ICRYlJqeWpGWmQNMLDBpJg5OkHYeoHZFkBre4oLE3OLMdIj8 KUZVjqNv5j5kFGLJy89LlRLnNQUpEgApyijNg5vzilEc6GBhXmWQLA8wNcJNeAU0nAlo+Ppt ILcVlyQipKQaGNfN3KL43HLmrjOlwUGfzJ2+33tzslHm2u3r2kaOH/iDy1fxn47TupWw+SvX 4rDLmZYyc7mb5k221Vq+ZdPeQ/Ns/FbY9ZbOzlxmsmSBUlrM+clmy9rjYxRULrvsVz7K7LSr L0xx49pVnNNaBN2DJBRyPidd3fRCZ0nK8QMvt3s88p/x/J1L5RwlluKMREMt5qLiRADS5Isq SgMAAA==
References: <1e8757a8-659a-42d2-9708-309f4b8de076@email.android.com> <E6D8B95470ED0845B3376F61DCAB1A0452AD8F3F@EX10-MB2-MAD.hi.inet> <2A886F9088894347A3BE0CC5B7A85F3E9AA0F3999B@FRMRSSXCHMBSE3.dc-m.alcatel-lucent.com> <E6D8B95470ED0845B3376F61DCAB1A0452AE0EB0@EX10-MB2-MAD.hi.inet> <2A886F9088894347A3BE0CC5B7A85F3E9AA0F0A840@FRMRSSXCHMBSE3.dc-m.alcatel-lucent.com>
Cc: "alto@ietf.org" <alto@ietf.org>
Subject: Re: [alto] [apps-discuss] Simple Web Discovery (SWD) Enabling	Hosted	Deployments
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Mon, 12 Nov 2012 14:13:02 -0000

SGkgTWljaGFlbCwNCg0KT24gOSBOb3YgMjAxMiwgYXQgMjA6NTMgLCBTY2hhcmYsIE1pY2hhZWwg
KE1pY2hhZWwpIHdyb3RlOg0KPiBVLU5BUFRSIGFwcGxpY2F0aW9uIHNlcnZpY2UgdGFncyBhcmUg
cmVnaXN0ZXJlZCB3aXRoIElBTkEsIGFuZCB0aGF0IGlzIHdoYXQgdGhlIGN1cnJlbnQgQUxUTyBk
aXNjb3ZlcnkgZHJhZnQgZG9lcy4NCj4NCj4gSSB3b25kZXIgaG93IGFuZCB3aGVyZSBBTFRPIHdv
dWxkIHJlZ2lzdGVyIGl0cyBVUkkgaWYgaXQgd2VyZSB1c2luZyBkcmFmdC1qb25lcy1zaW1wbGUt
d2ViLWRpc2NvdmVyeSBmb3IgZGlzY292ZXJ5LiBQcm9iYWJseSBpbiBuZXcgSUFOQSByZWdpc3Ry
eT8NCj4NCj4gU3VjaCBxdWVzdGlvbnMgd291bGQgcHJvYmFibHkgaGF2ZSB0byBiZSBzb3J0ZWQg
b3V0IGVsc2V3aGVyZSBpbiB0aGUgSUVURiBiZWZvcmUgQUxUTyBkaXNjb3ZlcnkgY291bGQgcmVs
eSBvbiBkcmFmdC1qb25lcy1zaW1wbGUtd2ViLWRpc2NvdmVyeS4NCg0KSG1tbSwgSSB0aGluayB5
b3UgaGF2ZSBhIHBvaW50IGhlcmUuIEJ1dCBJJ2xsIGludmVzdGlnYXRlIHdoZXRoZXIgdGhlcmUg
aXMNCmEgVVJOIG5hbWVzcGFjZSBhc3NvY2lhdGVkIHdpdGggRE5TIG5hbWVzLCBzbyBhbiBVUkkg
YnVpbHQgYWNjb3JkaW5nIHRvDQpjdXJyZW50IHJlZ2lzdHJhdGlvbiBjb3VsZCBiZSBkaXJlY3Rs
eSB1c2VkLg0KDQo+IEkgZG9uJ3QgcmVhbGx5IHVuZGVyc3RhbmQgeW91ciBhcmd1bWVudCByZWdh
cmRpbmcgdGhlIGNsaWVudC4gVGhlIEFMVE8gY2xpZW50IGhhcyB0byBwZXJmb3JtIEROUyBxdWVy
aWVzIGFueXdheSwgaS4gZS4sIEROUyBpcyBub3QgYSBuZXcgcHJvdG9jb2wgb24gdGhlIGNsaWVu
dCBzaWRlLg0KDQpJbmRlZWQsIGJ1dCBteSB0YWtlIGlzIHRoYXQgdGhlIGNsaWVudCByZWxpZXMg
b24gRE5TIGluIGFuIGluZGlyZWN0IHdheSwNCmJ5IHJlcXVlc3RpbmcgSFRUUChTKSBjb25uZWN0
aW9ucyB0aGF0IHVzZSBETlMgdG8gcGFyc2UgdGhlIFVSTCwgYnV0IG5vdA0KZGlyZWN0bHkgYWNj
ZXNzaW5nIHRoZSBETlMgaW50ZXJmYWNlLiBUaGVyZWZvcmUsIHVzaW5nIEhUVFAoUykgYWdhaW4g
d291bGQNCmJlIHRoZSBtb3N0IG5hdHVyYWwgd2F5IHRvIHBlcmZvcm0gZGlzY292ZXJ5Lg0KDQo+
IEhvd2V2ZXIsIG15IGltcHJlc3Npb24gaXMgdGhhdCBkcmFmdC1qb25lcy1zaW1wbGUtd2ViLWRp
c2NvdmVyeSBjb3VsZCByZXN1bHQgaW4gcXVpdGUgc29tZSBjb21wbGV4aXR5IG9uIHRoZSBzZXJ2
ZXIgc2lkZS4gTXkgdW5kZXJzdGFuZGluZyBvZiB0aGUgcHJvcG9zYWwgaXMgdGhhdCwgaWYgYXBw
bGllZCB0byBBTFRPLCBhbiBhY2Nlc3MgbmV0d29yayBwcm92aWRlciB3b3VsZCBoYXZlIHRvIHJ1
biBhIFdlYiBzZXJ2ZXIgZm9yIGVhY2ggYWNjZXNzIG5ldHdvcmsgZG9tYWluIG5hbWVzIGFubm91
bmNlZCBpbiB0aGUgREhDUCBvcHRpb24gYWNjb3JkaW5nIHRvIFJGQyA1OTg2LiBJIGNvdWxkIGlt
YWdpbmUgdGhhdCB0aGlzIHJlc3VsdHMgaW4gcXVpdGUgc29tZSBvcGVyYXRpb25hbCBpc3N1ZXMg
Zm9yIGFuIElTUDoNCj4NCj4gLSBUb2RheSwgYW4gb3BlcmF0b3IgbWlnaHQgbm90IHJ1biBXZWIg
c2VydmVycyBmb3IgZG9tYWluIG5hbWVzIHN1Y2ggYXMgImRzbC53ZXN0Y29hc3QubXlpc3AubmV0
IiwgaS4gZS4sIHRoaXMgbWlnaHQgcmVxdWlyZSBhIG5ldyBzZXJ2ZXIgaW5mcmFzdHJ1Y3R1cmUu
IENvbXBhcmVkIHRvIHRoYXQsIHRoZSBETlMgaW5mcmFzdHJ1Y3R1cmUgYWxyZWFkeSBleGlzdHMg
YW5kIGp1c3QgaGFzIHRvIGJlIGV4dGVuZGVkIGJ5IGVudHJpZXMuDQoNCkRlcGxveWluZyB2aXJ0
dWFsIFdlYiBzZXJ2ZXJzIGlzIGEgcmF0aGVyIHRyaXZpYWwgdGFzayAoaW4gYSB0eXBpY2FsIEFw
YWNoZQ0Kc2V0dXAsIHdlIGFyZSB0YWxraW5nIGFib3V0IGFkZGluZyBhIGZldyBsaW5lcyB0byBj
b25maWd1cmF0aW9uIGZpbGVzKSwgYW5kDQp5b3UgbmVlZCBXZWIgc2VydmVycyBhbnl3YXkgdG8g
cnVuIHRoZSBBTFRPIGJhc2UgcHJvdG9jb2wNCg0KPiAtIFRoZXJlIG1heSBiZSBzeW5jaHJvbml6
YXRpb24gaXNzdWVzLCBlLiBnLiBpbiBjYXNlIG9mIGRvbWFpbiBtYW1lIHJlbnVtYmVyaW5nLCBi
ZWNhdXNlIGRpZmZlcmVudCBkYXRhYmFzZXMgaGF2ZSB0byBiZSBrZXB0IGluIHN5bmMuIFJpZ2h0
IG5vdywgZm9yIEFMVE8gZGlzY292ZXJ5IHRvIHdvcmsgd2VsbCwgYW4gSVNQIG1heSBoYXZlIHRv
IGtlZXAgREhDUCBhbmQgRE5TIGluIHN5bmMsIHdoaWNoIGFyZSBib3RoIHdlbGwtZXN0YWJsaXNo
ZWQgbmV0d29yayBzZXJ2aWNlcy4gV2l0aCBkcmFmdC1qb25lcy1zaW1wbGUtd2ViLWRpc2NvdmVy
eSwgYSB0aGlyZCBXZWIgaW5mcmFzdHJ1Y3R1cmUgaGFzIHRvIGJlIHRha2VuIGludG8gYWNjb3Vu
dC4NCg0KQWdhaW4sIHRoaXMgbWFpbnRlbmFuY2UgaXMgc3RyYWlnaHRmb3J3YXJkLCBzaW5jZSBp
dCBpcyByZWxhdGVkIHRvDQpkZWFsaW5nIHdpdGggdmlydHVhbCBzZXJ2ZXJzIGluIGFueSBtb2Rl
cm4gV2ViIHNlcnZlciBmcmFtZXdvcmsuIEl0IGlzIG1vcmUNCmEgbWF0dGVyIG9mIHdoaWNoIGJy
YW5jaCBpbiBhbiBvcmdhbml6YXRpb24gaGFzIGFjY2VzcyB0byBESENQLCBETlMsIGFuZA0KV2Vi
IHNlcnZlcnMgZm9yIGluZnJhdHNydWN0dXJhbCBtYXR0ZXJzLiBNeSBwb2ludCBpcyB0aGF0IERO
UyBpcyB1c3VhbGx5DQp0aGUgbW9zdCBoYXJkIHRvIGNoYW5nZSwgZHVlIHRvIGl0IGJlaW5nIGEg
Y3JpdGljYWwgc2VydmljZSBmb3IgbWFueQ0Kb3RoZXJzLg0KDQo+IC0gSSBjb3VsZCBpbWFnaW5l
IHRoYXQgbG9hZCBiYWxhbmNpbmcgbWVjaGFuaXNtcyBhbmQgc3RyYXRlZ2llcyBmb3IgRE5TIGNv
dWxkIGJlIHF1aXRlIGRpZmZlcmVudCBmcm9tIFdlYiBsb2FkIGJhbGFuY2luZywgYWxzbyB0YWtp
bmcgaW50byBhY2NvdW50IEhUVFAgcHJveGllcyBldGMuIEFMVE8gZGlzY292ZXJ5IHJlcXVpcmVz
IHRoYXQgYSB0b3BvbG9naWNhbGx5IGNsb3NlIHNlcnZlciBpcyBkaXNjb3ZlcmVkLiBUaGUgRE5T
IGluZnJhc3RydWN0dXJlIGlzIGEgbmV0d29yayBzZXJ2aWNlIGFuZCB0aHVzIHNvbWVob3cgbGlu
a2VkIHRvIHRvcG9sb2d5LCB1bmxpa2UgYSBXZWIgcGxhdGZvcm0uDQoNClNvcnJ5LCBJIGRvIG5v
dCBmb2xsb3cgeW91ciByZWFzb25pbmcgaGVyZS4gV2lsbCBub3QgdGhhdCBpbXBseSB0aGF0IHRo
ZSB3aG9sZQ0KQUxUTyBpbmZyYXN0cnVjdHVyZSB3b3VsZCBiZSBiZXR0ZXIgc3VpdGVkIGZvciBy
dW5uaW5nIG9uIEROUz8NCg0KPiBSaWdodCBub3csIGFsbCB0aGUgcG9pbnRzIGFyZSBzcGVjdWxh
dGlvbi4gSXQgbWlnaHQgYmUgZG9hYmxlIHRvIGVuZ2luZWVyIGFuIEFMVE8gZGlzY292ZXJ5IHNv
bHV0aW9uIGJhc2VkIG9uIGRyYWZ0LWpvbmVzLXNpbXBsZS13ZWItZGlzY292ZXJ5LCBpZiBpdCBi
ZWNvbWVzIGFuIElFVEYgc3RhbmRhcmQuIEJ1dCwgYXMgb2Ygbm93LCBJIGRvbid0IHJlYWxseSB1
bmRlcnN0YW5kIHdoYXQgdGhlIGJlbmVmaXQgd291bGQgYmUgZm9yIEFMVE8uDQoNCg0KVW5pZnlp
bmcgcHJvdG9jb2wgc3RhY2sgdG8gYSBzaW5nbGUgb25lLCBIVFRQKFMpLCBhbmQgcmVseWluZyBp
biBhIGZ1bGx5DQpjb250cm9sZWQgc2VydmVyIGZyYW1ld29yay4gQW5kIHRoZXJlIGlzIGFub3Ro
ZXIgcmVhc29uIHJlbGF0ZWQgdG8gdHJ1c3QgYW5kDQpzZWN1cml0eTogd2hpbGUgSFRUUFMgaXMg
d2VsbCB1bmRlcnN0b29kIGFuZCBlYXN5IHRvIGRlcGxveSwgRE5Tc2VjIGlzIGluDQpub3Qgc3Vj
aCBhIGdvb2Qgc2l0dWF0aW9uLiBBIHRydXN0d29ydGh5IGRpc2NvdmVyeSBtZWNoYW5pc20gd291
bGQgYmUgbXVjaA0Kc2ltcGxlciB0byBpbXBsZW1lbnQgYW5kIGVhc2llciB0byBhZG9wZ3QgYnkg
dXNpbmcgSFRUUFMuLi4NCg0KSWYgdGhlIGN1cnJlbnQgc3RhdHVzIG9mIGRyYWZ0LWpvbmVzLXNp
bXBsZS13ZWItZGlzY292ZXJ5IHdlIGNvdWxkIGV2ZW4gZGFyZQ0KaW5jb3Jwb3JhdGUgaW4gdGhl
IGRyYWZ0IHRoZSBtZWNoYW5pc21zIHRoZXJlIHRoYXQgYXJlIHJlbGF0ZWQgdG8gQUxUTw0KZGlz
Y292ZXJ5LiBBcyBmYXIgYXMgSSBjYW4gdGVsbCwgdGhleSBhcmUgcmF0aGVyIHN0cmFpZ2h0Zm9y
d2FyZC4NCg0KQmUgZ29vZGUsDQoNCi0tDQoiRXN0YSB2ZXogbm8gZmFsbGFyZW1vcywgRG9jdG9y
IEluZmllcm5vIg0KDQpEciBEaWVnbyBSLiBMb3Bleg0KVGVsZWZvbmljYSBJK0QNCmh0dHA6Ly9w
ZW9wbGUudGlkLmVzL2RpZWdvLmxvcGV6Lw0KDQplLW1haWw6IGRpZWdvQHRpZC5lcw0KVGVsOiAg
ICArMzQgOTEzIDEyOSAwNDENCk1vYmlsZTogKzM0IDY4MiAwNTEgMDkxDQotLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQ0KDQoNCl9fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fDQoNCkVzdGUgbWVuc2FqZSBzZSBkaXJpZ2UgZXhjbHVzaXZhbWVudGUgYSBzdSBk
ZXN0aW5hdGFyaW8uIFB1ZWRlIGNvbnN1bHRhciBudWVzdHJhIHBvbMOtdGljYSBkZSBlbnbDrW8g
eSByZWNlcGNpw7NuIGRlIGNvcnJlbyBlbGVjdHLDs25pY28gZW4gZWwgZW5sYWNlIHNpdHVhZG8g
bcOhcyBhYmFqby4NClRoaXMgbWVzc2FnZSBpcyBpbnRlbmRlZCBleGNsdXNpdmVseSBmb3IgaXRz
IGFkZHJlc3NlZS4gV2Ugb25seSBzZW5kIGFuZCByZWNlaXZlIGVtYWlsIG9uIHRoZSBiYXNpcyBv
ZiB0aGUgdGVybXMgc2V0IG91dCBhdDoNCmh0dHA6Ly93d3cudGlkLmVzL0VTL1BBR0lOQVMvZGlz
Y2xhaW1lci5hc3B4DQo=

From diego@tid.es  Mon Nov 12 06:13:04 2012
Return-Path: <diego@tid.es>
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 24E8421F85D5 for <alto@ietfa.amsl.com>; Mon, 12 Nov 2012 06:13:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.938
X-Spam-Level: 
X-Spam-Status: No, score=-5.938 tagged_above=-999 required=5 tests=[AWL=0.061,  BAYES_00=-2.599, J_CHICKENPOX_44=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mzkorAZUcNKK for <alto@ietfa.amsl.com>; Mon, 12 Nov 2012 06:13:03 -0800 (PST)
Received: from correo-bck.tid.es (correo-bck.tid.es [195.235.93.200]) by ietfa.amsl.com (Postfix) with ESMTP id E1C3821F8568 for <alto@ietf.org>; Mon, 12 Nov 2012 06:13:02 -0800 (PST)
Received: from sbrightmailg02.hi.inet (Sbrightmailg02.hi.inet [10.95.78.105]) by tid.hi.inet (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0MDD00AODOTI9J@tid.hi.inet> for alto@ietf.org; Mon, 12 Nov 2012 15:13:02 +0100 (MET)
Received: from vanvan (vanvan.hi.inet [10.95.78.49])	by sbrightmailg02.hi.inet (Symantec Messaging Gateway) with SMTP id 54.FF.05494.DE301A05; Mon, 12 Nov 2012 15:13:01 +0100 (CET)
Received: from correo.tid.es (mailhost.hi.inet [10.95.64.100]) by tid.hi.inet (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPS id <0MDD00APAOTP9J@tid.hi.inet> for alto@ietf.org; Mon, 12 Nov 2012 15:13:01 +0100 (MET)
Received: from EX10-MB2-MAD.hi.inet ([169.254.2.64]) by EX10-HTCAS5-MAD.hi.inet ([::1]) with mapi id 14.02.0318.004; Mon, 12 Nov 2012 15:13:01 +0100
Date: Mon, 12 Nov 2012 14:13:00 +0000
From: "Diego R. Lopez" <diego@tid.es>
In-reply-to: <20121109210042.GK3249@gw01.ehlo.wurstkaes.de>
X-Originating-IP: [10.95.64.115]
To: Sebastian Kiesel <ietf-alto@skiesel.de>
Message-id: <E6D8B95470ED0845B3376F61DCAB1A0452AE54EC@EX10-MB2-MAD.hi.inet>
Content-id: <98C4C2E30F92684588F8F99D92C914BF@hi.inet>
MIME-version: 1.0
Content-type: text/plain; charset=utf-8
Content-language: en-US
Content-transfer-encoding: base64
Accept-Language: en-US, es-ES
Thread-topic: [alto] [apps-discuss] Simple Web Discovery (SWD) Enabling	Hosted Deployments
Thread-index: AQHNvqaRADfxHISJBE2aQ8YJfrM/WJfh7H4AgARFFIA=
X-AuditID: 0a5f4e69-b7fc06d000001576-9e-50a103ed02f2
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrFKsWRmVeSWpSXmKPExsXCFe9nqPuWeWGAwf3rFhYPt+9ldWD0WLLk J1MAYxSXTUpqTmZZapG+XQJXxtRf91kKPghUzP+zgrGBcYdAFyMnh4SAicTFvUeZIWwxiQv3 1rN1MXJxCAlsY5S4t/kZI4TznVHiz4suKGcao0R/+3FWkBYWAVWJc+vfs4PYbED2o+bfYLaw QLTE3RkfmUBsTgFriaMXn7BCrFCQ+HPuMQuILSKgLfHn7SOwemaBNIk1ryDm8Ap4S8y9vA+o ngMobibx46c4RFhQ4sfkeywQYXWJKVNyITrFJZpbb7JA2IoS0xY1MILYjAKyEu/mz2eF2BQj 8bn9BCOEbSXxa/V6dohrBCSW7DkP9byoxMvH/8DqhQTOM0lMnJ04gVFiFsIRs5AcMQvhiFlI jpiF5IgFjKyrGMWKk4oy0zNKchMzc9INjPQyMvUy81JLNjFCIi5zB+PynSqHGAU4GJV4eHfc XRAgxJpYVlyZe4hRkoNJSZSXn2lhgBBfUn5KZUZicUZ8UWlOavEhRgkOZiUR3t8g5bwpiZVV qUX5MCkZDg4lCV5/YHIQEixKTU+tSMvMAaYVmDQTBydIOw9QuyJIDW9xQWJucWY6RP4Uo6SU OK8pSEIAJJFRmgfX+4pRHOhIYV5lkCwPMAHCdb0CGsgENHD9NpB7iksSEVJSDYyp8+5c233O 7tCTDUWz3/95rZL0KDX7W80i8XsLl7AoxR2ZYpd3ZWqwJNtW/p2+NhK6m96pdr31jdfjqOLW elOx6OZMy6rGxpvzeaVvZJWWVJ/Xib2ntKCz9VuFyA1u82x1IxuXypwQq+Vbylh29Gxhuux/ 6PKRNYUFO24pOvGzBe2/WPNizRMlluKMREMt5qLiRAAZ/waBPQMAAA==
References: <1e8757a8-659a-42d2-9708-309f4b8de076@email.android.com> <E6D8B95470ED0845B3376F61DCAB1A0452AD8F3F@EX10-MB2-MAD.hi.inet> <2A886F9088894347A3BE0CC5B7A85F3E9AA0F3999B@FRMRSSXCHMBSE3.dc-m.alcatel-lucent.com> <E6D8B95470ED0845B3376F61DCAB1A0452AE0EB0@EX10-MB2-MAD.hi.inet> <20121109210042.GK3249@gw01.ehlo.wurstkaes.de>
Cc: "alto@ietf.org" <alto@ietf.org>
Subject: Re: [alto] [apps-discuss] Simple Web Discovery (SWD) Enabling	Hosted	Deployments
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Mon, 12 Nov 2012 14:13:04 -0000

SGkgU2ViYXN0aWFuLA0KDQpPbiA5IE5vdiAyMDEyLCBhdCAyMjowMCAsIFNlYmFzdGlhbiBLaWVz
ZWwgd3JvdGU6DQo+IEkgdGhpbmsgd2UgY291bGQgZXZlbiBkbyB0aGF0IHdpdGhpbiB0aGUgQUxU
TyBwcm90b2NvbCwgc2VlDQo+IGh0dHA6Ly90b29scy5pZXRmLm9yZy9pZC9kcmFmdC1raWVzZWwt
YWx0by1hbHRvNGFsdG8tMDAudHh0IGJ1dCBJIGFsc28NCj4gYmVsaWV2ZSB0aGF0IGluIGEgbXVs
dGktZG9tYWluIHNjZW5hcmlvIHRoaXMgaW50ZXItQUxUTy1zZXJ2ZXIgbWVzaA0KPiBzdHJ1Y3R1
cmUgd291bGQgYmUgbXVjaCBtb3JlIGN1bWJlcnNvbWUgdGhhbiByZWx5aW5nIG9uIEROUywgYW5k
IGEgRE5TDQo+IHJlc29sdmVyIHN0dWIgaXMgYW55d2F5IGluY2x1ZGVkIGluIHZpcnR1YWxseSBl
dmVyeSBuZXR3b3JrZWQgZGV2aWNlLg0KDQoNCldhcyBub3QgYXdhcmUgYWJvdXQgdGhpcyBkcmFm
dCwgdGhhbmtzIGZvciB0aGUgcG9pbnRlci4gSSB0aGluayB0aGlzIGNvdWxkDQpiZSB0aGUgYmFz
ZSBmb3Igd2hhdCBJIG1lbnRpb25lZCBpbiBteSBsYXN0IHJlcGx5IHRvIE1pY2hhZWwgb24gcmVs
eWluZw0Kb24gb25seS1BTFRPIGRvY3VtZW50cyB0byBtYWtlIHRoZSBzcGVjaWZpY2F0aW9uLiBJ
IHN0aWxsIHRoaW5rIHRoYXQgYQ0Kc2luZ2xlIEdFVCBxdWVyeSBzb3VuZHMgc2ltcGxlciB0aGFu
IGEgZGlyZWN0IGFjY2VzcyB0byB0aGUgRE5TIGludGVyZmFjZSwNCmFzIHdlbGwgYXMgdGhlIHRy
dXN0IGNvbnNpZGVyYXRpb25zIGFyZSBhcHBsaWNhYmxlLg0KDQpXaGF0IHdvdWxkIHlvdSB0aGlu
ayBvZiBsZWF2aW5nIHRoZSBjdXJyZW50IGRpc2NvdmVyeSBkb2N1bWVudCBhcyBpdCBpcw0Kbm93
IGFuZCBleHBsb3JpbmcgdGhlIHBvc3NpYmlsaXR5IG9mIGFsaWduaW5nIEhUVFBTIGRpc2NvdmVy
eSB3aXRoIHRoaXMNCkFMVE80QUxUTyBpZGVhPw0KDQpCZSBnb29kZSwNCg0KDQotLQ0KIkVzdGEg
dmV6IG5vIGZhbGxhcmVtb3MsIERvY3RvciBJbmZpZXJubyINCg0KRHIgRGllZ28gUi4gTG9wZXoN
ClRlbGVmb25pY2EgSStEDQpodHRwOi8vcGVvcGxlLnRpZC5lcy9kaWVnby5sb3Blei8NCg0KZS1t
YWlsOiBkaWVnb0B0aWQuZXMNClRlbDogICAgKzM0IDkxMyAxMjkgMDQxDQpNb2JpbGU6ICszNCA2
ODIgMDUxIDA5MQ0KLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0NCg0K
DQpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KDQpFc3RlIG1lbnNhamUgc2UgZGly
aWdlIGV4Y2x1c2l2YW1lbnRlIGEgc3UgZGVzdGluYXRhcmlvLiBQdWVkZSBjb25zdWx0YXIgbnVl
c3RyYSBwb2zDrXRpY2EgZGUgZW52w61vIHkgcmVjZXBjacOzbiBkZSBjb3JyZW8gZWxlY3Ryw7Nu
aWNvIGVuIGVsIGVubGFjZSBzaXR1YWRvIG3DoXMgYWJham8uDQpUaGlzIG1lc3NhZ2UgaXMgaW50
ZW5kZWQgZXhjbHVzaXZlbHkgZm9yIGl0cyBhZGRyZXNzZWUuIFdlIG9ubHkgc2VuZCBhbmQgcmVj
ZWl2ZSBlbWFpbCBvbiB0aGUgYmFzaXMgb2YgdGhlIHRlcm1zIHNldCBvdXQgYXQ6DQpodHRwOi8v
d3d3LnRpZC5lcy9FUy9QQUdJTkFTL2Rpc2NsYWltZXIuYXNweA0K

From michael.scharf@alcatel-lucent.com  Wed Nov 14 12:45:55 2012
Return-Path: <michael.scharf@alcatel-lucent.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 0547D21F84DB for <alto@ietfa.amsl.com>; Wed, 14 Nov 2012 12:45:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.608
X-Spam-Level: 
X-Spam-Status: No, score=-9.608 tagged_above=-999 required=5 tests=[AWL=0.641,  BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7dBzpsNyt+XU for <alto@ietfa.amsl.com>; Wed, 14 Nov 2012 12:45:53 -0800 (PST)
Received: from smail3.alcatel.fr (smail3.alcatel.fr [64.208.49.56]) by ietfa.amsl.com (Postfix) with ESMTP id 85C5821F84DE for <alto@ietf.org>; Wed, 14 Nov 2012 12:45:53 -0800 (PST)
Received: from FRMRSSXCHHUB03.dc-m.alcatel-lucent.com (FRMRSSXCHHUB03.dc-m.alcatel-lucent.com [135.120.45.63]) by smail3.alcatel.fr (8.14.3/8.14.3/ICT) with ESMTP id qAEKjAkr014500 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Wed, 14 Nov 2012 21:45:51 +0100
Received: from FRMRSSXCHMBSE3.dc-m.alcatel-lucent.com ([135.120.45.56]) by FRMRSSXCHHUB03.dc-m.alcatel-lucent.com ([135.120.45.63]) with mapi; Wed, 14 Nov 2012 21:45:36 +0100
From: "Scharf, Michael (Michael)" <michael.scharf@alcatel-lucent.com>
To: "Diego R. Lopez" <diego@tid.es>
Date: Wed, 14 Nov 2012 21:45:35 +0100
Thread-Topic: [alto] [apps-discuss] Simple Web Discovery (SWD) Enabling Hosted	Deployments
Thread-Index: AQHNvqaRADfxHISJBE2aQ8YJfrM/WJfh1IeggARdBwCAA5CUEA==
Message-ID: <2A886F9088894347A3BE0CC5B7A85F3E9AA0F0A8E4@FRMRSSXCHMBSE3.dc-m.alcatel-lucent.com>
References: <1e8757a8-659a-42d2-9708-309f4b8de076@email.android.com> <E6D8B95470ED0845B3376F61DCAB1A0452AD8F3F@EX10-MB2-MAD.hi.inet> <2A886F9088894347A3BE0CC5B7A85F3E9AA0F3999B@FRMRSSXCHMBSE3.dc-m.alcatel-lucent.com> <E6D8B95470ED0845B3376F61DCAB1A0452AE0EB0@EX10-MB2-MAD.hi.inet> <2A886F9088894347A3BE0CC5B7A85F3E9AA0F0A840@FRMRSSXCHMBSE3.dc-m.alcatel-lucent.com> <E6D8B95470ED0845B3376F61DCAB1A0452AE54E3@EX10-MB2-MAD.hi.inet>
In-Reply-To: <E6D8B95470ED0845B3376F61DCAB1A0452AE54E3@EX10-MB2-MAD.hi.inet>
Accept-Language: de-DE, en-US
Content-Language: de-DE
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: de-DE, en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.69 on 155.132.188.83
Cc: "alto@ietf.org" <alto@ietf.org>
Subject: Re: [alto] [apps-discuss] Simple Web Discovery (SWD) Enabling	Hosted	Deployments
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Wed, 14 Nov 2012 20:45:55 -0000

Diego,=20

> Hi Michael,
>=20
> On 9 Nov 2012, at 20:53 , Scharf, Michael (Michael) wrote:
> > U-NAPTR application service tags are registered with IANA,=20
> and that is what the current ALTO discovery draft does.
> >
> > I wonder how and where ALTO would register its URI if it=20
> were using draft-jones-simple-web-discovery for discovery.=20
> Probably in new IANA registry?
> >
> > Such questions would probably have to be sorted out=20
> elsewhere in the IETF before ALTO discovery could rely on=20
> draft-jones-simple-web-discovery.
>=20
> Hmmm, I think you have a point here. But I'll investigate=20
> whether there is a URN namespace associated with DNS names,=20
> so an URI built according to current registration could be=20
> directly used.

My main point is that this has to be sorted out e. g. in APPAREA before we =
can rely on an RFC in that space. It is unclear to me whether draft-jones-s=
imple-web-discovery will be a mature and widely used technique any time soo=
n.
=20
> > I don't really understand your argument regarding the=20
> client. The ALTO client has to perform DNS queries anyway, i.=20
> e., DNS is not a new protocol on the client side.
>=20
> Indeed, but my take is that the client relies on DNS in an=20
> indirect way, by requesting HTTP(S) connections that use DNS=20
> to parse the URL, but not directly accessing the DNS=20
> interface. Therefore, using HTTP(S) again would be the most=20
> natural way to perform discovery.

Sure, a HTTP(S) discovery mechanisms has benefits in a Web world. But DNS a=
lso has benefits. There is an engineering tradeoff.

Thus, I disagree that HTTP(S) is the "most natural way".

> > However, my impression is that=20
> draft-jones-simple-web-discovery could result in quite some=20
> complexity on the server side. My understanding of the=20
> proposal is that, if applied to ALTO, an access network=20
> provider would have to run a Web server for each access=20
> network domain names announced in the DHCP option according=20
> to RFC 5986. I could imagine that this results in quite some=20
> operational issues for an ISP:
> >
> > - Today, an operator might not run Web servers for domain=20
> names such as "dsl.westcoast.myisp.net", i. e., this might=20
> require a new server infrastructure. Compared to that, the=20
> DNS infrastructure already exists and just has to be extended=20
> by entries.
>=20
> Deploying virtual Web servers is a rather trivial task (in a=20
> typical Apache setup, we are talking about adding a few lines=20
> to configuration files), and you need Web servers anyway to=20
> run the ALTO base protocol

My concern is that RFC 5986 announces an access network domain name, such a=
s "dsl.westcoast.myisp.net".

In my understanding, draft-jones-simple-web-discovery requires that a Web s=
erver is running at https://sl.westcoast.myisp.net/.well-known/simple-web-d=
iscovery . Furthermore, unless I miss something, there is no need for an DN=
S entry that maps "dsl.westcoast.myisp.net" to specific host right now.

Thus, for draft-jones-simple-web-discovery to work with RFC 5986, an ISP mi=
ght have to add new DNS entries for each access network domain name, pointi=
ng to a Web server, that then figures out the closest ALTO server URI. With=
 U-NAPTR, the DNS server just gives the closest ALTO server URI directly.=20

In summary:

- Both variants are likely to require new DNS entries
- draft-jones-simple-web-discovery requires one more indirection, i. e., on=
e more system to configure, and one more system that has to be aware of the=
 network topology to figure out the closest ALTO server, etc.

Obviously, an alternative would be to specify a new DHCP option that direct=
ly announces the URI of the SWD Web Server. That is not very different to a=
 DHCP option that just encodes the ALTO server URI. This is all doable, at =
least in principle. But the approach of encoding URIs in DHCP got pretty st=
rong pushback in previous ALTO meetings, as far as I recall.

> > - There may be synchronization issues, e. g. in case of=20
> domain mame renumbering, because different databases have to=20
> be kept in sync. Right now, for ALTO discovery to work well,=20
> an ISP may have to keep DHCP and DNS in sync, which are both=20
> well-established network services. With=20
> draft-jones-simple-web-discovery, a third Web infrastructure=20
> has to be taken into account.
>=20
> Again, this maintenance is straightforward, since it is=20
> related to dealing with virtual servers in any modern Web=20
> server framework. It is more a matter of which branch in an=20
> organization has access to DHCP, DNS, and Web servers for=20
> infratsructural matters. My point is that DNS is usually the=20
> most hard to change, due to it being a critical service for=20
> many others.

My point is that ALTO server discovery has to figure out what server can pr=
ovide guidance for a specific access network, taking into account renumberi=
ng, domain name migrations, etc. I am not sure if the organizational unit o=
f an ISP that runs the Web platform really has a better understanding of th=
e access network topology and naming than the organization unit that runs D=
NS and DHCP. I'd assume the opposite. Sure, it is up to an ISP to sort this=
 out.

> > - I could imagine that load balancing mechanisms and=20
> strategies for DNS could be quite different from Web load=20
> balancing, also taking into account HTTP proxies etc. ALTO=20
> discovery requires that a topologically close server is=20
> discovered. The DNS infrastructure is a network service and=20
> thus somehow linked to topology, unlike a Web platform.
>=20
> Sorry, I do not follow your reasoning here. Will not that=20
> imply that the whole ALTO infrastructure would be better=20
> suited for running on DNS?

No. The sole purpose for the discovery is to find the URI of a suitable ALT=
O server.

For instance, I am concerned about a scenario where a transparent HTTP prox=
y is deployed inside the access network. For instance, assume that all clie=
nt traffic on port 80 and 443 is forced through a proxy. The scenario is th=
en as follows:

ALTO discovery client <---> HTTP proxy <---> SWD discovery server

In that setting, unless I miss something, it can be difficult for the SWD d=
iscovery server to figure what ALTO server could provide guidance to client=
s behind the proxy. Also, note that the ALTO server does not have to run on=
 port 80 or 443, i. e., ALTO queries may or may not have to pass through th=
e HTTP proxy themselves.

Any middlebox scenario is difficult for ALTO discovery, similar like NAPT. =
But middleboxes on port 80 and 443 are quite frequent. And I don't think it=
 is well understood how this affects ALTO discovery.=20
=20
> > Right now, all the points are speculation. It might be=20
> doable to engineer an ALTO discovery solution based on=20
> draft-jones-simple-web-discovery, if it becomes an IETF=20
> standard. But, as of now, I don't really understand what the=20
> benefit would be for ALTO.
>=20
> Unifying protocol stack to a single one, HTTP(S), and relying=20
> in a fully controled server framework. And there is another=20
> reason related to trust and
> security: while HTTPS is well understood and easy to deploy,=20
> DNSsec is in not such a good situation. A trustworthy=20
> discovery mechanism would be much simpler to implement and=20
> easier to adopgt by using HTTPS...

I am not a security expert. But in a typical access network scenario both t=
he network (DHCP infrastructure) and the DNS server is under control of the=
 access network operator. If there is a successful attack on the DNS infras=
tructure, there are probably worse problems than ALTO server discovery.

Also, please have a look at the security consideration section in draft-iet=
f-alto-server-discovery. The main attack on ALTO server discovery is to pro=
vide a forged ALTO server URI, e. g., an server that provides suboptimal gu=
idance regarding peer-selection. While "worse-than-random" traffic optimiza=
tion is certainly not optimal, it doesn't seem to result in a tremendous se=
curity issue neither.

Thus, unless I miss something, I don't see a significant security and trust=
 benefit for HTTP(S)-based ALTO discovery.

Michael



> If the current status of draft-jones-simple-web-discovery we=20
> could even dare incorporate in the draft the mechanisms there=20
> that are related to ALTO discovery. As far as I can tell,=20
> they are rather straightforward.
>=20
> Be goode,
>=20
> --
> "Esta vez no fallaremos, Doctor Infierno"
>=20
> Dr Diego R. Lopez
> Telefonica I+D
> http://people.tid.es/diego.lopez/
>=20
> e-mail: diego@tid.es
> Tel:    +34 913 129 041
> Mobile: +34 682 051 091
> -----------------------------------------
>=20
>=20
> ________________________________
>=20
> Este mensaje se dirige exclusivamente a su destinatario.=20
> Puede consultar nuestra pol=EDtica de env=EDo y recepci=F3n de=20
> correo electr=F3nico en el enlace situado m=E1s abajo.
> This message is intended exclusively for its addressee. We=20
> only send and receive email on the basis of the terms set out at:
> http://www.tid.es/ES/PAGINAS/disclaimer.aspx
> =

From vkg@bell-labs.com  Thu Nov 15 06:26:51 2012
Return-Path: <vkg@bell-labs.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 7A22221F8772 for <alto@ietfa.amsl.com>; Thu, 15 Nov 2012 06:26:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.799
X-Spam-Level: 
X-Spam-Status: No, score=-109.799 tagged_above=-999 required=5 tests=[AWL=0.800, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KahGLvLSufgR for <alto@ietfa.amsl.com>; Thu, 15 Nov 2012 06:26:50 -0800 (PST)
Received: from ihemail2.lucent.com (ihemail2.lucent.com [135.245.0.35]) by ietfa.amsl.com (Postfix) with ESMTP id 9E56F21F869B for <alto@ietf.org>; Thu, 15 Nov 2012 06:26:50 -0800 (PST)
Received: from usnavsmail1.ndc.alcatel-lucent.com (usnavsmail1.ndc.alcatel-lucent.com [135.3.39.9]) by ihemail2.lucent.com (8.13.8/IER-o) with ESMTP id qAFEQjvu019798 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <alto@ietf.org>; Thu, 15 Nov 2012 08:26:46 -0600 (CST)
Received: from umail.lucent.com (umail-ce2.ndc.lucent.com [135.3.40.63]) by usnavsmail1.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id qAFEQj2c026402 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <alto@ietf.org>; Thu, 15 Nov 2012 08:26:45 -0600
Received: from shoonya.ih.lucent.com (shoonya.ih.lucent.com [135.185.237.229]) by umail.lucent.com (8.13.8/TPES) with ESMTP id qAFEQjip018921 for <alto@ietf.org>; Thu, 15 Nov 2012 08:26:45 -0600 (CST)
Message-ID: <50A4FBF3.8040206@bell-labs.com>
Date: Thu, 15 Nov 2012 08:28:03 -0600
From: "Vijay K. Gurbani" <vkg@bell-labs.com>
Organization: Bell Laboratories, Alcatel-Lucent
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:13.0) Gecko/20120605 Thunderbird/13.0
MIME-Version: 1.0
To: alto <alto@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.35
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.9
Subject: [alto] Draft minutes for ALTO session in Atlanta
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Thu, 15 Nov 2012 14:26:51 -0000

Folks: The draft minutes for the ALTO session in Atlanta IETF
have been posted.  Please see

   http://www.ietf.org/proceedings/85/minutes/minutes-85-alto

As before, the above page includes links to individual MP3 recordings
for each session as well as links to individual Meetecho recordings
in case you must see the faces of the presenters.

Please send any corrections to me and Enrico at your earliest
convenience, otherwise these will become the official minutes
of the session.

Thanks,

- 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/


From sebi@gw01.ehlo.wurstkaes.de  Thu Nov 15 12:27:10 2012
Return-Path: <sebi@gw01.ehlo.wurstkaes.de>
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 8880521F88A9 for <alto@ietfa.amsl.com>; Thu, 15 Nov 2012 12:27:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.3
X-Spam-Level: 
X-Spam-Status: No, score=-2.3 tagged_above=-999 required=5 tests=[AWL=-0.300,  BAYES_00=-2.599, J_CHICKENPOX_44=0.6, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9qFUKsQZKEH8 for <alto@ietfa.amsl.com>; Thu, 15 Nov 2012 12:27:10 -0800 (PST)
Received: from gw01.ehlo.wurstkaes.de (gw01.ehlo.wurstkaes.de [IPv6:2a02:a00:e000:116::41]) by ietfa.amsl.com (Postfix) with ESMTP id CD14F21F8B0C for <alto@ietf.org>; Thu, 15 Nov 2012 12:27:09 -0800 (PST)
Received: from sebi by gw01.ehlo.wurstkaes.de with local (Exim 4.72) (envelope-from <sebi@gw01.ehlo.wurstkaes.de>) id 1TZ61T-0001fW-Es; Thu, 15 Nov 2012 21:26:51 +0100
Date: Thu, 15 Nov 2012 21:26:51 +0100
From: Sebastian Kiesel <ietf-alto@skiesel.de>
To: "Diego R. Lopez" <diego@tid.es>
Message-ID: <20121115202651.GL3249@gw01.ehlo.wurstkaes.de>
References: <1e8757a8-659a-42d2-9708-309f4b8de076@email.android.com> <E6D8B95470ED0845B3376F61DCAB1A0452AD8F3F@EX10-MB2-MAD.hi.inet> <2A886F9088894347A3BE0CC5B7A85F3E9AA0F3999B@FRMRSSXCHMBSE3.dc-m.alcatel-lucent.com> <E6D8B95470ED0845B3376F61DCAB1A0452AE0EB0@EX10-MB2-MAD.hi.inet> <20121109210042.GK3249@gw01.ehlo.wurstkaes.de> <E6D8B95470ED0845B3376F61DCAB1A0452AE54EC@EX10-MB2-MAD.hi.inet>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <E6D8B95470ED0845B3376F61DCAB1A0452AE54EC@EX10-MB2-MAD.hi.inet>
Accept-Languages: en, de
Organization: my personal mail account
User-Agent: Mutt/1.5.20 (2009-06-14)
Cc: "alto@ietf.org" <alto@ietf.org>
Subject: Re: [alto] [apps-discuss] Simple Web Discovery (SWD) Enabling	Hosted Deployments
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Thu, 15 Nov 2012 20:27:10 -0000

Hi Diego,

On Mon, Nov 12, 2012 at 02:13:00PM +0000, Diego R. Lopez wrote:
> Hi Sebastian,
> 
> On 9 Nov 2012, at 22:00 , Sebastian Kiesel wrote:
> > I think we could even do that within the ALTO protocol, see
> > http://tools.ietf.org/id/draft-kiesel-alto-alto4alto-00.txt but I also
> > believe that in a multi-domain scenario this inter-ALTO-server mesh
> > structure would be much more cumbersome than relying on DNS, and a DNS
> > resolver stub is anyway included in virtually every networked device.
> 
> 
> Was not aware about this draft, thanks for the pointer. I think this could
> be the base for what I mentioned in my last reply to Michael on relying
> on only-ALTO documents to make the specification. I still think that a
> single GET query sounds simpler than a direct access to the DNS interface,
> as well as the trust considerations are applicable.
> 
> What would you think of leaving the current discovery document as it is
> now and exploring the possibility of aligning HTTPS discovery with this
> ALTO4ALTO idea?


As you can see the ALTO4ALTO draft has expired quite some time ago.
We've been discussing architectural options for quite a while now
and there was not much positive feedback about this draft so far.

My personal favorite topic is still the third-party discovery. If we
had a working solution for that we could also use it for the resource
consumer initiated discovery.  

But 3pdisc causes lots of headaches so we decided to push forward a
simple solution at least for resource consumer initiated discovery. From
a technical point of view I think both is feasible, DHCP/DNS based
discovery as well as ALTO4ALTO style discovery, but I cannot see a clear
winner.  From procedural point of view the DHCP/DNS way has advantages
as it is based on more established and solid base protocols.

Thanks
Sebastian

From diego@tid.es  Mon Nov 19 07:49:22 2012
Return-Path: <diego@tid.es>
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 D014721F865B for <alto@ietfa.amsl.com>; Mon, 19 Nov 2012 07:49:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.644
X-Spam-Level: 
X-Spam-Status: No, score=-4.644 tagged_above=-999 required=5 tests=[AWL=-1.245, BAYES_50=0.001, J_CHICKENPOX_44=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XC6EsJ0NSYMZ for <alto@ietfa.amsl.com>; Mon, 19 Nov 2012 07:49:22 -0800 (PST)
Received: from correo-bck.tid.es (correo-bck.tid.es [195.235.93.200]) by ietfa.amsl.com (Postfix) with ESMTP id 84FAF21F8639 for <alto@ietf.org>; Mon, 19 Nov 2012 07:49:21 -0800 (PST)
Received: from sbrightmailg02.hi.inet (Sbrightmailg02.hi.inet [10.95.78.105]) by tid.hi.inet (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0MDQ00DEBRY1KO@tid.hi.inet> for alto@ietf.org; Mon, 19 Nov 2012 16:49:20 +0100 (MET)
Received: from vanvan (vanvan.hi.inet [10.95.78.49])	by sbrightmailg02.hi.inet (Symantec Messaging Gateway) with SMTP id 8C.3E.05494.0055AA05; Mon, 19 Nov 2012 16:49:20 +0100 (CET)
Received: from correo.tid.es (mailhost.hi.inet [10.95.64.100]) by tid.hi.inet (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPS id <0MDQ00DQMRY8G5@tid.hi.inet> for alto@ietf.org; Mon, 19 Nov 2012 16:49:20 +0100 (MET)
Received: from EX10-MB2-MAD.hi.inet ([169.254.2.64]) by ex10-htcas3-mad.hi.inet ([::1]) with mapi id 14.02.0318.004; Mon, 19 Nov 2012 16:48:45 +0100
Date: Mon, 19 Nov 2012 15:49:19 +0000
From: "Diego R. Lopez" <diego@tid.es>
In-reply-to: <20121115202651.GL3249@gw01.ehlo.wurstkaes.de>
X-Originating-IP: [10.95.64.115]
To: Sebastian Kiesel <ietf-alto@skiesel.de>
Message-id: <E6D8B95470ED0845B3376F61DCAB1A0452B00236@EX10-MB2-MAD.hi.inet>
Content-id: <14518D6F6CD076438D84B8A235A25B44@hi.inet>
MIME-version: 1.0
Content-type: text/plain; charset=utf-8
Content-language: en-US
Content-transfer-encoding: base64
Accept-Language: en-US
Thread-topic: [alto] [apps-discuss] Simple Web Discovery (SWD) Enabling	Hosted Deployments
Thread-index: AQHNw2+HNn7Xrdd+00a7zBhELsZ285fxDm8A
X-AuditID: 0a5f4e69-b7fc06d000001576-cf-50aa55004aad
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrLKsWRmVeSWpSXmKPExsXCFe9nqMsQuirAYMI8KYuH2/eyOjB6LFny kymAMYrLJiU1J7MstUjfLoErY8/lY+wFC4QrLqxZzdrA+ECoi5GTQ0LAROLd2vPsELaYxIV7 69m6GLk4hAS2MUqcu7qbBcL5zijRt2UXlDONUeL/xH4mkBYWAVWJeRf6mUFsNiD7UfNvsFHC AtES3y61gsU5BawlLm4EaQZZoSDx59xjMFtEQFviz9tHYPXMAmkSa169B7N5Bbwlbq5phYqb Sfyb8JcFIi4o8WPyPSCbAyiuLjFlSi5EibhEc+tNFghbUWLaogZGEJsR6Jvvp9YwQayKkZix dBOUbSRx/+41qI8FJJbsOc8MYYtKvHz8jxXix0PMEidev2KdwCgxC8kZs5CcMQvhjFlIzpiF 5IwFjKyrGMWKk4oy0zNKchMzc9INjPQyMvUy81JLNjFC4i5zB+PynSqHGAU4GJV4eD1urwwQ Yk0sK67MPcQoycGkJMqbH7wqQIgvKT+lMiOxOCO+qDQntfgQowQHs5II7ysloBxvSmJlVWpR PkxKhoNDSYJ3I0ibYFFqempFWmYOMLnApJk4OEHaeYDaj4DU8BYXJOYWZ6ZD5E8xSkqJ8+4C SQiAJDJK8+B6XzGKAx0pzDsXJMsDTINwXa+ABjIBDbwWsBxkYEkiQkqqgTFymbLvr0/trPv6 p2x7usysL/uWpU7DGdkl3OJzAwuWSbRHZMzaxzdZ02r7PTONaVnl+WftU8//njlxup/qg9fn z27dZMPGaqfDmlTW/0N6172bztbxTkvvXeoqSm/uu7ru1h3zqeIJfm9Ki148O5M2Ofa8stbT 7pnWdqut1l98VTV3/6z+p/xKLMUZiYZazEXFiQCrXLnSQAMAAA==
References: <1e8757a8-659a-42d2-9708-309f4b8de076@email.android.com> <E6D8B95470ED0845B3376F61DCAB1A0452AD8F3F@EX10-MB2-MAD.hi.inet> <2A886F9088894347A3BE0CC5B7A85F3E9AA0F3999B@FRMRSSXCHMBSE3.dc-m.alcatel-lucent.com> <E6D8B95470ED0845B3376F61DCAB1A0452AE0EB0@EX10-MB2-MAD.hi.inet> <20121109210042.GK3249@gw01.ehlo.wurstkaes.de> <E6D8B95470ED0845B3376F61DCAB1A0452AE54EC@EX10-MB2-MAD.hi.inet> <20121115202651.GL3249@gw01.ehlo.wurstkaes.de>
Cc: "alto@ietf.org" <alto@ietf.org>
Subject: Re: [alto] [apps-discuss] Simple Web Discovery (SWD) Enabling	Hosted Deployments
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Mon, 19 Nov 2012 15:49:22 -0000

SGkgU2ViYXN0aWFuLA0KDQpPbiAxNSBOb3YgMjAxMiwgYXQgMjE6MjYgLCBTZWJhc3RpYW4gS2ll
c2VsIHdyb3RlOg0KPiBBcyB5b3UgY2FuIHNlZSB0aGUgQUxUTzRBTFRPIGRyYWZ0IGhhcyBleHBp
cmVkIHF1aXRlIHNvbWUgdGltZSBhZ28uDQo+IFdlJ3ZlIGJlZW4gZGlzY3Vzc2luZyBhcmNoaXRl
Y3R1cmFsIG9wdGlvbnMgZm9yIHF1aXRlIGEgd2hpbGUgbm93DQo+IGFuZCB0aGVyZSB3YXMgbm90
IG11Y2ggcG9zaXRpdmUgZmVlZGJhY2sgYWJvdXQgdGhpcyBkcmFmdCBzbyBmYXIuDQo+DQo+IE15
IHBlcnNvbmFsIGZhdm9yaXRlIHRvcGljIGlzIHN0aWxsIHRoZSB0aGlyZC1wYXJ0eSBkaXNjb3Zl
cnkuIElmIHdlDQo+IGhhZCBhIHdvcmtpbmcgc29sdXRpb24gZm9yIHRoYXQgd2UgY291bGQgYWxz
byB1c2UgaXQgZm9yIHRoZSByZXNvdXJjZQ0KPiBjb25zdW1lciBpbml0aWF0ZWQgZGlzY292ZXJ5
Lg0KPg0KPiBCdXQgM3BkaXNjIGNhdXNlcyBsb3RzIG9mIGhlYWRhY2hlcyBzbyB3ZSBkZWNpZGVk
IHRvIHB1c2ggZm9yd2FyZCBhDQo+IHNpbXBsZSBzb2x1dGlvbiBhdCBsZWFzdCBmb3IgcmVzb3Vy
Y2UgY29uc3VtZXIgaW5pdGlhdGVkIGRpc2NvdmVyeS4gRnJvbQ0KPiBhIHRlY2huaWNhbCBwb2lu
dCBvZiB2aWV3IEkgdGhpbmsgYm90aCBpcyBmZWFzaWJsZSwgREhDUC9ETlMgYmFzZWQNCj4gZGlz
Y292ZXJ5IGFzIHdlbGwgYXMgQUxUTzRBTFRPIHN0eWxlIGRpc2NvdmVyeSwgYnV0IEkgY2Fubm90
IHNlZSBhIGNsZWFyDQo+IHdpbm5lci4gIEZyb20gcHJvY2VkdXJhbCBwb2ludCBvZiB2aWV3IHRo
ZSBESENQL0ROUyB3YXkgaGFzIGFkdmFudGFnZXMNCj4gYXMgaXQgaXMgYmFzZWQgb24gbW9yZSBl
c3RhYmxpc2hlZCBhbmQgc29saWQgYmFzZSBwcm90b2NvbHMuDQoNCg0KQXMgSSBzYWlkIGluIG15
IHJlcGx5IHRvIE1pY2hhZWwsIHByb2JhYmx5IGl0IG1ha2VzIHNlbnNlIHRvIGNvbnNpZGVyDQp0
aGUgSFRUUChTKSBiYXNlZCBkaXNjb3ZlcnkgZm9yIHRoZSBmdXR1cmUgZXZvbHV0aW9uIG9mIHRo
ZSBwcm90b2NvbCAoYXMNCm1vc3RseSBkaXNjdXNzZWQgaW4gdGhlIGkyYWV4IEJvRiksIGFuZCBz
dGF5IGluIHRoZSBETlMgcGF0aCBzbyB3ZQ0KaGF2ZSBhIGZpcnN0IHZlcnNpb24gb2YgYWxsIHJl
cXVpcmVkIG1lY2hhbmlzbXMgc29vbi4NCg0KQmUgZ29vZGUsDQoNCi0tDQoiRXN0YSB2ZXogbm8g
ZmFsbGFyZW1vcywgRG9jdG9yIEluZmllcm5vIg0KDQpEciBEaWVnbyBSLiBMb3Bleg0KVGVsZWZv
bmljYSBJK0QNCmh0dHA6Ly9wZW9wbGUudGlkLmVzL2RpZWdvLmxvcGV6Lw0KDQplLW1haWw6IGRp
ZWdvQHRpZC5lcw0KVGVsOiAgICArMzQgOTEzIDEyOSAwNDENCk1vYmlsZTogKzM0IDY4MiAwNTEg
MDkxDQotLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQ0KDQoNCl9fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fDQoNCkVzdGUgbWVuc2FqZSBzZSBkaXJpZ2UgZXhj
bHVzaXZhbWVudGUgYSBzdSBkZXN0aW5hdGFyaW8uIFB1ZWRlIGNvbnN1bHRhciBudWVzdHJhIHBv
bMOtdGljYSBkZSBlbnbDrW8geSByZWNlcGNpw7NuIGRlIGNvcnJlbyBlbGVjdHLDs25pY28gZW4g
ZWwgZW5sYWNlIHNpdHVhZG8gbcOhcyBhYmFqby4NClRoaXMgbWVzc2FnZSBpcyBpbnRlbmRlZCBl
eGNsdXNpdmVseSBmb3IgaXRzIGFkZHJlc3NlZS4gV2Ugb25seSBzZW5kIGFuZCByZWNlaXZlIGVt
YWlsIG9uIHRoZSBiYXNpcyBvZiB0aGUgdGVybXMgc2V0IG91dCBhdDoNCmh0dHA6Ly93d3cudGlk
LmVzL0VTL1BBR0lOQVMvZGlzY2xhaW1lci5hc3B4DQo=

From diego@tid.es  Mon Nov 19 07:49:23 2012
Return-Path: <diego@tid.es>
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 6DC3021F8639 for <alto@ietfa.amsl.com>; Mon, 19 Nov 2012 07:49:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.831
X-Spam-Level: 
X-Spam-Status: No, score=-4.831 tagged_above=-999 required=5 tests=[AWL=-0.832, BAYES_50=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id w5PctLQ2aUf9 for <alto@ietfa.amsl.com>; Mon, 19 Nov 2012 07:49:22 -0800 (PST)
Received: from tidos.tid.es (tidos.tid.es [195.235.93.44]) by ietfa.amsl.com (Postfix) with ESMTP id 638A521F8593 for <alto@ietf.org>; Mon, 19 Nov 2012 07:49:21 -0800 (PST)
Received: from sbrightmailg01.hi.inet (sbrightmailg01.hi.inet [10.95.64.104]) by tid.hi.inet (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0MDQ006TARY1JY@tid.hi.inet> for alto@ietf.org; Mon, 19 Nov 2012 16:49:19 +0100 (MET)
Received: from tid (tid.hi.inet [10.95.64.10])	by sbrightmailg01.hi.inet (Symantec Messaging Gateway) with SMTP id 33.F8.03143.FF45AA05; Mon, 19 Nov 2012 16:49:19 +0100 (CET)
Received: from correo.tid.es (mailhost.hi.inet [10.95.64.100]) by tid.hi.inet (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPS id <0MDQ0063DRY7LT@tid.hi.inet> for alto@ietf.org; Mon, 19 Nov 2012 16:49:19 +0100 (MET)
Received: from EX10-MB2-MAD.hi.inet ([169.254.2.64]) by EX10-HTCAS6-MAD.hi.inet ([fe80::e1e3:e2fc:beda:deb9%15]) with mapi id 14.02.0318.004; Mon, 19 Nov 2012 16:49:18 +0100
Date: Mon, 19 Nov 2012 15:49:18 +0000
From: "Diego R. Lopez" <diego@tid.es>
In-reply-to: <2A886F9088894347A3BE0CC5B7A85F3E9AA0F0A8E4@FRMRSSXCHMBSE3.dc-m.alcatel-lucent.com>
X-Originating-IP: [10.95.64.115]
To: "Scharf, Michael (Michael)" <michael.scharf@alcatel-lucent.com>
Message-id: <E6D8B95470ED0845B3376F61DCAB1A0452B0022C@EX10-MB2-MAD.hi.inet>
Content-id: <91552DD1C3FFAD4AA3D782CA8FE6DA49@hi.inet>
MIME-version: 1.0
Content-type: text/plain; charset=utf-8
Content-language: en-US
Content-transfer-encoding: base64
Accept-Language: en-US, es-ES
Thread-topic: [alto] [apps-discuss] Simple Web Discovery (SWD) Enabling	Hosted Deployments
Thread-index: AQHNvqaRADfxHISJBE2aQ8YJfrM/WJfh1IeggARdBwCAA5CUEIAHVduA
X-AuditID: 0a5f4068-b7f746d000000c47-77-50aa54ffb1e8
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrHKsWRmVeSWpSXmKPExsXCFe/Apfs/ZFWAwe7nYhYPt+9ldWD0WLLk J1MAYxSXTUpqTmZZapG+XQJXRmPDZNaCI94V+z7/Ym5gPOPZxcjJISFgIrGivZcRwhaTuHBv PVsXIxeHkMAGRokdmxawQzjfGSU6r7VDZTYySnx5dRSshUVAVaKtfy8LiM0GZD9q/s0OYgsL REvcnfGRqYuRg4NTIEmi7105xAYFiT/nHoOViwg4S/xa3cQMYjMLKEucW3GTFcTmFfCW+N22 DCpuJvG2+xkbRFxQ4sfkeywgI5kF1CWmTMmFKBGXaG69yQJhK0pMW9QAdhmjgKzEu/nzWSFW xUh8bj/BCGG7SdxYfZ8V4hwBiSV7zjND2KISLx//Y4V4sYdFonvHAuYJjBKzkJwxC8kZsxDO mIXkjFlIzljAyLqKUaw4qSgzPaMkNzEzJ93AUC8jUy8zL7VkEyMk6jJ2MC7fqXKIUYCDUYmH 1+P2ygAh1sSy4srcQ4ySHExKorz5wasChPiS8lMqMxKLM+KLSnNSiw8xSnAwK4nwvlICyvGm JFZWpRblw6RkODiUJHi/grQJFqWmp1akZeYAUwtMmomDE6SdB6idKQSkvbggMbc4Mx0if4pR m2POzPYnjBwdh7qfMAqx5OXnpUqJ8+4CGScAUppRmgc37RWjONDZwry3QLI8wEQJN+cV0Aom oBXXApaDrChJREhJNTAWT5P0D93wR/D7/hPidma5izI32/UJik15U8Rftn7mkXfv+M8t6t3w 82b7PranSzoM9q5ZmG+gdCG47rvknswNz98uTGz9tGDyyoLT8R1Nm8QCpPNUzwjNypS+yBiV WWqbbXZFcm9kYvNpgWn7z92+9+TvxJenJodNeHnA4F3gC/dbd7VVAhdOVGIpzkg01GIuKk4E AKo/70VRAwAA
References: <1e8757a8-659a-42d2-9708-309f4b8de076@email.android.com> <E6D8B95470ED0845B3376F61DCAB1A0452AD8F3F@EX10-MB2-MAD.hi.inet> <2A886F9088894347A3BE0CC5B7A85F3E9AA0F3999B@FRMRSSXCHMBSE3.dc-m.alcatel-lucent.com> <E6D8B95470ED0845B3376F61DCAB1A0452AE0EB0@EX10-MB2-MAD.hi.inet> <2A886F9088894347A3BE0CC5B7A85F3E9AA0F0A840@FRMRSSXCHMBSE3.dc-m.alcatel-lucent.com> <E6D8B95470ED0845B3376F61DCAB1A0452AE54E3@EX10-MB2-MAD.hi.inet> <2A886F9088894347A3BE0CC5B7A85F3E9AA0F0A8E4@FRMRSSXCHMBSE3.dc-m.alcatel-lucent.com>
Cc: "alto@ietf.org" <alto@ietf.org>
Subject: Re: [alto] [apps-discuss] Simple Web Discovery (SWD) Enabling	Hosted	Deployments
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Mon, 19 Nov 2012 15:49:23 -0000

SGkgTWljaGFlbCwNCg0KT24gMTQgTm92IDIwMTIsIGF0IDIxOjQ1ICwgU2NoYXJmLCBNaWNoYWVs
IChNaWNoYWVsKSB3cm90ZToNCj4gTXkgbWFpbiBwb2ludCBpcyB0aGF0IHRoaXMgaGFzIHRvIGJl
IHNvcnRlZCBvdXQgZS4gZy4gaW4gQVBQQVJFQSBiZWZvcmUgd2UgY2FuIHJlbHkgb24gYW4gUkZD
IGluIHRoYXQgc3BhY2UuIEl0IGlzIHVuY2xlYXIgdG8gbWUgd2hldGhlciBkcmFmdC1qb25lcy1z
aW1wbGUtd2ViLWRpc2NvdmVyeSB3aWxsIGJlIGEgbWF0dXJlIGFuZCB3aWRlbHkgdXNlZCB0ZWNo
bmlxdWUgYW55IHRpbWUgc29vbi4NCg0KQW5kLCBhcyBJIHNhaWQsIHRoYXQncyBhIGdvb2QgcG9p
bnQgaW4gd2hhdCByZWxhdGVzIHRvIHRoYXQgZHJhZnQgaXRzZWxmLg0KDQo+IFN1cmUsIGEgSFRU
UChTKSBkaXNjb3ZlcnkgbWVjaGFuaXNtcyBoYXMgYmVuZWZpdHMgaW4gYSBXZWIgd29ybGQuIEJ1
dCBETlMgYWxzbyBoYXMgYmVuZWZpdHMuIFRoZXJlIGlzIGFuIGVuZ2luZWVyaW5nIHRyYWRlb2Zm
Lg0KPg0KPiBUaHVzLCBJIGRpc2FncmVlIHRoYXQgSFRUUChTKSBpcyB0aGUgIm1vc3QgbmF0dXJh
bCB3YXkiLg0KDQpJdCBpcyBuYXR1cmFsIGluIHRoZSBzZW5zZSB0aGF0IHlvdSBjb25jZWl2YWJs
eSB3cml0ZSBhIGZ1bGwgQUxUTyBjbGllbnQNCnVzaW5nIGhpZ2gtbGV2ZWwgaW50ZXJmYWNlcyB0
byBIVFRQKFMpIGNvbm5lY3Rpb25zIChJIHRoaW5rIHdlIGFsbA0Ka25vdyBtYW55IG9mIHRoZW0g
aW4gSmF2YSwgUHl0aG9uIG9yIFBlcmwganVzdCB0byBuYW1lIGEgZmV3IGxhbmd1YWdlcyksDQp3
aXRob3V0IHJlcXVpcmluZyBhbnkgYWRkaXRpb25hbCBpbnRlcmZhY2UgdG8gbmV0d29yayBzZXJ2
aWNlcywgd2l0aA0KdGhlIGV4Y2VwdGlvbiBvZiB0aGUgcmVxdWlyZW1lbnRzIGZvciBkaXNjb3Zl
cnkuDQoNCj4gTXkgY29uY2VybiBpcyB0aGF0IFJGQyA1OTg2IGFubm91bmNlcyBhbiBhY2Nlc3Mg
bmV0d29yayBkb21haW4gbmFtZSwgc3VjaCBhcyAiZHNsLndlc3Rjb2FzdC5teWlzcC5uZXQiLg0K
Pg0KPiBJbiBteSB1bmRlcnN0YW5kaW5nLCBkcmFmdC1qb25lcy1zaW1wbGUtd2ViLWRpc2NvdmVy
eSByZXF1aXJlcyB0aGF0IGEgV2ViIHNlcnZlciBpcyBydW5uaW5nIGF0IGh0dHBzOi8vc2wud2Vz
dGNvYXN0Lm15aXNwLm5ldC8ud2VsbC1rbm93bi9zaW1wbGUtd2ViLWRpc2NvdmVyeSAuIEZ1cnRo
ZXJtb3JlLCB1bmxlc3MgSSBtaXNzIHNvbWV0aGluZywgdGhlcmUgaXMgbm8gbmVlZCBmb3IgYW4g
RE5TIGVudHJ5IHRoYXQgbWFwcyAiZHNsLndlc3Rjb2FzdC5teWlzcC5uZXQiIHRvIHNwZWNpZmlj
IGhvc3QgcmlnaHQgbm93Lg0KPg0KPiBUaHVzLCBmb3IgZHJhZnQtam9uZXMtc2ltcGxlLXdlYi1k
aXNjb3ZlcnkgdG8gd29yayB3aXRoIFJGQyA1OTg2LCBhbiBJU1AgbWlnaHQgaGF2ZSB0byBhZGQg
bmV3IEROUyBlbnRyaWVzIGZvciBlYWNoIGFjY2VzcyBuZXR3b3JrIGRvbWFpbiBuYW1lLCBwb2lu
dGluZyB0byBhIFdlYiBzZXJ2ZXIsIHRoYXQgdGhlbiBmaWd1cmVzIG91dCB0aGUgY2xvc2VzdCBB
TFRPIHNlcnZlciBVUkkuIFdpdGggVS1OQVBUUiwgdGhlIEROUyBzZXJ2ZXIganVzdCBnaXZlcyB0
aGUgY2xvc2VzdCBBTFRPIHNlcnZlciBVUkkgZGlyZWN0bHkuDQo+DQo+IEluIHN1bW1hcnk6DQo+
DQo+IC0gQm90aCB2YXJpYW50cyBhcmUgbGlrZWx5IHRvIHJlcXVpcmUgbmV3IEROUyBlbnRyaWVz
DQo+IC0gZHJhZnQtam9uZXMtc2ltcGxlLXdlYi1kaXNjb3ZlcnkgcmVxdWlyZXMgb25lIG1vcmUg
aW5kaXJlY3Rpb24sIGkuIGUuLCBvbmUgbW9yZSBzeXN0ZW0gdG8gY29uZmlndXJlLCBhbmQgb25l
IG1vcmUgc3lzdGVtIHRoYXQgaGFzIHRvIGJlIGF3YXJlIG9mIHRoZSBuZXR3b3JrIHRvcG9sb2d5
IHRvIGZpZ3VyZSBvdXQgdGhlIGNsb3Nlc3QgQUxUTyBzZXJ2ZXIsIGV0Yy4NCg0KTXkgZXhwZXJp
ZW5jZSB3aXRoIHRlYW1zIG9wZXJhdGluZyBwcm9kdWN0aW9uIEROUyBzZXJ2ZXJzIGlzIHRoYXQg
dGhleSBhcmUNCm1vcmUga2VlbiBvbiBkZXBsb3lpbmcgIndlbGwta25vd24iIHJlY29yZHMgKG5v
dGUgdGhlIHF1b3RlcywgSSBrbm93DQpVLU5BUFRSIGlzIHBhcnQgb2YgdGhlIHN0YW5kYXJkIHJl
Y29yZHMpIGxpa2UgdGhlIENOQU1FcyB0aGF0IHdvdWxkIGJlDQpyZXF1aXJlZCBpbiB0aGUgY2Fz
ZSBvZiB1c2luZyBIVFRQKFMpIGZvciBkaXNjb3ZlcnkuIEZ1cnRoZXJtb3JlLCB0aGUNCmFkZGl0
aW9uYWwgbGV2ZWwgb2YgaW5kaXJlY3Rpb24gY2FuIGJlIGFuIGFkdmFudGFnZSBmb3Igb3BlcmF0
aW9ucyBzaW5jZToNCg0KMSkgWW91IHdvbid0IG5lZWQgdG8gY29vcmRpbmF0ZSB0aGUgRE5TIGFu
ZCBBTFRPIHRlYW1zIGlmIHRoZXkgYXJlIG5vdCB0aGUNCnNhbWUuIEROUyBiZWluZyBhIGN1cnJl
bnRseSBjcml0aWNhbCBpbmZyYXN0cnVjdHVyZSBtYWtlcyBpdCBoYXJkZXIgdG8gdHdlYWsuDQoN
CjIpIFVwZGF0ZXMgd29uJ3QgcmVxdWlyZSBkZWFsaW5nIHdpdGggdGhlIHVzdWFsIEROUyBUVEwg
cHJvY2VkdXJlcy4NCg0KPiBPYnZpb3VzbHksIGFuIGFsdGVybmF0aXZlIHdvdWxkIGJlIHRvIHNw
ZWNpZnkgYSBuZXcgREhDUCBvcHRpb24gdGhhdCBkaXJlY3RseSBhbm5vdW5jZXMgdGhlIFVSSSBv
ZiB0aGUgU1dEIFdlYiBTZXJ2ZXIuIFRoYXQgaXMgbm90IHZlcnkgZGlmZmVyZW50IHRvIGEgREhD
UCBvcHRpb24gdGhhdCBqdXN0IGVuY29kZXMgdGhlIEFMVE8gc2VydmVyIFVSSS4gVGhpcyBpcyBh
bGwgZG9hYmxlLCBhdCBsZWFzdCBpbiBwcmluY2lwbGUuIEJ1dCB0aGUgYXBwcm9hY2ggb2YgZW5j
b2RpbmcgVVJJcyBpbiBESENQIGdvdCBwcmV0dHkgc3Ryb25nIHB1c2hiYWNrIGluIHByZXZpb3Vz
IEFMVE8gbWVldGluZ3MsIGFzIGZhciBhcyBJIHJlY2FsbC4NCg0KQWdyZWVkLiBObyBpbnRlbnRp
b24gdG8gcmUtb3BlbiB0aGlzIGlzc3VlIGFueXdheS4NCg0KPiBNeSBwb2ludCBpcyB0aGF0IEFM
VE8gc2VydmVyIGRpc2NvdmVyeSBoYXMgdG8gZmlndXJlIG91dCB3aGF0IHNlcnZlciBjYW4gcHJv
dmlkZSBndWlkYW5jZSBmb3IgYSBzcGVjaWZpYyBhY2Nlc3MgbmV0d29yaywgdGFraW5nIGludG8g
YWNjb3VudCByZW51bWJlcmluZywgZG9tYWluIG5hbWUgbWlncmF0aW9ucywgZXRjLiBJIGFtIG5v
dCBzdXJlIGlmIHRoZSBvcmdhbml6YXRpb25hbCB1bml0IG9mIGFuIElTUCB0aGF0IHJ1bnMgdGhl
IFdlYiBwbGF0Zm9ybSByZWFsbHkgaGFzIGEgYmV0dGVyIHVuZGVyc3RhbmRpbmcgb2YgdGhlIGFj
Y2VzcyBuZXR3b3JrIHRvcG9sb2d5IGFuZCBuYW1pbmcgdGhhbiB0aGUgb3JnYW5pemF0aW9uIHVu
aXQgdGhhdCBydW5zIEROUyBhbmQgREhDUC4gSSdkIGFzc3VtZSB0aGUgb3Bwb3NpdGUuIFN1cmUs
IGl0IGlzIHVwIHRvIGFuIElTUCB0byBzb3J0IHRoaXMgb3V0Lg0KDQpUaGUgcG9pbnQgaGVyZSBp
cyBob3cgb3BlcmF0aW9ucyBhcmUgb3JnYW5pemVkLiBZb3UgYXNzdW1lIERIQ1AgYW5kIEROUyAo
YW5kDQpBTFRPKSBtYW5hZ2VtZW50IGNvcnJlc3BvbmQgdG8gdGhlIHNhbWUgdW5pdC4gTXkgcG9p
bnQgaXMgdGhhdCB3aG9ldmVyIGlzDQppbiBjaGFyZ2Ugb2YgdGhlIEFMVE8gY29udGVudCAobm90
IHRoZSBXZWIgc2VydmVycyB0aGVtc2VsdmVzKSBjb3VsZCBtYWtlDQp0aGUgdXBkYXRlcyBpbiB0
aGUgY2FzZSBvZiBIVFRQKFMpIGRpc2NvdmVyeS4NCg0KPiBOby4gVGhlIHNvbGUgcHVycG9zZSBm
b3IgdGhlIGRpc2NvdmVyeSBpcyB0byBmaW5kIHRoZSBVUkkgb2YgYSBzdWl0YWJsZSBBTFRPIHNl
cnZlci4NCg0KQnV0LCBmb2xsb3dpbmcgdGhlIHNhbWUgbW9kZWwgb2YgVS1OQVBUUiwgSSBndWVz
cyBtYW55IEFMVE8gcXVlcmllcyBjb3VsZA0KYmUgcGVmb3JtZWQgYXMgd2VsbC4gQnV0LCBhbnl3
YXksIEkgYWNrbm93bGVkZ2UgaXQgd2FzIGEgcmF0aGVyIHJoZXRvcmljYWwNCnF1ZXN0aW9uLg0K
DQo+IEZvciBpbnN0YW5jZSwgSSBhbSBjb25jZXJuZWQgYWJvdXQgYSBzY2VuYXJpbyB3aGVyZSBh
IHRyYW5zcGFyZW50IEhUVFAgcHJveHkgaXMgZGVwbG95ZWQgaW5zaWRlIHRoZSBhY2Nlc3MgbmV0
d29yay4gRm9yIGluc3RhbmNlLCBhc3N1bWUgdGhhdCBhbGwgY2xpZW50IHRyYWZmaWMgb24gcG9y
dCA4MCBhbmQgNDQzIGlzIGZvcmNlZCB0aHJvdWdoIGEgcHJveHkuIFRoZSBzY2VuYXJpbyBpcyB0
aGVuIGFzIGZvbGxvd3M6DQo+DQo+IEFMVE8gZGlzY292ZXJ5IGNsaWVudCA8LS0tPiBIVFRQIHBy
b3h5IDwtLS0+IFNXRCBkaXNjb3Zlcnkgc2VydmVyDQo+DQo+IEluIHRoYXQgc2V0dGluZywgdW5s
ZXNzIEkgbWlzcyBzb21ldGhpbmcsIGl0IGNhbiBiZSBkaWZmaWN1bHQgZm9yIHRoZSBTV0QgZGlz
Y292ZXJ5IHNlcnZlciB0byBmaWd1cmUgd2hhdCBBTFRPIHNlcnZlciBjb3VsZCBwcm92aWRlIGd1
aWRhbmNlIHRvIGNsaWVudHMgYmVoaW5kIHRoZSBwcm94eS4gQWxzbywgbm90ZSB0aGF0IHRoZSBB
TFRPIHNlcnZlciBkb2VzIG5vdCBoYXZlIHRvIHJ1biBvbiBwb3J0IDgwIG9yIDQ0MywgaS4gZS4s
IEFMVE8gcXVlcmllcyBtYXkgb3IgbWF5IG5vdCBoYXZlIHRvIHBhc3MgdGhyb3VnaCB0aGUgSFRU
UCBwcm94eSB0aGVtc2VsdmVzLg0KPg0KPiBBbnkgbWlkZGxlYm94IHNjZW5hcmlvIGlzIGRpZmZp
Y3VsdCBmb3IgQUxUTyBkaXNjb3ZlcnksIHNpbWlsYXIgbGlrZSBOQVBULiBCdXQgbWlkZGxlYm94
ZXMgb24gcG9ydCA4MCBhbmQgNDQzIGFyZSBxdWl0ZSBmcmVxdWVudC4gQW5kIEkgZG9uJ3QgdGhp
bmsgaXQgaXMgd2VsbCB1bmRlcnN0b29kIGhvdyB0aGlzIGFmZmVjdHMgQUxUTyBkaXNjb3Zlcnku
DQoNCkJ1dCB0aGUgcHJvYmxlbSB5b3UgZGVzY3JpYmUgd291bGQgYmUgdGhlIHNhbWUgaW4gdGhl
IGNhc2Ugb2Ygbm9ybWFsIEFMVE8NCnF1ZXJpZXMgdW5sZXNzIGV4cGxpY2l0IGNsaWVudCBpZGVu
dGlmaWNhdGlvbiBpcyByZXF1aXJlZC4gVGhlIHVzYWdlIG9mDQpIVFRQKFMpIHRyYW5zcGFyZW50
IG1pZGRsZWJveGVzIGlzIGFuIGlzc3VlIGZvciBhbnkgcHJvdG9jb2wgcmVseWluZyBvbg0KdGhh
dCB0cmFuc3BvcnQuDQoNCj4gSSBhbSBub3QgYSBzZWN1cml0eSBleHBlcnQuIEJ1dCBpbiBhIHR5
cGljYWwgYWNjZXNzIG5ldHdvcmsgc2NlbmFyaW8gYm90aCB0aGUgbmV0d29yayAoREhDUCBpbmZy
YXN0cnVjdHVyZSkgYW5kIHRoZSBETlMgc2VydmVyIGlzIHVuZGVyIGNvbnRyb2wgb2YgdGhlIGFj
Y2VzcyBuZXR3b3JrIG9wZXJhdG9yLiBJZiB0aGVyZSBpcyBhIHN1Y2Nlc3NmdWwgYXR0YWNrIG9u
IHRoZSBETlMgaW5mcmFzdHJ1Y3R1cmUsIHRoZXJlIGFyZSBwcm9iYWJseSB3b3JzZSBwcm9ibGVt
cyB0aGFuIEFMVE8gc2VydmVyIGRpc2NvdmVyeS4NCg0KU3VyZS4gQnV0IGRvZXMgbm90IHByZWNs
dWRlIHRoYXQgQUxUTyBzZXJ2ZXIgZGlzY292ZXJ5IHdvdWxkIGJlIGFuIGFkZGl0aW9uYWwNCnNl
cnZpY2UgYXQgcmlzay4NCg0KPiBBbHNvLCBwbGVhc2UgaGF2ZSBhIGxvb2sgYXQgdGhlIHNlY3Vy
aXR5IGNvbnNpZGVyYXRpb24gc2VjdGlvbiBpbiBkcmFmdC1pZXRmLWFsdG8tc2VydmVyLWRpc2Nv
dmVyeS4gVGhlIG1haW4gYXR0YWNrIG9uIEFMVE8gc2VydmVyIGRpc2NvdmVyeSBpcyB0byBwcm92
aWRlIGEgZm9yZ2VkIEFMVE8gc2VydmVyIFVSSSwgZS4gZy4sIGFuIHNlcnZlciB0aGF0IHByb3Zp
ZGVzIHN1Ym9wdGltYWwgZ3VpZGFuY2UgcmVnYXJkaW5nIHBlZXItc2VsZWN0aW9uLiBXaGlsZSAi
d29yc2UtdGhhbi1yYW5kb20iIHRyYWZmaWMgb3B0aW1pemF0aW9uIGlzIGNlcnRhaW5seSBub3Qg
b3B0aW1hbCwgaXQgZG9lc24ndCBzZWVtIHRvIHJlc3VsdCBpbiBhIHRyZW1lbmRvdXMgc2VjdXJp
dHkgaXNzdWUgbmVpdGhlci4NCg0KSW5kZWVkLCB0aGF0IGFwcGxpZXMgZm9yIHRoZSBjdXJyZW50
IEFMVE8gdXNlIGNhc2VzLiBCdXQgaWYgd2UgdGhpbmsgYWJvdXQNCnRob3NlIGRpc2N1c3NlZCBp
biB0aGUgaTJhZXggQm9GLCBhbmQgdGhlIGV4dGVuc2lvbnMgcmVjZW50bHkgcHJvcG9zZWQgb24N
ClNjaGVkdWxlZCBNYXBzIHRoYXQgZGVwaWN0cyB1c2FnZSBmb3IgaW5mb3JtYXRpb24gb24gU0RO
IHBvbGljaWVzLCB0cnVzdA0KYmVjb21lIGEgbXVjaCBtb3JlIGltcG9ydGFudCBwYXJ0IG9mIHRo
ZSBlcXVhdGlvbi4NCg0KPiBUaHVzLCB1bmxlc3MgSSBtaXNzIHNvbWV0aGluZywgSSBkb24ndCBz
ZWUgYSBzaWduaWZpY2FudCBzZWN1cml0eSBhbmQgdHJ1c3QgYmVuZWZpdCBmb3IgSFRUUChTKS1i
YXNlZCBBTFRPIGRpc2NvdmVyeS4NCg0KDQpZZWFoLiBZb3UgYXJlIHByb2JhYmx5IHJpZ2h0IGlu
IHRoYXQgdGhlc2UgdHJ1c3QgY29uc2lkZXJhdGlvbnMgYXBwbHkgdG8gdXNlDQpjYXNlcyBvdXRz
aWRlIG9mIHRoZSBjdXJyZW50IHNjb3BlLiBCdXQgSSBzdGlsbCB0aGluayB0aGV5IGFyZSByZWxl
dmFudCBmb3INCnRoZSBmdXR1cmUgZXZvbHV0aW9uIG9mIHRoZSBwcm90b2NvbC4NCg0KQmUgZ29v
ZGUsDQotLQ0KIkVzdGEgdmV6IG5vIGZhbGxhcmVtb3MsIERvY3RvciBJbmZpZXJubyINCg0KRHIg
RGllZ28gUi4gTG9wZXoNClRlbGVmb25pY2EgSStEDQpodHRwOi8vcGVvcGxlLnRpZC5lcy9kaWVn
by5sb3Blei8NCg0KZS1tYWlsOiBkaWVnb0B0aWQuZXMNClRlbDogICAgKzM0IDkxMyAxMjkgMDQx
DQpNb2JpbGU6ICszNCA2ODIgMDUxIDA5MQ0KLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0NCg0KDQpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KDQpFc3Rl
IG1lbnNhamUgc2UgZGlyaWdlIGV4Y2x1c2l2YW1lbnRlIGEgc3UgZGVzdGluYXRhcmlvLiBQdWVk
ZSBjb25zdWx0YXIgbnVlc3RyYSBwb2zDrXRpY2EgZGUgZW52w61vIHkgcmVjZXBjacOzbiBkZSBj
b3JyZW8gZWxlY3Ryw7NuaWNvIGVuIGVsIGVubGFjZSBzaXR1YWRvIG3DoXMgYWJham8uDQpUaGlz
IG1lc3NhZ2UgaXMgaW50ZW5kZWQgZXhjbHVzaXZlbHkgZm9yIGl0cyBhZGRyZXNzZWUuIFdlIG9u
bHkgc2VuZCBhbmQgcmVjZWl2ZSBlbWFpbCBvbiB0aGUgYmFzaXMgb2YgdGhlIHRlcm1zIHNldCBv
dXQgYXQ6DQpodHRwOi8vd3d3LnRpZC5lcy9FUy9QQUdJTkFTL2Rpc2NsYWltZXIuYXNweA0K

From michael.scharf@alcatel-lucent.com  Mon Nov 19 08:54:41 2012
Return-Path: <michael.scharf@alcatel-lucent.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 8BABB21F855E for <alto@ietfa.amsl.com>; Mon, 19 Nov 2012 08:54:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.643
X-Spam-Level: 
X-Spam-Status: No, score=-7.643 tagged_above=-999 required=5 tests=[AWL=-1.394, BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JXStfygL3rvS for <alto@ietfa.amsl.com>; Mon, 19 Nov 2012 08:54:41 -0800 (PST)
Received: from smail2.alcatel.fr (smail2.alcatel.fr [62.23.212.57]) by ietfa.amsl.com (Postfix) with ESMTP id C432321F8559 for <alto@ietf.org>; Mon, 19 Nov 2012 08:54:40 -0800 (PST)
Received: from FRMRSSXCHHUB03.dc-m.alcatel-lucent.com (FRMRSSXCHHUB03.dc-m.alcatel-lucent.com [135.120.45.63]) by smail2.alcatel.fr (8.14.3/8.14.3/ICT) with ESMTP id qAJGouAT023527 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Mon, 19 Nov 2012 17:54:37 +0100
Received: from FRMRSSXCHMBSE3.dc-m.alcatel-lucent.com ([135.120.45.56]) by FRMRSSXCHHUB03.dc-m.alcatel-lucent.com ([135.120.45.63]) with mapi; Mon, 19 Nov 2012 17:54:23 +0100
From: "Scharf, Michael (Michael)" <michael.scharf@alcatel-lucent.com>
To: "Diego R. Lopez" <diego@tid.es>
Date: Mon, 19 Nov 2012 17:54:21 +0100
Thread-Topic: [alto] [apps-discuss] Simple Web Discovery (SWD) Enabling Hosted	Deployments
Thread-Index: AQHNvqaRADfxHISJBE2aQ8YJfrM/WJfh1IeggARdBwCAA5CUEIAHVduAgABJLCA=
Message-ID: <2A886F9088894347A3BE0CC5B7A85F3E9AA0F0A953@FRMRSSXCHMBSE3.dc-m.alcatel-lucent.com>
References: <1e8757a8-659a-42d2-9708-309f4b8de076@email.android.com> <E6D8B95470ED0845B3376F61DCAB1A0452AD8F3F@EX10-MB2-MAD.hi.inet> <2A886F9088894347A3BE0CC5B7A85F3E9AA0F3999B@FRMRSSXCHMBSE3.dc-m.alcatel-lucent.com> <E6D8B95470ED0845B3376F61DCAB1A0452AE0EB0@EX10-MB2-MAD.hi.inet> <2A886F9088894347A3BE0CC5B7A85F3E9AA0F0A840@FRMRSSXCHMBSE3.dc-m.alcatel-lucent.com> <E6D8B95470ED0845B3376F61DCAB1A0452AE54E3@EX10-MB2-MAD.hi.inet> <2A886F9088894347A3BE0CC5B7A85F3E9AA0F0A8E4@FRMRSSXCHMBSE3.dc-m.alcatel-lucent.com> <E6D8B95470ED0845B3376F61DCAB1A0452B0022C@EX10-MB2-MAD.hi.inet>
In-Reply-To: <E6D8B95470ED0845B3376F61DCAB1A0452B0022C@EX10-MB2-MAD.hi.inet>
Accept-Language: de-DE, en-US
Content-Language: de-DE
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: de-DE, en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.69 on 155.132.188.80
Cc: "alto@ietf.org" <alto@ietf.org>
Subject: Re: [alto] [apps-discuss] Simple Web Discovery (SWD) Enabling	Hosted	Deployments
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Mon, 19 Nov 2012 16:54:41 -0000

Diego, all,

I won't give further pushback, even if I don't agree to quite a number of y=
our statements. Just one further example to explain why SWD won't solve all=
 problems: Even if we replace U-NAPTR by HTTP(S), according to RFC 5986, th=
e ALTO client still needs access to DHCP options, which is yet another non-=
HTTP(S) interface to care about.

For what it is worth, I am convinced both a DNS-based and a HTTP(S) solutio=
n can be engineered, each with pros and cons. Yet, the former variant is mu=
ch better understood in the IETF, and I fail to see a fundamental benefit o=
f SWD that would compensate this.

In order to move forward, if this helps to sort this issue, I think that we=
 could add a non-normative section to the current draft (or, better, an app=
endix) that discusses an alternative HTTP-based discovery, in case that suc=
h a solution gets widely used in future. It could for instance summarize pr=
os and cons according to this e-mail thread, and leave it up to a future do=
cument to standardize this variant (possible, after the mechanism is better=
 worked out in the IETF). It is pretty clear anyway that the current ALTO d=
iscovery specification does not address all possible use cases of ALTO (cf.=
 third party discovery).

Any thoughts on that proposal?

Michael=

From sebi@gw01.ehlo.wurstkaes.de  Mon Nov 19 09:01:55 2012
Return-Path: <sebi@gw01.ehlo.wurstkaes.de>
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 D553421F859D for <alto@ietfa.amsl.com>; Mon, 19 Nov 2012 09:01:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.45
X-Spam-Level: 
X-Spam-Status: No, score=-2.45 tagged_above=-999 required=5 tests=[AWL=0.150,  BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KWvlyMIuWHWm for <alto@ietfa.amsl.com>; Mon, 19 Nov 2012 09:01:55 -0800 (PST)
Received: from gw01.ehlo.wurstkaes.de (gw01.ehlo.wurstkaes.de [IPv6:2a02:a00:e000:116::41]) by ietfa.amsl.com (Postfix) with ESMTP id 3B37521F8484 for <alto@ietf.org>; Mon, 19 Nov 2012 09:01:54 -0800 (PST)
Received: from sebi by gw01.ehlo.wurstkaes.de with local (Exim 4.72) (envelope-from <sebi@gw01.ehlo.wurstkaes.de>) id 1TaUiz-0004FZ-19; Mon, 19 Nov 2012 18:01:33 +0100
Date: Mon, 19 Nov 2012 18:01:32 +0100
From: Sebastian Kiesel <ietf-alto@skiesel.de>
To: "Scharf, Michael (Michael)" <michael.scharf@alcatel-lucent.com>
Message-ID: <20121119170132.GM3249@gw01.ehlo.wurstkaes.de>
References: <1e8757a8-659a-42d2-9708-309f4b8de076@email.android.com> <E6D8B95470ED0845B3376F61DCAB1A0452AD8F3F@EX10-MB2-MAD.hi.inet> <2A886F9088894347A3BE0CC5B7A85F3E9AA0F3999B@FRMRSSXCHMBSE3.dc-m.alcatel-lucent.com> <E6D8B95470ED0845B3376F61DCAB1A0452AE0EB0@EX10-MB2-MAD.hi.inet> <2A886F9088894347A3BE0CC5B7A85F3E9AA0F0A840@FRMRSSXCHMBSE3.dc-m.alcatel-lucent.com> <E6D8B95470ED0845B3376F61DCAB1A0452AE54E3@EX10-MB2-MAD.hi.inet> <2A886F9088894347A3BE0CC5B7A85F3E9AA0F0A8E4@FRMRSSXCHMBSE3.dc-m.alcatel-lucent.com> <E6D8B95470ED0845B3376F61DCAB1A0452B0022C@EX10-MB2-MAD.hi.inet> <2A886F9088894347A3BE0CC5B7A85F3E9AA0F0A953@FRMRSSXCHMBSE3.dc-m.alcatel-lucent.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <2A886F9088894347A3BE0CC5B7A85F3E9AA0F0A953@FRMRSSXCHMBSE3.dc-m.alcatel-lucent.com>
Accept-Languages: en, de
Organization: my personal mail account
User-Agent: Mutt/1.5.20 (2009-06-14)
Cc: "alto@ietf.org" <alto@ietf.org>
Subject: Re: [alto] [apps-discuss] Simple Web Discovery (SWD) Enabling	Hosted	Deployments
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Mon, 19 Nov 2012 17:01:55 -0000

On Mon, Nov 19, 2012 at 05:54:21PM +0100, Scharf, Michael (Michael) wrote:
> Diego, all,
> 
> I won't give further pushback, even if I don't agree to quite a number of your statements. Just one further example to explain why SWD won't solve all problems: Even if we replace U-NAPTR by HTTP(S), according to RFC 5986, the ALTO client still needs access to DHCP options, which is yet another non-HTTP(S) interface to care about.
> 
> For what it is worth, I am convinced both a DNS-based and a HTTP(S) solution can be engineered, each with pros and cons. Yet, the former variant is much better understood in the IETF, and I fail to see a fundamental benefit of SWD that would compensate this.
> 
> In order to move forward, if this helps to sort this issue, I think that we could add a non-normative section to the current draft (or, better, an appendix) that discusses an alternative HTTP-based discovery, in case that such a solution gets widely used in future. It could for instance summarize pros and cons according to this e-mail thread, and leave it up to a future document to standardize this variant (possible, after the mechanism is better worked out in the IETF). It is pretty clear anyway that the current ALTO discovery specification does not address all possible use cases of ALTO (cf. third party discovery).
> 
> Any thoughts on that proposal?

I propose to add such a discussion to the Deployment Considerations
document, if we want to have one at all.  The discovery document should
contain a technical specification as short and as precise as possible.

S.

From internet-drafts@ietf.org  Wed Nov 28 04:56:43 2012
Return-Path: <internet-drafts@ietf.org>
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 96F7B21F850C; Wed, 28 Nov 2012 04:56:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.52
X-Spam-Level: 
X-Spam-Status: No, score=-102.52 tagged_above=-999 required=5 tests=[AWL=0.079, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cIExJVL+PSKu; Wed, 28 Nov 2012 04:56:43 -0800 (PST)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2C79A21F84EE; Wed, 28 Nov 2012 04:56:43 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 4.36
Message-ID: <20121128125643.29070.61272.idtracker@ietfa.amsl.com>
Date: Wed, 28 Nov 2012 04:56:43 -0800
Cc: alto@ietf.org
Subject: [alto] I-D Action: draft-ietf-alto-server-discovery-06.txt
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Wed, 28 Nov 2012 12:56:43 -0000

A New Internet-Draft is available from the on-line Internet-Drafts director=
ies.
 This draft is a work item of the Application-Layer Traffic Optimization Wo=
rking Group of the IETF.

	Title           : ALTO Server Discovery
	Author(s)       : Sebastian Kiesel
                          Martin Stiemerling
                          Nico Schwan
                          Michael Scharf
                          Haibin Song
	Filename        : draft-ietf-alto-server-discovery-06.txt
	Pages           : 16
	Date            : 2012-11-28

Abstract:
   The goal of Application-Layer Traffic Optimization (ALTO) is to
   provide guidance to applications that have to select one or several
   hosts from a set of candidates capable of providing a desired
   resource.  ALTO is realized by a client-server protocol.  Before an
   ALTO client can ask for guidance it needs to discover one or more
   ALTO servers that can provide suitable guidance.

   This document specifies a procedure for resource consumer initiated
   ALTO server discovery, which can be used if the ALTO client is
   embedded in the resource consumer.



The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-alto-server-discovery

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-alto-server-discovery-06

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-alto-server-discovery-06


Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From sebi@gw01.ehlo.wurstkaes.de  Wed Nov 28 05:01:44 2012
Return-Path: <sebi@gw01.ehlo.wurstkaes.de>
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 B061621F859D for <alto@ietfa.amsl.com>; Wed, 28 Nov 2012 05:01:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 756RHNt+l7+6 for <alto@ietfa.amsl.com>; Wed, 28 Nov 2012 05:01:43 -0800 (PST)
Received: from gw01.ehlo.wurstkaes.de (gw01.ehlo.wurstkaes.de [IPv6:2a02:a00:e000:116::41]) by ietfa.amsl.com (Postfix) with ESMTP id D5D5A21F850C for <alto@ietf.org>; Wed, 28 Nov 2012 05:01:33 -0800 (PST)
Received: from sebi by gw01.ehlo.wurstkaes.de with local (Exim 4.72) (envelope-from <sebi@gw01.ehlo.wurstkaes.de>) id 1TdhGb-0001nI-CN for alto@ietf.org; Wed, 28 Nov 2012 14:01:29 +0100
Date: Wed, 28 Nov 2012 14:01:29 +0100
From: Sebastian Kiesel <ietf-alto@skiesel.de>
To: alto@ietf.org
Message-ID: <20121128130129.GQ3249@gw01.ehlo.wurstkaes.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Accept-Languages: en, de
Organization: my personal mail account
User-Agent: Mutt/1.5.20 (2009-06-14)
Subject: [alto] Fwd:  I-D Action: draft-ietf-alto-server-discovery-06.txt
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Wed, 28 Nov 2012 13:01:44 -0000

Dear ALTO WG members,

we have slightly updated the ALTO server discovery draft: In
section 3.1.2. we have clarified which DHCP options to use
for IPv4 and IPv6, respectively.

Thanks,
Sebastian



----- Forwarded message from internet-drafts@ietf.org -----
Date: Wed, 28 Nov 2012 04:56:43 -0800
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
Cc: alto@ietf.org
Subject: [alto] I-D Action: draft-ietf-alto-server-discovery-06.txt


A New Internet-Draft is available from the on-line Internet-Drafts directories.
 This draft is a work item of the Application-Layer Traffic Optimization Working Group of the IETF.

	Title           : ALTO Server Discovery
	Author(s)       : Sebastian Kiesel
                          Martin Stiemerling
                          Nico Schwan
                          Michael Scharf
                          Haibin Song
	Filename        : draft-ietf-alto-server-discovery-06.txt
	Pages           : 16
	Date            : 2012-11-28

Abstract:
   The goal of Application-Layer Traffic Optimization (ALTO) is to
   provide guidance to applications that have to select one or several
   hosts from a set of candidates capable of providing a desired
   resource.  ALTO is realized by a client-server protocol.  Before an
   ALTO client can ask for guidance it needs to discover one or more
   ALTO servers that can provide suitable guidance.

   This document specifies a procedure for resource consumer initiated
   ALTO server discovery, which can be used if the ALTO client is
   embedded in the resource consumer.



The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-alto-server-discovery

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-alto-server-discovery-06

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-ietf-alto-server-discovery-06


Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

_______________________________________________
alto mailing list
alto@ietf.org
https://www.ietf.org/mailman/listinfo/alto

----- End forwarded message -----

From vkg@bell-labs.com  Wed Nov 28 14:23:16 2012
Return-Path: <vkg@bell-labs.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 03E7F21F8943 for <alto@ietfa.amsl.com>; Wed, 28 Nov 2012 14:23:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eMd-n3AAX-Zl for <alto@ietfa.amsl.com>; Wed, 28 Nov 2012 14:23:15 -0800 (PST)
Received: from ihemail3.lucent.com (ihemail3.lucent.com [135.245.0.37]) by ietfa.amsl.com (Postfix) with ESMTP id 50BDD21F893B for <alto@ietf.org>; Wed, 28 Nov 2012 14:23:15 -0800 (PST)
Received: from usnavsmail2.ndc.alcatel-lucent.com (usnavsmail2.ndc.alcatel-lucent.com [135.3.39.10]) by ihemail3.lucent.com (8.13.8/IER-o) with ESMTP id qASMNDDX012303 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <alto@ietf.org>; Wed, 28 Nov 2012 16:23:14 -0600 (CST)
Received: from umail.lucent.com (umail-ce2.ndc.lucent.com [135.3.40.63]) by usnavsmail2.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id qASMNDnS005450 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <alto@ietf.org>; Wed, 28 Nov 2012 16:23:13 -0600
Received: from shoonya.ih.lucent.com (shoonya.ih.lucent.com [135.185.237.229]) by umail.lucent.com (8.13.8/TPES) with ESMTP id qASMNCFR006401 for <alto@ietf.org>; Wed, 28 Nov 2012 16:23:13 -0600 (CST)
Message-ID: <50B68F27.8040408@bell-labs.com>
Date: Wed, 28 Nov 2012 16:24:39 -0600
From: "Vijay K. Gurbani" <vkg@bell-labs.com>
Organization: Bell Laboratories, Alcatel-Lucent
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: alto <alto@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.37
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.10
Subject: [alto] WGLC for draft-ietf-alto-server-discovery-06
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Wed, 28 Nov 2012 22:23:16 -0000

[as chair]

Folks: Based on conversations with the authors of the document and
recent list discussions on the draft, we believe that the ALTO server
discovery document is ready for WGLC.

The current incarnation of the document is -06 and is available for
review at

    http://tools.ietf.org/html/draft-ietf-alto-server-discovery-06

We urge the working group participants to perform a dedicated review
of the document.  Short statements in support of moving the work ahead,
or statements that provide constructive solutions for any aspect lacking
in the draft, are helpful.  Please do post such statements on the list.

This WGLC runs until Friday, December 14 2012.

Thank you,

- 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/
