Dear all,

Part of the IETF process is to ensure all concerns have been addressed
(and hopefully resolved). A concern was raised about "best vs active".
My takeaway from the conversation at IETF 104's GROW session is that
there is significant interest to progress towards publication - and
both Jeff Haas and John Scudder seemed to indicate to have ideas for
text on how to resolve issues they saw.

Version -03 didn't receive any feedback on the WG, so it is not clear
to me whether we have converged on consensus or not.

A -02/-03 diff be found here
https://tools.ietf.org/rfcdiff?url2=draft-ietf-grow-bmp-local-rib-03.txt

I'd like to ask that folks with skin in the game take a look and share
with the working group whether we are good to go, or follow up with
proposals for changes to the draft, or at least affirm outstanding
issues still remain.

Kind regards,

Job

On Wed, Feb 20, 2019 at 6:49 AM Paolo Lucente <[email protected]> wrote:
>
>
> Hi John,
>
> > On 07 Feb 2019, at 21:06, John Scudder <[email protected]> wrote:
> >
> > [ .. ]
> >
> >> Although not going in the ideal direction, for shorter-term I was thinking 
> >> about somewhat a mix of the two solutions you propose, to work as a 
> >> Charon: use a new reason code (or perhaps two, one for local terminated 
> >> session, one for remotely terminated session) since, as you said in your 
> >> follow-up email, it is the more conservative and would give the most hope 
> >> against what has been already coded. And make this/these new reason 
> >> code(s) carry "additional data [that] would be TLVized. It would obviously 
> >> need to have a registry created for it” so not to make all too “expedient” 
> >> and revolving around the specifics of VRF/Table Name and 
> >> draft-ietf-grow-bmp-local-rib.
> >
> > If I understand you correctly this seems fine to me. I guess the easiest 
> > way to be fully clear would be to rev the draft, and then we can have a 
> > look at the new text?
>
> I contributed some text in section 5.3 (and updated IANA considerations in 
> section 8), see:
>
> https://github.com/TimEvens/draft-ietf-grow-bmp-loc-rib/blob/master/draft-ietf-grow-bmp-local-rib.txt
>
> Look forward to your thoughts.
>
> Paolo
>
> _______________________________________________
> GROW mailing list
> [email protected]
> https://www.ietf.org/mailman/listinfo/grow

_______________________________________________
GROW mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/grow

Reply via email to