alto Discussion Archive - Thread Index

[Prev Page] [Next Page] [Date Index] [IETF Mailing List Directory] [alto List Information]

• [alto] Call for participation: altonext, Vijay K. Gurbani
• [alto] CfP "International Workshop on Cross-Stratum Optimization for Cloud Computing and Distributed Networked Applications", LUIS MIGUEL CONTRERAS MURILLO
• [alto] Are ALTO costs always End to End?, Ben Niven-Jenkins
  • Re: [alto] Are ALTO costs always End to End?, Vijay K. Gurbani
    • Re: [alto] Are ALTO costs always End to End?, Ben Niven-Jenkins
      • Re: [alto] Are ALTO costs always End to End?, Jan Medved
      • Re: [alto] Are ALTO costs always End to End?, stefano previdi
      • Re: [alto] Are ALTO costs always End to End?, Vijay K. Gurbani
      • Re: [alto] Are ALTO costs always End to End?, stefano previdi
      • Re: [alto] Are ALTO costs always End to End?, Vijay K. Gurbani
      • Re: [alto] Are ALTO costs always End to End?, Jan Medved
      • Re: [alto] Are ALTO costs always End to End?, Ben Niven-Jenkins
      • Re: [alto] Are ALTO costs always End to End?, Jan Medved
  • Re: [alto] Are ALTO costs always End to End?, Richard Alimi
    • Re: [alto] Are ALTO costs always End to End?, stefano previdi
      • Re: [alto] Are ALTO costs always End to End?, Richard Alimi
      • Re: [alto] Are ALTO costs always End to End?, stefano previdi
      • Re: [alto] Are ALTO costs always End to End?, Richard Alimi
  • <Possible follow-ups>
  • Re: [alto] Are ALTO costs always End to End?, Bill Roome
    • Re: [alto] Are ALTO costs always End to End?, Sebastian Kiesel
      • Re: [alto] Are ALTO costs always End to End?, Vijay K. Gurbani
      • Re: [alto] Are ALTO costs always End to End?, stefano previdi
      • Re: [alto] Are ALTO costs always End to End?, Sebastian Kiesel
      • Re: [alto] Are ALTO costs always End to End?, stefano previdi
      • Re: [alto] Are ALTO costs always End to End?, Sebastian Kiesel
      • Re: [alto] Are ALTO costs always End to End?, stefano previdi
      • Re: [alto] Are ALTO costs always End to End?, Sebastian Kiesel
      • Re: [alto] Are ALTO costs always End to End?, stefano previdi
      • Re: [alto] Are ALTO costs always End to End?, Richard Alimi
• [alto] ALTO extensions: new list + problem statement, Enrico Marocco
• [alto] [internet-drafts at ietf.org: I-D Action: draft-ietf-alto-reqs-13.txt], Sebastian Kiesel
• [alto] I-D Action: draft-ietf-alto-reqs-13.txt, internet-drafts
• [alto] One small comment to ALTO protocol, Songhaibin
  • Re: [alto] One small comment to ALTO protocol, Ben Niven-Jenkins
    • Re: [alto] One small comment to ALTO protocol, Richard Alimi
      • Re: [alto] One small comment to ALTO protocol, Songhaibin
• [alto] Last Call: <draft-ietf-alto-reqs-12.txt> (Application-Layer Traffic Optimization (ALTO) Requirements) to Informational RFC, The IESG
  • <Possible follow-ups>
  • [alto] Last Call: <draft-ietf-alto-reqs-12.txt> (Application-Layer Traffic Optimization (ALTO) Requirements) to Informational RFC, The IESG
• [alto] Call for Papers for the "International Workshop on Cross-Stratum Optimization for Cloud Computing and Distributed Networked Applications", Leeyoung
• [alto] New Draft on Incremental Updates: draft-schwan-alto-incr-updates-00.txt, SCHWAN, Nico
• [alto] CfP: IEEE Workshop on Algorithms and Operating Procedures for Federated Virtualized Networks (FEDNET2012), Kurt Tutschku
  • <Possible follow-ups>
  • [alto] CfP: IEEE Workshop on Algorithms and Operating Procedures for Federated Virtualized Networks (FEDNET2012), Kurt Tutschku
  • [alto] CfP: IEEE Workshop on Algorithms and Operating Procedures for Federated Virtualized Networks (FEDNET2012), Kurt Tutschku
• [alto] [CfP] IEEE/IFIP International Workshop on Management of the Future Internet (ManFI 2012) - April 16, 2012 - Hawaii, USA, Peoples, Cathryn
• [alto] ALTO session recording available, Meetecho IETF support
• [alto] non-intercepting ALTO home proxy, Picconi Fabio
  • Re: [alto] non-intercepting ALTO home proxy, Songhaibin
• [alto] Nomcom feedback, Enrico Marocco
• [alto] I-D Action: draft-ietf-alto-deployments-03.txt, internet-drafts
  • Re: [alto] I-D Action: draft-ietf-alto-deployments-03.txt, Martin Stiemerling
• [alto] I-D Action: draft-ietf-alto-reqs-12.txt, internet-drafts
• [alto] FW: Uploaded meeting agenda and slides, Leeyoung
• [alto] Work related to ALTO at IETF82, Enrico Marocco
  • Re: [alto] Work related to ALTO at IETF82, Martin Stiemerling
    • Re: [alto] Work related to ALTO at IETF82, Richard Alimi
      • Re: [alto] Work related to ALTO at IETF82, Martin Stiemerling
      • Re: [alto] Work related to ALTO at IETF82, Vijay K. Gurbani
      • Re: [alto] Work related to ALTO at IETF82, Richard Alimi
      • Re: [alto] Work related to ALTO at IETF82, Vijay K. Gurbani
      • Re: [alto] Work related to ALTO at IETF82, Richard Alimi
