[alto] Fwd: Publication has been requested for draft-ietf-alto-performance-metrics-15

Dear all, here is my write-up for the publication request on draft-ietf-alto-performance-metrics: 1. Summary Jan Seedorf is the document shepherd for draft-ietf-alto-performance-metrics. Martin Duke is the responsible Area Director. The ALTO base protocol (RFC7285) defines only a single

[alto] Publication has been requested for draft-ietf-alto-performance-metrics-15

Jan Seedorf has requested publication of draft-ietf-alto-performance-metrics-15 as Proposed Standard on behalf of the ALTO working group. Please verify the document's state at https://datatracker.ietf.org/doc/draft-ietf-alto-performance-me

Re: [alto] WGLC for draft-ietf-alto-performance-metrics-12

Dear authors of draft-ietf-alto-performance-metrics-12, may I kindly ask about the status and your plans for moving this forward? (see below) Thanks, Jan Am 08.11.20 um 22:56 schrieb Jan Seedorf: Dear all, this ends the WGLC for draft-ietf-alto-performance-metrics-12. No objections on

[alto] Normative References in draft-ietf-alto-performance-metrics-12

e; so please update the ref and move it to informative references Can you please address these issues as well when you address the WGLC comments received (see below)? Thanks, Jan Am 08.11.20 um 22:56 schrieb Jan Seedorf: Dear all, this ends the WGLC for draft-ietf-alto-performance-met

Re: [alto] Welcome Qin Wu

Dear Qin, welcome as new chair for the ALTO WG! Vijay and I will contact you soon regarding IETF-109 and how we can manage the planned re-charter discussions there most effectively.  - Jan Am 11.11.20 um 10:35 schrieb Qin Wu: Hi, Martin, et al : Thank for having me.  Jan and Vijay, I am h

Re: [alto] WGLC for draft-ietf-alto-performance-metrics-12

I kindly ask the authors of the document to address these comments ASAP and post a new version of the document? Thanks, Jan Am 28.09.20 um 18:42 schrieb Jan Seedorf: Dear all, as discussed during the ALTO session at IETF-108, we are moving forward with all the remaining milestones. Thus

[alto] ALTO@IETF-109

Dear all, ALTO has a slot at IETF 109.  We would like to devote the entire slot to the re-charter discussion that started in IETF 108. However, we would like to advise that the presentation for re-charter discussion be more focused in this iteration as compared to the previous one, where we ha

Re: [alto] WGLC for draft-ietf-alto-performance-metrics-12

e step up. Thank you. On Tue, Sep 29, 2020 at 8:32 AM Danny Alex Lachos Perez mailto:dlachos...@gmail.com>> wrote: Hello Jan & Vijay I will review the Performance Metrics document. Bestregards, Danny Lachos On Mon, Sep 28, 2020 at

[alto] WGLC for draft-ietf-alto-path-vector-11

Dear all, as discussed during the ALTO session at IETF-108, we are moving forward with all the remaining milestones. Thus, this email starts a WGLC for draft-ietf-alto-path-vector-11. The WGLC will run two weeks, so from today, Monday, September 28, until Monday, Oktober 12, 2020. We would

[alto] WGLC for draft-ietf-alto-performance-metrics-12

Dear all, as discussed during the ALTO session at IETF-108, we are moving forward with all the remaining milestones. Thus, this email starts a WGLC for draft-ietf-alto-performance-metrics-12. The WGLC will run two weeks, so from today, Monday, September 28, until Monday, Oktober 12, 2020.

[alto] ALTO Minutes from IETF-108

ngs/108/bluesheets/bluesheets-108-alto-202007271410-00.txt WG Chairs: Vijay Gurbani, Jan Seedorf Area Director: Martin Duke Minute takers: Sabine Randriamasy, Qiao Xiang - ACRONYMS AND NAMES USED IN THE MINUTES --- CX Chunshan Xiong DL Danny Lachos JS Jan

Re: [alto] WGLC for draft-ietf-alto-unified-props-new-12

Hi Richard, sure, that suffices, great. Thanks, Jan Am 24.07.20 um 14:40 schrieb Y. Richard Yang: Hi Jan, I remember that Danny and Luis will review the updated UP draft. Is this enough? Richard On Fri, Jul 24, 2020 at 8:36 AM Jan Seedorf <mailto:i...@j-f-s.de>> wrote:

