What an efficient shepherd, you are, Med 😊
Thanks for your quick reply, a variation of your text at the bottom about http
vs. https would be nice in section 5.3.1.1
Regards
-éric
From: iesg on behalf of mohamed.boucad...@orange.com
Date: Wednesday, 25 October 2023 at 13:15
To: Eric Vyncke
?
>
>
>
> -Qin
>
> *发件人:* alto [mailto:alto-boun...@ietf.org] *代表 *Eric
> *发送时间:* 2022年7月20日 10:13
> *收件人:* Y. Richard Yang
> *抄送:* IETF ALTO
> *主题:* Re: [alto] Cellular information exposure discussion (Fwd: New
> Version Notification for draft-huang-alto-mowie-fo
Hi Richard and Med,
This is Yixue from Tencent who works in 3GPP for 15 years but new to
IETF.___^ . But actually from years ago, even in my Ph. D study, I like
reading some IETF and IRTF drafts and several years ago,I have noticed
ALTO WG in IETF as in Tencent my research and standard interes
Hello Jensen,
Thank you for addressing my comments, the document is better in that way.
Regards
-éric
From: Jensen Zhang
Date: Tuesday, 14 December 2021 at 10:45
To: Eric Vyncke
Cc: The IESG , Donald Eastlake , alto-chairs
, IETF ALTO ,
"draft-ietf-alto-cdni-request-routing-a...@iet
The new text looks good to me, thank you
-éric
From: "kai...@scu.edu.cn"
Date: Monday, 6 December 2021 at 04:34
To: Eric Vyncke
Cc: The IESG , "draft-ietf-alto-path-vec...@ietf.org"
, "alto-cha...@ietf.org"
, "alto@ietf.org" ,
"vijay.gurb...@
Hello Kai,
Thank you for your prompt reply and your actions on the document.
Please find some further comment below, look for EV>
Regards
-éric
On 30/11/2021, 18:01, "kai...@scu.edu.cn" wrote:
Hi Éric,
Thanks for the review and please see the responses inline.
Best,
Kai
Thank you Donald,
I just balloted a NO OBJECTION notably based on your Int-dir review.
Regards
-éric
On 27/11/2021, 03:19, "Int-dir on behalf of Donald Eastlake via Datatracker"
wrote:
Reviewer: Donald Eastlake
Review result: Ready with Issues
I am an assigned INT directorate r
Bonjour Sabine,
Thank you for revision -21, it addresses all my previous non-blocking comments.
Have a nice WE!
Regards
-éric
On 26/11/2021, 14:57, "Randriamasy, Sabine (Nokia - FR/Paris-Saclay)"
wrote:
Hello Éric,
A new version has been posted to address your comments.
We ho
ow TCP
throughput is estimated. The spatial aggregation level is specified
in the query context (e.g., PID to PID, or endpoint to endpoint).
So, it is RFC 8312 in the text, RFC 8312 is vaguely related to TCP bandwidth
-éric
From: Martin Duke
Date: Monday, 22 November 2021 at 16:40
To: Eric
On Wed, Jan 16, 2019 at 4:15 PM Sebastian Kiesel
wrote:
> On Wed, Dec 19, 2018 at 12:49:22PM -0800, Eric Rescorla wrote:
> > Eric Rescorla has entered the following ballot position for
> > draft-ietf-alto-xdom-d
Eric Rescorla has entered the following ballot position for
draft-ietf-alto-xdom-disc-04: Discuss
When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)
Please refer to https
Thanks. I have removed my discuss.
-Ekr
On Tue, Apr 25, 2017 at 10:36 AM, Randriamasy, Sabine (Nokia - FR/Nozay) <
sabine.randriam...@nokia-bell-labs.com> wrote:
> Hello Eric,
>
> Thanks a lot for your feedback and suggested text on privacy or security
> issues.
> I have
Eric Rescorla has entered the following ballot position for
draft-ietf-alto-multi-cost-08: Discuss
When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)
Please refer to
All of the "elements" are logical. Whether an element is instantiated
on a big honking mainframe at a service provider or a distributed p2p
ring, is simply an implementation matter. However, we need to talk
about a well-known, locatable "service" that offer the ALTO "stuff."
We tend to cal
There is no physical method prevent an ALTO client from sharing query
results, so there is no point in having it in the protocol.
On Jun 16, 2009, at 12:16 PM, Richard Alimi wrote:
Hi Salman,
On Tuesday 16 June 2009 12:59:00 am Salman Abdul Baset wrote:
In general, the question is when a nod
Sounds even better.
On Jun 3, 2009, at 4:13 AM, Sebastian Kiesel wrote:
On Tue, Jun 02, 2009 at 09:39:55PM -0400, Eric Burger wrote:
Inline.
On Jun 2, 2009, at 11:05 AM, Linda Dunbar wrote:
Eric,
Thank you very much for the explanation. Since I haven't
participated
in the
Inline.
On Jun 2, 2009, at 11:05 AM, Linda Dunbar wrote:
Eric,
Thank you very much for the explanation. Since I haven't
participated in the ALTO discussion until recently, I am not aware
that working group has already reached consensus on the document.
Seeing the document is only a
is.
On Jun 1, 2009, at 12:01 PM, Linda Dunbar wrote:
Jan and Eric,
I have following comments to the “draft-ietf-alto-problem-
statement-01:
The Figure 1 of the draft (i.e. the ALTO server providing client
protocol to peers and Resource Directory) demonstrates a solution
for the
I would expect that do do content discovery or peer discovery one
would need a relatively fixed identifier for that content.
On May 1, 2009, at 3:57 PM, Y. R. Yang wrote:
Hi Eric,
On Fri, 1 May 2009, 3:53pm -0400, Eric Burger wrote:
I think such a proposal would require a globally unique
I think such a proposal would require a globally unique and time
invariant content ID. That sounds challenging at best.
On May 1, 2009, at 12:36 PM, Y. R. Yang wrote:
Hi All,
I found the discussion related with content ID interesting.
Pushing upper layer information, in particular, conten
I would also like to point out the mechanism described in Nicholas'
original email, taking intelligent action based on the content ID, is
something an ALTO Server *can* implement. There is NOTHING so far
proposed in ALTO that would prevent a server from somehow figuring out
the request is
I was preparing the slides for the IETF 74 ALTO meeting for the
ProblemStatement,
http://www.ietf.org/internet-drafts/draft-marocco-alto-problem-statement-05.txt
(Full URL here for you to click on...)
I believe that the current text incorporates all open issues raised on
the list. To me, this
Popkin, CTO, Pando Networks
mobile: 646/465-0570
- Original Message -
From: "Robert Raszuk"
To: "Laird Popkin"
Cc: "Eric Burger" , alto@ietf.org
Sent: Tuesday, February 10, 2009 11:34:10 AM (GMT-0500) America/
New_York
Subject: Re: [alto] differences a
I would offer it is important to have the client specify what it
thinks is important. However, I would also offer it would be fatal to
have "Profile B", "Profile N", "Profile S" selection algorithms, where
B, N, and S are different applications. I will guarantee that by the
time we're done
This draft is an update to the problem statement that Enrico and Vijay
wrote. Jan and I think it addresses the basic issues raised during
the BOF and first WG meetings. Of course, we are sure you will find
something to comment on.
One issue that we made an arbitrary change on is there used
25 matches
Mail list logo