• [alto] [CfP] IEEE/IFIP International Workshop on Management of the Future Internet (ManFI 2012) - April 16, 2012 - Maui, Hawaii, USA, Peoples, Cathryn
• [alto] What about adding 'le', 'ge' and 'eq' constraints?, Bill Roome
  • Re: [alto] What about adding 'le', 'ge' and 'eq' constraints?, Richard Alimi
• [alto] What do constraints mean for ordinal costs?, Bill Roome
  • Re: [alto] What do constraints mean for ordinal costs?, Richard Alimi
• [alto] Multi-Cost ALTO - Representation of variable Cost values, Sabine Randriamasy
  • Re: [alto] Multi-Cost ALTO - Representation of variable Cost values, Martin Stiemerling
    • Re: [alto] Multi-Cost ALTO - Representation of variable Cost values, Sabine Randriamasy
      • Re: [alto] Multi-Cost ALTO - Representation of variable Cost values, Martin Stiemerling
• [alto] Fwd: [apps-discuss] JSON Patch, Richard Alimi
• [alto] [Fwd: New Version Notification for draft-randriamasy-alto-multi-cost-05.txt], Sabine Randriamasy
• [alto] I-D Action: draft-ietf-alto-protocol-10.txt, internet-drafts
• [alto] Agenda requests for IETF 82, Enrico Marocco
• [alto] draft submitted on ALTO home proxies, Picconi Fabio
• [alto] Draft submitted on ALTO for CDNi request routing, Jan Seedorf
• [alto] Fwd: Nomcom 2011-2012: Second Call for Nominations, Enrico Marocco
• [alto] Fwd: WG Action: Javascript Object Signing and Encryption (jose), Enrico Marocco
• [alto] I suggest adding map-vtag to a few messages, Bill Roome
  • Re: [alto] I suggest adding map-vtag to a few messages, Richard Alimi
    • Re: [alto] I suggest adding map-vtag to a few messages, Bill Roome
      • Re: [alto] I suggest adding map-vtag to a few messages, Richard Alimi
      • Re: [alto] I suggest adding map-vtag to a few messages, Richard Alimi
      • Re: [alto] I suggest adding map-vtag to a few messages, Bill Roome
      • Re: [alto] I suggest adding map-vtag to a few messages, Richard Alimi
• [alto] ALTO Implementation available, Richard Alimi
• [alto] (fwd) I-D Action: draft-ietf-alto-server-discovery-02.txt, Sebastian Kiesel
• [alto] I-D Action: draft-ietf-alto-server-discovery-02.txt, internet-drafts
• [alto] How many PIDs in an ALTO server?, Bill Roome
  • Re: [alto] How many PIDs in an ALTO server?, Sebastian Kiesel
    • Re: [alto] How many PIDs in an ALTO server?, Songhaibin
    • Re: [alto] How many PIDs in an ALTO server?, Richard Alimi
      • Re: [alto] How many PIDs in an ALTO server?, Bill Roome
      • Re: [alto] How many PIDs in an ALTO server?, Richard Alimi
      • Re: [alto] How many PIDs in an ALTO server?, Sebastian Kiesel
      • Re: [alto] How many PIDs in an ALTO server?, Richard Alimi
      • Re: [alto] How many PIDs in an ALTO server?, Sebastian Kiesel
      • Re: [alto] How many PIDs in an ALTO server?, Richard Alimi
  • Re: [alto] How many PIDs in an ALTO server?, Richard Alimi
• [alto] map-vtag format rules, Bill Roome
  • Re: [alto] map-vtag format rules, Richard Alimi
    • Re: [alto] map-vtag format rules, Bill Roome
      • Re: [alto] map-vtag format rules, Robert Varga
      • Re: [alto] map-vtag format rules, Richard Alimi
• [alto] Large cost-map requests, Bill Roome
  • Re: [alto] Large cost-map requests, Richard Alimi
  • <Possible follow-ups>
  • Re: [alto] Large cost-map requests, Vijay K. Gurbani
• [alto] Fwd: WG Review: Javascript Object Signing and Encryption (jose), Enrico Marocco
• Re: [alto] Authoritative status of costs, Bill Roome
  • Re: [alto] Authoritative status of costs, Ben Niven-Jenkins
    • Re: [alto] Authoritative status of costs, Bill Roome
      • Re: [alto] Authoritative status of costs, Ben Niven-Jenkins
      • Re: [alto] Authoritative status of costs, Richard Alimi
    • Re: [alto] Authoritative status of costs, Woundy, Richard
  • <Possible follow-ups>
  • Re: [alto] Authoritative status of costs, Vijay K. Gurbani
    • Re: [alto] Authoritative status of costs, Richard Alimi
      • Re: [alto] Authoritative status of costs, Vijay K. Gurbani
      • Re: [alto] Authoritative status of costs, Richard Alimi
      • Re: [alto] Authoritative status of costs, Vijay K. Gurbani
      • Re: [alto] Authoritative status of costs, Richard Alimi
      • Re: [alto] Authoritative status of costs, Vijay K. Gurbani
      • Re: [alto] Authoritative status of costs, Sabine Randriamasy
  • Re: [alto] Authoritative status of costs, Bill Roome
    • Re: [alto] Authoritative status of costs, Sabine Randriamasy
    • Re: [alto] Authoritative status of costs, Ben Niven-Jenkins
    • Re: [alto] Authoritative status of costs, Vijay K. Gurbani
      • Re: [alto] Authoritative status of costs, Richard Alimi
      • Re: [alto] Authoritative status of costs, Vijay K. Gurbani
      • Re: [alto] Authoritative status of costs, Y. Richard Yang
      • Re: [alto] Authoritative status of costs, Richard Alimi