Re: [alto] WGLC for draft-ietf-alto-unified-props-new-12

Dear all, we are still looking for individual reviewers for draft-ietf-alto-unified-props-new-12 (see below). We will bring this up on Monday during the ALTO session, in hope of finding volunteers.  - Jan Am 17.07.20 um 19:01 schrieb Jan Seedorf: Dear all, after a discussion with Vijay on

[alto] WGLC for draft-ietf-alto-unified-props-new-12

Dear all, after a discussion with Vijay on how to move forward with the pending documents, we decided to start a WGLC for the unified properties document now. Thus, this email starts a WGLC for draft-ietf-alto-unified-props-new-12. The WGLC will run from today, Fri, July 17, 2020, to Fri, Aug

[alto] ALTO at IETF-108: Finishing the current milestones and discussion on re-chartering the WG

Dear all, Martin (our new AD), Vijay and myself had some discussions on how to generally move forward with the WG and how to plan the IETF-108 ALTO session accordingly. We believe we should finalize the remaining milestones (see https://tools.ietf.org/wg/alto/charters) by or at the latest dur

[alto] Agenda requests for IETF 107

prg Key Participant Conflict: nmrg People who must be present: Vijay K. Gurbani Jan Seedorf Mirja Kuehlewind Resources Requested: Special Requests: - ___ alto mailing list alt

Re: [alto] [CDNi] [E] WGLC for draft-ietf-alto-cdni-request-routing-alto-09

Dear Sanjay, thank you very much for reading the draft carefully and for your comments! We will go through them and address them.  - Jan (and co-authors) On 20.02.20 00:12, sanjay.mishra=40verizon@dmarc.ietf.org wrote: I have review draft-ietf-alto-cdni-request-routing-alto-09 and don’t

Re: [alto] [CDNi] WGLC for draft-ietf-alto-cdni-request-routing-alto-09

Dear Danny, thank you very much for reading the draft carefully and for your comments! We will go through them and address them.  - Jan (and co-authors) On 17.02.20 18:19, Danny Alex Lachos Perez wrote: Dear authors, I have performed a review of this draft (-09). My comments are below: 1)

[alto] Finalizing draft-ietf-alto-cdni-request-routing-alto

Dear CDNI chairs and CDNI WG, the ALTO WG is finalizing "Content Delivery Network Interconnection (CDNI) Request Routing: CDNI Footprint and Capabilities Advertisement using ALTO" (draft-ietf-alto-cdni-request-routing-alto-08). For the WGLC we are about to issue, we would like to have one indi

[alto] Finalizing the ALTO CDNI-FCI Document

-- Prof. Dr. Jan Seedorf Chief Information Security Officer (CISO) jan.seed...@hft-stuttgart.de Hochschule für Technik Stuttgart Fakultät Vermessung, Informatik und Mathematik Schellingstr. 24 D-70174 Stuttgart www.hft-stuttgart.de

Re: [alto] Progress on CDNI FCI Draft

Dear Jensen, it is too late for such drastic design changes. What has long been agreed in the CDNI WG is that RFC8006/8008 define the JSON format for CDNI which suit the CDNI requirements. These had been discussed in CDNI for many years at many meetings. So that is fixed. What we need to do in

[alto] Fwd: Remote presentations at IETF105 - cutoff date July 20

Dear all, if you intend to present at IETF105 in ALTO remotely, please let us (the chairs) know soon, so that we can request a remote presentation for you (see below).  - Jan Forwarded Message Subject:Remote presentations at IETF105 - cutoff date July 20 Date: T

[alto] Minutes from ALTO Session at IETF104

ijay * ALTO WG IETF 104 Prague, Czech Republic March 26, 2019 Notetakers: Sabine Randriamasy Krystof Miziewicz ACRONYMS ACAL    ALTO Calendar DL     Danny Lachos DC    Dawn Chen JS    Jan Seedorf MK    Mirja K¸ehlewind PV    Path Vector RY    Richard Yang SSE    Server Sent Events TC   

[alto] Fwd: URL for interim material

