[spring] SPRING Session Agenda for IETF119

[Pengshuping (Peng Shuping)]

Dear all,

The SPRING Agenda is posted.
https://datatracker.ietf.org/meeting/119/materials/agenda-119-spring-01

If any amendment is needed, please get in touch.

To all the presenters, please directly upload your slides 
https://datatracker.ietf.org/meeting/119/session/31932/slides or send them to 
the spring-cha...@ietf.org before Monday evening 
in the IETF week. Please be aware that the number of slides should be 
compatible with the number of minutes on the agenda (e.g. max 6 slides with 
content for a 10 minutes slot).

Please get more attention and discussions in the mailing list before the 
meeting if you have not done so, which could facilitate the discussions during 
the meeting.

Thank you!

Best regards,
Shuping
___
spring mailing list
spring@ietf.org
https://www.ietf.org/mailman/listinfo/spring

[spring] IETF 119 Slot Requests Collection

[Pengshuping (Peng Shuping)]

Hi all,

The IETF 119 Preliminary agenda is out, and the SPRING WG session is arranged 
on 2024-3-20, Wednesday.

https://datatracker.ietf.org/meeting/119/agenda/

For building the IETF 119 SPRING agenda, we will continue to using the Google 
Form to collect presentation slot requests. Please submit your requests in the 
following form before 2024-3-4 EOD.

https://docs.google.com/forms/d/e/1FAIpQLSfQAIYubXfPDQBN9b4I9vfjr7qrG8zVWBbD4zSMAdmJ8YpJAQ/viewform

If there is any issue for you to access this Form, please send your request 
with the following information directly to 
spring-cha...@ietf.org and my email 
pengshup...@huawei.com.
Title*
URL*
Minutes*
Presenters & Email*
Note/info
Have you also asked for a slot request in a different WG? If so, which WG(s)*

Thank you!

Best regards,
Shuping

___
spring mailing list
spring@ietf.org
https://www.ietf.org/mailman/listinfo/spring

[spring] The SPRING WG meeting minutes @IETF118

[Pengshuping (Peng Shuping)]

Hi all,

The SPRING Meeting Minutes has been uploaded. Please let us know if you want to 
make any changes.
https://datatracker.ietf.org/doc/minutes-118-spring-202311090830/

Cheers!

Best Regards,
Shuping
___
spring mailing list
spring@ietf.org
https://www.ietf.org/mailman/listinfo/spring

Re: [spring] SPRING Session Agenda for 118

[Pengshuping (Peng Shuping)]

Hi all,

A kind reminder to all the presenters.

Please directly upload your slides 
https://datatracker.ietf.org/meeting/118/session/31599/slides or send them to 
the spring-cha...@ietf.org<mailto:spring-cha...@ietf.org> before Monday evening 
in the IETF week. Please be aware that the number of slides should be 
compatible with the number of minutes on the agenda (e.g. max 6 slides with 
content for a 10 minutes slot).

Best Regards,
Shuping


From: spring [mailto:spring-boun...@ietf.org] On Behalf Of Pengshuping (Peng 
Shuping)
Sent: Wednesday, October 25, 2023 11:44 AM
To: SPRING WG List 
Cc: spring-cha...@ietf.org
Subject: [spring] SPRING Session Agenda for 118

Dear all,

The SPRING Agenda is posted.
https://datatracker.ietf.org/doc/agenda-118-spring/00/

If any amendment is needed, please get in touch.

To all the presenters, please directly upload your slides 
https://datatracker.ietf.org/meeting/118/session/31599/slides or send them to 
the spring-cha...@ietf.org<mailto:spring-cha...@ietf.org> before Monday evening 
in the IETF week. Please be aware that the number of slides should be 
compatible with the number of minutes on the agenda (e.g. max 6 slides with 
content for a 10 minutes slot).

Please get more attention and discussions in the mailing list before the 
meeting if you have not done so, which could facilitate the discussions during 
the meeting.

Thank you!

Best regards,
Shuping
___
spring mailing list
spring@ietf.org
https://www.ietf.org/mailman/listinfo/spring

[spring] SPRING Session Agenda for 118

[Pengshuping (Peng Shuping)]

Dear all,

The SPRING Agenda is posted.
https://datatracker.ietf.org/doc/agenda-118-spring/00/

If any amendment is needed, please get in touch.

To all the presenters, please directly upload your slides 
https://datatracker.ietf.org/meeting/118/session/31599/slides or send them to 
the spring-cha...@ietf.org before Monday evening 
in the IETF week. Please be aware that the number of slides should be 
compatible with the number of minutes on the agenda (e.g. max 6 slides with 
content for a 10 minutes slot).

Please get more attention and discussions in the mailing list before the 
meeting if you have not done so, which could facilitate the discussions during 
the meeting.

Thank you!

Best regards,
Shuping
___
spring mailing list
spring@ietf.org
https://www.ietf.org/mailman/listinfo/spring

[spring] IETF 118 Slot Requests Collection

[Pengshuping (Peng Shuping)]

Hi all,

The IETF 118 Preliminary agenda is out, and the SPRING WG session is arranged 
on 2023-11-9, Thursday.

For building the IETF 118 SPRING agenda, we will continue to using the Google 
Form to collect presentation slot requests. Please submit your requests in the 
following form before 2023-10-23 EOD.

https://docs.google.com/forms/d/e/1FAIpQLScfU8TskdMRHl8jrOgx4ZZafgiy6IoFXXiWpw7npKSBtRu2nA/viewform

If there is any issue for you to access this Form, please send your request 
with the following information directly to spring-cha...@ietf.org and my email 
pengshup...@huawei.com.
Title*
URL*
Minutes*
Presenters & Email*
Note/info
Have you also asked for a slot request in a different WG? If so, which WG(s)*

Thank you!

Best regards,
Shuping
___
spring mailing list
spring@ietf.org
https://www.ietf.org/mailman/listinfo/spring

[spring] The SPRING WG meeting minutes @ IETF117

[Pengshuping (Peng Shuping)]

Hi all,

The SPRING Meeting Minutes has been uploaded. Please let us know if you want to 
make any changes.
https://datatracker.ietf.org/meeting/117/materials/minutes-117-spring-00.md

Cheers!

Best Regards,
Shuping
___
spring mailing list
spring@ietf.org
https://www.ietf.org/mailman/listinfo/spring

Re: [spring] SPRING Session Agenda for 117

[Pengshuping (Peng Shuping)]

Uploaded. Please check.
https://datatracker.ietf.org/meeting/117/materials/slides-117-spring-problem-statement-for-inter-domain-intent-aware-routing-using-color-00.pdf

Shuping


From: Shraddha Hegde [mailto:shrad...@juniper.net]
Sent: Tuesday, July 25, 2023 12:43 PM
To: Pengshuping (Peng Shuping) ; 
SPRING WG List 
Cc: spring-cha...@ietf.org
Subject: RE: SPRING Session Agenda for 117

Pls find slides attached.

Rgds
Shraddha




Juniper Business Use Only
From: spring mailto:spring-boun...@ietf.org>> On 
Behalf Of Pengshuping (Peng Shuping)
Sent: Friday, July 21, 2023 7:56 AM
To: SPRING WG List mailto:spring@ietf.org>>
Cc: spring-cha...@ietf.org<mailto:spring-cha...@ietf.org>
Subject: Re: [spring] SPRING Session Agenda for 117

[External Email. Be cautious of content]

Dear all,

A kind reminder for your slides. Thank you!

Best Regards,
Shuping


From: spring [mailto:spring-boun...@ietf.org] On Behalf Of Pengshuping (Peng 
Shuping)
Sent: Wednesday, July 12, 2023 11:32 AM
To: SPRING WG List mailto:spring@ietf.org>>
Cc: spring-cha...@ietf.org<mailto:spring-cha...@ietf.org>
Subject: [spring] SPRING Session Agenda for 117

Dear all,

The SPRING Agenda is posted. The associated drafts are also linked.
https://datatracker.ietf.org/meeting/117/materials/agenda-117-spring-00<https://urldefense.com/v3/__https:/datatracker.ietf.org/meeting/117/materials/agenda-117-spring-00__;!!NEt6yMaO-gk!AHTsR7nFZ15Y8S0MHjdeAJ6EkBYA2FkjUqiAfonJcmRkWvcCENz4n86MB-k59N-XnZXZ3ELUuUaiPeHCahj2TPKZf9yovPH7$>

If any amendment is needed, please get in touch.

To all the presenters, please directly upload your slides 
https://datatracker.ietf.org/meeting/117/session/30537/slides<https://urldefense.com/v3/__https:/datatracker.ietf.org/meeting/117/session/30537/slides__;!!NEt6yMaO-gk!AHTsR7nFZ15Y8S0MHjdeAJ6EkBYA2FkjUqiAfonJcmRkWvcCENz4n86MB-k59N-XnZXZ3ELUuUaiPeHCahj2TPKZf9p4A7Yg$>
 or send them to the spring-cha...@ietf.org<mailto:spring-cha...@ietf.org> 
before Monday evening. Please be aware that the number of slides should be 
compatible with the number of minutes on the agenda (e.g. max 6 slides with 
content for a 10 minutes slot).

Thank you!

Best regards,
Shuping
___
spring mailing list
spring@ietf.org
https://www.ietf.org/mailman/listinfo/spring

Re: [spring] SPRING Session Agenda for 117

[Pengshuping (Peng Shuping)]

Dear all,

A kind reminder for your slides. Thank you!

Best Regards,
Shuping


From: spring [mailto:spring-boun...@ietf.org] On Behalf Of Pengshuping (Peng 
Shuping)
Sent: Wednesday, July 12, 2023 11:32 AM
To: SPRING WG List 
Cc: spring-cha...@ietf.org
Subject: [spring] SPRING Session Agenda for 117

Dear all,

The SPRING Agenda is posted. The associated drafts are also linked.
https://datatracker.ietf.org/meeting/117/materials/agenda-117-spring-00

If any amendment is needed, please get in touch.

To all the presenters, please directly upload your slides 
https://datatracker.ietf.org/meeting/117/session/30537/slides or send them to 
the spring-cha...@ietf.org<mailto:spring-cha...@ietf.org> before Monday 
evening. Please be aware that the number of slides should be compatible with 
the number of minutes on the agenda (e.g. max 6 slides with content for a 10 
minutes slot).

Thank you!

Best regards,
Shuping
___
spring mailing list
spring@ietf.org
https://www.ietf.org/mailman/listinfo/spring

[spring] SPRING Session Agenda for 117

[Pengshuping (Peng Shuping)]

Dear all,

The SPRING Agenda is posted. The associated drafts are also linked.
https://datatracker.ietf.org/meeting/117/materials/agenda-117-spring-00

If any amendment is needed, please get in touch.

To all the presenters, please directly upload your slides 
https://datatracker.ietf.org/meeting/117/session/30537/slides or send them to 
the spring-cha...@ietf.org before Monday 
evening. Please be aware that the number of slides should be compatible with 
the number of minutes on the agenda (e.g. max 6 slides with content for a 10 
minutes slot).

Thank you!

Best regards,
Shuping
___
spring mailing list
spring@ietf.org
https://www.ietf.org/mailman/listinfo/spring

Re: [spring] IETF 117 Slot Requests Collection

[Pengshuping (Peng Shuping)]

Hi all,

A kind reminder of your slot request.
https://docs.google.com/forms/d/e/1FAIpQLSfLF45EJmXgGSERiEp7spwpMeRV3xdJGj9GS5FEs5C-rXP5OA/viewform

Best Regards,
Shuping


From: spring [mailto:spring-boun...@ietf.org] On Behalf Of Pengshuping (Peng 
Shuping)
Sent: Wednesday, June 28, 2023 10:46 AM
To: SPRING WG List 
Cc: spring-cha...@ietf.org
Subject: [spring] IETF 117 Slot Requests Collection


Dear all,



For building the IETF 117 SPRING agenda, we will continue to using the Google 
Form to collect presentation slot requests. Please submit your requests in the 
following form up to 2023-07-10 EOD.



https://docs.google.com/forms/d/e/1FAIpQLSfLF45EJmXgGSERiEp7spwpMeRV3xdJGj9GS5FEs5C-rXP5OA/viewform



If there is any issue for you to access this Form, please send your request 
with the following information directly to 
spring-cha...@ietf.org<mailto:spring-cha...@ietf.org> and my email 
pengshup...@huawei.com<mailto:pengshup...@huawei.com>.
Title*
URL*
Minutes*
Presenters & Email*
Note/info
Did you asked for a slot request in a different WG? If so which WG(s)*



Thank you!



Best regards,

Shuping


___
spring mailing list
spring@ietf.org
https://www.ietf.org/mailman/listinfo/spring

[spring] IETF 117 Slot Requests Collection

[Pengshuping (Peng Shuping)]

Dear all,



For building the IETF 117 SPRING agenda, we will continue to using the Google 
Form to collect presentation slot requests. Please submit your requests in the 
following form up to 2023-07-10 EOD.



https://docs.google.com/forms/d/e/1FAIpQLSfLF45EJmXgGSERiEp7spwpMeRV3xdJGj9GS5FEs5C-rXP5OA/viewform



If there is any issue for you to access this Form, please send your request 
with the following information directly to 
spring-cha...@ietf.org and my email 
pengshup...@huawei.com.
Title*
URL*
Minutes*
Presenters & Email*
Note/info
Did you asked for a slot request in a different WG? If so which WG(s)*



Thank you!



Best regards,

Shuping


___
spring mailing list
spring@ietf.org
https://www.ietf.org/mailman/listinfo/spring

[spring] The SPRING WG meeting minutes @ IETF116

[Pengshuping (Peng Shuping)]

Hi all,

Please find the meeting minutes for this IETF116.
https://datatracker.ietf.org/doc/minutes-116-spring/

Many thanks to Dhruv for taking the minutes.

Best Regards,
Shuping
___
spring mailing list
spring@ietf.org
https://www.ietf.org/mailman/listinfo/spring

[spring] SPRING Session Agenda for 116

[Pengshuping (Peng Shuping)]

Dear all,

The SPRING Agenda is posted.
https://datatracker.ietf.org/meeting/116/materials/agenda-116-spring-00

Please also see the associated drafts for our session, which are listed on this 
page:
https://datatracker.ietf.org/meeting/116/session/spring

If there are comments or amendments needed, please get in touch.

To all the presenters, please directly upload your slides 
https://datatracker.ietf.org/meeting/116/session/spring or send them to the 
spring-cha...@ietf.org before Monday evening. 
Please be aware that the number of slides should be compatible with the number 
of minutes on the agenda (e.g. max 3 slides with content for a 5 minutes slot).

Thank you!

Best regards,
Shuping
___
spring mailing list
spring@ietf.org
https://www.ietf.org/mailman/listinfo/spring

[spring] SPRING Session Agenda for 116

[Pengshuping (Peng Shuping)]

Dear all,

The SPRING Agenda is posted.
https://datatracker.ietf.org/meeting/116/materials/agenda-116-spring-00

Please also see the associated drafts for our session, which are listed on this 
page:
https://datatracker.ietf.org/meeting/116/session/spring

If there are comments or amendments needed, please get in touch.

To all the presenters, please directly upload your slides 
https://datatracker.ietf.org/meeting/116/session/spring or send them to the 
spring-cha...@ietf.org before Monday evening. 
Please be aware that the number of slides should be compatible with the number 
of minutes on the agenda (e.g. max 3 slides with content for a 5 minutes slot).

Thank you!

Best regards,
Shuping

___
spring mailing list
spring@ietf.org
https://www.ietf.org/mailman/listinfo/spring

[spring] IETF 116 Slot Requests Collection

[Pengshuping (Peng Shuping)]

Dear all,



For building the IETF 116 SPRING agenda, we will continue to using the Google 
Form to collect presentation slot requests. Please submit your requests in the 
following form up to 2023-03-13 EOD.



https://docs.google.com/forms/d/e/1FAIpQLSdTc4VAGJuLL4n8l9ulq58SqLmf85gE_flvQ18nAhCgYiV-og/viewform



If there is any issue for you to access this Form, please send your request 
with the following information directly to 
spring-cha...@ietf.org and my email 
pengshup...@huawei.com.
Title*
URL*
Minutes*
Presenters & Email*
Note/info
Did you asked for a slot request in a different WG? If so which WG(s)*



Thank you!



Best regards,

Shuping

___
spring mailing list
spring@ietf.org
https://www.ietf.org/mailman/listinfo/spring