• [alto] Protocol issue: mandatory vs. optional features, Enrico Marocco
• [alto] Protocol issue: multi-cost information, Enrico Marocco
  • Re: [alto] Protocol issue: multi-cost information, Reinaldo Penno
    • Re: [alto] Protocol issue: multi-cost information, Richard Alimi
      • Re: [alto] Protocol issue: multi-cost information, Sabine Randriamasy
      • Re: [alto] Protocol issue: multi-cost information, Richard Alimi
      • Re: [alto] Protocol issue: multi-cost information, Sabine Randriamasy
• [alto] Protocol issue: non-authoritative information, Enrico Marocco
  • Re: [alto] Protocol issue: non-authoritative information, Reinaldo Penno
    • Re: [alto] Protocol issue: non-authoritative information, Vijay K. Gurbani
      • Re: [alto] Protocol issue: non-authoritative information, Reinaldo Penno
      • Re: [alto] Protocol issue: non-authoritative information, Vijay K. Gurbani
      • Re: [alto] Protocol issue: non-authoritative information, Reinaldo Penno
• [alto] Protocol issue: map-vtag length, Enrico Marocco
  • Re: [alto] Protocol issue: map-vtag length, Richard Alimi
• [alto] Remaining issues with the protocol, Enrico Marocco
• Re: [alto] #4: Provisioned bandwidth, alto issue tracker
• [alto] Nomcom 2011-2012: Call for Nominations, Vijay K. Gurbani
• [alto] Reminder: Draft minutes for IETF-81, Vijay K. Gurbani
  • Re: [alto] Reminder: Draft minutes for IETF-81, Ben Niven-Jenkins
    • Re: [alto] Reminder: Draft minutes for IETF-81, Vijay K. Gurbani
• [alto] Publication Requested: draft-ietf-alto-reqs-11, Enrico Marocco
• [alto] Draft minutes for IETF-81, Vijay K. Gurbani
• [alto] ALTO interoperability results in IETF-81, Vijay K. Gurbani
• [alto] Caching ALTO, Thomson, Martin
  • Re: [alto] Caching ALTO, Richard Alimi
  • Re: [alto] Caching ALTO, Robert Varga
    • Re: [alto] Caching ALTO, Vijay K. Gurbani
      • Re: [alto] Caching ALTO, Picconi Fabio
• [alto] Info Resource Dirs, OPTIONS, 300 Multiple Choices and all that jazz ...., Bill Roome
  • Re: [alto] Info Resource Dirs, OPTIONS, 300 Multiple Choices and all that jazz ...., Thomson, Martin
    • Re: [alto] Info Resource Dirs, OPTIONS, 300 Multiple Choices and all that jazz ...., Bill Roome
      • Re: [alto] Info Resource Dirs, OPTIONS, 300 Multiple Choices and all that jazz ...., Thomson, Martin
      • Re: [alto] Info Resource Dirs, OPTIONS, 300 Multiple Choices and all that jazz ...., Bill Roome
      • Re: [alto] Info Resource Dirs, OPTIONS, 300 Multiple Choices and all that jazz ...., Thomson, Martin
      • Re: [alto] Info Resource Dirs, OPTIONS, 300 Multiple Choices and all that jazz ...., Bill Roome
      • Re: [alto] Info Resource Dirs, OPTIONS, 300 Multiple Choices and all that jazz ...., Thomson, Martin
      • Re: [alto] Info Resource Dirs, OPTIONS, 300 Multiple Choices and all that jazz ...., Robert Varga
      • Re: [alto] Info Resource Dirs, OPTIONS, 300 Multiple Choices and all that jazz ...., Richard Alimi
      • Re: [alto] Info Resource Dirs, OPTIONS, 300 Multiple Choices and all that jazz ...., Ben Niven-Jenkins
      • Re: [alto] Info Resource Dirs, OPTIONS, 300 Multiple Choices and all that jazz ...., Richard Alimi
      • Re: [alto] Info Resource Dirs, OPTIONS, 300 Multiple Choices and all that jazz ...., Richard Alimi
      • Re: [alto] Info Resource Dirs, OPTIONS, 300 Multiple Choices and all that jazz ...., Richard Alimi
    • Re: [alto] Info Resource Dirs, OPTIONS, 300 Multiple Choices and all that jazz ...., Robert Varga
      • Re: [alto] Info Resource Dirs, OPTIONS, 300 Multiple Choices and all that jazz ...., Thomson, Martin
    • Re: [alto] Info Resource Dirs, OPTIONS, 300 Multiple Choices and all that jazz ...., Richard Alimi
      • Re: [alto] Info Resource Dirs, OPTIONS, 300 Multiple Choices and all that jazz ...., Thomson, Martin
  • Re: [alto] Info Resource Dirs, OPTIONS, 300 Multiple Choices and all that jazz ...., Richard Alimi
• [alto] ALTO recording available, Meetecho IETF support
• [alto] CSO Coordination meeting, Leeyoung
• [alto] Meetecho support for ALTO WG meeting session, Meetecho IETF support
  • <Possible follow-ups>
  • [alto] Meetecho support for ALTO WG meeting session, Meetecho IETF support
• [alto] Mandatory and optional in alto protocol, Enrico Marocco
  • Re: [alto] Mandatory and optional in alto protocol, manbhard
    • Re: [alto] Mandatory and optional in alto protocol, Robert Varga
      • Re: [alto] Mandatory and optional in alto protocol, Richard Alimi
    • Re: [alto] Mandatory and optional in alto protocol, Richard Alimi
  • Re: [alto] Mandatory and optional in alto protocol, Richard Alimi
    • Re: [alto] Mandatory and optional in alto protocol, Vijay K. Gurbani
• [alto] Servers temporarily up, Enrico Marocco
• [alto] Meetecho support for ALTO interop session, Meetecho IETF support
• [alto] Interop meeting coordinates, Enrico Marocco
  • Re: [alto] Interop meeting coordinates, Softgear Ko
    • Re: [alto] Interop meeting coordinates, Vijay K. Gurbani
