On Fri, Mar 5, 2010 at 1:00 AM, <[email protected]> wrote:
> If you have received this digest without all the individual message > attachments you will need to update your digest options in your list > subscription. To do so, go to > > https://www.ietf.org/mailman/listinfo/alto > > Click the 'Unsubscribe or edit options' button, log in, and set "Get > MIME or Plain Text Digests?" to MIME. You can set this option > globally for all the list digests you receive at this point. > > > > Send alto mailing list submissions to > [email protected] > > To subscribe or unsubscribe via the World Wide Web, visit > https://www.ietf.org/mailman/listinfo/alto > or, via email, send a message with subject or body 'help' to > [email protected] > > You can reach the person managing the list at > [email protected] > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of alto digest..." > > > Today's Topics: > > 1. Re: #1: Message format (alto issue tracker) > 2. I-D Action:draft-ietf-alto-protocol-02.txt > ([email protected]) > 3. Re: #2: Protocol details: version number (alto issue tracker) > 4. Re: #3: Protocol details: map version tags (alto issue tracker) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Thu, 04 Mar 2010 19:44:59 -0000 > From: "alto issue tracker" <[email protected]> > Subject: Re: [alto] #1: Message format > To: [email protected] > Cc: [email protected] > Message-ID: <[email protected]> > Content-Type: text/plain; charset="utf-8" > > #1: Message format > > ---------------------------------------------+------------------------------ > Reporter: enrico.maro...@? | Owner: > richard.al...@? > Type: enhancement | Status: new > Priority: blocker | Milestone: > Component: protocol | Version: > Severity: Active WG Document | Keywords: > > ---------------------------------------------+------------------------------ > > Comment(by richard.al...@?): > > draft-ietf-alto-protocol-02 now includes a more complete protocol > specification. The current encoding specification provides example > requests and responses, as well as documenting the syntax and enumerating > the components of the messages. > > The current encoding specification is not as formal and compact as it > probably could be, so work is needed in this area. One possibility for a > more compact representation is a C-style syntax where JSON objects are > formally documented as C-style structs. > > -- > Ticket URL: <http://trac.tools.ietf.org/wg/alto/trac/ticket/1#comment:1> > alto <http://tools.ietf.org/alto/> > > > > ------------------------------ > > Message: 2 > Date: Thu, 4 Mar 2010 11:45:01 -0800 (PST) > From: [email protected] > Subject: [alto] I-D Action:draft-ietf-alto-protocol-02.txt > To: [email protected] > Cc: [email protected] > Message-ID: <[email protected]> > Content-Type: text/plain; charset="us-ascii" > > > > ------------------------------ > > Message: 3 > Date: Thu, 04 Mar 2010 19:53:21 -0000 > From: "alto issue tracker" <[email protected]> > Subject: Re: [alto] #2: Protocol details: version number > To: [email protected] > Cc: [email protected] > Message-ID: <[email protected]> > Content-Type: text/plain; charset="utf-8" > > #2: Protocol details: version number > > ---------------------------------------------+------------------------------ > Reporter: enrico.maro...@? | Owner: > richard.al...@? > Type: enhancement | Status: new > Priority: major | Milestone: > Component: protocol | Version: > Severity: Active WG Document | Keywords: > > ---------------------------------------------+------------------------------ > > Comment(by richard.al...@?): > > draft-ietf-alto-protocol-02 now includes protocol versioning. The current > approach to versioning assumes that a distinct host handles a single > protocol version. (Virtual hosting can be used to allow a single physical > server to handle multiple protocol versions.) Protocol version numbers are > echoed in the responses to allow responses to be redistributed to other > hosts. The Server Capability allows an ALTO Client to discover ALTO > Servers providing other protocol versions. Feedback on this approach is > welcomed. > > -- > Ticket URL: <http://trac.tools.ietf.org/wg/alto/trac/ticket/2#comment:1> > alto <http://tools.ietf.org/alto/> > > > > ------------------------------ > > Message: 4 > Date: Thu, 04 Mar 2010 19:54:22 -0000 > From: "alto issue tracker" <[email protected]> > Subject: Re: [alto] #3: Protocol details: map version tags > To: [email protected] > Cc: [email protected] > Message-ID: <[email protected]> > Content-Type: text/plain; charset="utf-8" > > #3: Protocol details: map version tags > > ---------------------------------------------+------------------------------ > Reporter: enrico.maro...@? | Owner: > richard.al...@? > Type: enhancement | Status: new > Priority: major | Milestone: > Component: protocol | Version: > Severity: Active WG Document | Keywords: > > ---------------------------------------------+------------------------------ > > Comment(by richard.al...@?): > > draft-ietf-alto-protocol-02 now includes map version tags in responses > including Network Maps and Cost Maps. > > -- > Ticket URL: <http://trac.tools.ietf.org/wg/alto/trac/ticket/3#comment:1> > alto <http://tools.ietf.org/alto/> > > > > ------------------------------ > > _______________________________________________ > alto mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/alto > > > End of alto Digest, Vol 17, Issue 2 > *********************************** >
_______________________________________________ alto mailing list [email protected] https://www.ietf.org/mailman/listinfo/alto