Re: [spring] [IPv6] WG Adoption call for Segment Routing Header encapsulation for Alternate Marking Method

[Pengshuping (Peng Shuping)]

Hi Joel, all, 

I support the adoption of this work since this is important for deploying 
alternative marking in SRv6 networks. 

Regarding the choices of SRH TLV and DOH, since both are related with the usage 
of the IPv6 extension headers, I wonder whether we could have a separate draft, 
in 6man or v6ops together with spring, on analyzing these two choices in 
various aspects, maybe covering considerations on usage scenarios, 
implementations, cost, and providing guidance on deployment preference. 

Best Regards, 
Shuping 



-Original Message-
From: ipv6 [mailto:ipv6-boun...@ietf.org] On Behalf Of Joel Halpern
Sent: Thursday, February 2, 2023 8:44 AM
To: SPRING WG List 
Cc: 6man 
Subject: [IPv6] WG Adoption call for Segment Routing Header encapsulation for 
Alternate Marking Method

This call is for the draft at: 
https://datatracker.ietf.org/doc/draft-fz-spring-srv6-alt-mark

This email starts the WG adoption call for the subject draft (as requested by 
the authors, with apologies from the WG chairs for how long it has taken to 
kick this out.)  This call will run through the end of the day on Feb 16.  
Pleaes read the whole email as there are a few points, and it is not that long.

Please comment on whether you think this topic is something you think the 
spring WG should work, whether you think this draft is a good starting point 
for such work, any issues or concerns you have, and whether you would be 
willing to help be contributing and / or reviewing the work if the WG does 
choose to work on it.

6man is copied for their information, as this is different from but related to 
an extension header proposal in front of 6man.

Authors and named contributors, please confirm to the list that all known, 
relevant, IPR has been disclosed.  If it has note, please remedy this gap.

The spring chairs have noted one aspect of this draft that caught our eye, and 
we would appreciate WG members who comment on the adoption to consider, and if 
possible opine, on this.  As we read this draft, as distinct from the related 
6man extension header work, this causes the recorded altmarks to only be 
updated at routers identified in the SRH segment list.  (We presume this would 
include all identified points in a compressed container.) We could not tell 
from the document what the value was for this as distinct from getting the 
measurements at all routers.  Do WG members understand and agree that it does 
have value?

As a lesser point, we consider that one quote in the draft is misleading and 
will likely need to be reworded in the near future.  The draft say "SRH TLV can 
also be used to encode the AltMark Data Fields for SRv6 and to monitor every 
node along the SR path."  It is unclear if these was intended to mean all 
routers (most of which would not see this TLV) or if it was intended to refer 
to only those routers identified in the SRH, in which case we presume it will 
be reworded.

Thank you,

Joel


IETF IPv6 working group mailing list
i...@ietf.org
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6

___
spring mailing list
spring@ietf.org
https://www.ietf.org/mailman/listinfo/spring

[spring] IETF 115 SPRING Meeting Minutes to be reviewed

[Pengshuping (Peng Shuping)]

Hi all,

The SPRING Meeting Minutes has been uploaded. Please let us know if you want to 
make any changes.
https://datatracker.ietf.org/doc/minutes-115-spring/

The SPRING Wiki is also updated accordingly, in the section of "Documents 
requested by authors for WG adoption".
https://wiki.ietf.org/group/spring

Thank you!

Best Regards,
Shuping
___
spring mailing list
spring@ietf.org
https://www.ietf.org/mailman/listinfo/spring

Re: [spring] SPRING Session Agenda for 115

[Pengshuping (Peng Shuping)]

Hi all,

A kind reminder to all the presenters, please upload your slides in time.
https://datatracker.ietf.org/meeting/115/session/spring

Best Regards,
Shuping


From: spring [mailto:spring-boun...@ietf.org] On Behalf Of Pengshuping (Peng 
Shuping)
Sent: Thursday, October 27, 2022 10:46 AM
To: spring@ietf.org
Cc: spring-cha...@ietf.org
Subject: [spring] SPRING Session Agenda for 115

Dear all,

The SPRING Agenda is posted.
https://datatracker.ietf.org/meeting/115/materials/agenda-115-spring-00.md

Please also see the associated drafts for our session, which are listed on this 
page:
https://datatracker.ietf.org/meeting/115/session/spring

If there are comments or amendments needed, please get in touch.

To all the presenters, please directly upload your slides 
https://datatracker.ietf.org/meeting/115/session/spring or send them to the 
spring-cha...@ietf.org<mailto:spring-cha...@ietf.org> before Monday. Thank you!

Best regards,
Shuping
___
spring mailing list
spring@ietf.org
https://www.ietf.org/mailman/listinfo/spring

[spring] SPRING Session Agenda for 115

[Pengshuping (Peng Shuping)]

Dear all,

The SPRING Agenda is posted.
https://datatracker.ietf.org/meeting/115/materials/agenda-115-spring-00.md

Please also see the associated drafts for our session, which are listed on this 
page:
https://datatracker.ietf.org/meeting/115/session/spring

If there are comments or amendments needed, please get in touch.

To all the presenters, please directly upload your slides 
https://datatracker.ietf.org/meeting/115/session/spring or send them to the 
spring-cha...@ietf.org before Monday. Thank you!

Best regards,
Shuping
___
spring mailing list
spring@ietf.org
https://www.ietf.org/mailman/listinfo/spring

[spring] IETF 115 Slot Requests Collection

[Pengshuping (Peng Shuping)]

Dear all,



For building the IETF 115 SPRING agenda, we will continue to using the Google 
Form to collect presentation slot requests. Please submit your requests in the 
following form up to 2022-07-24 EOD.



https://docs.google.com/forms/d/e/1FAIpQLSdkvXL-RUUCvXwyoTArAAs-Z2mOJ-hevfYHvVnx4M3iJ9hcyg/viewform



If there is any issue for you to access this Form, please send your request 
with the following information directly to 
spring-cha...@ietf.org and my email 
pengshup...@huawei.com.
Title*
URL*
Minutes*
Presenters & Email*
Note/info
Did you asked for a slot request in a different WG? If so which WG(s)*





Thank you!



Best regards,

Shuping

___
spring mailing list
spring@ietf.org
https://www.ietf.org/mailman/listinfo/spring

[spring] IETF 114 SPRING Meeting Minutes to be reviewed

[Pengshuping (Peng Shuping)]

Hi all,

The Meeting Minutes has been uploaded. Please let us know if you want to make 
any changes.

https://datatracker.ietf.org/meeting/114/materials/minutes-114-spring-202207271000-00.md

Thank you!

Best Regards,
Shuping
___
spring mailing list
spring@ietf.org
https://www.ietf.org/mailman/listinfo/spring

[spring] SPRING@IETF114 Agenda is posted

[Pengshuping (Peng Shuping)]

Dear all,

The SPRING@IETF114 Agenda is posted.
https://datatracker.ietf.org/meeting/114/materials/agenda-114-spring-00.md

You can either directly upload your slides using this link 
https://datatracker.ietf.org/meeting/114/session/29622/slides or send it to the 
spring-cha...@ietf.org before Monday 25 July. 
Thank you!

Information about the SPRING WG @IETF 114:

Wednesday 27 July 2022

Room: Liberty D

10:00-12:00 UTC -4

Log into the IETF datatracker to access:

*MeetEcho

*Notes

*Jabber

Best regards,
Shuping


___
spring mailing list
spring@ietf.org
https://www.ietf.org/mailman/listinfo/spring

Re: [spring] IETF 114 Slot Requests Collection

[Pengshuping (Peng Shuping)]

Dear all,

The SPRING session has been scheduled on 10:00-12:00 Wednesday, July 27, 2022 
(Philadelphia local time, UTC -4).

Please submit your presentation request via this link below.
https://docs.google.com/forms/d/e/1FAIpQLSeGQdV6VAllzgtcVaxTx3KCx3SEkk-ZV6Yue4MjDjC8SOdJmg/viewform

If there is any issue for you to access this Form, please send your request 
directly to spring-cha...@ietf.org<mailto:spring-cha...@ietf.org> and my email 
pengshup...@huawei.com<mailto:pengshup...@huawei.com>.

Best Regards,
Shuping


From: Pengshuping (Peng Shuping)
Sent: Saturday, June 25, 2022 3:02 PM
To: Pengshuping (Peng Shuping) 
Cc: spring-cha...@ietf.org; spring@ietf.org
Subject: IETF 114 Slot Requests Collection

Dear all,


For building the IETF 114 SPRING agenda, we will continue to using the Google 
Form to collect presentation slot requests. Please submit your requests in the 
following form up to 2022-07-11 EOD.

https://docs.google.com/forms/d/e/1FAIpQLSeGQdV6VAllzgtcVaxTx3KCx3SEkk-ZV6Yue4MjDjC8SOdJmg/viewform

If there is any issue for you to access this Form, please send your request 
directly to spring-cha...@ietf.org<mailto:spring-cha...@ietf.org> and my email 
pengshup...@huawei.com<mailto:pengshup...@huawei.com>.

Thank you!

Best regards,
Shuping




___
spring mailing list
spring@ietf.org
https://www.ietf.org/mailman/listinfo/spring

[spring] SPRING Meeting Minutes to be reviewed

[Pengshuping (Peng Shuping)]

Hi all,

The Meeting Minutes has been uploaded. Please let us know if you want to make 
any changes.

https://datatracker.ietf.org/doc/minutes-113-spring/

Thank you!

Best Regards,
Shuping
___
spring mailing list
spring@ietf.org
https://www.ietf.org/mailman/listinfo/spring

[spring] SPRING agenda is posted @IETF113

[Pengshuping (Peng Shuping)]

Dear all,

The agenda has been posted. Please let us know if you want to make any changes.

https://datatracker.ietf.org/meeting/113/materials/agenda-113-spring-00.txt

Please upload your slides directly to 
https://datatracker.ietf.org/meeting/113/session/spring  or send them to 
spring-cha...@ietf.org.

Please upload your slides 24H or 48H before the section.

Thank you!

Best regards,
Shuping
___
spring mailing list
spring@ietf.org
https://www.ietf.org/mailman/listinfo/spring

Re: [spring] IETF 113 Slot Requests Collection

[Pengshuping (Peng Shuping)]

Dear all,

The IETF 113 preliminary agenda is out. The SPRING session has been scheduled 
in the following slot.

Vienna local time, UTC +1
Friday, March 25, 2022
12:30-14:30
Friday Afternoon session I

Best Regards,
Shuping


From: spring [mailto:spring-boun...@ietf.org] On Behalf Of Pengshuping (Peng 
Shuping)
Sent: Thursday, February 17, 2022 10:09 AM
To: spring@ietf.org
Cc: spring-cha...@ietf.org
Subject: [spring] IETF 113 Slot Requests Collection

Dear all,


For building the IETF 113 SPRING agenda, we will continue to using the Google 
Form to collect presentation slot requests. Please submit your requests in the 
following form up to 2022-03-04 EOD.

https://docs.google.com/forms/d/e/1FAIpQLSfxY7TXAl53aMSpclmHjH-90ZTLsWoaZz7_BvHvlYcewJeaFw/viewform

If there is any issue for you to access this Form, please send your request 
directly to spring-cha...@ietf.org<mailto:spring-cha...@ietf.org>.

Thank you!

Best regards,
Shuping

___
spring mailing list
spring@ietf.org
https://www.ietf.org/mailman/listinfo/spring

[spring] IETF 113 Slot Requests Collection

[Pengshuping (Peng Shuping)]

Dear all,


For building the IETF 113 SPRING agenda, we will continue to using the Google 
Form to collect presentation slot requests. Please submit your requests in the 
following form up to 2022-03-04 EOD.

https://docs.google.com/forms/d/e/1FAIpQLSfxY7TXAl53aMSpclmHjH-90ZTLsWoaZz7_BvHvlYcewJeaFw/viewform

If there is any issue for you to access this Form, please send your request 
directly to spring-cha...@ietf.org.

Thank you!

Best regards,
Shuping

___
spring mailing list
spring@ietf.org
https://www.ietf.org/mailman/listinfo/spring

[spring] The SPRING session minutes

[Pengshuping (Peng Shuping)]

Hi all,



The meeting minutes from the SPRING session have been uploaded:

https://datatracker.ietf.org/meeting/112/materials/minutes-112-spring-00.txt



Please check the minutes and let the Chairs know if any changes are needed.



Thank you!



Best regards,

Shuping

___
spring mailing list
spring@ietf.org
https://www.ietf.org/mailman/listinfo/spring

[spring] SPRING Agenda is posted

[Pengshuping (Peng Shuping)]

Dear all,

The SPRING Agenda is posted.
https://datatracker.ietf.org/doc/agenda-112-spring/

Please directly upload your slides 
https://datatracker.ietf.org/meeting/112/session/spring or send it to the 
spring-cha...@ietf.org<mailto:spring-cha...@ietf.org> before Monday since we 
are the first session. Thank you!

Best regards,
Shuping


From: Pengshuping (Peng Shuping)
Sent: Monday, October 18, 2021 11:44 AM
To: spring@ietf.org
Cc: spring-cha...@ietf.org
Subject: IETF 112 Slot Requests

Dear all,


The IETF 112 Final Agenda is now available 
https://datatracker.ietf.org/meeting/112/agenda.html

and the SPRING session is arranged on Monday as below.



Monday, November 8, 2021

12:00-14:00

Monday Session I

Room 5   rtgspring Source Packet Routing in Networking

We will continue to using the Google Form to collect presentation slot requests 
in the SPRING WG for this IETF112. Please fill in your request in the following 
Form.

https://docs.google.com/forms/d/1MkWm0817Qibt1JaOQjaMEmzbWOEJZAA1XxeKvnL2NQQ/edit

If there is any issue for you to access this Form, please send your request 
directly to spring-cha...@ietf.org<mailto:spring-cha...@ietf.org>.

Thank you!

Best regards,
Shuping
___
spring mailing list
spring@ietf.org
https://www.ietf.org/mailman/listinfo/spring

Re: [spring] IETF 112 Slot Requests

[Pengshuping (Peng Shuping)]

Hi all,

Please find the slot request link below.

https://docs.google.com/forms/d/1MkWm0817Qibt1JaOQjaMEmzbWOEJZAA1XxeKvnL2NQQ/edit

Or you can directly send to 
spring-cha...@ietf.org<mailto:spring-cha...@ietf.org>.

Best regards,
Shuping

From: spring [mailto:spring-boun...@ietf.org] On Behalf Of Pengshuping (Peng 
Shuping)
Sent: Monday, October 18, 2021 11:44 AM
To: spring@ietf.org
Cc: spring-cha...@ietf.org
Subject: [spring] IETF 112 Slot Requests

Dear all,


The IETF 112 Final Agenda is now available 
https://datatracker.ietf.org/meeting/112/agenda.html

and the SPRING session is arranged on Monday as below.



Monday, November 8, 2021

12:00-14:00

Monday Session I

Room 5   rtgspring Source Packet Routing in Networking

We will continue to using the Google Form to collect presentation slot requests 
in the SPRING WG for this IETF112. Please fill in your request in the following 
Form.

https://docs.google.com/forms/d/1MkWm0817Qibt1JaOQjaMEmzbWOEJZAA1XxeKvnL2NQQ/edit

If there is any issue for you to access this Form, please send your request 
directly to spring-cha...@ietf.org<mailto:spring-cha...@ietf.org>.

Thank you!

Best regards,
Shuping
___
spring mailing list
spring@ietf.org
https://www.ietf.org/mailman/listinfo/spring

[spring] IETF 112 Slot Requests

[Pengshuping (Peng Shuping)]

Dear all,


The IETF 112 Final Agenda is now available 
https://datatracker.ietf.org/meeting/112/agenda.html

and the SPRING session is arranged on Monday as below.



Monday, November 8, 2021

12:00-14:00

Monday Session I

Room 5   rtgspring Source Packet Routing in Networking

We will continue to using the Google Form to collect presentation slot requests 
in the SPRING WG for this IETF112. Please fill in your request in the following 
Form.

https://docs.google.com/forms/d/1MkWm0817Qibt1JaOQjaMEmzbWOEJZAA1XxeKvnL2NQQ/edit

If there is any issue for you to access this Form, please send your request 
directly to spring-cha...@ietf.org.

Thank you!

Best regards,
Shuping
___
spring mailing list
spring@ietf.org
https://www.ietf.org/mailman/listinfo/spring