• [alto] ALTO Interop document updated (v1.1), Vijay K. Gurbani
• [alto] [Fwd: New Version Notification for draft-randriamasy-alto-multi-cost-03.txt], Sabine Randriamasy
• [alto] ALTO Interop document updated (v1.0), Vijay K. Gurbani
  • Re: [alto] ALTO Interop document updated (v1.0), Robert Varga
  • <Possible follow-ups>
  • Re: [alto] ALTO Interop document updated (v1.0), Vijay K. Gurbani
• [alto] ALTO Interop document updated (v0.91), Vijay K. Gurbani
  • Re: [alto] ALTO Interop document updated (v0.91), Zhang, Ning
    • Re: [alto] ALTO Interop document updated (v0.91), Vijay K. Gurbani
• [alto] ALTO Interop document updated (v0.9), Vijay K. Gurbani
  • Re: [alto] ALTO Interop document updated (v0.9), Mikio Hara
    • Re: [alto] ALTO Interop document updated (v0.9), Vijay K. Gurbani
  • Re: [alto] ALTO Interop document updated (v0.9), Zhang, Ning
    • Re: [alto] ALTO Interop document updated (v0.9), Vijay K. Gurbani
  • Re: [alto] ALTO Interop document updated (v0.9), Richard Alimi
    • Re: [alto] ALTO Interop document updated (v0.9), Vijay K. Gurbani
      • Re: [alto] ALTO Interop document updated (v0.9), Richard Alimi
• [alto] New ALTO web application, Enrico Marocco
  • Re: [alto] New ALTO web application, Enrico Marocco
• [alto] Draft agenda and interop date confirmation, Enrico Marocco
• [alto] How strict should we be about JSON syntax?, Bill Roome
  • Re: [alto] How strict should we be about JSON syntax?, Mikio Hara
  • Re: [alto] How strict should we be about JSON syntax?, Enrico Marocco
• [alto] I-D Action: draft-ietf-alto-reqs-11.txt, internet-drafts
  • [alto] Comments in 3.1.4. Re: I-D Action: draft-ietf-alto-reqs-11.txt, Reinaldo Penno
    • Re: [alto] Comments in 3.1.4. Re: I-D Action: draft-ietf-alto-reqs-11.txt, Sebastian Kiesel
      • Re: [alto] Comments in 3.1.4. Re: I-D Action: draft-ietf-alto-reqs-11.txt, Reinaldo Penno
• [alto] I-D Action: draft-ietf-alto-deployments-02.txt, internet-drafts
• [alto] Fwd: I-D Action: draft-dulinski-alto-inter-problem-statement-01.txt, Piotr Wydrych
• [alto] DHCP based ALTO Server Discovery, Hannes Tschofenig
• [alto] I-D Action: draft-ietf-alto-server-discovery-01.txt, internet-drafts
• [alto] ALTO reqs: support of the target-independent and/or target-aware modes, Martin Stiemerling
  • Re: [alto] ALTO reqs: support of the target-independent and/or target-aware modes, Sebastian Kiesel
• [alto] Update (v0.8) of ALTO interoperability test case document, Vijay K. Gurbani
  • <Possible follow-ups>
  • [alto] Update (v0.8) of ALTO interoperability test case document, Vijay K. Gurbani
    • Re: [alto] Update (v0.8) of ALTO interoperability test case document, manbhard
• [alto] Is E_INVALID_PROPERTY really needed?, Bill Roome
  • Re: [alto] Is E_INVALID_PROPERTY really needed?, Richard Alimi
    • Re: [alto] Is E_INVALID_PROPERTY really needed?, Bill Roome
      • Re: [alto] Is E_INVALID_PROPERTY really needed?, Richard Alimi
• Re: [alto] alto Digest, Vol 32, Issue 31, Bill Roome
• [alto] FW: New Version Notification for draft-bernstein-alto-large-bandwidth-cases-00.txt, Leeyoung
  • [alto] Background on draft-bernstein-alto-large-bandwidth-cases-00.txt, Greg Bernstein
• [alto] Test case 1 contributed, Vijay K. Gurbani
• [alto] Agenda requests for IETF 81, Enrico Marocco
• [alto] Updated ALTO Interoperability test cases (version 0.5), Vijay K. Gurbani
• [alto] Proposed dates for interop event in Quebec City, Enrico Marocco
• [alto] I-D Action: draft-ietf-alto-protocol-09.txt, internet-drafts
  • Re: [alto] I-D Action: draft-ietf-alto-protocol-09.txt, Richard Alimi
• Re: [alto] alto Digest, Vol 32, Issue 26, Bill Roome
• [alto] Questions about ordinals & properties, Bill Roome
  • Re: [alto] Questions about ordinals & properties, Richard Alimi
    • Re: [alto] Questions about ordinals & properties, Vijay K. Gurbani
    • Re: [alto] Questions about ordinals & properties, Ben Niven-Jenkins
      • Re: [alto] Questions about ordinals & properties, Richard Alimi
• [alto] Fwd: Please help the Nomcom, Vijay K. Gurbani
• [alto] Is source address optional in Endpoint Property lookup requests?, Ben Niven-Jenkins
  • Re: [alto] Is source address optional in Endpoint Property lookup requests?, Reinaldo Penno
    • Re: [alto] Is source address optional in Endpoint Property lookup requests?, Ben Niven-Jenkins
      • Re: [alto] Is source address optional in Endpoint Property lookup requests?, Richard Alimi
    • Re: [alto] Is source address optional in Endpoint Property lookup requests?, Robert Varga
      • Re: [alto] Is source address optional in Endpoint Property lookup requests?, Richard Alimi
• [alto] cost-constraints definition in draft-08, Robert Varga
  • Re: [alto] cost-constraints definition in draft-08, Richard Alimi