https://datatracker.ietf.org/meeting/interim-2018-alto-01/session/alto Forwarded Message Subject:[alto] URL for interim material Date: Mon, 10 Dec 2018 23:38:26 -0600 From: Vijay Gurbani To: alto@ietf.org https://datatracker.ietf.org/meeting/interim-2018-al

[alto] Agenda for virtual interim on Dec 11, 13:00-15:00 CET

Dear all, here is the agenda for the interim tomorrow: *** ALTO Virtual Interim Meeting *** Dec 11, 2018 13:00-15:00 CET 13:00 Introduction and Agenda Bash (Chairs) 13:10 draft-ietf-alto-cost-calendar-09 (Sabine) 13:30 draft-ietf-alto-unified-props-new (Jensen) 13:45 draft-ietf-alto-incr-update

Re: [alto] Alvaro Retana's Discuss on draft-ietf-alto-cost-calendar-09: (with DISCUSS)

Vijay, can you update the shepherd write up and re-run the wg last call with a note to the working group that this IPR exists? As co-chair I agree: we need to inform the WG and re-do a WG last call, giving people the chance to comment if they think necessary Sabine, maybe you can also address

Re: [alto] AD review of draft-ietf-alto-xdom-disc

Martin, Sebastian, I suggest you get to the editorial comments from Mirja sometime soon, so we that a new version is published by the time this goes into the IESG call in December.  - Jan On 30.10.18 18:33, Mirja Kuehlewind (IETF) wrote: Hi authors, hi shepherd, thanks for the well-writte

[alto] Publication has been requested for draft-ietf-alto-xdom-disc-03

Jan Seedorf has requested publication of draft-ietf-alto-xdom-disc-03 as Proposed Standard on behalf of the ALTO working group. Please verify the document's state at https://datatracker.ietf.org/doc/draft-ietf-alto-xdom-disc/ ___ alto mailing

[alto] ALTO Minutes for IETF-101 Session uploaded to datatracker

Hi all, the subject line says it all. Please let us know if you spot anything or think something needs to be changed.  - Jan ___ alto mailing list alto@ietf.org https://www.ietf.org/mailman/listinfo/alto

Re: [alto] SSE final touches

multipart, which can be a nice feature to support composition without the need of accumulating all objects into a single object, as future work. We edited a few sentences to make clear. Thanks a lot for the guidance! Richard On Sun, Mar 18, 2018 at 5:55 AM, Jan Seedorf <mailto:i...@j-f-s

Re: [alto] SSE final touches

Hi Richard, 2. One next step we are considering is the support of multipart update. The sever may send a multipart message consisting of multiple objects say A, B, ... each of which is a top level JSON object.. Both merge patch and JSON patch support only a single object and hence cannot ap

Re: [alto] I-D Action: draft-ietf-alto-unified-props-new-03.txt

NA considerations. Hope this answers your question, Sabine -Original Message- From: alto [mailto:alto-boun...@ietf.org] On Behalf Of Jan Seedorf Sent: Thursday, March 15, 2018 11:28 PM To: alto@ietf.org Subject: Re: [alto] I-D Action: draft-ietf-alto-unified-props-new-03.txt Authors,

Re: [alto] I-D Action: draft-ietf-alto-unified-props-new-03.txt

Authors, can you please update the WG regarding the following: I am taking a look again at the possibility of integrating cellular into UP quickly. An alternative is that we get it done shortly, in the next couple days. If this is the approach, Sabine is a great person to work together. Mak

Re: [alto] Updated ALTO agenda

Presenters: please have a look at the agenda, it is really tight. We therefore strongly encourage you to plan accordingly and stick to your allocated time. As the agenda is so full and tight, we will have to cut each presentation after the allocated time has passed. So please focus on the mai

[alto] Agenda requests for IETF 101 in London

Dear all, please let us (the chairs) know if you want to present during the ALTO session at IETF-101 in London. We really want to make progress with the milestones, so clear preference in the agenda will be given to documents that address the milestones. We hope to see many of you in London

[alto] ALTO Virtual Interim Meeting (DEC 4th, 2017, 13:00 CET): Call for agenda items

Dear all, the ALTO WG will have an ALTO virtual meeting on: *** Dec 4, 2017 @ 1300 CET *** WebEx Details will follow. Please let us know if you intend to present something, i.e. want agenda time. We will then prepare an agenda accordingly.     - Vijay & Jan

