Dear WG
As an co-author, I support the adoption of this draft.
As Shuping mentioned some background on this draft:
During the adoption of the related PCEP draft“draf-ietf-pce-pcep-pmtu-02”,
a need for a document in SPRING was requested and confirmed by both PCE &
SPRING WG chairs. As well
.
On Fri, Jun 14, 2024 at 1:29 AM Gyan Mishra wrote:
>
> Hi Tom / All
>
> AFAIK what Robert is trying to say is that compare to IPv4, the IPv6
> header does not have a checksum field. The designers of IPv6 believed
> that the link layer checksumming provided by protocols like PPP and
&g
Hi Tom / All
AFAIK what Robert is trying to say is that compare to IPv4, the IPv6 header
does not have a checksum field. The designers of IPv6 believed that the
link layer checksumming provided by protocols like PPP and Ethernet,
combined with checksums in upper layer protocols like TCP and UDP,
Reviewer: Gyan Mishra
Review result: Ready
I have reviewed the latest version 16 of the draft with Operational
Considerations section 9.3 added to address L4 checksum discussion on ML. The
draft is well written and is ready for publication.
I have been following the ML thread since it began
I support publication.
Thanks
Gyan
On Sun, Apr 21, 2024 at 10:37 PM Michael McBride <
michael.mcbr...@futurewei.com> wrote:
> Hello good people,
>
>
>
> Today begins a two week wglc for
> https://datatracker.ietf.org/doc/html/draft-ietf-pim-sr-p2mp-policy-08.
> The related (normative)
Hi Gurminder
Yes I see it mentioned in section 2.4.2 End.TAP (uSID).
Thank you
<http://www.verizon.com/>
*Gyan Mishra*
*Network Solutions A**rchitect *
*Email gyan.s.mis...@verizon.com *
*M 301 502-1347*
On Fri, Mar 15, 2024 at 12:52 PM Gurminderjit Bajwa <
gurmin
Hi Jeffrey
This is a great idea Network tapping in an SR network.
I am guessing this would support SRv6 compression C-SID with Next SID
(uSID) F3216 format supports 16 bit uSID MicroTap sid instruction or
Replace SID 32 bit instruction?
Kind Regards
<http://www.verizon.com/>
*Gyan
ttp://www.verizon.com/>
*Gyan Mishra*
*Network Solutions A**rchitect *
*Email gyan.s.mis...@verizon.com *
*M 301 502-1347*
On Fri, Feb 9, 2024 at 2:30 PM Yingzhen Qu wrote:
> Hi,
>
> This email begins a 2 week WG adoption poll for the following
> draft:draft-cheng-rtgwg-srv
uch
transit nodes and any changes are restricted to SR aware nodes.¶
<https://datatracker.ietf.org/doc/html/draft-ietf-6man-sids-05#section-4-2>
Maybe some of section 4 verbiage could be even applied to the C-SID draft
operational considerations section.
Kind Regards
<http://www.verizo
As a contributor I am not aware of any undisclosed IPRs.
Thank you
<http://www.verizon.com/>
*Gyan Mishra*
*Network Solutions A**rchitect *
*Email gyan.s.mis...@verizon.com *
*M 301 502-1347*
On Thu, Feb 1, 2024 at 11:36 AM Joel Halpern wrote:
> 1) This email initiates an
ou
<http://www.verizon.com/>
*Gyan Mishra*
*Network Solutions A**rchitect *
*Email gyan.s.mis...@verizon.com *
*M 301 502-1347*
___
spring mailing list
spring@ietf.org
https://www.ietf.org/mailman/listinfo/spring
Jie mentioned the same and are are in sync.
Thanks
<http://www.verizon.com/>
*Gyan Mishra*
*Network Solutions A**rchitect *
*Email gyan.s.mis...@verizon.com *
*M 301 502-1347*
On Fri, Jan 26, 2024 at 1:07 AM Alexander Vainshtein <
alexander.vainsht...@rbbn.com> wrote:
&g
Hi Jie
Responses in-line Gyan>
<http://www.verizon.com/>
*Gyan Mishra*
*Network Solutions A**rchitect *
*Email gyan.s.mis...@verizon.com *
*M 301 502-1347*
On Wed, Jan 24, 2024 at 2:57 AM Dongjie (Jimmy) wrote:
> Hi Gyan,
>
>
>
> Thanks for sharing your t
update the existing SR-MPLS and SRv6, OSPF and
ISIS RFCs / drafts.
Kind Regards
<http://www.verizon.com/>
*Gyan Mishra*
*Network Solutions A**rchitect *
*Email gyan.s.mis...@verizon.com *
*M 301 502-1347*
On Thu, Jan 25, 2024 at 11:16 AM Acee Lindem wrote:
> Hi Sasha, Gyan,
&g
update the existing SR-MPLS and SRv6, OSPF and
ISIS RFCs / drafts.
Kind Regards
<http://www.verizon.com/>
*Gyan Mishra*
*Network Solutions A**rchitect *
*Email gyan.s.mis...@verizon.com *
*M 301 502-1347*
On Tue, Jan 23, 2024 at 4:00 AM Alexander Vainshtein <
alexander.vainsht...
Dear Joel & Spring WG chairs,
I believe I saw a request for Shepherd volunteers for this draft. I cannot
find the the exact email to respond directly to now.
I would like to volunteer as shepherd.
Thank you
<http://www.verizon.com/>
*Gyan Mishra*
*Network Solutions A**rchitect
such as
latency and jitter for NRP network slice.
Kind Regards
<http://www.verizon.com/>
*Gyan Mishra*
*Network Solutions A**rchitect *
*Email gyan.s.mis...@verizon.com *
*M 301 502-1347*
On Mon, Jan 22, 2024 at 3:39 AM Dongjie (Jimmy) wrote:
> Hi Sasha,
>
>
>
> Thanks for t
I support publication.
Thanks
<http://www.verizon.com/>
*Gyan Mishra*
*Network Solutions A**rchitect *
*Email gyan.s.mis...@verizon.com *
*M 301 502-1347*
On Mon, Jan 22, 2024 at 9:28 AM Joel Halpern wrote:
> (One of the other chairs pointed out that this had not gone to
I support publication of this draft as it is mature and ready and all
issues brought up have now been resolved.
Thanks
<http://www.verizon.com/>
*Gyan Mishra*
*Network Solutions A**rchitect *
*Email gyan.s.mis...@verizon.com *
*M 301 502-1347*
On Mon, Jan 22, 2024 at 9:46 AM We
I support publication.
Thanks
<http://www.verizon.com/>
*Gyan Mishra*
*Network Solutions A**rchitect *
*Email gyan.s.mis...@verizon.com *
*M 301 502-1347*
On Thu, Jan 18, 2024 at 6:45 PM Yingzhen Qu wrote:
> Hi,
>
> This starts the Working Group Last Call for
>
Hi Ahmed
I agree that IPPM is a very good fit for path tracing work and falls
in-line with the WG charter.
Kind Regards
Gyan
On Fri, Dec 1, 2023 at 11:52 AM Ahmed Abdelsalam (ahabdels) wrote:
> Hi Tal,
>
>
>
> Thanks for the feedback.
>
>
>
> We moved the draft to the IPPM WG based on the
ic loss.
> >
> > Action items for authors of the ti-lfa draft:
> > • To include text from RFC7490 second paragraph of section 10
> > • To include the text summary in the email thread
> > • Change the text in section 6.1 from node to link
> >
> > Next step
Hi Yingzhen
Does not seem that link will start working on its own.
I think you may have to request a new link since it’s saying this is an
invalid personal url link.
Can we just send out a different link to use?
Thanks
Gyan
On Wed, Nov 8, 2023 at 3:47 AM Yingzhen Qu wrote:
> Forwarding to
> Yisong
>
>
> 发件人: Gyan Mishra
> 时间: 2023/10/08(星期日)06:22
> 收件人: SPRING WG ;
> draft-liu-spring-sr-policy-flexible-path-selection
> ;
> 主题:
> https://datatracker.ietf.org/doc/html/draft-liu-spring-sr-policy-flexible-path-selection
> review
>
>
> Dear Au
Dear Authors
I reviewed the draft presented at IETF 117 and had some questions relating
to the draft.
SRv6 with it’s simplicity does not require SR policy VPN color overlay to
SR policy intent mapping to instantiate the data plane forwarding as does
SR-MPLS so generally this does not come into
I agree with the resolution for all issues and can all be closed.
Thank you
Gyan
On Tue, Aug 22, 2023 at 10:26 AM Gyan Mishra wrote:
> I agree the resolution is sufficient and issue #3 can be closed.
>
> Thank you
>
> Gyan
>
> On Tue, Aug 8, 2023 at 11:00 AM Joel Halpern
t; call is open for two weeks, through August 22.
> ___
> spring mailing list
> spring@ietf.org
> https://www.ietf.org/mailman/listinfo/spring
>
--
<http://www.verizon.com/>
*Gyan Mishra*
*Network Solutions
r have further concerns that should be
> addressed. If you have concerns, clarity about them is appreciated. This
> call is open for two weeks, through August 22.
> ___
> spring mailing list
> spring@ietf.org
> https://www.ietf.org/mailman/listi
__
> spring mailing list
> spring@ietf.org
> https://www.ietf.org/mailman/listinfo/spring
>
--
<http://www.verizon.com/>
*Gyan Mishra*
*Network Solutions A**rchitect *
*Email gyan.s.mis...@verizon.com *
*M 301 502-1347*
___
spring mailing list
spring@ietf.org
https://www.ietf.org/mailman/listinfo/spring
y will help us in all dimensions. If we
> determine that not all issues can be marked as closed, the chairs will work
> with the document editors to determine suitable next steps.
>
> Thank you,
>
> Joel
> ___
> spring mailing list
:
>
> draft-ietf-6man-sids addresses this issue and it has been WG Last Called
> by 6man.
>
> Thank you,
>
> Joel
>
>
> ___
> spring mailing list
> spring@ietf.org
> https://www.ietf.org/mailman/listinfo/sp
/draft-ali-spring-bfd-sr-policy-10#section-3.3
>> - there are also other mechanisms like using the BSID of the reverse path
>> to return.
>>
>> Thanks,
>> Ketan
>>
>> ___
>> spring mailing list
>> spring@ietf.org
>> https://www.ietf.org/m
attachments.
>
>
>
>
> Notice: This e-mail together with any attachments may contain information
> of Ribbon Communications Inc. and its Affiliates that is confidential
> and/or proprietary for the sole use of the intended recipient. Any review,
> disclosure, reliance or di
does not provide a control plane to optical
> transport stitching. Quite contrary it attempts to mimic characteristics of
> fixed channel transport to stuff it into an IP connection-less paradigm.
>
> Regards,
> R.
>
> On Thu, May 25, 2023 at 8:27 PM Gyan Mishra wrote:
>
>
Thank you, Joel (for the WG
> Chairs)
>
> We expect to close this call at the end of May, 2023.
>
> ___
> spring mailing list
> spring@ietf.org
> https://www.ietf.org/mailman/listinfo/spring
>
--
<http://www.verizon.com/>
*Gya
;
> Joel
>
>
> IETF IPv6 working group mailing list
> i...@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
>
您立即电话或邮件通知发件人并删除本邮件！
> This e-mail and its attachments may contain confidential information from
> HUAWEI, which is intended only for the person or entity whose address is
> listed above. Any use of the information contained herein in any way
> (including, but not limited to, total or parti
etf.org
> *Subject:* WGLC for draft-ietf-spring-sr-replication-segment
>
>
>
> Dear WG:
>
>
>
> This email starts a 2-week Working Group Last Call for
> https://datatracker.ietf.org/doc/draft-ietf-spring-sr-replication-segment/
>
>
>
> Please read the
) by persons other than the intended recipient(s) is
> prohibited. If you receive this e-mail in error, please notify the sender
> by phone or email immediately and delete it!
>
>
>
> *From:* spring [mailto:spring-boun...@ietf.org] *On Behalf Of *Gyan Mishra
> *Sent:* Wednesd
analogous to
BGP multicast using SP MVPN procedures hard state described above.
Thanks
Gyan
On Wed, Jan 4, 2023 at 2:45 AM Gyan Mishra wrote:
>
> RFC 7473 SAC stands for Selective Advertisement Capability.
>
> Thanks
>
> Gyan
>
> On Wed, Jan 4, 2023 at 2:36 AM Gyan M
RFC 7473 SAC stands for Selective Advertisement Capability.
Thanks
Gyan
On Wed, Jan 4, 2023 at 2:36 AM Gyan Mishra wrote:
>
> +1
>
> Segment Routing has been built for unicast routing for both SR-MPLS and
> SRv6 flavors - “Unicast SR”.
>
> All legacy existing technologies
mp; Bruno
>
>
>
>
>
>
>
> ___
>
> spring mailing list
>
> spring@ietf.org
>
> https://www.ietf.org/mailman/listinfo/spring
> <https://urldefense.com/v3/__https:/www.ietf.org/mailman/listinfo/spring__
o deploy.
>
> I think PBT-M could be a way to help the deployment of on path telemetry.
>
>
> Best regards,
>
> Pang Ran.
>
>
> *发件人：* Gyan Mishra
> *发送时间：* 2022-12-14 11:25
> *收件人：* IETF IPPM WG ; SPRING WG
> *主题：* [ippm]Progressing the PBT-M “Zero Overhea
that this draft should be Standards
Track and update the base specification RFC 9326 for PBT.
I believe that would be the best path forward for the WG.
All comments are welcome on this important topic.
Many Thanks
Gyan
--
<http://www.verizon.com/>
*Gyan Mishra*
*Network Solutions A**rc
R related to this document.
>
>
>
> Thanks!
>
>
>
> Jim, Joel & Bruno
>
>
>
>
> ___
> spring mailing list
> spring@ietf.org
> https://www.ietf.org/mailman/listinfo/spring
>
--
<h
Hi Suresh
Responses in-line
On Thu, Sep 29, 2022 at 4:12 PM Suresh Krishnan
wrote:
> Hi Gyan,
> Thanks for your comments. Please find responses inline.
>
> On Sep 28, 2022, at 11:06 PM, Gyan Mishra wrote:
>
>
> I support publication of the draft.
>
> I have revie
Kind Regards
Gyan
On Thu, Sep 29, 2022 at 2:24 PM Gyan Mishra wrote:
>
> Hi Robert
>
> Understood and agreed. I see what you are saying.
>
> I was just thinking of ULA with added flexibility in mind.
>
> Kind Regards
>
> Gyan
> On Thu, Sep 29, 2022 at 1:01 PM Robert
d relax need for ULA space.
>
> Thx,
> R.
>
>
> On Thu, Sep 29, 2022 at 6:16 PM Gyan Mishra wrote:
>
>> Brian
>>
>> On Thu, Sep 29, 2022 at 5:50 AM Brian Carpenter <
>> brian.e.carpen...@gmail.com> wrote:
>>
>>> No Gyan, fc00::/7 is not available
not internet routable and that mitigates any possibility of security issues
with SRV6 SID leaking to the internet.
Thoughts?
>
> Regards,
> Brian Carpenter
> (via tiny screen & keyboard)
>
>
> On Thu, 29 Sep 2022, 19:45 Gyan Mishra, wrote:
>
>>
>>
>> On
justify its own prefix.
>
> Regards,
> Brian Carpenter
> (via tiny screen & keyboard)
>
>
> On Thu, 29 Sep 2022, 19:45 Gyan Mishra, wrote:
>
>>
>>
>> On Wed, Sep 28, 2022 at 11:31 PM Brian E Carpenter <
>> brian.e.ca
On Wed, Sep 28, 2022 at 11:31 PM Brian E Carpenter <
brian.e.carpen...@gmail.com> wrote:
> On 29-Sep-22 16:06, Gyan Mishra wrote:
> ...
>
> > We should qualify the IANA request to make the /16 non internet routable
> identical to ULA addressing.
> >
> > If that
ry
>
>
> IETF IPv6 working group mailing list
> i...@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
>
>
--
>> of Ribbon Communications Inc. and its Affiliates that is confidential
>> and/or proprietary for the sole use of the intended recipient. Any review,
>> disclosure, reliance or distribution by others or forwarding without
>> express permission is s
; such reports were received.
>
> Yours,
>
> Bruno, Jim, and Joel
>
>
> ___
> spring mailing list
> spring@ietf.org
> https://www.ietf.org/mailman/listinfo/spring
>
--
<http://www.verizon.com/>
*Gyan Mishra*
tf.org/doc/draft-ietf-idr-sr-p2mp-policy/>
>
>
>
> Jeffrey Zhang has joined as co-author.
>
> Work is undergoing in the author group
>
> To help align it to other work.
>
>
>
> It will be WG LC in IDR and BESS.
>
>
>
> Cheers, Sue
>
>
of using SR-TE BSID for inter-as path stitching E2E EPE path
instead of inter-as options.
Kind Regards
Gyan
--
<http://www.verizon.com/>
*Gyan Mishra*
*Network Solutions A**rchitect *
*Email gyan.s.mis...@verizon.com *
*M 301 50
cast
https://datatracker.ietf.org/doc/html/draft-ietf-bess-bgp-multicast-00
BGP Multicast Controller
https://datatracker.ietf.org/doc/html/draft-ietf-bess-bgp-multicast-controller-09#section-3.1.1
Kind Regards
Gyan
On Mon, May 30, 2022 at 9:56 AM Gyan Mishra wrote:
> I agree wi
This e-mail together with any attachments may contain information
> of Ribbon Communications Inc. and its Affiliates that is confidential
> and/or proprietary for the sole use of the intended recipient. Any review,
> disclosure, reliance or distribution by others or forwarding without
> express permission is strictly prohibited. If you are not the intended
> recipient, please notify the sender immediately and then delete all copies,
> including any attachments.
> ___
> Pals mailing list
> p...@ietf.org
> https://www.ietf.org/mailman/listinfo/pals
>
--
<http://www.verizon.com/>
*Gyan Mishra*
*Network Solutions A**rchitect *
*Email gyan.s.mis...@verizon.com *
*M 301 502-1347*
___
spring mailing list
spring@ietf.org
https://www.ietf.org/mailman/listinfo/spring
>
> Andrew
>
>
>
>
>
>
> ___
> spring mailing list
> spring@ietf.org
> https://www.ietf.org/mailman/listinfo/spring
>
--
<http://www.verizon.com/>
*Gyan Mishra*
*Network Solutions A**rchitect *
*Email gyan.s.mis...@verizon.com *
*M 301 502-1347*
___
spring mailing list
spring@ietf.org
https://www.ietf.org/mailman/listinfo/spring
-+---+
> >>
> >> | 43| 0x002B | End with NEXT-CSID |
> >> [This.ID] |
> >>
> >>
> >> +---++--+---+
> >>
> >> (Looks like a similar question was asked before here
> >&g
__
> Pce mailing list
> p...@ietf.org
> https://www.ietf.org/mailman/listinfo/pce
>
--
<http://www.verizon.com/>
*Gyan Mishra*
*Network Solutions A**rchitect *
*Email gyan.s.mis...@verizon.com *
*M 301 502-1347*
___
spring mailing list
spring@ietf.org
https://www.ietf.org/mailman/listinfo/spring
Kind regards,
>
> --
> Tom
>
> ___
> 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 mailing list
> spring@ietf.org
> https://www.ietf.org/mailman/listinfo/spring
>
--
<http://www.verizon.com/>
*Gyan Mishra*
*Network Solutions A**rchitect *
*Email gyan.s.mis...@verizon.com *
*M 301 502-1347*
___
spring mailing list
spring@ietf.org
https://www.ietf.org/mailman/listinfo/spring
Hi Haoyu
On Thu, Jan 27, 2022 at 1:42 PM Haoyu Song wrote:
> Hi Gyan,
>
>
>
> Thank you for your comments! Please see inline for response marked with
> [HS]
>
>
>
> Best,
>
> Haoyu
>
>
>
> *From:* Gyan Mishra
> *Sent:* Wednesday, January
work,
> please also let me know.
> https://datatracker.ietf.org/doc/draft-song-spring-siam/
>
>
>
> Thank you very much!
>
>
>
> Best regards,
>
> Haoyu
>
> ___
> spring mailing lis
out 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.
>
>
Friday 13:00-14:30 UTC.
> > Agenda, related documents and other information of the side meeting
> could be found:
> https://trac.ietf.org/trac/ietf/meeting/wiki/112sidemeetings .
> > Welcome to join the discussion!
> >
> > Best Regards
> > Yisong
> >
n a GSID container?
>
>
>
> Respect,
>
> Cheng
>
>
>
>
>
> *From:* ipv6 [mailto:ipv6-boun...@ietf.org] *On Behalf Of *Gyan Mishra
> *Sent:* Friday, October 22, 2021 6:58 AM
> *To:* Darren Dukes (ddukes)
> *Cc:* spring@ietf.org; i...@ietf.org
> *Subjec
th to the value of NF
>
>
> S.29 Initialize local parameter BitIndex to (Argument * NF)
>
>
>
> S.30 Set S[B..B+BitLength-1] to the value of
>
>ActiveSegment[BitIndex..(BitIndex+BitLength-1)]
>
> S.32 Set S[B+BitLength..B+BitLength+A-1] to the value of A
t; >> Note that in the common case where the SIDS needed all fit in to a
> >> single container, the analysis also assumes the use of the reduced
> >> encapsulation options which omits the SRH that is not needed as it
> would
> >> have no entr
efix and that compressed
> SID.
> > > >>
> > > >> When the packet arrives at that node, it looks up the configured
> > > >> portion, the compressed SID, and determines the behavior and
> flavor. In
> > > >> the case of the NEXT-C-SID flavor, the resulting operation is
> t
em to mix them up and makes it
difficult for me to understand your questions.
Gyan> Will do
> Thanks,
>
> Francois
>
>
>
> *From: *Gyan Mishra
> *Date: *Sunday, 10 October 2021 at 22:23
> *To: *Chengli (Cheng Li) , Francois Clad (fclad) <
> fc...@cisco.com>
&
t;
> Gyan>. Good. That is a very important point.
>
> so we should avoid to mix different length of CSIDs in a single container,
> though we can do it.
>
> Gyan> This important verbiage should be added to the draft.
>
> I think we should add recommendation to avoi
ct, the local,
>> per-router function defined in the draft) in order for the forwarding to
>> succeed. By the definitions I’m using here, that is exactly a data plane
>> change.
>>
>> What, precisely, is then being claimed?
>>
>> Thanks,
>>
>> —John
>> ____
on is required (in fact, the local,
>> per-router function defined in the draft) in order for the forwarding to
>> succeed. By the definitions I’m using here, that is exactly a data plane
>> change.
>>
>> What, precisely, is then being claimed?
>>
>> Thanks,
>>
>> —John
>
>
> ___
> spring mailing list
> spring@ietf.org
> https://www.ietf.org/mailman/listinfo/spring
>
--
<http://www.verizon.com/>
*Gyan Mishra*
*Network Solutions A**rchitect *
*Email gyan.s.mis...@verizon.com *
*M 301 502-1347*
___
spring mailing list
spring@ietf.org
https://www.ietf.org/mailman/listinfo/spring
[2] = 2001:db8:0:0600:0001::
>
>
>
> Therefore, there is no notion of lowest common denominator for C-SID length
> . Based on the deployment requirements, an operator has the flexibility
> to select the SRv6 SID flavor and C-SID lengths of their choice.
>
>
>
> We can upda
ich...@futurewei.com> wrote:
> Hi Gyan,
>
>
>
> Please see the chairs response to the email from Andrew Alston.
>
>
>
> Yours,
>
>
>
> Jim, Bruno & Joel.
>
>
>
> *From:* Gyan Mishra
> *Sent:* Friday, October 1, 2021 7:26 PM
> *To:* Tony
above-described open issues
>>section:
>> - "Given that the working group has said that it wants to
>> standardize one data plane solution, and given that the document
>> contains
>> multiple SRv6 EndPoint behaviors that some WG members have
at 4:01 PM Gyan Mishra wrote:
> Hi Darren & Authors
>
> In addition to that editorial fix can we take below into account and
> addressed in the draft.
>
> The main goal for operators is interoperability. As interoperability is
> the key reason for a single SRv6 compres
SID column is
> replaced by three columns (NEXT-C-SID, REPLACE-C-SID, and
> NEXT-AND-REPLACE-C-SID).
>
>
>
> If the numbers in these columns are different from one another, this may
> inform our discussion about whether NEXT-C-SID, REPLACE-C-SID, and
> NEXT-AND-REPLACE-C-SID are diff
ll as any open discussion points you would like
> addressed should the document be adopted into the working group.
>
>
>
> Thanks!
>
>
>
> Jim, Bruno & Joel
>
>
>
>
> ___
> spring mailing list
> spring@i
scussion about whether NEXT-C-SID, REPLACE-C-SID, and
> NEXT-AND-REPLACE-C-SID are different behaviors or different flavors of a
> behavior.
>
>
>
>
> Ron
>
>
>
>
>
>
>
> Juniper Business Use Only
>
> *From:* spring *On Behalf Of *Gyan Mishra
> *Se
option. Please express clearly your reasoning for
> support/non-support as well as any open discussion points you would like
> addressed should the document be adopted into the working group.
>
> Thanks!
>
> Jim, Bruno & Joel
>
>
> ___
> > Thank you,
> > Joel, Bruno, and Jim
> >
> > ___
> > spring mailing list
> > spring@ietf.org
> > https://www.ietf.org/mailman/listinfo/spring
>
> ___
> sprin
ate the comments into different threads, and we can address them
one by one.
Again! Thank you for your comments!
Respect,
Cheng
*From:* Gyan Mishra [mailto:hayabusa...@gmail.com]
*Sent:* Tuesday, September 28, 2021 5:04 AM
*To:* SPRING WG ; spring-cha...@ietf.org; j00406941 <
jguic...@futurew
ated on
the mailing list, consider using a specific email/thread for this point.
Lastly, if you are an author or contributor please response to indicate
whether you know of any undisclosed IPR related to this document.
Thanks!
Jim, Joel & Bruno
[1] https://datatracker.ietf.org/doc/draft-ie
t any further SID
> lookup to happen in separate SID tables.
>
> Thx,
> R.
>
> On Sat, Sep 25, 2021 at 6:23 PM Gyan Mishra wrote:
>
>>
>> Interesting you mention indexing as CRH in fact moves the forwarding
>> state to the FIB, thereby eliminating the MSD iss
etwork.
>
> - - -
>
> As we have been via MPLS deployments in the past one of the often
> requested features was application/services prioritization. If we have one
> flat SID space this may not be easy.
>
> Thx,
> Robert
>
> ___
boundaries for example
MPLS 20 bit label or go even smaller 8 or 12 bit we mentioned by Robert.
Kind Regards
Gyan
On Fri, Sep 24, 2021 at 2:16 PM Darren Dukes (ddukes)
wrote:
> Section 6.1
>
>
>
> On 2021-09-24, 10:53 AM, "Gyan Mishra" wrote:
>
>
>
> Thank you Darre
e REPLACE-C-SID flavor supports both 16- and 32-bit C-SID lengths.
>
>A C-SID length of 32-bit is recommended.
>
>
>
> Jim
>
>
>
>
>
> *From:* Gyan Mishra
> *Sent:* Friday, September 24, 2021 10:53 AM
> *To:* Darren Dukes (ddukes)
> *Cc:* SPRING WG ;
> draft-fils
ttps://datatracker.ietf.org/doc/html/draft-cl-spring-generalized-srv6-for-cmpr-03
>
>
>
> SRv6 uSID micro-segment “ NEXT-C-SID”
>
>
> https://datatracker.ietf.org/doc/html/draft-filsfils-spring-net-pgm-extension-srv6-usid-10
>
>
>
> Kind Reg
.
This is a critical question that has come up by the WG and Chairs, and
answering this question will help pave the way to an adoption call for
C-SID.
Kind Regards
Gyan
On Sun, Sep 19, 2021 at 3:33 PM Gyan Mishra wrote:
> Dear Authors
>
> After having a few discussions on threads related to
-srv6-usid-10
Kind Regards
Gyan
--
<http://www.verizon.com/>
*Gyan Mishra*
*Network Solutions A**rchitect *
*Email gyan.s.mis...@verizon.com *
*M 301 502-1347*
___
spring mailing list
spring@ietf.org
https://www.ietf.org/mailman/listinfo/spring
ietf.org
> https://www.ietf.org/mailman/listinfo/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
>
--
<http://www.verizon.com/>
*Gyan Mishra*
*Network Solutions A**rchitect *
*Email gyan.s.mis...@verizon.com *
*M 301 502-1347*
___
spring mailing list
spring@ietf.org
https://www.ietf.org/mailman/listinfo/spring
; Regards,
> > Tony
> >
> > ___
> > spring mailing list
> > spring@ietf.org
> > https://www.ietf.org/mailman/listinfo/spring
>
> ___
> spring m
I would be happy to collaborate on the progression of these two drafts to
RFC as well as the single compression solution that the WG has final
consensus to adopt and progress to RFC.
Kind Regards
Gyan
Verizon
On Fri, Sep 10, 2021 at 10:11 AM Gyan Mishra wrote:
>
> I support WG ad
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 mes
Regards
Gyan
On Fri, Sep 10, 2021 at 12:20 AM Dongjie (Jimmy)
wrote:
> Hi Gyan,
>
>
>
> Thanks for providing your thoughts on this. Please see some replies inline
> with [Jie]:
>
>
>
> *From:* Gyan Mishra [mailto:hayabusa...@gmail.com]
> *Sent:* Saturday, Septem
3a1d5591fedc%7C1%7C0%7C637636999654946952
> > %7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiL
> > CJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000sdata=JyUjJng7gmClXGUs
> > Ll9AV6YWYWLQUFpmTPud8%2F0LRWE%3Dreserved=0
> >
> > ___
> > spring mailing list
> > spring@
you,
> Joel, Jim, and Bruno
>
> ___
> spring mailing list
> spring@ietf.org
> https://www.ietf.org/mailman/listinfo/spring
> _______
> spring mailing list
> spring@ietf.org
> https://ww
2697462524718%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000=v18Zntmw18jYiIXCNMDa7bYNQMZ90U29GVEkuPh5CjE%3D=0>
>
>
>
>
>
>
>
>
> ___
> spring mailing list
> spring@ietf.org
> https://www.ietf.org/mailman/listinfo/spring
>
--
<http://www.verizon.com/>
*Gyan Mishra*
*Network Solutions A**rchitect *
*Email gyan.s.mis...@verizon.com *
*M 301 502-1347*
___
spring mailing list
spring@ietf.org
https://www.ietf.org/mailman/listinfo/spring
1 - 100 of 233 matches
Mail list logo