• [alto] ALTO Interoperability test cases (draft), Vijay K. Gurbani
  • Re: [alto] ALTO Interoperability test cases (draft), Ben Niven-Jenkins
    • Re: [alto] ALTO Interoperability test cases (draft), Vijay K. Gurbani
      • Re: [alto] ALTO Interoperability test cases (draft), Ben Niven-Jenkins
      • Re: [alto] ALTO Interoperability test cases (draft), Vijay K. Gurbani
      • Re: [alto] ALTO Interoperability test cases (draft), Reinaldo Penno
      • Re: [alto] ALTO Interoperability test cases (draft), Vijay K. Gurbani
      • Re: [alto] ALTO Interoperability test cases (draft), Reinaldo Penno
      • Re: [alto] ALTO Interoperability test cases (draft), Robert Varga
      • [alto] VRFs & ALTO (was Re: ALTO Interoperability test cases (draft)), Ben Niven-Jenkins
      • Re: [alto] VRFs & ALTO (was Re: ALTO Interoperability test cases (draft)), Reinaldo Penno
      • Re: [alto] ALTO Interoperability test cases (draft), Ben Niven-Jenkins
      • Re: [alto] ALTO Interoperability test cases (draft), Richard Alimi
      • Re: [alto] ALTO Interoperability test cases (draft), Ben Niven-Jenkins
      • Re: [alto] ALTO Interoperability test cases (draft), Richard Alimi
• Re: [alto] alto Digest, Vol 32, Issue 19, Bill Roome
  • Re: [alto] alto Digest, Vol 32, Issue 19, Richard Alimi
    • Re: [alto] alto Digest, Vol 32, Issue 19, Richard Alimi
• Re: [alto] alto Digest, Vol 32, Issue 18, Bill Roome
  • Re: [alto] alto Digest, Vol 32, Issue 18, Richard Alimi
• [alto] Short WGLC for draft-ietf-alto-reqs-08, Enrico Marocco
  • [alto] WGLC on ALTO reqs 10, not 08, Sebastian Kiesel
    • Re: [alto] WGLC on ALTO reqs 10, not 08, Enrico Marocco
    • [alto] Second round of comments on Re: WGLC on ALTO reqs 10, not 08, Reinaldo Penno
      • Re: [alto] Second round of comments on Re: WGLC on ALTO reqs 10, not 08, Martin Stiemerling
      • Re: [alto] Second round of comments on Re: WGLC on ALTO reqs 10, not 08, Reinaldo Penno
      • Re: [alto] Second round of comments on Re: WGLC on ALTO reqs 10, not 08, Martin Stiemerling
      • Re: [alto] Second round of comments on Re: WGLC on ALTO reqs 10, not 08, Reinaldo Penno
      • Re: [alto] Second round of comments on Re: WGLC on ALTO reqs 10, not 08, Sebastian Kiesel
      • Re: [alto] Second round of comments on Re: WGLC on ALTO reqs 10, not 08, Reinaldo Penno
      • Re: [alto] Second round of comments on Re: WGLC on ALTO reqs 10, not 08, Sebastian Kiesel
      • Re: [alto] Second round of comments on Re: WGLC on ALTO reqs 10, not 08, Reinaldo Penno
      • Re: [alto] Second round of comments on Re: WGLC on ALTO reqs 10, not 08, Sebastian Kiesel
      • Re: [alto] Second round of comments on Re: WGLC on ALTO reqs 10, not 08, Reinaldo Penno
    • [alto] Comments on Re: WGLC on ALTO reqs 10, not 08, Reinaldo Penno
      • Re: [alto] Comments on Re: WGLC on ALTO reqs 10, not 08, Martin Stiemerling
  • Re: [alto] Short WGLC for draft-ietf-alto-reqs-08, Ben Niven-Jenkins
    • Re: [alto] Short WGLC for draft-ietf-alto-reqs-08, Martin Stiemerling
      • Re: [alto] Short WGLC for draft-ietf-alto-reqs-08, Ben Niven-Jenkins
• Re: [alto] alto Digest, Vol 32, Issue 15, Bill Roome
• Re: [alto] alto Digest, Vol 32, Issue 14, Bill Roome
  • Re: [alto] alto Digest, Vol 32, Issue 14, Zhang, Ning
    • Re: [alto] alto Digest, Vol 32, Issue 14, Thomson, Martin
      • Re: [alto] alto Digest, Vol 32, Issue 14, Richard Alimi
      • Re: [alto] alto Digest, Vol 32, Issue 14, Thomson, Martin
  • Re: [alto] alto Digest, Vol 32, Issue 14, Richard Alimi
  • <Possible follow-ups>
  • Re: [alto] alto Digest, Vol 32, Issue 14, Bill Roome
    • Re: [alto] alto Digest, Vol 32, Issue 14, Ben Niven-Jenkins
      • Re: [alto] alto Digest, Vol 32, Issue 14, Bill Roome
      • Re: [alto] alto Digest, Vol 32, Issue 14, Ben Niven-Jenkins
      • Re: [alto] alto Digest, Vol 32, Issue 14, Richard Alimi
    • Re: [alto] alto Digest, Vol 32, Issue 14, Richard Alimi
  • Re: [alto] alto Digest, Vol 32, Issue 14, Bill Roome
    • Re: [alto] alto Digest, Vol 32, Issue 14, Ben Niven-Jenkins
      • Re: [alto] alto Digest, Vol 32, Issue 14, Richard Alimi
• [alto] Fwd: New Version Notification for draft-jenkins-alto-cdn-use-cases-01.txt, Ben Niven-Jenkins
• [alto] Specifying supported Cost Types, EP properties & attributes, Sabine Randriamasy
  • Re: [alto] Specifying supported Cost Types, EP properties & attributes, Richard Alimi
• [alto] Interim meeting notes and material, Enrico Marocco
  • <Possible follow-ups>
  • [alto] Interim meeting notes and material, Enrico Marocco