[alto] Date/time for ALTO Virtual Interim

Hi all, according to the doodle, we will hold the ALTO Virtual Interim Meeting *** DEC 4th, 2017, 13:00-15:00 CET time *** Please mark your calendars, more details will follow,  - Vijay & Jan On 13.10.17 20:38, Jan Seedorf wrote: Hi all, Vijay and I have discussed possible dates fo

[alto] Doodle for ALTO Virtual Interim

Hi all, Vijay and I have discussed possible dates for an ALTO Virtual Interim Meeting in December, as we will not have an ALTO session at IETF-100 in Singapore. I have set up a doodle with 2 possible options: Monday DEC 4th or Monday DEC 18; time will be 07:00-09:00 Chicago time = 13:00-15:00

Re: [alto] ALTO minutes from IETF99 meeting

Hi all, since there were no comments, I have just uploaded the minutes to the datatracker. - Jan On 07.08.17 13:00, Jan Seedorf wrote: Dear all, please find attached the minutes from the ALTO session at IETF99. Please let Vijay and myself have any comments/corrections within a week

[alto] ALTO minutes from IETF99 meeting

Dear all, please find attached the minutes from the ALTO session at IETF99. Please let Vijay and myself have any comments/corrections within a week. Many thanks to our note-takers Lyle and Sabine! - Jan *** IETF 99, July 16-21, 2017. Prague, Czech Republic ALTO WG Meeting, Thu Jul 20, 2017

Re: [alto] fci alto transport design discussion

ntal updates harder. In other words, this issue will determine whether we should integrate JSON Patch. The current alto incremental updates, based on SSE and JSON Merge Patch, is pretty useful. The FCI use case may argue that we extend the incremental update w/ JSON Patch, to better handle array

[alto] ALTO Session Requests for IETF 99

Attendees: 20 Conflicts to Avoid: First Priority: tsvarea tsvwg tcpm i2rs nvo3 supa netmod netconf cdni ippm nfvrg Second Priority: dispatch rtcweb sipcore lmap People who must be present: Vijay K. Gurbani Jan Seedorf Mirja Kuehlewind Resources Requested: Specia

[alto] Adding a milestone to ALTO regarding the CDNI FCI interface