[spring] Meeting minutes for the SPRING session on Monday

[Pengshuping (Peng Shuping)]

Dear all,

The meeting minutes for the SPRING session has been uploaded for your review.

https://datatracker.ietf.org/meeting/111/materials/minutes-111-spring-01.txt

Please let me know if there is any change that needs to make.

Thank you!

Best regards,
Shuping
___
spring mailing list
spring@ietf.org
https://www.ietf.org/mailman/listinfo/spring

Re: [spring] IETF 111 SPRING agenda is posted

[Pengshuping (Peng Shuping)]

Dear all,

A kind reminder for the presenters to post your slides.

Please upload your slides directly to 
https://datatracker.ietf.org/meeting/111/session/28894/slides or send them to 
spring-cha...@ietf.org.

Since we are the first session on Monday. So please upload your slides 24H or 
48H before the section.

Thank you!

Best regards,
Shuping



From: spring [mailto:spring-boun...@ietf.org] On Behalf Of Pengshuping (Peng 
Shuping)
Sent: Wednesday, July 14, 2021 5:35 PM
To: spring@ietf.org
Cc: spring-cha...@ietf.org
Subject: [spring] IETF 111 SPRING agenda is posted


Dear all,



The agenda has been posted. Please let us know if there are any changes 
required.



https://datatracker.ietf.org/doc/agenda-111-spring/



Please upload your slides directly to 
https://datatracker.ietf.org/meeting/111/session/28894/slides or send them to 
spring-cha...@ietf.org<mailto:spring-cha...@ietf.org>.



Since we are the first session on Monday. So please upload your slides 24H or 
48H before the section.



Thank you!



Best regards,

Shuping

___
spring mailing list
spring@ietf.org
https://www.ietf.org/mailman/listinfo/spring

[spring] IETF 111 SPRING agenda is posted

[Pengshuping (Peng Shuping)]

Dear all,



The agenda has been posted. Please let us know if there are any changes 
required.



https://datatracker.ietf.org/doc/agenda-111-spring/



Please upload your slides directly to 
https://datatracker.ietf.org/meeting/111/session/28894/slides or send them to 
spring-cha...@ietf.org.



Since we are the first session on Monday. So please upload your slides 24H or 
48H before the section.



Thank you!



Best regards,

Shuping

___
spring mailing list
spring@ietf.org
https://www.ietf.org/mailman/listinfo/spring

[spring] Presentation slot request in SPRING WG - IETF111

[Pengshuping (Peng Shuping)]

Dear all,



We will continue to using the Google Form to collect presentation slot requests 
in the SPRING WG for this IETF111. Please fill in your request in the following 
Form.

https://docs.google.com/forms/d/e/1FAIpQLSdgEW3Db8CK8l3C9OE2hTua8LA3qtEzMgbdbGQwdg72oa_1Vw/viewform?usp=sf_link


If there is any issue for you to access this Form, please send your request 
directly to spring-cha...@ietf.org.



Thank you!



Best regards,

Shuping

___
spring mailing list
spring@ietf.org
https://www.ietf.org/mailman/listinfo/spring

Re: [spring] WGLC for draft-ietf-spring-segment-routing-policy

[Pengshuping (Peng Shuping)]

Hi,

This is an important draft. I support the WGLC of this draft.

Thank you!

Best regards,
Shuping

From: spring [mailto:spring-boun...@ietf.org] On Behalf Of James Guichard
Sent: Friday, April 16, 2021 2:57 AM
To: spring@ietf.org
Cc: spring-cha...@ietf.org
Subject: [spring] WGLC for draft-ietf-spring-segment-routing-policy

Dear WG:

This email starts a 2 week Working Group Last Call for 
draft-ietf-spring-segment-routing-policy [1].

Please read this document if you haven't read the most recent version and send 
your comments to the SPRING WG list no later than April 29th 2021.

If you are raising a point which you expect will be specifically debated on the 
mailing list, consider using a specific email/thread for this point.

Lastly, if you are an author or contributors for this document please response 
to the IPR call in the previous email thread.

Thanks!

Jim, Joel & Bruno


[1] https://datatracker.ietf.org/doc/draft-ietf-spring-segment-routing-policy/




___
spring mailing list
spring@ietf.org
https://www.ietf.org/mailman/listinfo/spring

Re: [spring] SRv6 Service Programming using TLV

[Pengshuping (Peng Shuping)]

Hi Fabrice,

An interesting demo! APN could refer to this way to do with the SRv6 SFC. Thank 
you!

Maybe folks @SPRING WG would know more about it, so I copied the SPRING WG. 
Anybody would like to help here?

https://www.youtube.com/watch?v=NCZzhdu1OCE

Thanks!

Best Regards,
Shuping



From: Apn [mailto:apn-boun...@ietf.org] On Behalf Of Luc-Fabrice Ndifor Ngwa [ 
MTN Cameroon ]
Sent: Tuesday, March 30, 2021 12:11 PM
To: a...@ietf.org
Subject: [Apn] SRv6 Service Programming using TLV

Hi all,

Anybody knows about this demo (youtube link below) ? Would you like to 
introduce a bit more about the use case scenario? It seems to use the argument 
field and SRH TLV to carry the protocol.

This video was published in 2019. Any new updates on it would be very 
appreciated.

https://www.youtube.com/watch?v=NCZzhdu1OCE


[cid:image003.jpg@01D7263D.B49B0DC0]

​Warm regards,​


Luc‑Fabrice





Ndifor



Specialist ‑ IP Access and Data center



luc-fabrice.ndi...@mtn.com


T +237 677 55 02 13



Head Office: 360, Rue Drouot
​P.O. Box 15 574 Douala, Cameroon


T +237 679 00 90 90


 |


mtn.cm




This email is confidential. If you have received it in error, you are on notice 
of its status. Please notify ​the ​​sender immediately by
​reply email and then delete this message from your system. Please do not copy 
it ​or use it for any purpose or disclose its content
​to any other person as to do so could be a breach of ​confidentiality.
​
Please be informed that no employee or agent is authorized to conclude any 
legally binding agreement ​on behalf of MTN Cameroon
​via email. This can be only done if the email is confirmed explicitly in 
writing ​by an MTN Cameroon authorized officer. In no event
​will this email or its content be construed as a written ​approval.




[cid:image004.jpg@01D7263D.B49B0DC0]


___
spring mailing list
spring@ietf.org
https://www.ietf.org/mailman/listinfo/spring

[spring] SPRING Meeting Minutes @IETF110

[Pengshuping (Peng Shuping)]

Hi all,

Please find the SPRING meeting minutes @IETF110.
https://codimd.ietf.org/notes-ietf-110-spring?view

If you have any comments, please send them to the list.

Please note that the minutes are going to be submitted and published. Thank you!

Best regards,
Shuping
___
spring mailing list
spring@ietf.org
https://www.ietf.org/mailman/listinfo/spring

Re: [spring] SPRING agenda is posted

[Pengshuping (Peng Shuping)]

Hi all,

It seems that the system has some issues for you to directly upload your slides.

Please feel free to send them to 
spring-cha...@ietf.org<mailto:spring-cha...@ietf.org>.

Thank you!

Best regards,
Shuping


From: Pengshuping (Peng Shuping)
Sent: Wednesday, March 3, 2021 6:18 PM
To: 'spring@ietf.org' 
Cc: 'spring-cha...@ietf.org' 
Subject: SPRING agenda is posted

Dear all,

The agenda has been posted. Please let us know if you want to make any changes.

https://datatracker.ietf.org/meeting/110/materials/agenda-110-spring-02.txt

Please upload your slides directly to 
https://datatracker.ietf.org/meeting/110/session/spring or send them to 
spring-cha...@ietf.org<mailto:spring-cha...@ietf.org>.
Since we are the first session on Monday. So please upload your slides 24H or 
48H before the section.

Thank you!

Best regards,
Shuping
___
spring mailing list
spring@ietf.org
https://www.ietf.org/mailman/listinfo/spring

[spring] SPRING agenda is posted

[Pengshuping (Peng Shuping)]

Dear all,

The agenda has been posted. Please let us know if you want to make any changes.

https://datatracker.ietf.org/meeting/110/materials/agenda-110-spring-02.txt

Please upload your slides directly to 
https://datatracker.ietf.org/meeting/110/session/spring or send them to 
spring-cha...@ietf.org.
Since we are the first session on Monday. So please upload your slides 24H or 
48H before the section.

Thank you!

Best regards,
Shuping
___
spring mailing list
spring@ietf.org
https://www.ietf.org/mailman/listinfo/spring

Re: [spring] Presentation slot request in SPRING WG - IETF110

[Pengshuping (Peng Shuping)]

Dear all,

Just a kind reminder if you haven't posted your request in the form.


https://docs.google.com/forms/d/e/1FAIpQLSfx2a78nDG_3uAhy2Piz665JY668T6I5uFAv8l0Mrb3SOSy0w/viewform<https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.google.com%2Fforms%2Fd%2Fe%2F1FAIpQLSfx2a78nDG_3uAhy2Piz665JY668T6I5uFAv8l0Mrb3SOSy0w%2Fviewform=04%7C01%7Cjames.n.guichard%40futurewei.com%7C0c044258ac7444230de408d8cca2b1f2%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637484346452353876%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000=cKtd%2FPWNg2Itkp6IPo4eQtom2ld1NQu76x9Ss87Z6Nk%3D=0>

Please note, if you have already filled in the form, please also indicate that 
whether you have asked for a slot request in a different WG.

Thank you!

Best regards,
Shuping



From: Pengshuping (Peng Shuping)
Sent: Tuesday, February 9, 2021 10:16 PM
To: spring@ietf.org
Cc: 'spring-cha...@ietf.org' 
Subject: Presentation slot request in SPRING WG - IETF110


Dear all,



We will continue to using the Google Form to collect presentation slot requests 
in the SPRING WG for this IETF110. Please fill in your request in the following 
Form.



https://docs.google.com/forms/d/e/1FAIpQLSfx2a78nDG_3uAhy2Piz665JY668T6I5uFAv8l0Mrb3SOSy0w/viewform<https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.google.com%2Fforms%2Fd%2Fe%2F1FAIpQLSfx2a78nDG_3uAhy2Piz665JY668T6I5uFAv8l0Mrb3SOSy0w%2Fviewform=04%7C01%7Cjames.n.guichard%40futurewei.com%7C0c044258ac7444230de408d8cca2b1f2%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637484346452353876%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000=cKtd%2FPWNg2Itkp6IPo4eQtom2ld1NQu76x9Ss87Z6Nk%3D=0>



If there is any issue for you to access this Form, please send your request 
directly to spring-cha...@ietf.org<mailto:spring-cha...@ietf.org>.



Thank you!



Best regards,

Shuping

___
spring mailing list
spring@ietf.org
https://www.ietf.org/mailman/listinfo/spring

Re: [spring] more on IDs for slices

[Pengshuping (Peng Shuping)]

Dear Deborah,

Thank you very much for attracting people's attention on APN (Application-aware 
Networking) and having more discussions on this work to further clarify things. 
Thank you!

To all, please find more discussions in the APN mailing list 
(https://datatracker.ietf.org/wg/apn/about/). Please you are interest in this 
topic, please join us in the discussions. I have also copied the APN mailing 
list to make the subscribers of APN aware of these discussions happening here.

To us, the definition of a slice is not in the scope of APN.

APN is focused on developing a framework and set of mechanisms to derive, 
convey and use the APN attribute to allow for the implementation of fine-grain 
user (group)-, application (group)-, and service-level requirements at the 
network layer.

APN could be used to select TE paths, but it is not just about traffic 
engineering or traffic steering. It is about selecting next-hop paths in the 
network to route traffic onto links depending on the needs of the traffic. APN 
can also be used for the fine-granularity performance measurement and 
visualization within operator's network domain.

Best regards,
Shuping


From: spring [mailto:spring-boun...@ietf.org] On Behalf Of BRUNGARD, DEBORAH A
Sent: Tuesday, February 9, 2021 5:04 AM
To: t...@ietf.org; spring@ietf.org
Subject: [spring] more on IDs for slices

Hi,

Not sure if you are aware, there was a BoF proposed on using an identifier to 
signal user requirements (APN) in a slice, APN BoF. It was decided it would be 
better to first have it further discussed at IETF110's RTGWG as it would allow 
for a broader coverage:
https://www.ietf.org/blog/ietf110-bofs/

Considering the current discussion in spring and the work already on-going in 
teas on IDs and "what is a slice", and to help focus the discussion at the 
meeting, I wanted to bring the following drafts to your attention. I have asked 
the authors to help us understand the gaps with the on-going work not being 
addressed and what new work is needed. The authors have done a lot of work, 
this is just a selection:

https://www.ietf.org/archive/id/draft-peng-apn-scope-gap-analysis-00.txt
https://www.ietf.org/archive/id/draft-li-apn-framework-01.txt
https://www.ietf.org/archive/id/draft-li-apn-problem-statement-usecases-01.txt

If you search documents on APN, you will find more.

Happy reading,
Deborah

___
spring mailing list
spring@ietf.org
https://www.ietf.org/mailman/listinfo/spring

[spring] Presentation slot request in SPRING WG - IETF110

[Pengshuping (Peng Shuping)]

Dear all,



We will continue to using the Google Form to collect presentation slot requests 
in the SPRING WG for this IETF110. Please fill in your request in the following 
Form.



https://docs.google.com/forms/d/e/1FAIpQLSfx2a78nDG_3uAhy2Piz665JY668T6I5uFAv8l0Mrb3SOSy0w/viewform



If there is any issue for you to access this Form, please send your request 
directly to spring-cha...@ietf.org.



Thank you!



Best regards,

Shuping

___
spring mailing list
spring@ietf.org
https://www.ietf.org/mailman/listinfo/spring

Re: [spring] Meeting minutes for the SPRING sessions @IETF109

[Pengshuping (Peng Shuping)]

Dear all,

Please find the published meeting minutes and relevant materials.
https://datatracker.ietf.org/meeting/109/session/spring

Best regards,
Shuping


From: spring [mailto:spring-boun...@ietf.org] On Behalf Of Pengshuping (Peng 
Shuping)
Sent: Saturday, November 21, 2020 11:15 PM
To: spring@ietf.org
Cc: spring-cha...@ietf.org
Subject: [spring] Meeting minutes for the SPRING sessions @IETF109

Hi Folks,

Please find the meeting minutes for the two SPRING sessions @IETF109.
https://codimd.ietf.org/notes-ietf-109-spring?edit

Please check and correct. e.g. , your name and your comments. Thank you!

Cheers!

Best regards,
Shuping


___
spring mailing list
spring@ietf.org
https://www.ietf.org/mailman/listinfo/spring

[spring] Meeting minutes for the SPRING sessions @IETF109

[Pengshuping (Peng Shuping)]

Hi Folks,

Please find the meeting minutes for the two SPRING sessions @IETF109.
https://codimd.ietf.org/notes-ietf-109-spring?edit

Please check and correct. e.g. , your name and your comments. Thank you!

Cheers!

Best regards,
Shuping


___
spring mailing list
spring@ietf.org
https://www.ietf.org/mailman/listinfo/spring

[spring] IETF109 SPRING WG Agenda

[Pengshuping (Peng Shuping)]

Hi all,

The SPRING Agenda has been published. Please let us know if any change is 
needed.
https://datatracker.ietf.org/meeting/109/materials/agenda-109-spring-00

To the presenters, please send your slides to 
spring-cha...@ietf.org and/or upload them in the 
data tracker before Sunday evening.
https://datatracker.ietf.org/meeting/109/session/spring

Thank you!

Best regards,
Shuping

___
spring mailing list
spring@ietf.org
https://www.ietf.org/mailman/listinfo/spring

Re: [spring] Presentation slot request in SPRING WG - IETF109

[Pengshuping (Peng Shuping)]

Dear all,

Just a kind reminder. If you would like to present, please send your request if 
you have not done so. The cut-off date is 9th November.

Best regards,
Shuping


From: spring [mailto:spring-boun...@ietf.org] On Behalf Of Pengshuping (Peng 
Shuping)
Sent: Thursday, October 22, 2020 9:37 AM
To: spring@ietf.org
Cc: spring-cha...@ietf.org
Subject: [spring] Presentation slot request in SPRING WG - IETF109

Dear all,

We will continue to using the Google Form to collect presentation slot requests 
in the SPRING WG for this IETF109. Please fill in your request in the following 
Form.

https://docs.google.com/forms/d/e/1FAIpQLSdEJ90WoDxTFGRXiNhFgKADPFdOTtSpetI9geRNw1FfzsSRqw/viewform

If there is any issue for you to access this Form, please send your request 
directly to spring-cha...@ietf.org<mailto:spring-cha...@ietf.org>.

Thank you!

Best regards,
Shuping
___
spring mailing list
spring@ietf.org
https://www.ietf.org/mailman/listinfo/spring

[spring] Presentation slot request in SPRING WG - IETF109

[Pengshuping (Peng Shuping)]

Dear all,
We will continue to using the Google Form to collect presentation slot requests 
in the SPRING WG for this IETF109. Please fill in your request in the following 
Form.

https://docs.google.com/forms/d/e/1FAIpQLSdEJ90WoDxTFGRXiNhFgKADPFdOTtSpetI9geRNw1FfzsSRqw/viewform

If there is any issue for you to access this Form, please send your request 
directly to spring-cha...@ietf.org.

Thank you!
Best regards,
Shuping
___
spring mailing list
spring@ietf.org
https://www.ietf.org/mailman/listinfo/spring

[spring] SPRING WG Meeting Minutes

[Pengshuping (Peng Shuping)]

Dear all,

Hope you enjoyed this week!

Please review the meeting minutes for our SPRING session in this IETF on Monday.
https://datatracker.ietf.org/meeting/108/session/spring

Please let us know if there is any correction needed.

Thank you and take care! :)