• Re: [alto] alto Digest, Vol 32, Issue 12, Bill Roome
  • Re: [alto] alto Digest, Vol 32, Issue 12, Richard Alimi
  • <Possible follow-ups>
  • Re: [alto] alto Digest, Vol 32, Issue 12, Bill Roome
    • Re: [alto] alto Digest, Vol 32, Issue 12, Richard Alimi
    • Re: [alto] alto Digest, Vol 32, Issue 12, Ben Niven-Jenkins
• [alto] Questions on draft 8, Bill Roome
  • Re: [alto] Questions on draft 8, Ben Niven-Jenkins
    • Re: [alto] Questions on draft 8, Richard Alimi
• [alto] Reminder: Virtual interim meeting, Enrico Marocco
• [alto] RFC2616 vs. draft-ietf-alto-protocol-08, Robert Varga
  • Re: [alto] RFC2616 vs. draft-ietf-alto-protocol-08, Thomson, Martin
    • Re: [alto] RFC2616 vs. draft-ietf-alto-protocol-08, Richard Alimi
      • Re: [alto] RFC2616 vs. draft-ietf-alto-protocol-08, Ben Niven-Jenkins
• [alto] Draft-08 Information Resource Directory, Robert Varga
  • Re: [alto] Draft-08 Information Resource Directory, Ben Niven-Jenkins
    • Re: [alto] Draft-08 Information Resource Directory, Thomson, Martin
    • Re: [alto] Draft-08 Information Resource Directory, Robert Varga
      • Re: [alto] Draft-08 Information Resource Directory, Ben Niven-Jenkins
• [alto] Some comments on draft-ietf-alto-protocol-08.txt, Zhang, Ning
  • Re: [alto] Some comments on draft-ietf-alto-protocol-08.txt, Richard Alimi
    • Re: [alto] Some comments on draft-ietf-alto-protocol-08.txt, Zhang, Ning
      • Re: [alto] Some comments on draft-ietf-alto-protocol-08.txt, Richard Alimi
      • Re: [alto] Some comments on draft-ietf-alto-protocol-08.txt, Zhang, Ning
      • Re: [alto] Some comments on draft-ietf-alto-protocol-08.txt, Richard Alimi
      • Re: [alto] Some comments on draft-ietf-alto-protocol-08.txt, Zhang, Ning
      • Re: [alto] Some comments on draft-ietf-alto-protocol-08.txt, Richard Alimi
      • Re: [alto] Some comments on draft-ietf-alto-protocol-08.txt, Ben Niven-Jenkins
• [alto] FW: I-D Action: draft-ietf-alto-reqs-10.txt, Martin Stiemerling
• [alto] I-D Action: draft-ietf-alto-reqs-10.txt, internet-drafts
• [alto] Virtual interim meeting, Enrico Marocco
• [alto] ALTO Working Group Virtual Interim Meeting: Wednesday, June 15 2011, IESG Secretary
• [alto] Address type in Filtered Network Map queries, Robert Varga
  • Re: [alto] Address type in Filtered Network Map queries, Richard Alimi
    • Re: [alto] Address type in Filtered Network Map queries, Richard Alimi
    • Re: [alto] Address type in Filtered Network Map queries, Reinaldo Penno
      • Re: [alto] Address type in Filtered Network Map queries, Richard Alimi
• [alto] PID Properties in ALTO, Richard Alimi
  • Re: [alto] PID Properties in ALTO, Robert Varga
    • Re: [alto] PID Properties in ALTO, Richard Alimi
      • Re: [alto] PID Properties in ALTO, Reinaldo Penno
      • Re: [alto] PID Properties in ALTO, Y. Richard Yang
  • Re: [alto] PID Properties in ALTO, Ben Niven-Jenkins
    • Re: [alto] PID Properties in ALTO, Richard Alimi
      • Re: [alto] PID Properties in ALTO, Ben Niven-Jenkins
      • Re: [alto] PID Properties in ALTO, Richard Alimi
• [alto] Opaque Cost Types in ALTO Cost Maps, Richard Alimi
  • Re: [alto] Opaque Cost Types in ALTO Cost Maps, Ben Niven-Jenkins
    • Re: [alto] Opaque Cost Types in ALTO Cost Maps, Richard Alimi
      • Re: [alto] Opaque Cost Types in ALTO Cost Maps, Ben Niven-Jenkins
      • Re: [alto] Opaque Cost Types in ALTO Cost Maps, Richard Alimi
      • Re: [alto] Opaque Cost Types in ALTO Cost Maps, Richard Alimi
      • Re: [alto] Opaque Cost Types in ALTO Cost Maps, Reinaldo Penno
      • Re: [alto] Opaque Cost Types in ALTO Cost Maps, Y. Richard Yang
      • Re: [alto] Opaque Cost Types in ALTO Cost Maps, Reinaldo Penno
      • Re: [alto] Opaque Cost Types in ALTO Cost Maps, Richard Alimi
      • Re: [alto] Opaque Cost Types in ALTO Cost Maps, Richard Alimi
• [alto] Multiple Cost Types in an ALTO Cost Map, Richard Alimi
  • Re: [alto] Multiple Cost Types in an ALTO Cost Map, Robert Varga
    • Re: [alto] Multiple Cost Types in an ALTO Cost Map, Richard Alimi
      • Re: [alto] Multiple Cost Types in an ALTO Cost Map, RANDRIAMASY, SABINE (SABINE)
      • Re: [alto] Multiple Cost Types in an ALTO Cost Map, Richard Alimi
      • Re: [alto] Multiple Cost Types in an ALTO Cost Map, RANDRIAMASY, SABINE (SABINE)
  • Re: [alto] Multiple Cost Types in an ALTO Cost Map, Ben Niven-Jenkins
    • Re: [alto] Multiple Cost Types in an ALTO Cost Map, Richard Alimi
      • Re: [alto] Multiple Cost Types in an ALTO Cost Map, Ben Niven-Jenkins
      • Re: [alto] Multiple Cost Types in an ALTO Cost Map, Richard Alimi