Dear all, during the ALTO session at IETF-96 (the last F2F ALTO session), I presented on the CDNI-FCI interface and that it will be based on ALTO. In the meantime, RFC 8008 is done (https://tools.ietf.org/html/rfc8008), which is defining the JSON object to be transported in the CDNI-FCI inter

Re: [alto] Shepherd Write-up for draft-ietf-alto-multi-cost

tion". - Jan On 22/02/2017 18:27, Jan Seedorf wrote: Dear all, I just uploaded the shepherd write-up for draft-ietf-alto-multi-cost to the datatracker (fyi below). Authors: you still need to fix one downward ref (see below). Let me know when you intend to do this. Once this is

[alto] Shepherd Write-up for draft-ietf-alto-multi-cost

- Jan *1. Summary* Jan Seedorf is the document shepherd for draft-ietf-alto-multi-cost. Mirja Kühlewind is the responsible Area Director. The document itself has a long history, having started as a -00 document in the ALTO WG as an individual draft in October 2010 (author: Sabine Randr

[alto] Updated ALTO Milestones

and for others we have mature WG items drafts) let us know. We will have an ALTO session in Chicago, where we hope to make further progress towards these charter items, so we think the milestones are actually realistic. - Jan -- Prof. Dr. Jan Seedorf jan.seed

[alto] ALTO Session at IETF-98

ALTO-Folks, just to let you know: Vijay and I both will be at IETF-98 in Chicago and have requested a slot for an ALTO session at IETF-98. Happy new year! - Jan -- Prof. Dr. Jan Seedorf jan.seed...@hft-stuttgart.de Hochschule für

[alto] No virtual interim meeting

Dear all, since there was only very minor interest in having an ALTO virtual interim, we decided not to have one (at this point in time). As a reminder, there will be no physical ALTO session at the IETF meeting in Seoul. However, Vijay and I both plan to be at the IETF meeting in Chicago, s

Re: [alto] RFC 7971 on Application-Layer Traffic Optimization (ALTO) Deployment Considerations

mailing list alto@ietf.org https://www.ietf.org/mailman/listinfo/alto - vijay -- Prof. Dr. Jan Seedorf jan.seed...@hft-stuttgart.de Hochschule für Technik Stuttgart Fakultät Vermessung, Informatik und Mathematik Schellingstr. 24 D-70174

Re: [alto] review of draft-ietf-alto-incr-update-sse-02

that the server must use control URIs with enough randomness, so an attacker cannot guess them. Should that be added in 8.1? Or can we find a better mechanism to actually authenticate and autorize requests to the control URI? -- Sebastian ___ alto

Re: [alto] TR: I-D Action: draft-ietf-alto-multi-cost-03.txt

___ 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 -- Prof. Dr. Jan Seedorf jan.seed...@hft-stuttgart.

[alto] my email address

ee you all in Berlin, - Jan -- ******** Prof. Dr. Jan Seedorf jan.seed...@hft-stuttgart.de Hochschule für Technik Stuttgart Fakultät Vermessung, Informatik und Mathematik Schellingstr. 24 D-70174 Stuttgart

Re: [alto] I am reviewing Server-Sent Events(SSE)

draft. Thanks! Best Regards, Mingming Chen ___ alto mailing list alto@ietf.org https://www.ietf.org/mailman/listinfo/alto -- Prof. Dr. Jan Seedorf jan.seed...@hft-stuttgart.de Hochschule für

[alto] Call for adoption of draft-randriamasy-alto-cost-calendar-05

, July 18, 2016. Jan & Vijay -- Prof. Dr. Jan Seedorf jan.seed...@hft-stuttgart.de Hochschule für Technik Stuttgart Fakultät Vermessung, Informatik und Mathematik Schellingstr. 24 D-70174 Stuttgart www.hft-stuttgar

[alto] Working Group Last Call on draft-ietf-alto-multi-cost-02

you can volunteer for doing the individual review for this document. Jan & Vijay -- Prof. Dr. Jan Seedorf jan.seed...@hft-stuttgart.de Hochschule für Technik Stuttgart Fakultät Vermessung, Informatik und Mathematik Schellingstr. 24 D-7

[alto] Working Group Last Call on draft-ietf-alto-incr-update-sse-02

chairs know if you can volunteer for doing the individual review for this document. Jan & Vijay -- Prof. Dr. Jan Seedorf jan.seed...@hft-stuttgart.de Hochschule für Technik Stuttgart Fakultät Vermessung, Informatik und Mathematik Schellin

Re: [alto] Spam-Level: LOW ; Working on a new draft on applying ALTO for ExaScale Science Applications.

ailman/listinfo/alto -- ******** Prof. Dr. Jan Seedorf jan.seed...@hft-stuttgart.de Hochschule für Technik Stuttgart Fakultät Vermessung, Informatik und Mathematik Schellingstr. 24 D-70174 Stuttgart

[alto] Minutes from the ALTO Session at IETF-93 uploaded

Dear all, since we received no corrections/comments, I have just uploaded the notes from the IETF-93 ALTO session (as below) via the proceeding manager. - Jan From: alto [mailto:alto-boun...@ietf.org] On Behalf Of Jan Seedorf Sent: Dienstag, 28. Juli 2015 21:42 To: alto@ietf.org

[alto] Minutes from the ALTO Session at IETF-93

g 10' ddraft-wang-alto-large-data-framework-00 - Due to time we deferred comments to the mailing list 1710-1720 - Spill over/Conclusion/Wrap-up Chairs/WG 10' - General comment of encouraging WG to read each others' documents. Authors are encouraged to read each other's w

Re: [alto] Please read the documents from other WG participants

until the next IETF :) - Jan From: Songhaibin (A) [mailto:haibin.s...@huawei.com] Sent: Dienstag, 28. Juli 2015 08:04 To: Jan Seedorf; alto@ietf.org Subject: RE: Please read the documents from other WG participants I agree. Shall we try something like, if you would like to get a slot to present your dra

[alto] Please read the documents from other WG participants

have the backing of the majority of the WG (rough consensus) and drafts entering WGLC are ready for publication, so that we do not embarrass ourselves in front of the IESG. - Jan (with chair hat on) Prof. Dr. Jan Seedorf S

[alto] Room Info ALTO interim tonight

