date:20220407

Re: [alto] WGLC for draft-ietf-alto-cost-mode-00

2022-04-07 Thread Jordi Ros Giralt

Hi Kai,

I read this document and I support proceeding with its publication.

Thank you,
Jordi


From: alto  on behalf of kai...@scu.edu.cn 

Sent: Friday, March 25, 2022 1:46
To: alto@ietf.org 
Subject: [alto] WGLC for draft-ietf-alto-cost-mode-00

WARNING: This email originated from outside of Qualcomm. Please be wary of any 
links or attachments, and do not enable macros.

Hi all,

As discussed during the ALTO session in IETF 113, the ALTO cost mode document 
is now adopted as a working group document. A new WG version 
(draft-ietf-alto-cost-mode-00) [1] has been submitted to replace the individual 
draft and address comments from the Call for Adoption.

To move forward, this message starts the WGLC for draft-ietf-alto-cost-mode-00. 
The WGLC will run till April 8, 2022 (two weeks from now).

As both WG chairs are co-authoring the document, I’m taking care of this call 
as part of my document shepherding. We would like to have 2-3 reviewers from 
the working group. Please review and indicate your support or objection to 
proceed with the publication of this document.

Thanks!

[1] https://datatracker.ietf.org/doc/draft-ietf-alto-cost-mode/.

Best,
Kai
___
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

Re: [alto] [Editorial Errata Reported] RFC7285 (6876)

2022-04-07 Thread mohamed.boucadair

Hi Sebastien,

I can't act on the erratum to update the "Corrected Text" to reflect what we 
agreed together. 

