Re: [spring] Small SID/Compressed SID Design Team

Hi Jim, Bruno & Joel

I was wondering if it would be possible to provide a brief synopsis or
debriefing of where we stand thus far with deliberations on Small SID /
Compression SID design team results.

Also an ETA for the WG as to when this project will be wrapped up and the
compression technique to be used with SRV6 finalized.

My suggestion is that with the finalized compression technique feature,  in
order to provide complete parity as well as transparency with SRv6,  but
also more importantly make it holistic as well as seamless the change to
operators, it would be good if this is made part of the base SRv6
architecture and not a separate add on patch or workaround separate feature
if possible.  This would make it as if SRv6 architecture had the
compression technique all along built into the architecture.  This would
overall be very positive for SRv6.  I think to accomplish this would
require updating the main SR architecture RFC 8402 and RFC 8754 and PGM
draft referencing the new compression technique as part of the inherent
architecture framework.

Kind Regards

Gyan

On Tue, Jun 30, 2020 at 12:30 PM James Guichard <
james.n.guichard@futurewei.com> wrote:

>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> Dear SPRING WG:
>
>
>
>
>
> The WG chairs have been working with the relevant ADs to determine what
> needs to be done to move the SPRING segment routing work related to IPv6
> along effectively. We are going to establish a design team as soon as
> possible, with a specific
>
> objective to look at the compression-related work.
>
>
>
>
>
> The design team charge is still being worked on, but roughly it will be
> tasked to agree on a requirements proposal to the WG and a comparison
> document to be evaluated by the WG.  To be clear, as is the normal case for
> the IETF, the design
>
> team outputs are input to the WG.  Their output will not become a WG
> document until the WG agrees to adopt it.  Also, these documents are for WG
> use.  It will be for future analysis as to whether it is useful to the
> larger community to publish them as RFCs.
>
>
>
>
>
> While we have various thoughts as to membership in the design team, we
> would like proposals for people we should include. We expect that there are
> more people that we "should" include than can make up an effective design
> time for the rapid
>
> delivery that we need.  If you are willing to serve on the design team,
> please let the chairs know. If there is someone you think would be good on
> the design team, please ask them to let us know.  We are NOT soliciting
> evaluations of proposed people on the
>
> list.  So, it is best if volunteers come to us directly. To be explicit,
> the chairs will select the members of and the chair for this design team.
>
>
>
>
>
> We hope to appoint a small, effective, team that represents the varied
> interests and concerns that have been expressed on the list.  Folks
> volunteering should understand that we hope you can move quickly, so it
> will take a significant amount
>
> of your time. The deadline for volunteering is 6pm US PST this coming
> Friday.
>
>
>
>
>
> Thanks!
>
>
>
>
>
> Jim, Joel & Bruno
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> _______________________________________________
>
> spring mailing list
>
> spring@ietf.org
>
> https://www.ietf.org/mailman/listinfo/spring
>
> --

<http://www.verizon.com/>

*Gyan Mishra*

*Network Solutions A**rchitect *

*M 301 502-134713101 Columbia Pike *Silver Spring, MD