Dear chairs and group,
may I ask about the status of
draft-filsfils-spring-segment-routing-policy-05?
With the rechartering discussion I got the impression that nobody was
doubting that this work belongs in the SPRING wg. Would it be ready for
a wg adoption call now?
Best regards, Martin
Am 03.05.18 um 09:21 schrieb bruno.decra...@orange.com:
Hi Xiaohu,
We’d like to first clarify the content of the new charter.
Best regards,
--Bruno
*From:*spring [mailto:spring-boun...@ietf.org] *On Behalf Of *???(??)
*Sent:* Thursday, May 03, 2018 6:07 AM
*To:* ???(??); SPRING WG List
*Subject:* Re: [spring] Request WG adoption for
draft-xuclad-spring-sr-service-chaining-01
Hi SPRING WG co-chairs,
I wonder what the current status of this WG adoption request.
Best regards,
Xiaohu
------------------------------------------------------------------
From:徐小虎(义先) <xiaohu....@alibaba-inc.com
<mailto:xiaohu....@alibaba-inc.com>>
Send Time:2018年4月4日(星期三) 09:45
To:SPRING WG List <spring@ietf.org <mailto:spring@ietf.org>>
Cc:s...@ietf.org <s...@ietf.org <mailto:s...@ietf.org>>
Subject:Request WG adoption for
draft-xuclad-spring-sr-service-chaining-01
Hi SPRING WG co-chairs,
We authors believe this draft
(https://tools.ietf.org/html/draft-xuclad-spring-sr-service-chaining-01)
has been stable enough and therefore we would like to request a WG
adoption call for it.
We believe this work belongs to SPRING WG since the concept of
service segment has been mentioned in the Segment Routing
architecture from day one and the approaches as described in this
draft are exactly to leverage the stateless source routing
capability of segment routing to achieve a stateless SFC. To some
extent, SFC can be looked as a special case of source routing as
it requires the selected traffic to traverse an ordered list of
service nodes.
We believe the SFC WG review is still needed after the adoption
since we still hope to reuse the NSH for some special purposes
(e.g., use it as a metadata container).
BTW, implementations based on this draft have existed, as noted in
section 8 of the draft.
Best regards,
Xiaohu (on behalf of coauthors)
_________________________________________________________________________________________________________________________
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