Best Regards,
Shuping

___
spring mailing list
spring@ietf.org
https://www.ietf.org/mailman/listinfo/spring

Re: [spring] SPRING WG Agenda @IETF108

[Pengshuping (Peng Shuping)]

Hi all,

A kind reminder for the presenters to send your slides. Thank you!

https://datatracker.ietf.org/meeting/108/session/spring

Best regards,
Shuping


From: Pengshuping (Peng Shuping)
Sent: Monday, July 20, 2020 6:16 PM
To: 'spring@ietf.org' 
Cc: 'spring-cha...@ietf.org' 
Subject: SPRING WG Agenda @IETF108


Hi all,



The agenda for our virtual 108 meeting has been posted. Please let us know if 
any changes are needed.



https://www.ietf.org/proceedings/108/agenda/agenda-108-spring-00



To all presenters, please send your slides to 
spring-cha...@ietf.org<mailto:spring-cha...@ietf.org> no later than the 
Saturday July 25.



Thank you!



Best Regards,

Shuping


From: Pengshuping (Peng Shuping)
Sent: Sunday, June 28, 2020 9:56 PM
To: spring@ietf.org<mailto:spring@ietf.org>
Cc: spring-cha...@ietf.org<mailto:spring-cha...@ietf.org>
Subject: Presentation slot request in SPRING WG - IETF108

Hi all,

We have decided to use Google Form to collect presentation slot requests in the 
SPRING WG for this IETF108. Please fill in your request in the following Form.

https://docs.google.com/forms/d/e/1FAIpQLSeed9WSYsu5qlxNTOIzd49gFeZSlfny9C6xmB8ZxQTrERufyw/viewform
If there is any issue for you to access this Form, please send your request 
directly to spring-cha...@ietf.org<mailto:spring-cha...@ietf.org>.

Thank you!

Best regards,
Shuping
___
spring mailing list
spring@ietf.org
https://www.ietf.org/mailman/listinfo/spring

[spring] SPRING WG Agenda @IETF108

[Pengshuping (Peng Shuping)]

Hi all,



The agenda for our virtual 108 meeting has been posted. Please let us know if 
any changes are needed.



https://www.ietf.org/proceedings/108/agenda/agenda-108-spring-00



To all presenters, please send your slides to 
spring-cha...@ietf.org<mailto:spring-cha...@ietf.org> no later than the 
Saturday July 25.



Thank you!



Best Regards,

Shuping


From: Pengshuping (Peng Shuping)
Sent: Sunday, June 28, 2020 9:56 PM
To: spring@ietf.org
Cc: spring-cha...@ietf.org
Subject: Presentation slot request in SPRING WG - IETF108

Hi all,

We have decided to use Google Form to collect presentation slot requests in the 
SPRING WG for this IETF108. Please fill in your request in the following Form.

https://docs.google.com/forms/d/e/1FAIpQLSeed9WSYsu5qlxNTOIzd49gFeZSlfny9C6xmB8ZxQTrERufyw/viewform
If there is any issue for you to access this Form, please send your request 
directly to spring-cha...@ietf.org<mailto:spring-cha...@ietf.org>.

Thank you!

Best regards,
Shuping
___
spring mailing list
spring@ietf.org
https://www.ietf.org/mailman/listinfo/spring

[spring] Presentation slot request in SPRING WG - IETF108

[Pengshuping (Peng Shuping)]

Hi all,

We have decided to use Google Form to collect presentation slot requests in the 
SPRING WG for this IETF108. Please fill in your request in the following Form.

https://docs.google.com/forms/d/e/1FAIpQLSeed9WSYsu5qlxNTOIzd49gFeZSlfny9C6xmB8ZxQTrERufyw/viewform
If there is any issue for you to access this Form, please send your request 
directly to spring-cha...@ietf.org.

Thank you!

Best regards,
Shuping
___
spring mailing list
spring@ietf.org
https://www.ietf.org/mailman/listinfo/spring

Re: [spring] WG LC https://datatracker.ietf.org/doc/draft-ietf-spring-sr-yang/

[Pengshuping (Peng Shuping)]

I support the adoption.

Best regards,
Shuping


From: James Guichard [mailto:james.n.guich...@futurewei.com]
Sent: Wednesday, June 24, 2020 1:59 AM
To: spring@ietf.org
Cc: spring-cha...@ietf.org
Subject: WG LC https://datatracker.ietf.org/doc/draft-ietf-spring-sr-yang/

Dear SPRING WG:

This email starts a two week WG LC for 
https://datatracker.ietf.org/doc/draft-ietf-spring-sr-yang/.

Substantive comments should be directed to the mailing list no later than July 
7th. Editorial suggestions can be sent to the authors.

Thanks!

Jim, Joel & Bruno

___
spring mailing list
spring@ietf.org
https://www.ietf.org/mailman/listinfo/spring

Re: [spring] Leadership change

[Pengshuping (Peng Shuping)]

Thank you, Martin!

Thank you very much for your service, Rob! 

Welcome Jim and Joel! Congrats! 

Best Regards,
Shuping


-Original Message-
From: spring [mailto:spring-boun...@ietf.org] On Behalf Of Martin Vigoureux
Sent: Monday, June 15, 2020 4:25 AM
To: spring@ietf.org
Cc: 6...@ietf.org; int-...@ietf.org; bruno.decra...@orange.com; 
 ; Rob Shakir ; James 
Guichard ; Joel M. Halpern 

Subject: [spring] Leadership change

WG,

Rob had decided to step down as chair some time ago. There hasn't been any 
formal communication on that so I'd like, first, to thank Rob for his work and 
dedication to the group. Thank you very much Rob.

Since that time, I have been actively looking for one (or two) person(s) to 
replace him. This has proven to be a very challenging endeavour!

But it has finally came to an end.

I am pleased to inform you that I have appointed Jim Guichard and Joel Halpern 
as co-chairs of SPRING WG, alongside Bruno.
Thank you Jim, Thank you Joel, and thank you Bruno.


Martin
as AD for SPRING

___
spring mailing list
spring@ietf.org
https://www.ietf.org/mailman/listinfo/spring

___
spring mailing list
spring@ietf.org
https://www.ietf.org/mailman/listinfo/spring

Re: [spring] 答复: CRH is back to the SPRING Use-Case - Re: Size of CR in CRH

[Pengshuping (Peng Shuping)]

Hi,

Please see inline.

--
彭书萍 Peng Shuping
Mobile: +86-18210364128(优先)
Email: pengshup...@huawei.com

发件人：Aijun Wang 
收件人：'Andrew Alston' ;'Ketan Talaulikar 
(ketant)' ;'Joel M. Halpern' 

抄 送：rtg-ads ;spring ;'6man' <6...@ietf.org>
时 间：2020-05-22 23:55:46
主 题：[spring] 答复: CRH is back to the SPRING Use-Case - Re: Size of CR in CRH

Hi, Andrew and all:
Is using the “Routing Header” to maneuver the path of packet a good idea?
From the viewpoint of the service provider, if we depend on the central 
controller/PCE to assure the QoS of application, we should simplify the network 
design and the network device.
Currently, both SRH and CRH deployment requires the presence of SDN 
controller/PCE, but the network/device complexity is not decreased. How 
operator can benefit from the adoption of these technologies?

[Shuping] Protocols are simplified. Only need to care about IGP and BGP.

You have also mentioned the cloud provider. What their requirements is the 
openness/standard API from the device, this can give the most flexibility for 
network programming.
Why we don’t dive into this direction? There are several NorthBound 
interfaces/protocols exist in IETF standard.

[Shuping] PCEP and BGP can be taken as the standard API of an SRv6 network, by 
which you can program your network.

For CRH and SRH, I think there are some similarity between them. CRH does not 
conflict with the IPv6 address, but requires the map table exist. Many experts 
will dispute again the similar problem.
Is CRH the brick that cloud provider want?

[Shuping] SRv6 into DC is also appealing since it enables end-to-end true 
network and cloud convergence.

Best Regards.
Aijun Wang
China Telecom
发件人: spring-boun...@ietf.org 
[mailto:spring-boun...@ietf.org] 代表 Andrew Alston
发送时间: 2020年5月22日 17:25
收件人: Andrew Alston; Ketan Talaulikar (ketant); Joel M. Halpern
抄送: rtg-...@ietf.org; 
spring@ietf.org; 6man
主题: Re: [spring] CRH is back to the SPRING Use-Case - Re: Size of CR in CRH
Just as a followup – which I think illustrates my point here.
https://blogs.cisco.com/sp/cisco-goes-sonic-on-new-networking-platforms
If operators wanted fait accompli – why is it that Cisco – and other vendors – 
are starting to provide ASIC based API’s such that cloud providers and 
operators can do what they need on devices – rather than the dictates of 
vendors? I think the very fact that the above article exists – illustrates the 
desire for simple building blocks.
Thanks
Andrew
From: spring mailto:spring-boun...@ietf.org>> On 
Behalf Of Andrew Alston
Sent: Friday, 22 May 2020 12:15
To: Ketan Talaulikar (ketant) 
mailto:ketant=40cisco@dmarc.ietf.org>>; 
Joel M. Halpern mailto:j...@joelhalpern.com>>
Cc: rtg-...@ietf.org; 
spring@ietf.org; 6man 
<6...@ietf.org>
Subject: Re: [spring] CRH is back to the SPRING Use-Case - Re: Size of CR in CRH
Actually Ketan,
As an operator – I am looking for the tyre – I want the building block – 
because it allows me to both use what the vendors build on top of it – and to 
build my own stuff on top of it that is specific to my needs.
The tyre association is one such association – the brick is another – the brick 
was invented long before anyone created an architectural diagram to build a 
building. CRH is a brick – that can be shaped to many purposes.
And as an operator – it is *exactly* what I want – without the dictates of what 
any vendor says I can do with it.
There are unique conditions in every operator environment – and if an operator 
is given the right bricks – and those bricks can be used to build something 
that is inter-operable across the vendors and within their specific domain – it 
is that building that gives the operator their competitive advantage. If 
however, all operators are handed a completed building – its much harder to 
build something that differentiates.
I must point out – in a world where we are seeing more and more white box 
technology – and where content providers are moving to building their own 
things pretty quickly – why do you think that is? One reason I believe is 
because the requirements are not the same everywhere – and I have long believed 
that a standard should be such that an operator can take that standard – and 
use it within his specific domain to build on top of – and rather we have a 
standard brick such that the solutions that are built are portable – than every 
operator inventing their own bricks and nothing working together.
Again – the reason I support CRH – is because of the flexibility and simplicity 
it affords me as an operator – and because – we have specific use cases and 
things we wish to build on top of it – some of which – are pretty standard and 
happily in the public domain – other things – which are specific internally. 
And I for 

Re: [spring] CRH is back to the SPRING Use-Case - Re: Size of CR in CRH

[Pengshuping (Peng Shuping)]

Hi, 

To me all the discussions happened here are about a clear justification 
required for a I-D. 

Best regards, 
Shuping 


-Original Message-
From: ipv6 [mailto:ipv6-boun...@ietf.org] On Behalf Of Joel M. Halpern
Sent: Friday, May 22, 2020 10:36 PM
To: Ketan Talaulikar (ketant) 
Cc: rtg-...@ietf.org; spring@ietf.org; 6man <6...@ietf.org>
Subject: Re: [spring] CRH is back to the SPRING Use-Case - Re: Size of CR in CRH

None of those documents drive the need for SRv6.Even the problem 
statement doesn't really geet us there.

More importantly, SRH does not fully comply with those documents.   It 
has fields that are unrelated to those documents.  Heck, it still has the tag 
field that many of us are unable to understand.  And it has a TLV that has no 
meaningful use (the authentication use is internally inconsistent, as was 
discussed on the list.)  While wew objected to various parts on the substance, 
the fact that SRH is meant as a building block to support things beyond the 
SPRIGN archtiecture was not an objection.

Architectures are the closest the IEtF comes to building solutions. 
They are arguably not very useful.  MPLS, for example meets both the base MPLS 
architecture and the SPRING architecture.  And several different VPN 
architectures.

CRH can be used to meet the SPRING archtiecture.  It can also, has been clearly 
stated, be used in other ways.  There is not "an" architecture for using CRH.

And there was not "an" architecture for using SRH.  If there ere, we would have 
gotten the extraneous parts removed.

Yours,
Joel

On 5/22/2020 1:20 AM, Ketan Talaulikar (ketant) wrote:
> Hi Joel,
> 
> I'll point you to RFC7855, RFC8355 and RFC8402 that cover both the 
> data-planes for Spring. Then the RFC8354 which is focussed on SRv6. All this 
> body of work along with a whole lot of discussion and brainstorming happening 
> in the Spring WG provided the architecture, use-cases, applicability and 
> requirements for SRH (RFC8754).
> 
> It may be so that many people in 6man focussed on only the IPv6 specific 
> aspects as is their design expertise. But there were others (in 6man, Spring 
> and other WGs) that were able to look at the solution in a holistic manner 
> thanks to the body of work behind it.
> 
> Net-PGM builds on top of RFC8402 and RFC8754.
> 
> To give a real world analogy, let us understand what kind of a car we are 
> trying to build (to carry goods/passengers or both and how much/many, what 
> terrain it is meant for, what weather/environment conditions, how much 
> speed/performance/fuel efficiency parameters required, etc.) before we start 
> designing tyres for it.
> 
> Thanks,
> Ketan
> 
> -Original Message-
> From: Joel M. Halpern 
> Sent: 22 May 2020 10:02
> To: Ketan Talaulikar (ketant) 
> Cc: spring@ietf.org; 6man <6...@ietf.org>; rtg-...@ietf.org
> Subject: Re: [spring] CRH is back to the SPRING Use-Case - Re: Size of 
> CR in CRH
> 
> Ketan, I am trying to figure out which documents you think were adopted and 
> approved elsewhere to drive the 6man work on SRH.
> 
> I did find RFC 8354, which was a use case.  It is not a problem statement.  
> It is most definitely not an architecture.  The only architecture documents I 
> can find are general SR documents.  Those did not justify a need for SRH.  
> And I (at least) did not object to SRH on the basis of that gap.
> 
> Yes, SRH normatively references 8402.  But 8402 does not drive any need for 
> SRH.  In fact, the actual text references to SRH are fairly cursory.
>(The most significant is some terminology.)
> 
> In fact, as far as I can tell, the ties are such that there is no 
> evidence in the documents that SPRING had any say in SRH.  (the 
> reality is more complex, I grant you.  But there was no formal 
> approval or signoff.)
> 
> As far as I can tell, there was no formal approval of anything by SPRING that 
> can be read as a request to 6man to work on SRH.  (Do remember that the SRH 
> document was adopted by 6man in December of 2015.)  The network programming 
> draft did not even appear at 00 until March of 2017, 15 months later.
> 
> How, given this history, can you claim that CRH needs something more.
> We have operators asking for this.
> 
> Yours,
> Joel
> 
> On 5/21/2020 11:53 PM, Ketan Talaulikar (ketant) wrote:
>> Hi Bob,
>>
>> Perhaps I will try to make my case to you (and everyone else here) … 
>> one last time.
>>
>> This is how I've seen RH work being done in 6man until now (in a 
>> matter that fits its charter).
>>
>> 1) There is a WG (not 6man) that defines the problem statement, 
>> use-cases and architecture that requires RH
>>
>> 2) The 6man being the experts on IPv6 design, either take up the 
>> document that specifies that RH (or even if it is done in another WG, 
>> reviews it).
>>
>> So 6man has always had work done in (1) to reference and lean upon 
>> when doing (2).
>>
>> My argument of the shortcut in the case of this specific adoption is 
>> that we don't have 