I guess Martin or the RFC editor can make that update and then mark it as 
verified. Doing so would allow the corrected text to be seen as part of the 
rendered RFC version 
(https://www.rfc-editor.org/rfc/inline-errata/rfc7285.html). 

Cheers,
Med

> -Message d'origine-
> De : Sebastian Kiesel 
> Envoyé : jeudi 7 avril 2022 11:35
> À : BOUCADAIR Mohamed INNOV/NET 
> Cc : Chris Smiley ; martin.h.d...@gmail.com;
> Zaheduzzaman Sarker ;
> ral...@google.com; repe...@cisco.com; y...@cs.yale.edu;
> sprev...@cisco.com; w.ro...@alcatel-lucent.com;
> shalu...@shlang.com; richard_wou...@cable.comcast.com;
> alto@ietf.org; RFC Errata System 
> Objet : Re: [Editorial Errata Reported] RFC7285 (6876)
> 
> Hi Chris, Med, all,
> 
> how do we move on here?
> 
> my opinion is that the reported errata is not imperative to be
> recorded, but if we decide to do so, I would consider this as an
> editorial errata and I would really appreciate if we could add the
> proposed "Note: ..."
> sentence below the table (see quoted mail below), to make it
> absolutely clear that no policy or specification change is
> intended.
> 
> who needs to sign off on that errata?
> 
> (same for the other reported errata case)
> 
> Thanks
> Sebastian
> 
> 
> On Thu, Mar 10, 2022 at 12:21:19PM +,
> mohamed.boucad...@orange.com wrote:
> > Hi Sebastien, all,
> >
> > Works for me. Thanks.
> >
> > Cheers,
> > Med
> >
> > > -Message d'origine-
> > > De : Sebastian Kiesel  Envoyé : jeudi 10
> mars
> > > 2022 13:17 À : Chris Smiley  Cc :
> > > martin.h.d...@gmail.com; Zaheduzzaman Sarker
> > > ; BOUCADAIR Mohamed
> INNOV/NET
> > > ; ral...@google.com;
> > > repe...@cisco.com; y...@cs.yale.edu; sprev...@cisco.com;
> > > w.ro...@alcatel-lucent.com; shalu...@shlang.com;
> > > richard_wou...@cable.comcast.com; alto@ietf.org; RFC Errata
> System
> > >  Objet : Re: [Editorial Errata
> Reported]
> > > RFC7285 (6876)
> > >
> > > Hi Med,
> > >
> > > similar to the other case 6874, I think we should clarify that
> no
> > > policy change is intended, so:
> > >
> > >
> > > Type: Editorial
> > > Reported by: Mohamed BOUCADAIR 
> > >
> > > Section: 14.3
> > >
> > > Original Text
> > > -
> > >+++
> > >| Identifier | Intended Semantics |
> > >+++
> > >| pid| See Section 7.1.1  |
> > >| priv:  | Private use|
> > >+++
> > >
> > >   Table 4: ALTO Endpoint Property Types
> > >
> > >
> > > Corrected Text
> > > --
> > >+++
> > >| Identifier | Intended Semantics |
> > >+++
> > >| pid| See Section 7.1.1  |
> > >+++
> > >
> > >Note: Identifiers prefixed with "priv:" are
> > >reserved for Private Use (see Section
> 10.8.2.)
> > >
> > >   Table 4: ALTO Endpoint Property Types
> > >
> > >
> > > would that work for you?
> > >
> > > thanks
> > > Sebastian
> > >
> > > On Wed, Mar 09, 2022 at 01:23:35PM -0800, Chris Smiley wrote:
> > > >
> > > > Greetings,
> > > >
> > > > We are unable to verify this erratum that the submitter
> marked as
> > > editorial.
> > > > Please note that we have changed the “Type” of the following
> > > > errata report to “Technical”.  As Stream Approver, please
> review
> > > > and set the Status and Type accordingly (see the definitions
> at
> > > > https://www.rfc-editor.org/errata-definitions/).
> > > >
> > > > You may review the report at:
> > > > https://www.rfc-editor.org/errata/eid6876
> > > >
> > > > Please see https://www.rfc-editor.org/how-to-verify/ for
> further
> > > > information on how to verify errata reports.
> > > >
> > > > Further information on errata can be found at:
> > > > https://www.rfc-editor.org/errata.php.
> > > >
> > > > Thank you.
> > > >
> > > > RFC Editor/cs
> > > >
> > > >
> > > > > On Mar 8, 2022, at 10:21 PM, RFC Errata System  editor@rfc-
> > > editor.org> wrote:
> > > > >
> > > > > The following errata report has been submitted for
> RFC7285,
> > > > > "Application-Layer Traffic Optimization (ALTO) Protocol".
> > > > >
> > > > > --
> > > > > You may review the report below and at:
> > > > > https://www.rfc-editor.org/errata/eid6876
> > > > >
> > > > > --
> > > > > Type: Editorial
> > > > > Reported by: Mohamed BOUCADAIR
> 
> > > > >
> > > > > Section: 14.3
> > > > >
> > > > > Original Text
> > > > > -
> > > > >+++
> > > > >

Re: [alto] Call for adoption: draft-zhang-alto-oam-yang

2022-04-07 Thread maqiufang (A)

Hi, all

I support the adoption of this draft which I believe provides a good starting 
point.

The following are some comments, apologizes if I’ve missed something.

1.   I still don't see any statistics related to R2 and R4 defined in 
Sec4.2. IMO it is important to record statistics related to server failures.

2.   The following performance statistics of the alto server may be 
considered, or just clarified to be out of scope:

· Total number of queries received

· Total number of successful/error responses

· Number of queries processed per second

· Average response time

· Usage of system resources such as CPU, memory, and storage

· Connection statistics

3.   Should HTTP-server related configuration be in our scope(e.g., 
cache-control, Retry-After)?

Best Regards,
Qiufang Ma
From: alto [mailto:alto-boun...@ietf.org] On Behalf Of Randriamasy, Sabine 
(Nokia - FR/Paris-Saclay)
Sent: Thursday, April 7, 2022 9:54 PM
To: Qiao Xiang ; Luis M. Contreras 

Cc: roland.sch...@telekom.de; draft-zhang-alto-oam-y...@ietf.org; IETF ALTO 
; alto-cha...@ietf.org
Subject: Re: [alto] Call for adoption: draft-zhang-alto-oam-yang

+1,
Best regards
Sabine

From: alto mailto:alto-boun...@ietf.org>> On Behalf Of 
Qiao Xiang
Sent: Thursday, April 7, 2022 11:17 AM
To: Luis M. Contreras 
mailto:contreras.i...@gmail.com>>
Cc: roland.sch...@telekom.de; 
draft-zhang-alto-oam-y...@ietf.org; 
IETF ALTO mailto:alto@ietf.org>>; 
alto-cha...@ietf.org
Subject: Re: [alto] Call for adoption: draft-zhang-alto-oam-yang

Hi all,

I support the adoption of this draft.



Best
Qiao

On Thu, Apr 7, 2022 at 5:11 PM Luis M. Contreras 
mailto:contreras.i...@gmail.com>> wrote:
Hi all,

I support the adoption of this draft.

Best regards

Luis


El mié, 6 abr 2022 a las 18:30, 
mailto:roland.sch...@telekom.de>> escribió:
Hi,

I support the adoption of the draft as a good starting point for further work.

Best Regards

Roland



Von: mohamed.boucad...@orange.com 
mailto:mohamed.boucad...@orange.com>>
Gesendet: Montag, 4. April 2022 12:14
An: alto@ietf.org; 
draft-zhang-alto-oam-y...@ietf.org
Cc: alto-cha...@ietf.org
Betreff: RE: Call for adoption: draft-zhang-alto-oam-yang

Hi all,

This is a reminder that this call for adoption is still running.

Cheers,
Qin & Med

De : mohamed.boucad...@orange.com 
mailto:mohamed.boucad...@orange.com>>
Envoyé : mercredi 23 mars 2022 14:45
À : alto@ietf.org; 
draft-zhang-alto-oam-y...@ietf.org
Cc : alto-cha...@ietf.org
Objet : Call for adoption: draft-zhang-alto-oam-yang

Hi all,

As discussed during the IETF#113 meeting, this message initiates the call for 
adoption of draft-zhang-alto-oam-yang to meet the following ALTO WG milestone:

==
Dec 2022ALTO OAM Document/YANG Model
==

Please reply to this message indicating your support or objection to adopt the 
document.

The call will run till 08 April 2022.

Thank you
Qin & Med



_



Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc

pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce 
message par erreur, veuillez le signaler

a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
electroniques etant susceptibles d'alteration,

Orange decline toute responsabilite si ce message a ete altere, deforme ou 
falsifie. Merci.



This message and its attachments may contain confidential or privileged 
information that may be protected by law;

they should not be distributed, used or copied without authorisation.

If you have received this email in error, please notify the sender and delete 
this message and its attachments.

As emails may be altered, Orange is not liable for messages that have been 
modified, changed or falsified.

Thank you.
___
alto mailing list
alto@ietf.org
https://www.ietf.org/mailman/listinfo/alto


--
___
Luis M. Contreras
contreras.i...@gmail.com
luismiguel.contrerasmuri...@telefonica.com
Global CTIO unit / Telefonica
___
alto mailing list
alto@ietf.org
https://www.ietf.org/mailman/listinfo/alto


--
Qiao Xiang
Professor, Xiamen University
___
alto mailing list
alto@ietf.org

Re: [alto] [Editorial Errata Reported] RFC7285 (6876)

2022-04-07 Thread Sebastian Kiesel

Hi Chris, Med, all,

how do we move on here?

my opinion is that the reported errata is not imperative to be recorded,
but if we decide to do so, I would consider this as an editorial errata
and I would really appreciate if we could add the proposed "Note: ..."
sentence below the table (see quoted mail below), to make it absolutely
clear that no policy or specification change is intended.

who needs to sign off on that errata?

(same for the other reported errata case)

Thanks
Sebastian


On Thu, Mar 10, 2022 at 12:21:19PM +, mohamed.boucad...@orange.com wrote:
> Hi Sebastien, all, 
> 
> Works for me. Thanks. 
> 
> Cheers,
> Med
> 
> > -Message d'origine-
> > De : Sebastian Kiesel 
> > Envoyé : jeudi 10 mars 2022 13:17
> > À : Chris Smiley 
> > Cc : martin.h.d...@gmail.com; Zaheduzzaman Sarker
> > ; BOUCADAIR Mohamed INNOV/NET
> > ; ral...@google.com; repe...@cisco.com;
> > y...@cs.yale.edu; sprev...@cisco.com; w.ro...@alcatel-lucent.com;
> > shalu...@shlang.com; richard_wou...@cable.comcast.com; alto@ietf.org;
> > RFC Errata System 
> > Objet : Re: [Editorial Errata Reported] RFC7285 (6876)
> > 
> > Hi Med,
> > 
> > similar to the other case 6874, I think we should clarify that no policy
> > change is intended, so:
> > 
> > 
> > Type: Editorial
> > Reported by: Mohamed BOUCADAIR 
> > 
> > Section: 14.3
> > 
> > Original Text
> > -
> >+++
> >| Identifier | Intended Semantics |
> >+++
> >| pid| See Section 7.1.1  |
> >| priv:  | Private use|
> >+++
> > 
> >   Table 4: ALTO Endpoint Property Types
> > 
> > 
> > Corrected Text
> > --
> >+++
> >| Identifier | Intended Semantics |
> >+++
> >| pid| See Section 7.1.1  |
> >+++
> > 
> >Note: Identifiers prefixed with "priv:" are
> >reserved for Private Use (see Section 10.8.2.)
> > 
> >   Table 4: ALTO Endpoint Property Types
> > 
> > 
> > would that work for you?
> > 
> > thanks
> > Sebastian
> > 
> > On Wed, Mar 09, 2022 at 01:23:35PM -0800, Chris Smiley wrote:
> > >
> > > Greetings,
> > >
> > > We are unable to verify this erratum that the submitter marked as
> > editorial.
> > > Please note that we have changed the “Type” of the following errata
> > > report to “Technical”.  As Stream Approver, please review and set the
> > > Status and Type accordingly (see the definitions at
> > > https://www.rfc-editor.org/errata-definitions/).
> > >
> > > You may review the report at:
> > > https://www.rfc-editor.org/errata/eid6876
> > >
> > > Please see https://www.rfc-editor.org/how-to-verify/ for further
> > > information on how to verify errata reports.
> > >
> > > Further information on errata can be found at:
> > > https://www.rfc-editor.org/errata.php.
> > >
> > > Thank you.
> > >
> > > RFC Editor/cs
> > >
> > >
> > > > On Mar 8, 2022, at 10:21 PM, RFC Errata System  > editor.org> wrote:
> > > >
> > > > The following errata report has been submitted for RFC7285,
> > > > "Application-Layer Traffic Optimization (ALTO) Protocol".
> > > >
> > > > --
> > > > You may review the report below and at:
> > > > https://www.rfc-editor.org/errata/eid6876
> > > >
> > > > --
> > > > Type: Editorial
> > > > Reported by: Mohamed BOUCADAIR 
> > > >
> > > > Section: 14.3
> > > >
> > > > Original Text
> > > > -
> > > >+++
> > > >| Identifier | Intended Semantics |
> > > >+++
> > > >| pid| See Section 7.1.1  |
> > > >| priv:  | Private use|
> > > >+++
> > > >
> > > >   Table 4: ALTO Endpoint Property Types
> > > >
> > > >
> > > > Corrected Text
> > > > --
> > > >+++
> > > >| Identifier | Intended Semantics |
> > > >+++
> > > >| pid| See Section 7.1.1  |
> > > >+++
> > > >
> > > >   Table 4: ALTO Endpoint Property Types
> > > >
> > > >
> > > > Notes
> > > > -
> > > > priv: is not an identifier, but a prefix.
> > > >
> > > > Instructions:
> > > > -
> > > > This erratum is currently posted as "Reported". If necessary, please
> > > > use "Reply All" to discuss whether it should

Re: [alto] Call for adoption: draft-zhang-alto-oam-yang

2022-04-07 Thread Randriamasy, Sabine (Nokia - FR/Paris-Saclay)

+1,
Best regards
Sabine

From: alto  On Behalf Of Qiao Xiang
Sent: Thursday, April 7, 2022 11:17 AM
To: Luis M. Contreras 
Cc: roland.sch...@telekom.de; draft-zhang-alto-oam-y...@ietf.org; IETF ALTO 
; alto-cha...@ietf.org
Subject: Re: [alto] Call for adoption: draft-zhang-alto-oam-yang

Hi all,

I support the adoption of this draft.

Best
Qiao

On Thu, Apr 7, 2022 at 5:11 PM Luis M. Contreras 
mailto:contreras.i...@gmail.com>> wrote:
Hi all,

I support the adoption of this draft.

Best regards

Luis

El mié, 6 abr 2022 a las 18:30, 
mailto:roland.sch...@telekom.de>> escribió:
Hi,

I support the adoption of the draft as a good starting point for further work.

Best Regards

Roland

Von: mohamed.boucad...@orange.com 
mailto:mohamed.boucad...@orange.com>>
Gesendet: Montag, 4. April 2022 12:14
An: alto@ietf.org; 
draft-zhang-alto-oam-y...@ietf.org
Cc: alto-cha...@ietf.org
Betreff: RE: Call for adoption: draft-zhang-alto-oam-yang

Hi all,

This is a reminder that this call for adoption is still running.

Cheers,
Qin & Med

De : mohamed.boucad...@orange.com 
mailto:mohamed.boucad...@orange.com>>
Envoyé : mercredi 23 mars 2022 14:45
À : alto@ietf.org; 
draft-zhang-alto-oam-y...@ietf.org
Cc : alto-cha...@ietf.org
Objet : Call for adoption: draft-zhang-alto-oam-yang

Hi all,

As discussed during the IETF#113 meeting, this message initiates the call for 
adoption of draft-zhang-alto-oam-yang to meet the following ALTO WG milestone:

==
Dec 2022ALTO OAM Document/YANG Model
==

Please reply to this message indicating your support or objection to adopt the 
document.

The call will run till 08 April 2022.

Thank you
Qin & Med

_

Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc

pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce 
message par erreur, veuillez le signaler

a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
electroniques etant susceptibles d'alteration,

Orange decline toute responsabilite si ce message a ete altere, deforme ou 
falsifie. Merci.

This message and its attachments may contain confidential or privileged 
information that may be protected by law;

they should not be distributed, used or copied without authorisation.

If you have received this email in error, please notify the sender and delete 
this message and its attachments.

As emails may be altered, Orange is not liable for messages that have been 
modified, changed or falsified.

Thank you.
___
alto mailing list
alto@ietf.org
https://www.ietf.org/mailman/listinfo/alto

--
___
Luis M. Contreras
contreras.i...@gmail.com
luismiguel.contrerasmuri...@telefonica.com
Global CTIO unit / Telefonica
___
alto mailing list
alto@ietf.org
https://www.ietf.org/mailman/listinfo/alto

--
Qiao Xiang
Professor, Xiamen University
___
alto mailing list
alto@ietf.org
https://www.ietf.org/mailman/listinfo/alto

Re: [alto] Call for adoption: draft-zhang-alto-oam-yang

2022-04-07 Thread Qiao Xiang

Hi all,

I support the adoption of this draft.



Best
Qiao

On Thu, Apr 7, 2022 at 5:11 PM Luis M. Contreras 
wrote:

> Hi all,
>
> I support the adoption of this draft.
>
> Best regards
>
> Luis
>
>
> El mié, 6 abr 2022 a las 18:30,  escribió:
>
>> Hi,
>>
>>
>>
>> I support the adoption of the draft as a good starting point for further
>> work.
>>
>>
>>
>> Best Regards
>>
>>
>>
>> Roland
>>
>>
>>
>>
>>
>>
>>
>> *Von:* mohamed.boucad...@orange.com 
>> *Gesendet:* Montag, 4. April 2022 12:14
>> *An:* alto@ietf.org; draft-zhang-alto-oam-y...@ietf.org
>> *Cc:* alto-cha...@ietf.org
>> *Betreff:* RE: Call for adoption: draft-zhang-alto-oam-yang
>>
>>
>>
>> Hi all,
>>
>>
>>
>> This is a reminder that this call for adoption is still running.
>>
>>
>>
>> Cheers,
>>
>> Qin & Med
>>
>>
>>
>> *De :* mohamed.boucad...@orange.com 
>> *Envoyé :* mercredi 23 mars 2022 14:45
>> *À :* alto@ietf.org; draft-zhang-alto-oam-y...@ietf.org
>> *Cc :* alto-cha...@ietf.org
>> *Objet :* Call for adoption: draft-zhang-alto-oam-yang
>>
>>
>>
>> Hi all,
>>
>>
>>
>> As discussed during the IETF#113 meeting, this message initiates the call
>> for adoption of draft-zhang-alto-oam-yang to meet the following ALTO WG
>> milestone:
>>
>>
>>
>> ==
>>
>> Dec 2022ALTO OAM Document/YANG Model
>>
>> ==
>>
>>
>>
>> Please reply to this message indicating your support or objection to
>> adopt the document.
>>
>>
>>
>> The call will run till 08 April 2022.
>>
>>
>>
>> Thank you
>>
>> Qin & Med
>>
>>
>>
>> _
>>
>>
>>
>> Ce message et ses pieces jointes peuvent contenir des informations 
>> confidentielles ou privilegiees et ne doivent donc
>>
>> pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu 
>> ce message par erreur, veuillez le signaler
>>
>> a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
>> electroniques etant susceptibles d'alteration,
>>
>> Orange decline toute responsabilite si ce message a ete altere, deforme ou 
>> falsifie. Merci.
>>
>>
>>
>> This message and its attachments may contain confidential or privileged 
>> information that may be protected by law;
>>
>> they should not be distributed, used or copied without authorisation.
>>
>> If you have received this email in error, please notify the sender and 
>> delete this message and its attachments.
>>
>> As emails may be altered, Orange is not liable for messages that have been 
>> modified, changed or falsified.
>>
>> Thank you.
>>
>> ___
>> alto mailing list
>> alto@ietf.org
>> https://www.ietf.org/mailman/listinfo/alto
>>
>
>
> --
> ___
> Luis M. Contreras
> contreras.i...@gmail.com
> luismiguel.contrerasmuri...@telefonica.com
> Global CTIO unit / Telefonica
> ___
> alto mailing list
> alto@ietf.org
> https://www.ietf.org/mailman/listinfo/alto
>


-- 
Qiao Xiang
Professor, Xiamen University
___
alto mailing list
alto@ietf.org
https://www.ietf.org/mailman/listinfo/alto

Re: [alto] Call for adoption: draft-zhang-alto-oam-yang

2022-04-07 Thread Luis M. Contreras

Hi all,

I support the adoption of this draft.

Best regards

Luis


El mié, 6 abr 2022 a las 18:30,  escribió:

> Hi,
>
>
>
> I support the adoption of the draft as a good starting point for further
> work.
>
>
>
> Best Regards
>
>
>
> Roland
>
>
>
>
>
>
>
> *Von:* mohamed.boucad...@orange.com 
> *Gesendet:* Montag, 4. April 2022 12:14
> *An:* alto@ietf.org; draft-zhang-alto-oam-y...@ietf.org
> *Cc:* alto-cha...@ietf.org
> *Betreff:* RE: Call for adoption: draft-zhang-alto-oam-yang
>
>
>
> Hi all,
>
>
>
> This is a reminder that this call for adoption is still running.
>
>
>
> Cheers,
>
> Qin & Med
>
>
>
> *De :* mohamed.boucad...@orange.com 
> *Envoyé :* mercredi 23 mars 2022 14:45
> *À :* alto@ietf.org; draft-zhang-alto-oam-y...@ietf.org
> *Cc :* alto-cha...@ietf.org
> *Objet :* Call for adoption: draft-zhang-alto-oam-yang
>
>
>
> Hi all,
>
>
>
> As discussed during the IETF#113 meeting, this message initiates the call
> for adoption of draft-zhang-alto-oam-yang to meet the following ALTO WG
> milestone:
>
>
>
> ==
>
> Dec 2022ALTO OAM Document/YANG Model
>
> ==
>
>
>
> Please reply to this message indicating your support or objection to adopt
> the document.
>
>
>
> The call will run till 08 April 2022.
>
>
>
> Thank you
>
> Qin & Med
>
>
>
> _
>
>
>
> Ce message et ses pieces jointes peuvent contenir des informations 
> confidentielles ou privilegiees et ne doivent donc
>
> pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu 
> ce message par erreur, veuillez le signaler
>
> a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
> electroniques etant susceptibles d'alteration,
>
> Orange decline toute responsabilite si ce message a ete altere, deforme ou 
> falsifie. Merci.
>
>
>
> This message and its attachments may contain confidential or privileged 
> information that may be protected by law;
>
> they should not be distributed, used or copied without authorisation.
>
> If you have received this email in error, please notify the sender and delete 
> this message and its attachments.
>
> As emails may be altered, Orange is not liable for messages that have been 
> modified, changed or falsified.
>
> Thank you.
>
> ___
> alto mailing list
> alto@ietf.org
> https://www.ietf.org/mailman/listinfo/alto
>


-- 
___
Luis M. Contreras
contreras.i...@gmail.com
luismiguel.contrerasmuri...@telefonica.com
Global CTIO unit / Telefonica
___
alto mailing list
alto@ietf.org
https://www.ietf.org/mailman/listinfo/alto

Re: [alto] WGLC for draft-ietf-alto-cost-mode-00

Re: [alto] [Editorial Errata Reported] RFC7285 (6876)

Re: [alto] Call for adoption: draft-zhang-alto-oam-yang

Re: [alto] [Editorial Errata Reported] RFC7285 (6876)

Re: [alto] Call for adoption: draft-zhang-alto-oam-yang

Re: [alto] Call for adoption: draft-zhang-alto-oam-yang

Re: [alto] Call for adoption: draft-zhang-alto-oam-yang

7 matches

Site Navigation

Mail list logo

Footer information