• [alto] Interoperability @IETF81, Enrico Marocco
• [alto] Unsubscribe, Scott Poretsky
• [alto] I-D Action: draft-ietf-alto-protocol-08.txt, internet-drafts
  • Re: [alto] I-D Action: draft-ietf-alto-protocol-08.txt, Richard Alimi
    • Re: [alto] I-D Action: draft-ietf-alto-protocol-08.txt, Richard Alimi
  • Re: [alto] I-D Action: draft-ietf-alto-protocol-08.txt, manbhard
    • Re: [alto] I-D Action: draft-ietf-alto-protocol-08.txt, Richard Alimi
      • Re: [alto] I-D Action: draft-ietf-alto-protocol-08.txt, manbhard
      • Re: [alto] I-D Action: draft-ietf-alto-protocol-08.txt, Richard Alimi
      • Re: [alto] I-D Action: draft-ietf-alto-protocol-08.txt, manbhard
  • <Possible follow-ups>
  • Re: [alto] I-D Action: draft-ietf-alto-protocol-08.txt, Richard Alimi
    • Re: [alto] I-D Action: draft-ietf-alto-protocol-08.txt, manbhard
      • Re: [alto] I-D Action: draft-ietf-alto-protocol-08.txt, Richard Alimi
• [alto] ALTO Interoperability update for IETF-81, Vijay K. Gurbani
• [alto] I-D ACTION:draft-ietf-alto-reqs-09.txt, Internet-Drafts
  • [alto] Comments on - Re: I-D ACTION:draft-ietf-alto-reqs-09.txt, Reinaldo Penno
    • Re: [alto] Comments on - Re: I-D ACTION:draft-ietf-alto-reqs-09.txt, Ben Niven-Jenkins
      • Re: [alto] Comments on - Re: I-D ACTION:draft-ietf-alto-reqs-09.txt, Vijay K. Gurbani
      • Re: [alto] Comments on - Re: I-D ACTION:draft-ietf-alto-reqs-09.txt, Richard Alimi
      • Re: [alto] Comments on - Re: I-D ACTION:draft-ietf-alto-reqs-09.txt, Vijay K. Gurbani
      • Re: [alto] Comments on - Re: I-D ACTION:draft-ietf-alto-reqs-09.txt, Ben Niven-Jenkins
      • Re: [alto] Comments on - Re: I-D ACTION:draft-ietf-alto-reqs-09.txt, Vijay K. Gurbani
      • Re: [alto] Comments on - Re: I-D ACTION:draft-ietf-alto-reqs-09.txt, Robert Varga
      • Re: [alto] Comments on - Re: I-D ACTION:draft-ietf-alto-reqs-09.txt, Williams, Marcus (Contractor)
      • Re: [alto] Comments on - Re: I-D ACTION:draft-ietf-alto-reqs-09.txt, Richard Alimi
      • Re: [alto] Comments on - Re: I-D ACTION:draft-ietf-alto-reqs-09.txt, Sebastian Kiesel
• [alto] I-D Action: draft-ietf-alto-server-discovery-00.txt, internet-drafts
• [alto] Comments on draft-ietf-alto-reqs-08, Ben Niven-Jenkins
  • [alto] category of resource/consumer (was: Comments on draft-ietf-alto-reqs-08), Martin Stiemerling
    • Re: [alto] category of resource/consumer (was: Comments on draft-ietf-alto-reqs-08), Richard Alimi
      • Re: [alto] category of resource/consumer (was: Comments on draft-ietf-alto-reqs-08), Ben Niven-Jenkins
      • Re: [alto] category of resource/consumer (was: Comments on draft-ietf-alto-reqs-08), Martin Stiemerling
      • Re: [alto] category of resource/consumer (was: Comments on draft-ietf-alto-reqs-08), Martin Stiemerling
  • Re: [alto] Comments on draft-ietf-alto-reqs-08, Sebastian Kiesel
    • Re: [alto] Comments on draft-ietf-alto-reqs-08, Ben Niven-Jenkins
• [alto] draft-ietf-alto-reqs-08 & CDNs, Ben Niven-Jenkins
• [alto] New draft on use cases for ALTO & CDNs, Ben Niven-Jenkins
  • Re: [alto] New draft on use cases for ALTO & CDNs, stefano previdi
    • Re: [alto] New draft on use cases for ALTO & CDNs, Jan Medved
      • Re: [alto] New draft on use cases for ALTO & CDNs, Ben Niven-Jenkins
      • Re: [alto] New draft on use cases for ALTO & CDNs, stefano previdi
      • Re: [alto] New draft on use cases for ALTO & CDNs, Richard Alimi
      • Re: [alto] New draft on use cases for ALTO & CDNs, Bitar, Nabil N
      • Re: [alto] New draft on use cases for ALTO & CDNs, grant.watson
• [alto] Adopting draft-kiesel-alto-3pdisc-05, Enrico Marocco
  • Re: [alto] Adopting draft-kiesel-alto-3pdisc-05, Enrico Marocco