event! - Jan Prof. Dr. Jan Seedorf Senior Researcher NEC Europe Ltd., NEC Laboratories Europe, Network Division Kurfuerstenanlage 36, D-69115 Heidelberg Tel. +49 (0)6221 4342-221 Fax: +49 (0)6221 4342-155 e-mail

Re: [alto] Updated (draft) agenda posted

Dear all, please note that in the updated agenda the timeslots are now 10 instead of 15 minutes (as we have a couple more presentations). As we have a packed agenda and want to give everyone the chance to present, please plan your presentation slot accordingly and make sure you stick to the tim

[alto] ALTO Session / Agenda at IETF-93

. - Jan Prof. Dr. Jan Seedorf Senior Researcher NEC Europe Ltd., NEC Laboratories Europe, Network Division Kurfuerstenanlage 36, D-69115 Heidelberg Tel. +49 (0)6221 4342-221 Fax: +49 (0)6221 4342-155 e-mail: jan.seed

[alto] ALTO Session at IETF-93

Prof. Dr. Jan Seedorf Senior Researcher NEC Europe Ltd., NEC Laboratories Europe, Network Division Kurfuerstenanlage 36, D-69115 Heidelberg Tel. +49 (0)6221 4342-221 Fax: +49 (0)6221 4342-155 e-mail: jan.seed...@neclab.eu<mailto:jan.seed...@neclab

[alto] ALTO Interop at IETF-93 in Prague

this discussion, so that we can make the best use of the time in Prague. - Jan Prof. Dr. Jan Seedorf Senior Researcher NEC Europe Ltd., NEC Laboratories Europe, Network Division Kurfuerstenanlage 36, D-69115 Heidelberg Tel

Re: [alto] Interop test

Regarding the date/time: the chairs can likely only make it on one of the following evenings during the IETF week: MON, WED, THU. We are aiming at 3-4h. Does that work for the people interested? We have contacted the secretariat to tentatively reserve a room etc. - Jan -Original Message--

[alto] Minutes from IETF92 uploaded

Please check the minutes, and let the chairs know if you find something that needs to be corrected. - Jan Prof. Dr. Jan Seedorf Senior Researcher NEC Europe Ltd., NEC Laboratories Europe, Network Division Kurfuerstenanlage

Re: [alto] ALTO implementation interoperability

We have also put this topic on the chair slides for the session in Dallas to get feedback from the room, but please also continue raising your opinion on this here on the ML. - Jan From: alto [mailto:alto-boun...@ietf.org] On Behalf Of Y. Richard Yang Sent: Donnerstag, 19. März 2015 2

Re: [alto] Request for comments on two changes for RFC7285-to-be

> (2) However, some authors feel that we should not enforce too strong a > requirement to make deployment harder. Hence, instead of changing the > aforementioned MAY to MUST, these authors feel that it is better to make > the pid endpoint property optional. Hence, we make the two changes of E1 > an

Re: [alto] JSON Patch vs. custom representation for incremental updates

uses JSON patch. I guess I would like to hear other opinions ... - Jan > -Original Message- > From: Wendy Roome [mailto:w.ro...@alcatel-lucent.com] > Sent: Thursday, July 10, 2014 10:21 PM > To: Jan Seedorf; IETF ALTO > Subject: Re: [alto] JSON Patch vs. custom representati

Re: [alto] JSON Patch vs. custom representation for incremental updates