Re: [spring] CRH is back to the SPRING Use-Case - Re: Size of CR in CRH

[Pengshuping (Peng Shuping)]

The “mapping ID” indeed needs to be carefully explored, which may cause serious 
operational issue considering such a large number of local FIB entries imposed 
by CRH.

Shuping


From: ipv6 [mailto:ipv6-boun...@ietf.org] On Behalf Of Ketan Talaulikar (ketant)
Sent: Friday, May 22, 2020 11:53 AM
To: Bob Hinden 
Cc: spring@ietf.org; 6man <6...@ietf.org>; Robert Raszuk ; 
rtg-...@ietf.org
Subject: RE: [spring] CRH is back to the SPRING Use-Case - Re: Size of CR in CRH


Hi Bob,



Perhaps I will try to make my case to you (and everyone else here) … one last 
time.



This is how I've seen RH work being done in 6man until now (in a matter that 
fits its charter).



1) There is a WG (not 6man) that defines the problem statement, use-cases and 
architecture that requires RH

2) The 6man being the experts on IPv6 design, either take up the document that 
specifies that RH (or even if it is done in another WG, reviews it).



So 6man has always had work done in (1) to reference and lean upon when doing 
(2).



My argument of the shortcut in the case of this specific adoption is that we 
don't have (1).



It is not in 6man charter nor expertise to take up (1) because CRH is not 
purely IPv6 work. It is not meant for "Internet" but a specific "limited 
domain". The SIDs that it introduces is a new "mapping ID" concept. It is not 
an IPv6 address and neither it is MPLS. This is a Routing Header and part of a 
new Source Routing solution.



Therefore, without (1) being made available to 6man, I believe that working on 
(2) in 6man is to me a shortcutting of the IETF technical review process 
(specifically of the Routing area in this case) for a solution and does not 
provide the necessary reference for 6man to work on.



Why the rush?



I close my arguments.



Thanks,

Ketan



-Original Message-
From: Bob Hinden mailto:bob.hin...@gmail.com>>
Sent: 22 May 2020 09:03
To: Ketan Talaulikar (ketant) mailto:ket...@cisco.com>>
Cc: Bob Hinden mailto:bob.hin...@gmail.com>>; Brian 
Carpenter mailto:brian.e.carpen...@gmail.com>>; 
Ron Bonica mailto:rbon...@juniper.net>>; Chengli (Cheng 
Li) mailto:c...@huawei.com>>; Zafar Ali (zali) 
mailto:z...@cisco.com>>; Robert Raszuk 
mailto:rob...@raszuk.net>>; 
spring@ietf.org; 6man 
<6...@ietf.org>
Subject: Re: [spring] CRH is back to the SPRING Use-Case - Re: Size of CR in CRH



Ketan,



> On May 21, 2020, at 8:12 PM, Ketan Talaulikar (ketant) 
> mailto:ketant=40cisco@dmarc.ietf.org>> 
> wrote:

>

> Hi Brian,

>

> Please see my previous response to your comments.

>

> My argument is not legalistic. I am not as experience in IETF work as you and 
> Bob are. But what I understand is that the reason why we have these "legal" 
> process of charters and BoF is to enable a proper technical discussion with 
> the right context and details of the proposal presented for review of the 
> community.

>

> I do not see how shortcutting them helps anyone and I wonder why it is being 
> done in this case?



There is no short cutting here.  The adoption call is to determine if there is 
interest in the w.g. to take this work into 6man.   If it becomes a w.g. draft, 
then the w.g. is responsible to decide what happens next.



It’s a first step, it is not a decision to publish it.



Bob (w/ w.g. chair hat on)









>

> Thanks,

> Ketan

>

> -Original Message-

> From: Brian E Carpenter 
> mailto:brian.e.carpen...@gmail.com>>

> Sent: 22 May 2020 04:18

> To: Ketan Talaulikar (ketant) mailto:ket...@cisco.com>>; 
> Ron Bonica mailto:rbon...@juniper.net>>; Chengli (Cheng 
> Li) mailto:c...@huawei.com>>; Zafar Ali (zali) 
> mailto:z...@cisco.com>>; Robert Raszuk 
> mailto:rob...@raszuk.net>>

> Cc: spring@ietf.org; 6man 
> <6...@ietf.org>

> Subject: Re: CRH is back to the SPRING Use-Case - Re: Size of CR in CRH

>

> On 22-May-20 05:26, Ketan Talaulikar (ketant) wrote:

> ...> It is the 6man charter that precludes it from defining a new Source 
> Routing solution..

>> “It is not chartered to develop major changes or additions to the IPv6 
>> specifications.”

>

> If this addition was major, that would be true. But adding a new RH type is 
> well within the scope of maintenance, IMHO. We have already done it quite 
> recently.

>

> In any case, legalistic arguments about WG charters are really not how we 
> should take technical decisions.

>

> Regards

>Brian

>

>

> ___

> spring mailing list

> spring@ietf.org

> https://www.ietf.org/mailman/listinfo/spring


___
spring mailing list
spring@ietf.org
https://www.ietf.org/mailman/listinfo/spring

Re: [spring] How CRH support SFC/Segment Endpoint option?

[Pengshuping (Peng Shuping)]

Hi Ron,

If using DOH, then we would have DOH (VPN) + DOH (SFC) + RH per packet in some 
circumstances, right? What if more (ever-emerging) services are required? Not 
sure about the forwarding efficiency.

Best regards,
Shuping


From: ipv6 [mailto:ipv6-boun...@ietf.org] On Behalf Of Ron Bonica
Sent: Friday, May 22, 2020 10:17 PM
To: Chengli (Cheng Li) ; 6man <6...@ietf.org>; spring@ietf.org
Cc: spring@ietf.org
Subject: RE: How CRH support SFC/Segment Endpoint option?

Cheng,

The sole purpose of a Routing header is to steer a packet along a specified 
path to its destination. It shouldn't attempt to do any more than that.

The CRH does not attempt to deliver service function information to service 
function instances. However, it is compatible with:

-The Network Service Header (NSH)
-The Destination Options header that precedes the Routing header

Both of these can be used to deliver service function information to service 
function instances.


 Ron




Juniper Business Use Only
From: Chengli (Cheng Li) mailto:c...@huawei.com>>
Sent: Friday, May 22, 2020 2:56 AM
To: 6man <6...@ietf.org>; 
spring@ietf.org; Ron Bonica 
mailto:rbon...@juniper.net>>
Cc: spring@ietf.org
Subject: How CRH support SFC/Segment Endpoint option?

[External Email. Be cautious of content]

Hi Ron,

When reading the CRH draft, I have a question about how CRH support SFC?

For example, we have a SID List [S1, S2, S3, S4, S5], and S3 is a SFC related 
SID, how to indicate that? By PSSI? [1]

But how to know which segment endpoint node/egress node should process this 
PSSI? At the beginning of the SRm6 design, this is described in [2]. But you 
deleted the containers [2].

Without that, I don't really understand how SFC can be supported.


Best,
Cheng



[1]. 
https://tools.ietf.org/html/draft-bonica-spring-sr-mapped-six-01#section-4.1
[2]. 
https://tools.ietf.org/rfcdiff?url2=draft-bonica-6man-seg-end-opt-04..txt.


___
spring mailing list
spring@ietf.org
https://www.ietf.org/mailman/listinfo/spring

Re: [spring] CRH and RH0

[Pengshuping (Peng Shuping)]

Hi Ron,



I have short experience in IETF compared with most of you with decades of 
experience, but still I believe that people do care about the motivations as 
well as the students in 25 years. From my observation and understanding, in 
IETF even to bring a small extension to the existing protocol the community 
will require proper justifications. People will ask why we need this extension, 
and why the existing solutions cannot solve the same issue. Don’t need to 
mention about the justifications that would be required for a general purpose 
routing header as you call it.

There have been a few RHs already defined in IETF. For the one that I have 
experienced part of its standardization process, i.e. SRH, I have learned that 
there is an architecture (RFC8402) draft defined for it as well as related 
problem statement (RFC7855) and use cases (RFC8354, RFC8355) drafts in SPRING. 
There are so many other drafts active in SPRING and other working groups built 
upon the SRH in almost every aspect, which in the meantime also justify its 
value.

For CRH, the IPv6 Compressed Routing Header (CRH), from the title wise, I don’t 
see why it should be called a general purpose routing header. Its use to me is 
pretty clear, that is for compression. Can we say compression is the use case 
of this routing header? Is there any other use cases for it? If we call it a 
general purpose, it would be better if it can be used in general case or to 
cover more general use cases.

Regarding the justification of CRH, I did notice that in its version 10 there 
was a normative reference to a SPRING draft [I-D.bonica-spring-srv6-plus], but 
it was removed from version 11. I am not quite sure about your motivation to 
have this action. But I have been taken SRv6+ now SRm6 as the architecture and 
justification of CRH. Probably some people also had the same feeling.

If compression is the use case and SRm6 is the justification, currently there 
have already been a few solutions on the table of SPRING. People are working 
together to evaluate those solutions to solve the size issue, the same as one 
of the purpose of CRH. So would it be better for CRH to join the discussion 
there and solve the lengthy header issue altogether? That would mean a lot to 
the community for now.

My two cents.

Thank you!

Best regards, 
Shuping 


-Original Message-
From: ipv6 [mailto:ipv6-boun...@ietf.org] On Behalf Of Ron Bonica
Sent: Wednesday, May 13, 2020 4:13 AM
To: Darren Dukes (ddukes) 
Cc: 6man <6...@ietf.org>
Subject: RE: CRH and RH0

Hi Darren,

The answer to your question is a bit nuanced. My goals were to build a general 
purpose routing header that overcomes the RH0's limitations. Those being:

- Its size
- Its security issues

Now, is that a replacement for RH0? In one way, yes. RH0 and CRH are both 
general purpose routing headers. In another sense, no. RH0 is meant to traverse 
network boundaries. But RFC 5095 taught us that letting routing header traverse 
network boundaries might not be a wonderful idea. So, CRH is restricted to a 
network domain.

And now I return to my original question. When engineering students read the 
CRH RFC in 25 years, will they really care what my motivation was? Why should 
we burden them with this detail?


 Ron



 


Juniper Business Use Only

-Original Message-
From: Darren Dukes (ddukes)  
Sent: Tuesday, May 12, 2020 2:54 PM
To: Ron Bonica 
Cc: 6man <6...@ietf.org>
Subject: Re: CRH and RH0

[External Email. Be cautious of content]


Hi Ron,

The introduction spends its time likening CRH to RH0 and says it differs by 
“encoded in fewer bytes” and “addresses security vulnerabilities”

I was left with the impression that you are attempting to recreate another 
general use IPv6 routing header for the internet.  Like RH0.

It's only in section 9 where there is a hint that is not the case, you say 
“Networks that process the CRH MUST…”.  I could not find a definition of these 
networks.

Darren


> On May 12, 2020, at 2:32 PM, Ron Bonica  wrote:
>
> Hi Darren,
>
> The second issue is already addressed in the Security Consideration section.
>
> I would be glad to add a sentence saying that CRH is not a replacement for 
> RH0, but I am not sure what value that sentence will have to someone who will 
> read the document in 25 years. Could you help me understand the benefit? Why 
> would the reader care?
>
>Ron
>
>
>
> Juniper Business Use Only
>
> -Original Message-
> From: Darren Dukes (ddukes) 
> Sent: Tuesday, May 12, 2020 2:27 PM
> To: Ron Bonica 
> Cc: 6man <6...@ietf.org>
> Subject: CRH and RH0
>
> [External Email. Be cautious of content]
>
>
> Hi Ron,
>
> You mentioned in the 6man meeting that:
> 1 - CRH 

Re: [spring] SRv6 PSP use case--benifit of SRv6

[Pengshuping (Peng Shuping)]

Hi Weibin,

Please find in-line starting with [Answer].

From: Wang, Weibin (NSB - CN/Shanghai) [mailto:weibin.w...@nokia-sbell.com]
Sent: Friday, March 6, 2020 1:15 PM
To: Pengshuping (Peng Shuping) ; Ketan Talaulikar 
(ketant) ; Mark Smith 
; Joel M. Halpern 
Cc: SPRING WG 
Subject: RE: [spring] SRv6 PSP use case--benifit of SRv6

Hi authors：

Thanks for sharing the SRv6 deployment cases in china;

Can I express my views? From the contents of the section 2 and section 3 in 
your draft perspective:
   1)  Because the design of SRv6 is an incremental deployment over existing 
IPv6 network, it will not affect the existing IPv6 deployment and the existing 
IPv6 address allocation method. Therefore, the easiest way to allocate an IPv6 
address for an SRv6 deployment is to take a / 40 or / 48 address block directly 
from the IPv6 address blocks allocated from RIR. In ordinary IPv6 address 
allocation method, even each broadband user may also be assign a / 64 prefix, 
and an organization needs to assign prefixes such as / 48, / 56, or /60, etc. 
Therefore, / 48 for SRv6 deployment is not a waste of addresses.

[Answer] Just / 48 may not be enough. Please see more below.

   2) In section 3, it is not given how many bits each node needs to identify 
the node itself (i.e. N of B: N), which is a part of the locator. It is 
generally considered that 2 bytes are reasonable;

[Answer] 2 bytes could be used.

   3) For FUNC.Length and Argu.Length, I think its length is a multiple of byte 
is better, it is more conducive to the read operation of the router.

[Answer] For Ipv6 address planning, generally 4bits is used as a nibble. With 
8bits/Byte would also be ok, just it may cause address waste.

   4) Therefore, my point is that for a backbone network or a metropolitan area 
network, the / 48 address block is a reasonable deployment for SRv6, then / 64 
is used as the locator for each node, and the next 4 bytes are used as func 
.length, and 2 bytes as Argu.length, the last 2 bytes are filled with 0; of 
course, as service SID is becoming mature,  another /48 may be allocated for it 
for purpose of supporting SR service programming within SRv6 domain.

[Answer] It may not be enough to use / 48 address block for a SRv6 network and 
then / 64 for each node. It is because between the network locator and the 
device locator there would be many other identifiers that requires space 
allocation, such as device identifier, slice identifier as well as locator type 
identifier, etc..
It would be a bit long for using 4 bytes as func.length and 2 bytes as 
Argu.length.

  5) I believe, The benefits of SRv6-BE in section 2 are not brought by SRv6 
itself, it is only side effect of SRv6. If we use MPLS over UDP tunnel in IPv4 
environment, we can also achieve the same benefit of simple cross-domain VPN 
service deployment, which is the same as SRv6-BE, of course, it does not have 
TE capability.

[Answer] Yes, for this particular aspect, the benefit would be the same. 
However, please don't forget other advantages brought by SRv6 only instead of 
MPLS plus some additional add-ons. SRv6 can provide BE with route 
aggregatability as well as TE with simply the IPv6 as the data plane.

Cheers!

Wang Weibin

Best regards,
Shuping


From: spring mailto:spring-boun...@ietf.org>> On 
Behalf Of Pengshuping (Peng Shuping)
Sent: Friday, March 6, 2020 12:08 AM
To: Ketan Talaulikar (ketant) 
mailto:ketant=40cisco@dmarc.ietf.org>>; 
Mark Smith mailto:markzzzsm...@gmail.com>>; Joel M. 
Halpern mailto:j...@joelhalpern.com>>
Cc: SPRING WG mailto:spring@ietf.org>>
Subject: Re: [spring] SRv6 PSP use case

Hi all,

We just updated our draft on the SRv6 Deployment Consideration. One of the new 
updates in the draft is to add some of the PSP use cases, which is inspired by 
the discussions over the mailing list. Your comments on the draft are very 
welcomed as well as more PSP use cases. Thank you!

The posted draft can be found here,
https://tools.ietf.org/html/draft-tian-spring-srv6-deployment-consideration-01.

