Re: [Idr] //Re: Status changes as of 6/21/2022

[Jeffrey Haas <[e-mail]>]

Wenying,

Glad to hear you're having good experiences with work on your draft.

However, please remember two things as you take your work forward:
- New features implemented in Flowspec v1 will cause session resets in
  implementations that don't understand the new feature.
- Please don't ship code that squats on an unallocated code point.  Not only
  does this raise issues of session resets, but may cause issues as we start
  having Flowspec v2 work make progress.  The code points for Flowspec v1 and
  v2 are likely to be the same.

The IDR Chairs would encourage you to support moving Flowspec v2 work
forward to help you safely and interoperably deploy the new feature.

-- Jeff

On Thu, Jun 23, 2022 at 09:51:57AM +0800, 姜文颖 wrote:
> 
> 
> Hi Sue and WG,
> 
>  
> 
> draft-jiang-idr-ts-flowspec-srv6-policy has been presented at IETF#108/109/113 and got good feedback from WG. It has also been implemented by multiple vendors and successfully passed the joint interoperability test hosted  by China Mobile. We co-authors think that it is ready for WG adoption call. Would you please consider adding this document to the awaiting list of the adoption calls？
> 
>  
> 
> Thanks,
> 
> Wenying and co-authors