• [alto] some use cases and its considerations in ALTO, ææ
  • Re: [alto] some use cases and its considerations in ALTO, Sebastian Kiesel
    • Re: [alto] some use cases and its considerations in ALTO, stefano previdi
      • Re: [alto] some use cases and its considerations in ALTO, Sebastian Kiesel
      • Re: [alto] some use cases and its considerations in ALTO, ææ
      • Re: [alto] some use cases and its considerations in ALTO, Sebastian Kiesel
      • Re: [alto] some use cases and its considerations in ALTO, ææ
      • Re: [alto] some use cases and its considerations in ALTO, stefano previdi
      • Re: [alto] some use cases and its considerations in ALTO, ææ
      • Re: [alto] some use cases and its considerations in ALTO, ææ
      • Re: [alto] some use cases and its considerations in ALTO, Sebastian Kiesel
      • Re: [alto] some use cases and its considerations in ALTO, ææ
      • Re: [alto] some use cases and its considerations in ALTO, Sebastian Kiesel
      • Re: [alto] some use cases and its considerations in ALTO, stefano previdi
      • Re: [alto] some use cases and its considerations in ALTO, Sebastian Kiesel
    • Re: [alto] some use cases and its considerations in ALTO, ææ
      • Re: [alto] some use cases and its considerations in ALTO, Sebastian Kiesel
• [alto] Interop at IETF-81?, Robert Varga
  • Re: [alto] Interop at IETF-81?, Vijay K. Gurbani
• [alto] ns-3/ALTO: Influencing suboptimal peer selection, Vijay K. Gurbani
  • Re: [alto] ns-3/ALTO: Influencing suboptimal peer selection, Richard Alimi
    • Re: [alto] ns-3/ALTO: Influencing suboptimal peer selection, Vijay K. Gurbani
  • Re: [alto] ns-3/ALTO: Influencing suboptimal peer selection, Arnaud Legout
• [alto] Do we need to standardise an ALTO Server to Network API?, Ben Niven-Jenkins
  • Re: [alto] Do we need to standardise an ALTO Server to Network API?, Ping Pan
  • Re: [alto] Do we need to standardise an ALTO Server to Network API?, Jan Medved
    • Re: [alto] Do we need to standardise an ALTO Server to Network API?, Benjamin Niven-Jenkins
      • Re: [alto] Do we need to standardise an ALTO Server to Network API?, Woundy, Richard
      • Re: [alto] Do we need to standardise an ALTO Server to Network API?, Robert Raszuk
      • Re: [alto] Do we need to standardise an ALTO Server to Network API?, Woundy, Richard
      • Re: [alto] Do we need to standardise an ALTO Server to Network API?, Robert Raszuk
      • Re: [alto] Do we need to standardise an ALTO Server to Network API?, Ben Niven-Jenkins
      • Re: [alto] Do we need to standardise an ALTO Server to Network API?, Woundy, Richard
      • Re: [alto] Do we need to standardise an ALTO Server to Network API?, Mcdysan, David E
      • Re: [alto] Do we need to standardise an ALTO Server to Network API?, Ben Niven-Jenkins
      • Re: [alto] Do we need to standardise an ALTO Server to Network API?, Mcdysan, David E
      • Re: [alto] Do we need to standardise an ALTO Server to Network API?, Ben Niven-Jenkins
      • Re: [alto] Do we need to standardise an ALTO Server to Network API?, Woundy, Richard
      • Re: [alto] Do we need to standardise an ALTO Server to Network API?, Robert Raszuk
      • Re: [alto] Do we need to standardise an ALTO Server to Network API?, stefano previdi
      • Re: [alto] Do we need to standardise an ALTO Server to Network API?, Jan Medved
      • Re: [alto] Do we need to standardise an ALTO Server to Network API?, stefano previdi
      • Re: [alto] Do we need to standardise an ALTO Server to Network API?, Jan Medved
  • Re: [alto] Do we need to standardise an ALTO Server to Network API?, Robert Raszuk
• [alto] Draft minutes for alto at IETF-80, Vijay K. Gurbani
• [alto] ALTO session recordings, ietf at meetecho.com
• [alto] Regarding discussion during the Server-to-server presentation, Piotr Wydrych
  • Re: [alto] Regarding discussion during the Server-to-server presentation, Martin Stiemerling
• [alto] Demo session recording, ietf at meetecho.com
• [alto] NeuStar / Juniper ALTO demo ..., Ali, Syed Wasim
• [alto] Pictures of the ALTO Demo session at IETF-80, Martin Stiemerling
• [alto] Slides of running code show, Likai
• [alto] Demo event: Lunch will be provided!, Enrico Marocco
• [alto] Monday demo event, Enrico Marocco
  • Re: [alto] Monday demo event, Enrico Marocco
• [alto] Take 2: ALTO protocol - REST-ful Vs REST-like, Ben Niven-Jenkins
  • Re: [alto] Take 2: ALTO protocol - REST-ful Vs REST-like, Reinaldo Penno
    • Re: [alto] Take 2: ALTO protocol - REST-ful Vs REST-like, Ben Niven-Jenkins
    • Re: [alto] Take 2: ALTO protocol - REST-ful Vs REST-like, Thomson, Martin
      • Re: [alto] Take 2: ALTO protocol - REST-ful Vs REST-like, Reinaldo Penno
• [alto] Draft agenda for Prague, Enrico Marocco
  • Re: [alto] Draft agenda for Prague, Sabine Randriamasy
    • Re: [alto] Draft agenda for Prague, Vijay K. Gurbani
• [alto] FW: I-D Action:draft-kiesel-alto-3pdisc-05.txt, Martin Stiemerling
• [alto] I-D Action:draft-ietf-alto-protocol-07.txt, Internet-Drafts
  • Re: [alto] I-D Action:draft-ietf-alto-protocol-07.txt, Martin Stiemerling
    • Re: [alto] I-D Action:draft-ietf-alto-protocol-07.txt, Richard Alimi
• [alto] FW: I-D Action:draft-ietf-alto-deployments-01.txt, Martin Stiemerling
• [alto] I-D Action:draft-ietf-alto-deployments-01.txt, Internet-Drafts
• [alto] ALTO protocol: REST-ful vs. REST-like, Enrico Marocco
  • Re: [alto] ALTO protocol: REST-ful vs. REST-like, Martin Stiemerling
    • Re: [alto] ALTO protocol: REST-ful vs. REST-like, Vijay K. Gurbani