Hi Wendy, What about future, new ALTO services (e.g. as proposed in http://tools.ietf.org/html/draft-seedorf-cdni-request-routing-alto-07)? I am not a fan of JSON patch, but a solution for incremental updates based on JSON patch should be much more future-proof with respect to new, future ALTO

[alto] FW: FCI Analysis

ALTO Folks, Just a reminder and FYI: ALTO is currently one of two candidates for the CDNI FCI interface (draft-seedorf-cdni-request-routing-alto). Matt below provided a good comparison of the ALTO-based approach that Richard Yang and I am proposing, and the alternative approach which would be a

Re: [alto] Text proposal for charter update

Hi all, The text looks good to me and in my view reflects the agreement on re-chartering in the ALTO WG. Just two small comments: -- "where the host was a peer in a P2P network and desired to be rendezvoused with other peers for file sharing" --> When talking about the P2P use case I would not

Re: [alto] Work items for re-chartering

86; two proposals have been > studied. One way forward is to use an ALTO-specific incremental > update that may be more efficient, and the second approach is to > simply use JSON patch.) > > 4. Server-initiated update notifications > (Jan Seedorf and Enrico Marocco have

Re: [alto] WG adoption of *-3pdisc and *-ip-based-srv-disc drafts

I support the adoption of both documents. For the lmap use cases, 3rd party discovery may be necessary, e.g. if a web service provider want to find out which ALTO server can provide LMAP result for a given end user IP address. - Jan > -Original Message- > From: alto-boun...@ietf.org [

Re: [alto] Security problem: DoS attacks via overload

Just to second this, I am resending a comment I made a long time ago about DoS attacks / too large matrices (cut and paste from my IETF-75 notes): "Jan Seedorf: has concerns with the workload for ALTO servers caused by queries with multiple source network locations, risk of easy DoS at

Re: [alto] ALTO IETF-86 Side Meeting Info

Hi Richard, Enrico and I can also briefly present our "WebSocket-based server-to-client notifications for ALTO" draft (draft-marocco-alto-ws-01). Can you please add it to the agenda? Thanks, Jan > -Original Message- > From: alto-boun...@ietf.org [mailto:alto-boun...@ietf.org] On Behal

[alto] New Draft "ALTO for LMAP"

: enrico.maro...@telecomitalia.it Cc: v...@bell-labs.com; Jan Seedorf Subject: New Version Notification for draft-seedorf-lmap-alto-00.txt A new version of I-D, draft-seedorf-lmap-alto-00.txt has been successfully submitted by Enrico Marocco and posted to the IETF repository. Filename

[alto] FW: New Version Notification for draft-seedorf-cdni-request-routing-alto-02.txt

-dra...@ietf.org [mailto:internet-dra...@ietf.org] Sent: Monday, July 16, 2012 4:21 PM To: Jan Seedorf Subject: New Version Notification for draft-seedorf-cdni-request-routing-alto-02.txt A new version of I-D, draft-seedorf-cdni-request-routing-alto-02.txt has been successfully submitted by Jan

Re: [alto] draft-marocco-alto-next-00

Hi Haibin, > If ALTO provides the information about what contents/apps are > available on which endpoints/servers, that will make the ALTO server look > like a huge resource directory, which is hard to manage and should be > provided by the application themselves. True, if ALTOext would provide de

[alto] Draft submitted on ALTO for CDNi request routing

CDNi folks, ALTO folks, I have just submitted a new draft which discusses how ALTO could help in CDNi request routing: Abstract: "... This document focusses on the Request Routing Interface of CDNi, and more specifically on how the solutions currently being defined in the Application Layer Tra

Re: [alto] [decade] Live streaming of NAPA-WINE P2P-TV workshop with P2P software

> Sent: Dienstag, 18. Januar 2011 18:24 > To: Jan Seedorf; p2...@irtf.org; P2PSIP WG; p...@ietf.org; 'alto'; > dec...@ietf.org > Subject: Re: [decade] Live streaming of NAPA-WINE P2P-TV workshop with P2P > software > > This spam is highly unwelcome. > Also quite surp

[alto] Live streaming of NAPA-WINE P2P-TV workshop with P2P software

ls, please see http://www.napa-wine.eu/workshop/ - Jan ======== Jan Seedorf Senior Researcher NEC Europe Ltd., NEC Laboratories Europe, Network Division  Kurfuerstenanlage 36, D-69115 Heidelberg Tel. +49 (0)6221 4342-221 Fax: +49 (0

[alto] Call for Participation: International Workshop on P2P-TV (no registration fee)

indly invited to register their attendance by January 10th, 2011, at http://www.napa-wine.eu/workshop/registration.html. People that will not register may not be granted access due to seat limitations. *** ==== Jan Seedorf S

Re: [alto] Security section of draft-penno-alto-protocol-03

--Original Message- > From: alto-boun...@ietf.org [mailto:alto-boun...@ietf.org] On Behalf Of > Wang Yan > Sent: Donnerstag, 13. August 2009 04:51 > To: Jan Seedorf; alto > Subject: Re: [alto] Security section of draft-penno-alto-protocol-03 > > Hi, Jan > > > -- "

Re: [alto] [ALTO] Comments on [draft-stiemerling-alto-info-redist-00]

> -Original Message- > From: Y.J. Gu [mailto:guying...@huawei.com] > Sent: Donnerstag, 13. August 2009 05:56 > To: Jan Seedorf; 'alto' > Subject: RE: [alto] [ALTO] Comments on [draft-stiemerling-alto-info- > redist-00] > > Hi Jan, > See in line pl

Re: [alto] [ALTO] Comments on[draft-stiemerling-alto-info-redist-00]

mation. Still, what if an ALTO server realizes it was misconfigured or something changes unexpectedly, than the ALTO server has no way of controlling its already redistributed, now "wrong" information. What do you think? - Jan > -Original Message- > From: alto-bo

[alto] Security section of draft-penno-alto-protocol-03

much more work. I felt like giving it a start with some comments. - Jan Jan Seedorf Research Scientist NEC Europe Ltd., NEC Laboratories Europe, Network Division Kurfuerstenanlage 36, D-69115 Heidelberg Tel. +49 (0)622

Re: [alto] [ALTO] Comments on [draft-stiemerling-alto-info-redist-00]

Dear Yingjie, I think the problem of redistributed ALTO-information is not so easy, some comments below. > -- "However, there is no mean for the peers to verify whether the > information provided is actually intended >for their usage nor if the information is actually accurate at their > cu

[alto] FW: WGLC: draft-ietf-alto-problem-statement-01

...@ietf.org] On Behalf Of Jan Seedorf Sent: Freitag, 3. Juli 2009 17:04 To: Y. Richard Yang; alto@ietf.org Subject: Re: [alto] WGLC: draft-ietf-alto-problem-statement-01 Dear Richard, ALTO folks, we have discussed the comments received from Richard for the WGLC of "draft-ietf-alto-problem-stateme

Re: [alto] WGLC: draft-ietf-alto-problem-statement-01

Dear Richard, ALTO folks, we have discussed the comments received from Richard for the WGLC of "draft-ietf-alto-problem-statement-01" among the editors and addressed them accordingly. I have just submitted the new -02 version of the draft. For seeing how we addressed the comments please produce

Re: [alto] 'Link capacity' in scope?

Dear Salman, > In addition to provisioned link capacity, it is useful for end points > to > determine how much of their upload/download quota has been consumed > (assuming ISPs that have a montly bandwidth cap). Like provisioned link > capacity, this information is *indirectly* used by the peers t

[alto] -01 version of the ALTO problem statement draft submitted

", which is the proper term introduced in the terminology section. Of course, we also updated the corresponding text accordingly. Kind regards, Jan ======== Jan Seedorf Research Scientist NEC Europe Ltd., NEC Laboratories Euro

Re: [alto] Adopting two I-Ds as WG documents

Dear Greg, Thanks for your comments. We discussed these among the editors of the problem statement draft. We agree that the text on caching you highlight below is potentially misleading, and also that the phrasing of a "malicious" ISP is probably a bit strong. Thanks for raising these points.

Re: [alto] About relay in realtime communication use case in alto problem statement

O client-server protocol which are not already included in [draft-kiesel-alto-reqs]. But please elaborate on this list if you think so and specifically what those requirements are. - Jan > -Original Message- > From: Tao Ma [mailto:abcdma...@gmail.com] > Sent: Donnerstag, 2. Ap

[alto] FW: New Version Notification for draft-marocco-alto-problem-statement-05

ALTO WG. Feedback of course appreciated, - Jan -Original Message- From: IETF I-D Submission Tool [mailto:idsubmiss...@ietf.org] Sent: Sonntag, 8. März 2009 14:28 To: Jan Seedorf Cc: ebur...@standardstrack.com Subject: New Version Notification for draft-marocco-alto-problem-statement-05

[alto] my notes from the ALTO session at IETF73

<> Dear all, Attached are my notes from the ALTO session last week at IETF-73. Kind regards, Jan ALTO Session at IETF-73 Tuesday, 13:00-15:00 Notes, Notetaker: Jan Seedorf 13:00 -- Chairs present Agenda, no objections -- Lisa presents WG status: history of the WG (P2Pi workshop), since I