Best regards,
Shuping
___
spring mailing list
spring@ietf.org
https://www.ietf.org/mailman/listinfo/spring

Re: [spring] SRv6 PSP use case

[Pengshuping (Peng Shuping)]

Hi all,

We just updated our draft on the SRv6 Deployment Consideration. One of the new 
updates in the draft is to add some of the PSP use cases, which is inspired by 
the discussions over the mailing list. Your comments on the draft are very 
welcomed as well as more PSP use cases. Thank you!

The posted draft can be found here,
https://tools.ietf.org/html/draft-tian-spring-srv6-deployment-consideration-01.

Best regards,
Shuping


From: spring [mailto:spring-boun...@ietf.org] On Behalf Of Ketan Talaulikar 
(ketant)
Sent: Thursday, March 5, 2020 12:41 PM
To: Mark Smith ; Joel M. Halpern 
Cc: SPRING WG 
Subject: Re: [spring] SRv6 PSP use case

Hi Joel,

Thanks for your attempt at summarizing one of the use-cases of PSP which has 
been actively discussed/debated on the list. I see that you are suggesting to 
do something like a use-case review for it. It might be a useful discussion for 
the WG, but I am sure you are not suggesting any association with the 
progression of the net-pgm draft. Do clarify since that document is a standards 
track and does not discuss or cover use-cases. It only covers the 
standardization of the various SID behaviors as explained in its introduction.

Since we are talking use-cases, I think it is important again to remind what 
Bruno said here : 
https://mailarchive.ietf.org/arch/msg/spring/MkMkmNtEgnOYb5v_T-1HLLV6AB8/

"A negative claim is a colloquialism for an affirmative claim that asserts the 
non-existence or exclusion of something.[10] The difference with a positive 
claim is that it takes only a single example to demonstrate such a positive 
assertion ("there is a chair in this room," requires pointing to a single 
chair), while the inability to give examples demonstrates that the speaker has 
not yet found or noticed examples rather than demonstrates that no examples 
exist (the negative claim that a species is extinct may be disproved by a 
single surviving example or proven with omniscience)."

I would also like to add that it is perfectly likely that an operator has more 
use-case(s) for the building block of PSP in their network that they do not 
want to disclose. It may be their differentiator or innovation which they do 
not have to share with the IETF. There will also likely be other use-cases in 
the future that are built on top of the building blocks that we are 
standardizing. I don’t believe you are suggesting that we regulate use-cases at 
the IETF?

And then, I will again come back to the key point which we’ve debated before : 
why not have PSP?

Mark,

Perhaps you are rehashing the point that you raised and was answered here : 
https://mailarchive.ietf.org/arch/msg/spring/nOWf9iys3en1NN6IVbWodzaw7_M/

Also, it seems unfruitful to perform estimations of network operators 
upgrade/refresh plans or to analyse their financial conditions in this context. 
It seems more appropriate to support standardization work that enables rollout 
of innovation that is also attempting to be relevant for what is real and out 
there today.

Thanks,
Ketan

From: spring mailto:spring-boun...@ietf.org>> On 
Behalf Of Mark Smith
Sent: 05 March 2020 06:46
To: Joel M. Halpern mailto:j...@joelhalpern.com>>
Cc: SPRING WG mailto:spring@ietf.org>>
Subject: Re: [spring] SRv6 PSP use case


Hi Joel,


On Thu, 5 Mar 2020, 07:42 Joel M. Halpern, 
mailto:j...@joelhalpern.com>> wrote:
I think I have now inferred what the intended use case is for PSP.  I
really wish folks had stated it in full and explicitly, rather than
implicitly a piece at a time, on the list.

As noted below after the explanation, I think that supporting this use
case does require some explanations somewhere.  And given that the
support is in terms of PSP, I guess the NP draft is the place to put the
caveats.

As far as I can tell, the use case is as follows.
The operator has devices, that they reasonably wish to continue to use.

My understanding is that the operator wants to extend their SRv6 control plane 
domain onto PEs, past the edge of their current SRv6 forwarding plane domain, 
because they don't currently have budget available to upgrade the forwarding 
plane in those PEs.

This situation would be temporary until there is budget to upgrade the PEs' 
forwarding planes. I'd think this situation is likely to last no more than 2 to 
3 years in a big operator. The more successful SR is, the quicker the upgrades 
are likely to be.

So this is effectively a permanent IETF technical workaround for a temporary 
financial problem.

In 5 to 10 years time it is unlikely anybody would have a need or want PSP in 
this scenario, because all SRv6 control and SRv6 forwarding planes in all SR 
enabled networks would be congruent.

Regards,
Mark.


These devices can support encapsulation and decapsulation with
sufficiently arbitrary content.
These devices comply with the RFC 8200 requirement for ignoring routing
headers by punting those to the slow path.  With significant performance
penalty.
   --  Presumably, these devices 

Re: [spring] WGLC - draft-ietf-spring-srv6-network-programming

[Pengshuping (Peng Shuping)]

Hi Fernando,

My understanding on the Consensus expressed by Martin is that the SPRING WG has 
reached consensus on the direction of progressing this draft including what to 
improve in the draft and how to improve. What was left is just to update the 
text.

Now a new version of the draft has been posted with the new text based on the 
suggestions posted over the mailing list. You could have a further review and 
see whether you have any comments.

Best regards,
Shuping


-Original Message-
From: spring [mailto:spring-boun...@ietf.org] On Behalf Of Fernando Gont
Sent: Thursday, March 5, 2020 8:15 AM
To: Martin Vigoureux ; spring@ietf.org
Cc: 'i...@ietf.org' 
Subject: Re: [spring] WGLC - draft-ietf-spring-srv6-network-programming

Martin,

On 4/3/20 18:02, Martin Vigoureux wrote:
> WG,
> 
> I wanted to bring more context to my decision.
> 
> This document has received a lot of valuable reviews and comments 
> which improved it. That served me as a base to determine consensus on 
> the overall document.
> 
> The point I'd like to insist on is the one I was mentioning in my 
> previous e-mail. In my view, the remaining prominent discussion (and
> tension) point was about the text of 8200, its implications on the 
> optional PSP capability, and the ramifications of it.
> I have determined there is rough consensus, in SPRING, on the way to 
> read the specific text of 8200, but also that certain aspects go 
> beyond SPRING and would benefit from being discussed with a wider community.
> 
> 
> I'd like to remind that this was a WG Chair level decision. Indeed, 
> Bruno still needs to produce the shepherd write-up and submit the 
> document for publication.

May I ask what's the status of this I-D?  -

On one hand, both Bruno and you declared consensus to move it forward. 
On another hand, the authors keep making changes to address comments
(good) so what the wg will ship will be very different from the document on 
which you claimed consensus. Besides, the datatracker lists the document as "in 
WGLC", as opposed to "Waiting for WG Chair Go-Ahead" or "WG Consensus: Waiting 
for Write-Up".

Last, but not least, are you planning to do a second WGLC?

Thanks,
--
Fernando Gont
e-mail: ferna...@gont.com.ar || fg...@si6networks.com PGP Fingerprint: 7809 
84F5 322E 45C7 F1C9 3945 96EE A9EF D076 FFF1



___
spring mailing list
spring@ietf.org
https://www.ietf.org/mailman/listinfo/spring

___
spring mailing list
spring@ietf.org
https://www.ietf.org/mailman/listinfo/spring

Re: [spring] WG adoption request for draft-gandhi-spring-twamp-srpm {WAS: WG status - pending calls

[Pengshuping (Peng Shuping)]

Hi Rakesh,

The request has been recorded in the wiki.
https://trac.ietf.org/trac/spring/wiki/WikiStart

Best regards,
Shuping

From: spring [mailto:spring-boun...@ietf.org] On Behalf Of Rakesh Gandhi
Sent: Friday, January 3, 2020 3:58 AM
To: bruno.decra...@orange.com
Cc: SPRING WG List 
Subject: Re: [spring] WG adoption request for draft-gandhi-spring-twamp-srpm 
{WAS: WG status - pending calls

Hi Chairs, WG,

The draft was presented at the last IETF meeting and there was a good support 
in the session for WG adoption. We like to formally request WG adoption for 
this draft:

draft-gandhi-spring-twamp-srpm

Thanks,
Rakesh

On Fri, Dec 20, 2019 at 11:58 AM 
mailto:bruno.decra...@orange.com>> wrote:
Hi SPRING,

A number of authors have asked for their document to be adopted or last called.
Chairs have some backlog on this. The WG has also been pretty busy over the 
last 6 months with a set of subjects triggering many emails and this is not 
always the best time to ask for review of additional documents (versus short 
‘+1’).
Chairs/WG will work on this calls in 2020. In the meantime, for a better 
transparency, Shuping has been kind enough to track this on the wiki 
https://trac.ietf.org/trac/spring Thank you Shuping.
If your document is missing from the list of pending calls for adoption/last 
call, please send an email to the chairs or to the list, as you wish.
Otherwise, your request is been tracked.

Content of this page is subject to change. In particular, the goal is not to 
duplicate the information already tracked in the ietf datatracker. E.g. 
https://datatracker.ietf.org/doc/search?name===on=group=spring

I take this opportunity to wish everyone Merry Christmas, an Happy New Year and 
possibly Happy Holidays.
--Bruno



_



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.
___
spring mailing list
spring@ietf.org
https://www.ietf.org/mailman/listinfo/spring
___
spring mailing list
spring@ietf.org
https://www.ietf.org/mailman/listinfo/spring

Re: [spring] draft-ietf-spring-srv6-network-programming - 2 week Early Allocation Call

[Pengshuping (Peng Shuping)]

Hi Chairs, all,

I support this early allocation.

I agree that the criteria for the early allocation of this code point are met, 
and there are already multiple deployments worldwide.
https://tools.ietf.org/html/draft-matsushima-spring-srv6-deployment-status-04
https://tools.ietf.org/html/draft-tian-spring-srv6-deployment-consideration-00

Best regards,
Shuping


From: spring [mailto:spring-boun...@ietf.org] On Behalf Of 
bruno.decra...@orange.com
Sent: Friday, December 20, 2019 12:54 AM
To: SPRING WG 
Subject: [spring] draft-ietf-spring-srv6-network-programming - 2 week Early 
Allocation Call


Hi SPRING WG,



This begins a 2 week Early Allocation call for a "Ethernet" value from the 
"Protocol Numbers" registry.

https://tools.ietf.org/html/draft-ietf-spring-srv6-network-programming-07#section-9.1

https://tools.ietf.org/html/draft-ietf-spring-srv6-network-programming-07#section-5.3

https://www.iana.org/assignments/protocol-numbers/protocol-numbers.xhtml



In parallel of the Working Group Last Call which is currently running, the 
authors are requesting for early code point allocation from IANA as 
implementations are under way.



The criteria for early allocation are:

   a.  The code points must be from a space designated as "RFC

   Required", "IETF Review", or "Standards Action".  Additionally,

   requests for early assignment of code points from a

   "Specification Required" registry are allowed if the

   specification will be published as an RFC.



   b.  The format, semantics, processing, and other rules related to

   handling the protocol entities defined by the code points

   (henceforth called "specifications") must be adequately described

   in an Internet-Draft.



   c.  The specifications of these code points must be stable; i.e., if

   there is a change, implementations based on the earlier and later

   specifications must be seamlessly interoperable.



   d.  The Working Group chairs and Area Directors (ADs) judge that

   there is sufficient interest in the community for early (pre-RFC)

   implementation and deployment, or that failure to make an early

   allocation might lead to contention for the code point in the

   field.

https://tools.ietf.org/html/rfc7120#section-2



I believe the above conditions are met. (minus the AD judgement which is 
further down in the process)



As a reminder, this topic has mainly been discussed following IETF 105 
(Montréal) both during the meeting and on the mailing list.

During IETF 106 it has been discussed in the IntArea WG. 
https://datatracker.ietf.org/meeting/106/proceedings#intarea



Note that this code point is not to be specific to SRv6. Depending on AD 
guidance, this specific code point even be moved from 
draft-ietf-spring-srv6-network-programming into a specific 1 page draft.



If you support early adoption,  please include "support" along with any 
comments about the draft's technical solution.



If you do not support early allocation, please include "no support" in your 
email and indicate why.



Thank you,

--Bruno


_



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.
___
spring mailing list
spring@ietf.org
https://www.ietf.org/mailman/listinfo/spring

[spring] 答复: IPR Poll: draft-voyer-spring-sr-replication-segment

[Pengshuping (Peng Shuping)]

Dear Chairs, all,

We have received IPR confirmations from all authors and contributors of this 
draft.

Merry Christmas and Happy New Year!

Best regards,
Shuping


发件人: spring [mailto:spring-boun...@ietf.org] 代表 bruno.decra...@orange.com
发送时间: 2019年11月13日 1:04
收件人: draft-voyer-spring-sr-replication-segm...@ietf.org
抄送: spring 
主题: [spring] IPR Poll: draft-voyer-spring-sr-replication-segment

Hi Authors, SPRING WG,

Authors of draft-voyer-spring-sr-replication-segment [1] have asked for WG 
adoption.
Before the call for working group adoption we would like to poll for IPR.

If you are aware of IPR that applies to 
draft-voyer-spring-sr-replication-segment please respond to this email.
If you are aware of IPR, please indicate whether it has been disclosed in
accordance to the IETF IPR rules (detailed are described in RFCs 3979, 4879, 
3669 and 5378).

If you are an *author or contributor* please respond to this email, on the 
SPRING mailing list,
regardless of whether or not you're aware of any IPR. If you are not an
author or contributor, please explicitly respond only if you're aware of
IPR that has not yet been disclosed.

This document will not advance into the working group until such time as
we have received IPR confirmations from all authors and contributors.

Thanks!

Rob & Bruno


[1] https://tools.ietf.org/html/draft-voyer-spring-sr-replication-segment-00


_



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.
___
spring mailing list
spring@ietf.org
https://www.ietf.org/mailman/listinfo/spring

[spring] 答复: WG status - pending calls

[Pengshuping (Peng Shuping)]

Hi Ron,

It has been added.

Shuping

发件人: Ron Bonica [mailto:rbon...@juniper.net]
发送时间: 2019年12月24日 4:17
收件人: Pengshuping (Peng Shuping) ; Jeff Tantsura 
; SPRING WG List 
主题: RE: [spring] WG status - pending calls

Hi Shuping,

My mistake. Please register draft-bonica-spring-sr-mapped-six under “Documents 
requested by authors for WG adoption”.

 Ron




Juniper Business Use Only
From: spring mailto:spring-boun...@ietf.org>> On 
Behalf Of Pengshuping (Peng Shuping)
Sent: Saturday, December 21, 2019 9:41 PM
To: Jeff Tantsura mailto:jefftant.i...@gmail.com>>; 
SPRING WG List mailto:spring@ietf.org>>
Subject: Re: [spring] WG status - pending calls

Dear Ron, Jeff,

Do you mean to put under the "Documents placed in state "Candidate for WG 
adoption""?

Please note that in the current wiki, this item is only used to place the draft 
when its state is changed to the "Candidate for WG adoption". If I have missed 
such state change email for your draft, please do let me know. Thank you!

Merry Christmas and Happy New Year!

Best regards
Shuping


发件人：Jeff Tantsura mailto:jefftant.i...@gmail.com>>
收件人：SPRING WG List mailto:spring@ietf.org>>
时 间：2019-12-22 06:27:14
主 题：Re: [spring] WG status - pending calls

Shuping,

Please also add draft-anand-spring-poi-sr-08.

Thanks and happy holidays!

Regards,
Jeff

On Dec 21, 2019, at 12:37, Ron Bonica 
mailto:rbonica=40juniper@dmarc.ietf.org>>
 wrote:

Shuping,

Please add draft-bonica-spring-sr-mapped-six as a candidate for adoption.

   Ron




Juniper Business Use Only
From: spring mailto:spring-boun...@ietf.org>> On 
Behalf Of bruno.decra...@orange.com<mailto:bruno.decra...@orange.com>
Sent: Friday, December 20, 2019 11:58 AM
To: 'SPRING WG List' mailto:spring@ietf.org>>
Subject: [spring] WG status - pending calls

Hi SPRING,

A number of authors have asked for their document to be adopted or last called.
Chairs have some backlog on this. The WG has also been pretty busy over the 
last 6 months with a set of subjects triggering many emails and this is not 
always the best time to ask for review of additional documents (versus short 
‘+1’).
Chairs/WG will work on this calls in 2020. In the meantime, for a better 
transparency, Shuping has been kind enough to track this on the wiki 
https://trac.ietf.org/trac/spring<https://urldefense.com/v3/__https:/trac.ietf.org/trac/spring__;!!NEt6yMaO-gk!TG5-O8kd2fVPxVkN2IRvaGLVHkQ6cSPlDhE0xNBRC23Go4mlw3dAbBCJR3JqSYly$>
 Thank you Shuping.
If your document is missing from the list of pending calls for adoption/last 
call, please send an email to the chairs or to the list, as you wish.
Otherwise, your request is been tracked.

Content of this page is subject to change. In particular, the goal is not to 
duplicate the information already tracked in the ietf datatracker. E.g. 
https://datatracker.ietf.org/doc/search?name===on=group=spring<https://urldefense.com/v3/__https:/datatracker.ietf.org/doc/search?name===on=group=spring__;!!NEt6yMaO-gk!TG5-O8kd2fVPxVkN2IRvaGLVHkQ6cSPlDhE0xNBRC23Go4mlw3dAbBCJR469-5yL$>

I take this opportunity to wish everyone Merry Christmas, an Happy New Year and 
possibly Happy Holidays.
--Bruno



_



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.
___
spring mailing list
spring@ietf.org<mailto:spring@ietf.org>
https://www.ietf.org/mailman/listinfo/spring
___
spring mailing list
spring@ietf.org
https://www.ietf.org/mailman/listinfo/spring

Re: [spring] WG status - pending calls

[Pengshuping (Peng Shuping)]

Dear Ron, Jeff,

Do you mean to put under the "Documents placed in state "Candidate for WG 
adoption""?

Please note that in the current wiki, this item is only used to place the draft 
when its state is changed to the "Candidate for WG adoption". If I have missed 
such state change email for your draft, please do let me know. Thank you!

Merry Christmas and Happy New Year!

Best regards
Shuping



发件人：Jeff Tantsura 
收件人：SPRING WG List 
时 间：2019-12-22 06:27:14
主 题：Re: [spring] WG status - pending calls

Shuping,

Please also add draft-anand-spring-poi-sr-08.

Thanks and happy holidays!

Regards,
Jeff

On Dec 21, 2019, at 12:37, Ron Bonica  
wrote:


Shuping,

Please add draft-bonica-spring-sr-mapped-six as a candidate for adoption.

   Ron




Juniper Business Use Only
From: spring  On Behalf Of bruno.decra...@orange.com
Sent: Friday, December 20, 2019 11:58 AM
To: 'SPRING WG List' 
Subject: [spring] WG status - pending calls

Hi SPRING,

A number of authors have asked for their document to be adopted or last called.
Chairs have some backlog on this. The WG has also been pretty busy over the 
last 6 months with a set of subjects triggering many emails and this is not 
always the best time to ask for review of additional documents (versus short 
‘+1’).
Chairs/WG will work on this calls in 2020. In the meantime, for a better 
transparency, Shuping has been kind enough to track this on the wiki 
https://trac.ietf.org/trac/spring
 Thank you Shuping.
If your document is missing from the list of pending calls for adoption/last 
call, please send an email to the chairs or to the list, as you wish.
Otherwise, your request is been tracked.

Content of this page is subject to change. In particular, the goal is not to 
duplicate the information already tracked in the ietf datatracker. E.g. 
https://datatracker.ietf.org/doc/search?name===on=group=spring

I take this opportunity to wish everyone Merry Christmas, an Happy New Year and 
possibly Happy Holidays.
--Bruno



_



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.

___
spring mailing list
spring@ietf.org
https://www.ietf.org/mailman/listinfo/spring
___
spring mailing list
spring@ietf.org
https://www.ietf.org/mailman/listinfo/spring

[spring] 答复: 答复: IPR Poll: draft-voyer-spring-sr-replication-segment

[Pengshuping (Peng Shuping)]

Hi Rishabh,

Thank you for letting me know that both of you have replied. 

Best regards, 
Shuping 


-邮件原件-
发件人: Rishabh Parekh [mailto:risha...@gmail.com] 
发送时间: 2019年12月20日 13:46
收件人: Pengshuping (Peng Shuping) 
抄送: bruno.decra...@orange.com; 
draft-voyer-spring-sr-replication-segm...@ietf.org; spring 
主题: Re: [spring] 答复: IPR Poll: draft-voyer-spring-sr-replication-segment

Shuping,
Jeffrey Zhang has also replied on 13th Nov.


https://mailarchive.ietf.org/arch/msg/spring/bxoZuvyAY7X_roxnOULvqc1Dd-Q

-Rishabh

On Thu, Dec 19, 2019 at 7:52 PM Pengshuping (Peng Shuping) 
 wrote:
>
> Hi all,
>
>
>
> A reminder for this IPR Poll.
>
>
>
> The missing authors: R. Parekh, Z. Zhang
>
> The missing contributors: Kurtis Gillis
>
>
>
> Please let me know if you have already replied. Thank you!
>
>
>
> Best regards,
>
> Shuping
>
>
>
>
>
> 发件人: spring [mailto:spring-boun...@ietf.org] 代表 
> bruno.decra...@orange.com
> 发送时间: 2019年11月13日 1:04
> 收件人: draft-voyer-spring-sr-replication-segm...@ietf.org
> 抄送: spring 
> 主题: [spring] IPR Poll: draft-voyer-spring-sr-replication-segment
>
>
>
> Hi Authors, SPRING WG,
>
>
>
> Authors of draft-voyer-spring-sr-replication-segment [1] have asked for WG 
> adoption.
>
> Before the call for working group adoption we would like to poll for IPR.
>
>
>
> If you are aware of IPR that applies to 
> draft-voyer-spring-sr-replication-segment please respond to this email.
>
> If you are aware of IPR, please indicate whether it has been disclosed 
> in
>
> accordance to the IETF IPR rules (detailed are described in RFCs 3979, 4879, 
> 3669 and 5378).
>
>
>
> If you are an *author or contributor* please respond to this email, on 
> the SPRING mailing list,
>
> regardless of whether or not you're aware of any IPR. If you are not 
> an
>
> author or contributor, please explicitly respond only if you're aware 
> of
>
> IPR that has not yet been disclosed.
>
>
>
> This document will not advance into the working group until such time 
> as
>
> we have received IPR confirmations from all authors and contributors.
>
>
>
> Thanks!
>
>
>
> Rob & Bruno
>
>
>
>
>
> [1] 
> https://tools.ietf.org/html/draft-voyer-spring-sr-replication-segment-
> 00
>
>
>
> __
> ___
>
>
>
> 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.
>
> ___
> spring mailing list
> spring@ietf.org
> https://www.ietf.org/mailman/listinfo/spring
___
spring mailing list
spring@ietf.org
https://www.ietf.org/mailman/listinfo/spring

[spring] 答复: IPR Poll: draft-voyer-spring-sr-replication-segment

[Pengshuping (Peng Shuping)]

Hi all,

A reminder for this IPR Poll.

The missing authors: R. Parekh, Z. Zhang
The missing contributors: Kurtis Gillis

Please let me know if you have already replied. Thank you!

Best regards,
Shuping


发件人: spring [mailto:spring-boun...@ietf.org] 代表 bruno.decra...@orange.com
发送时间: 2019年11月13日 1:04
收件人: draft-voyer-spring-sr-replication-segm...@ietf.org
抄送: spring 
主题: [spring] IPR Poll: draft-voyer-spring-sr-replication-segment

Hi Authors, SPRING WG,

Authors of draft-voyer-spring-sr-replication-segment [1] have asked for WG 
adoption.
Before the call for working group adoption we would like to poll for IPR.

If you are aware of IPR that applies to 
draft-voyer-spring-sr-replication-segment please respond to this email.
If you are aware of IPR, please indicate whether it has been disclosed in
accordance to the IETF IPR rules (detailed are described in RFCs 3979, 4879, 
3669 and 5378).

If you are an *author or contributor* please respond to this email, on the 
SPRING mailing list,
regardless of whether or not you're aware of any IPR. If you are not an
author or contributor, please explicitly respond only if you're aware of
IPR that has not yet been disclosed.

This document will not advance into the working group until such time as
we have received IPR confirmations from all authors and contributors.

Thanks!

Rob & Bruno


[1] https://tools.ietf.org/html/draft-voyer-spring-sr-replication-segment-00


_



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.
___
spring mailing list
spring@ietf.org
https://www.ietf.org/mailman/listinfo/spring

[spring] 答复: IPR poll for draft-ietf-spring-srv6-network-programming

[Pengshuping (Peng Shuping)]

Hi all, 

A reminder for this IPR Poll. 

The missing authors: P. Camarillo
The missing contributors: Prem Jonnalagadda, Milad Sharif, Gaurav Naik, Arthi 
Ayyangar

Please let me know if you have already replied. Thank you! 

Best regards, 
Shuping



-邮件原件-
发件人: spring [mailto:spring-boun...@ietf.org] 代表 bruno.decra...@orange.com
发送时间: 2019年12月6日 0:50
收件人: 'SPRING WG List' ; 
draft-ietf-spring-srv6-network-programming 

主题: [spring] IPR poll for draft-ietf-spring-srv6-network-programming

Hi SPRING WG,

In parallel to the WGLC for draft-ietf-spring-srv6-network-programming, we 
would like to poll for IPR.

If you are aware of IPR that applies to 
draft-ietf-spring-srv6-network-programming [1] please respond to this email. If 
you are aware of IPR, please indicate whether it has been disclosed in 
accordance with IETF IPR rules (RFCs 3979, 4879, 3669 and 5378 provide more 
details).

If you are an *author or contributor* please respond to this email regardless 
of whether or not you're aware of any IPR. 

This document will not advance until IPR confirmations have been received from 
all authors and contributors.

Thank you,
Bruno

[1] https://tools.ietf.org/html/draft-ietf-spring-srv6-network-programming-05


_

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.

___
spring mailing list
spring@ietf.org
https://www.ietf.org/mailman/listinfo/spring
___
spring mailing list
spring@ietf.org
https://www.ietf.org/mailman/listinfo/spring

[spring] Minutes for SPRING sessions at IETF 106 Singapore

[Pengshuping (Peng Shuping)]

Hi all,



The minutes for the two SPRING sessions at IETF 106 can be found at:


https://datatracker.ietf.org/meeting/106/materials/minutes-106-spring-01.txt

Please let me know if any changes may be needed. Thank you!

Regards,

Shuping

___
spring mailing list
spring@ietf.org
https://www.ietf.org/mailman/listinfo/spring

[spring] IETF 106 SPRING WG Agenda uploaded

[Pengshuping (Peng Shuping)]

Hi all,

The SPRING WG agenda is now available and can be found at:
https://datatracker.ietf.org/meeting/106/materials/agenda-106-spring-11

Any comments on the current agenda please inform the Chairs.

Please note that we have got two sessions this time.
To the presenters, please upload your slides to the corresponding session at:
https://datatracker.ietf.org/meeting/106/session/spring

For the presenters in the Monday morning session, it would be good if you could 
upload your slides no later than Sunday 2PM (Singapore time). Thank you!

Looking forwards to meeting you all in Singapore. :)

Best Regards,
Shuping
___
spring mailing list
spring@ietf.org
https://www.ietf.org/mailman/listinfo/spring

Re: [spring] New SPRING WG Secretary

[Pengshuping (Peng Shuping)]

Dear Chairs, all, 

It is a great honor and pleasure for me to be involved as the WG Secretary. I 
will do my best to serve in this role by helping our Chairs consolidate the 
work in the group and facilitating the involvement process for our colleagues 
in the community. 

Thank you! 

Best regards, 
Shuping 



-Original Message-
From: bruno.decra...@orange.com [mailto:bruno.decra...@orange.com] 
Sent: Saturday, November 09, 2019 2:35 AM
To: SPRING WG List 
Cc: Pengshuping (Peng Shuping) 
Subject: New SPRING WG Secretary

Folks,

We are happy to have Shuping Peng as our working group secretary.

Welcome, Shuping.


--Rob, Bruno


_

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.

___
spring mailing list
spring@ietf.org
https://www.ietf.org/mailman/listinfo/spring

Re: [spring] SPRING SRv6 Deployment Status draft

[Pengshuping (Peng Shuping)]

Hi Satoru, Zafar,

We are announcing another deployment of SRv6. MTN has deployed SRv6, as 
described below.
Can you please also update the SRv6 deployment draft with the following details?

“
As part of the complete mobile IP network, Uganda MTN has deployed a SRv6 
network that carries all services in its backbone.
The following SRv6 features have been deployed:
o A Segment Routing Header 
[I-D.ietf-6man-segment-routing-header]
 based data plane.
o End, End.X, End.DT4, End.DX2, End.dt2u, End.dt2m functions as per 
[I-D.ietf-spring-srv6-network-programming].
o BGP VPN SRv6 extensions 
[I-D.dawra-bess-srv6-services].
o Topology Independent (TI-LFA) Fast Reroute mechanisms leveraging SRv6 for the 
O(50msec)  protection against node and link, as described in 
[I-D.ietf-rtgwg-segment-routing-ti-lfa].
o BGP Prefix Independent Convergence (PIC) core and edge 
[I-D.ietf-rtgwg-bgp-pic].
o Support for Ping and Traceroute as defined in [I-D.ietf-6man-spring-srv6-oam].
”

Best Regards,
Shuping




From: spring [mailto:spring-boun...@ietf.org] On Behalf Of 松嶋聡
Sent: Wednesday, November 06, 2019 6:54 PM
To: David Melman 
Cc: spring@ietf.org; Zafar Ali (zali) 
Subject: Re: [spring] SPRING SRv6 Deployment Status draft

Thanks David, that’s a good news !

Yes we’ll capture it in the next revision.

Best regards,
Sent from my iPhone


2019/11/06 18:19、David Melman 
mailto:davi...@marvell.com>>のメール:

Hi Zefar, Satoru.

Marvell’s Prestera Falcon CX 8500 family of Ethernet switches supports SRv6 
features, including processing of the SRH as described in 
[I-D.ietf-6man-segment-routing-header].

In the next draft of  
https://datatracker.ietf.org/doc/draft-matsushima-spring-srv6-deployment-status/,
 please add to the section “Additional Routing platforms”:


  *   Marvell

 *   Hardware implementation in the Prestera Falcon CX 8500 family of 
Ethernet switches

Thanks!
David Melman
___
spring mailing list
spring@ietf.org
https://www.ietf.org/mailman/listinfo/spring

[spring] 答复: IETF105 APN6 Side Meeting, Thursday Moring @Notre Dame Room

[Pengshuping (Peng Shuping)]

Dear all,

We had a very productive APN6 side meeting this morning and a lot of fruitful 
discussions.

FYI, we have uploaded all the slides presented at the side meeting as well as 
the meeting minutes to the Github.

https://github.com/shupingpeng/IETF105-Side-Meeting-APN6

We look forwards to more discussions with you.

Best regards,
Shuping



发件人: Lizhenbin
发送时间: 2019年7月23日 22:27
收件人: 6man WG; spring@ietf.org
抄送: Pengshuping (Peng Shuping)
主题: Re: IETF105 APN6 Side Meeting, Thursday Moring @Notre Dame Room


Dear all,

The agenda for the side meeting was updated as follows. We look forwards to 
your presence for a very productive discussion.



Best Regards,

Zhenbin (Robin)



Room: Notre Dame - Thursday

Occupancy: up to 50 attendees
Configuration: classroom
Location: ​Notre 
Dame<https://datatracker.ietf.org/meeting/105/floor-plan#2nd-floor>
Meeting NameAreaContact Meeting Description More information

08:30   APN66man/spring Zhenbin Li  APP-Aware IPv6/SRv6 Networking

Tentative Agenda:

  1.  Co-chairs
  2.  Problem Statements and Requirements

  1.  Topics

Part I: App-aware Info Conveying

  *   Application-aware IPv6 Networking Framework
  *   FAST: Firewall and Service Tickets
  *   SRH Metadata for Simplified Firewall

Part II: App-aware Services

  *   Detnet
  *   Path Segment
  *   IFIT/IOAM

  1.  Discussions





​https://datatracker.ietf.org/doc/draft-li-6man-app-aware-ipv6-network/<https://datatracker.ietf.org/doc/draft-li-6man-app-aware-ipv6-network/>
​https://datatracker.ietf.org/doc/draft-herbert-fast/<https://datatracker.ietf.org/doc/draft-herbert-fast/>
​https://datatracker.ietf.org/doc/draft-guichard-spring-srv6-simplified-firewall/<https://datatracker.ietf.org/doc/draft-guichard-spring-srv6-simplified-firewall/>
​https://datatracker.ietf.org/doc/draft-li-6man-ipv6-sfc-ifit/<https://datatracker.ietf.org/doc/draft-li-6man-ipv6-sfc-ifit/>
​https://datatracker.ietf.org/doc/draft-li-6man-srv6-path-segment-encap/<https://datatracker.ietf.org/doc/draft-li-6man-srv6-path-segment-encap/>
​https://datatracker.ietf.org/doc/draft-geng-spring-srv6-for-detnet<https://datatracker.ietf.org/doc/draft-geng-spring-srv6-for-detnet>





____________
发件人: Pengshuping (Peng Shuping)
发送时间: 2019年7月17日 11:18
收件人: 6man WG; spring@ietf.org
抄送: Lizhenbin
主题: IETF105 APN6 Side Meeting, Thursday Moring @Notre Dame Room

Dear all,
We are planning a Application-aware IPv6 Networking (APN6) Side meeting at this 
IETF Thursday morning @Notre Dame Room. Please find the meeting information 
(incl. Agenda) below and more details on the topic from the referenced drafts.
As the Internet is progressing, the decoupling of applications and network 
transport causes the service provider network pipelined which becomes the 
bottleneck of the network service development.  A multitude of applications are 
being carried over the IP network which have varying needs.  However the 
network is hard to learn the applications' service requirements which cause it 
is difficult to provide truly fine-granular traffic operations for the 
applications and guarantee their SLA requirements.  The Application-aware IPv6 
Networking (APN6) is to make use of IPv6 extensions header to convey the 
application related information including its requirements along with the 
packet to the network so to facilitate the service deployment and network 
resources adjustment.
We look forwards to your presence for a very productive discussion.
https://trac.ietf.org/trac/ietf/meeting/wiki/105sidemeetings
Room: Notre Dame - Thursday

Occupancy: up to 50 attendees
Configuration: classroom
Location: ​Notre 
Dame<https://datatracker.ietf.org/meeting/105/floor-plan#2nd-floor>

Meeting Name

Area

Contact

Meeting Description

More information

08:30

APN6

6man/spring

Zhenbin Li

APP-Aware IPv6/SRv6 Networking


Tentative Agenda:

  1.  Problem Statement
  2.  Relevant IETF work

  *   Application-aware IPv6 Networking
  *   FAST: Firewall and Service Tickets
  *   Path Segment
  *   IFIT/IOAM
  *   Detnet

  1.  Use cases
  2.  Discussions

​https://datatracker.ietf.org/doc/draft-li-cross-ietf-area-work/<https://datatracker.ietf.org/doc/draft-li-cross-ietf-area-work/>
​https://datatracker.ietf.org/doc/draft-li-6man-app-aware-ipv6-network/<https://datatracker.ietf.org/doc/draft-li-6man-app-aware-ipv6-network/>
​https://datatracker.ietf.org/doc/draft-li-6man-enhanced-extension-header/<https://datatracker.ietf.org/doc/draft-li-6man-enhanced-extension-header/>
​https://datatracker.ietf.org/doc/draft-li-6man-ipv6-sfc-ifit/<https://datatracker.ietf.org/doc/draft-li-6man-ipv6-sfc-ifit/>
​https://datatracker.ietf.org/doc/draft-li-6man-srv6-path-segment-encap/<https://datatracker.ietf.org/doc/draft-li-6man-srv6-path-segment-encap/>
​https://datatracker.ietf.org/doc/draft-geng-spring-srv6-for-det

[spring] IETF105 APN6 Side Meeting, Thursday Moring @Notre Dame Room

[Pengshuping (Peng Shuping)]

Dear all,
We are planning a Application-aware IPv6 Networking (APN6) Side meeting at this 
IETF Thursday morning @Notre Dame Room. Please find the meeting information 
(incl. Agenda) below and more details on the topic from the referenced drafts.
As the Internet is progressing, the decoupling of applications and network 
transport causes the service provider network pipelined which becomes the 
bottleneck of the network service development.  A multitude of applications are 
being carried over the IP network which have varying needs.  However the 
network is hard to learn the applications' service requirements which cause it 
is difficult to provide truly fine-granular traffic operations for the 
applications and guarantee their SLA requirements.  The Application-aware IPv6 
Networking (APN6) is to make use of IPv6 extensions header to convey the 
application related information including its requirements along with the 
packet to the network so to facilitate the service deployment and network 
resources adjustment.
We look forwards to your presence for a very productive discussion.
https://trac.ietf.org/trac/ietf/meeting/wiki/105sidemeetings
Room: Notre Dame - Thursday

Occupancy: up to 50 attendees
Configuration: classroom
Location: ​Notre 
Dame

Meeting Name

Area

Contact

Meeting Description

More information

08:30

APN6

6man/spring

Zhenbin Li

APP-Aware IPv6/SRv6 Networking


Tentative Agenda:

  1.  Problem Statement
  2.  Relevant IETF work

  *   Application-aware IPv6 Networking
  *   FAST: Firewall and Service Tickets
  *   Path Segment
  *   IFIT/IOAM
  *   Detnet

  1.  Use cases
  2.  Discussions

​https://datatracker.ietf.org/doc/draft-li-cross-ietf-area-work/
​https://datatracker.ietf.org/doc/draft-li-6man-app-aware-ipv6-network/
​https://datatracker.ietf.org/doc/draft-li-6man-enhanced-extension-header/
​https://datatracker.ietf.org/doc/draft-li-6man-ipv6-sfc-ifit/
​https://datatracker.ietf.org/doc/draft-li-6man-srv6-path-segment-encap/
​https://datatracker.ietf.org/doc/draft-geng-spring-srv6-for-detnet

09:45

NOT AVAILABLE

NOT AVAILABLE

NOT AVAILABLE

NOT AVAILABLE

NOT AVAILABLE



Best regards,
Shuping
___
spring mailing list
spring@ietf.org
https://www.ietf.org/mailman/listinfo/spring

[spring] New Version Notification for draft-peng-spring-srv6-compatibility-01.txt

[Pengshuping (Peng Shuping)]

Dear all, 

We have submitted the following draft which is related to the SRv6 network 
migration. Your review and comments are very welcomed. Thank you!

https://datatracker.ietf.org/doc/draft-peng-spring-srv6-compatibility/

Kind Regards, 
Shuping


-Original Message-
From: internet-dra...@ietf.org [mailto:internet-dra...@ietf.org] 
Sent: Monday, July 08, 2019 6:07 PM
Subject: New Version Notification for 
draft-peng-spring-srv6-compatibility-01.txt


A new version of I-D, draft-peng-spring-srv6-compatibility-01.txt
has been successfully submitted by Shuping Peng and posted to the IETF 
repository.

Name:   draft-peng-spring-srv6-compatibility
Revision:   01
Title:  SRv6 Compatibility with Legacy Devices
Document date:  2019-07-08
Group:  Individual Submission
Pages:  10

Abstract:
   When deploying SRv6 on legacy devices, there are some compatibility
   challenges such as the support of SRH processing.

   This document identifies some of the major challenges, and provides
   solutions that are able to mitigate those challenges and smooth the
   migration towards SRv6 deployment.


___
spring mailing list
spring@ietf.org
https://www.ietf.org/mailman/listinfo/spring

[spring] New Version Notification for draft-li-6man-app-aware-ipv6-network-00.txt

[Pengshuping (Peng Shuping)]

Dear all, 

We have submitted/updated the following draft. Your review and comments are 
very welcomed. Thank you! 
https://datatracker.ietf.org/doc/draft-li-6man-app-aware-ipv6-network/

Kind Regards, 
Shuping 



-Original Message-
From: internet-dra...@ietf.org [mailto:internet-dra...@ietf.org] 
Sent: Monday, July 08, 2019 11:17 PM
Subject: New Version Notification for 
draft-li-6man-app-aware-ipv6-network-00.txt

A new version of I-D, draft-li-6man-app-aware-ipv6-network-00.txt
has been successfully submitted by Shuping Peng and posted to the IETF 
repository.

Name:   draft-li-6man-app-aware-ipv6-network
Revision:   00
Title:  Application-aware IPv6 Networking
Document date:  2019-07-08
Group:  Individual Submission
Pages:  14

Abstract:
   A multitude of applications are carried over the network, which have
   varying needs for network bandwidth, latency, jitter, and packet
   loss, etc.  Some applications such as online gaming and live video
   streaming have very demanding network requirements thereof require
   special treatments in the network.  However, in current networks, the
   network and applications are decoupled, that is, the network is not
   aware of the applications' requirements in a finer granularity.
   Therefore, it is difficult to provide truly fine-granular traffic
   operations for the applications and guarantee their SLA requirements.

   This document proposes a new framework, named Application-aware IPv6
   Networking, and also the solution to guarantee SLA for applications,
   which makes use of IPv6 extensions header in order to convey the
   application related information including its requirements along with
   the packet to the network so to facilitate the service deployment and
   network resources adjustment.  Then, it defines the application-aware
   options which can be used in the different IPv6 extension headers for
   the purpose.



  


Please note that it may take a couple of minutes from the time of submission 
until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat

___
spring mailing list
spring@ietf.org
https://www.ietf.org/mailman/listinfo/spring

Re: [spring] Working Group Adoption Call for draft-filsfils-spring-srv6-network-programming

[Pengshuping (Peng Shuping)]

Support the WG adoption.

Thanks.
Shuping

发件人： bruno.decraenemailto:bruno.decra...@orange.com>>
收件人： SPRING WGmailto:spring@ietf.org>>
抄送： 
draft-filsfils-spring-srv6-network-programmingmailto:draft-filsfils-spring-srv6-network-programm...@ietf.org>>
主题： [spring] Working Group Adoption Call for 
draft-filsfils-spring-srv6-network-programming
时间： 2019-03-14 02:50:06


Hi SPRING WG,



This email initiates a three week call for working group adoption for 
draft-filsfils-spring-srv6-network-programming. (Three weeks to account for the 
IETF week)



Please indicate your support, comments, or objection, for adopting this draft 
as a working group item by April, 3rd, 2019 (aka 2019-04-03)

We are particularly interested in hearing from working group members that are 
not co-authors of this draft.



We are also looking for volunteers who would be ready to perform a technical 
review of this work at some later stage, such as before or during WG the last 
call.



In parallel to this adoption call, I will send an IPR call for this document. 
We will need all authors and contributors to confirm their IPR position on this 
document.

There is currently 1 IPR filled (2)



(1)  
https://tools.ietf.org/html/draft-filsfils-spring-srv6-network-programming-07

(2)  
https://datatracker.ietf.org/ipr/search/?id=draft-filsfils-spring-srv6-network-programming=draft





Thank you,

--Bruno & Rob.


_

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.

___
spring mailing list
spring@ietf.org
https://www.ietf.org/mailman/listinfo/spring

Re: [spring] IPR Poll for draft-filsfils-spring-srv6-network-programming

[Pengshuping (Peng Shuping)]

I am not aware of any IPR about the draft except the disclosed one.

Best regards,
Shuping

发件人： Pengshuping (Peng 
Shuping)mailto:pengshup...@huawei.com>>
收件人： 
bruno.decraenemailto:bruno.decra...@orange.com>>;SPRING
 WGmailto:spring@ietf.org>>
抄送： 
draft-filsfils-spring-srv6-network-programmingmailto:draft-filsfils-spring-srv6-network-programm...@ietf.org>>
主题： Re: [spring] IPR Poll for draft-filsfils-spring-srv6-network-programming
时间： 2019-03-14 10:01:07

Support the WG adoption.

Thanks,
Shuping

From: spring [mailto:spring-boun...@ietf.org] On Behalf Of 
bruno.decra...@orange.com
Sent: Thursday, March 14, 2019 2:50 AM
To: SPRING WG 
Cc: draft-filsfils-spring-srv6-network-programm...@ietf.org
Subject: [spring] IPR Poll for draft-filsfils-spring-srv6-network-programming


Hi authors, SPRING WG,



In parallel to the call for adoption for 
draft-filsfils-spring-srv6-network-programming (1), we would like to poll for 
IPR.



If you are aware of IPR that applies to 
draft-filsfils-spring-srv6-network-programming please respond to this email.

If you are aware of IPR, please indicate whether it has been disclosed in 
accordance with IETF IPR rules (RFCs 3979, 4879, 3669 and 5378 provide more 
details).



If you are an *author or contributor* please respond to this email regardless 
of whether or not you're aware of any IPR.

If you are not an author or contributor, please explicitly respond only if you 
are aware of IPR that has not yet been disclosed.



This document will not advance into the working group until IPR confirmations 
have been received from all authors and contributors.



Thank you,



(1)  
https://tools.ietf.org/html/draft-filsfils-spring-srv6-network-programming-07





--Bruno & Rob.


_



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.
___
spring mailing list
spring@ietf.org
https://www.ietf.org/mailman/listinfo/spring

Re: [spring] IPR Poll for draft-filsfils-spring-srv6-network-programming

[Pengshuping (Peng Shuping)]

Support the WG adoption.

Thanks,
Shuping

From: spring [mailto:spring-boun...@ietf.org] On Behalf Of 
bruno.decra...@orange.com
Sent: Thursday, March 14, 2019 2:50 AM
To: SPRING WG 
Cc: draft-filsfils-spring-srv6-network-programm...@ietf.org
Subject: [spring] IPR Poll for draft-filsfils-spring-srv6-network-programming


Hi authors, SPRING WG,



In parallel to the call for adoption for 
draft-filsfils-spring-srv6-network-programming (1), we would like to poll for 
IPR.



If you are aware of IPR that applies to 
draft-filsfils-spring-srv6-network-programming please respond to this email.

If you are aware of IPR, please indicate whether it has been disclosed in 
accordance with IETF IPR rules (RFCs 3979, 4879, 3669 and 5378 provide more 
details).



If you are an *author or contributor* please respond to this email regardless 
of whether or not you're aware of any IPR.

If you are not an author or contributor, please explicitly respond only if you 
are aware of IPR that has not yet been disclosed.



This document will not advance into the working group until IPR confirmations 
have been received from all authors and contributors.



Thank you,



(1)  
https://tools.ietf.org/html/draft-filsfils-spring-srv6-network-programming-07





--Bruno & Rob.


_



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.
___
spring mailing list
spring@ietf.org
https://www.ietf.org/mailman/listinfo/spring

[spring] 转发: New Version Notification for draft-peng-spring-srv6-compatibility-00.txt

[Pengshuping (Peng Shuping, IP Tech Dept)]

Dear WG, 

We have posted a new draft on SRv6 compatibility with legacy devices. 
https://www.ietf.org/internet-drafts/draft-peng-spring-srv6-compatibility-00.txt

Looking forwards to your comments. Thank you!  

Best Regards,
Shuping 


-邮件原件-
发件人: internet-dra...@ietf.org [mailto:internet-dra...@ietf.org] 
发送时间: 2018年10月22日 22:23
收件人: pengshuping ; Lizhenbin 
主题: New Version Notification for draft-peng-spring-srv6-compatibility-00.txt


A new version of I-D, draft-peng-spring-srv6-compatibility-00.txt
has been successfully submitted by Shuping Peng and posted to the IETF 
repository.

Name:   draft-peng-spring-srv6-compatibility
Revision:   00
Title:  SRv6 Compatibility with Legacy Devices
Document date:  2018-10-22
Group:  Individual Submission
Pages:  10
URL:
https://www.ietf.org/internet-drafts/draft-peng-spring-srv6-compatibility-00.txt
Status: 
https://datatracker.ietf.org/doc/draft-peng-spring-srv6-compatibility/
Htmlized:   
https://tools.ietf.org/html/draft-peng-spring-srv6-compatibility-00
Htmlized:   
https://datatracker.ietf.org/doc/html/draft-peng-spring-srv6-compatibility


Abstract:
   When deploying SRv6 on legacy devices, there are some compatibility
   challenges such as the support of SRH processing.  This document
   identifies some of the major challenges, and provides solutions that
   are able to mitigate those challenges and smooth the evolution
   towards SRv6 deployment.



  


Please note that it may take a couple of minutes from the time of submission 
until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat

___
spring mailing list
spring@ietf.org
https://www.ietf.org/mailman/listinfo/spring