[Dots] [IANA #1364390] [Errata Verified] RFC9132 (7058)

[David Dong via RT <[e-mail]>]

Hi Valery (and a question for Deb),

Apologies on the delay for my response.

The same YANG Parameters statement being corrected in this errata report also appears in the obsoleted RFC 8782, which has a separate YANG Module posted (https://www.iana.org/assignments/yang-parameters/)

Hi Deb, 

This may be more of a question for erratas against YANG Modules in general, but how should we update this IETF Module in response to this errata report (if at all)? This also may be more appropriate to discuss with the YANG Doctors.

We currently generate the YANG Modules from the XML/HTML files of the RFCs in question. As this errata modifies a YANG statement in the existing [e-mail], is it acceptable if we just added a reference to this errata report in the listing for [e-mail] in the YANG Module Names registry, or should we do something else? 

The ietf-dots-signal-channel@2021-09-02 YANG Module, generated from RFC 9132, does not contain the corrected YANG statement, as the errata process does not update the RFC itself and thus would not update any XML/HTML files generated from the RFC.

Please let us know what actions we should take, if any. Thank you!

Best regards,

David Dong
IANA Services Sr. Specialist

On Mon Jul 22 14:01:17 2024, [e-mail] wrote:
> Hi David,
> 
> [e-mail] is defined in RFC 9132,
> against which the errata was submitted.
> RFC 8782 defines [e-mail] and, in any
> case, it is obsoleted by RFC 9132.
> Can you please clarify what errata should be submitted against
> (obsoleted) RFC 8782?
> 
> Regards,
> Valery.
> 
> > -----Original Message-----
> > From: David Dong via RT <[e-mail]>
> > Sent: Monday, July 15, 2024 11:52 PM
> > Cc: [e-mail]; [e-mail];
> > [e-mail]; [e-mail]; [e-mail]; [e-mail];
> > [e-mail]; [e-mail]
> > Subject: [Dots] [IANA #1364390] [Errata Verified] RFC9132 (7058)
> >
> > Hi all,
> >
> > Following up on this; it appears that this errata affects ietf-dots-
> > signal-
> > [e-mail]. As this is an IETF YANG module, would you be
> > able to
> > submit an errata against RFC 8782?
> >
> > Thank you.
> >
> > Best regards,
> >
> > David Dong
> > IANA Services Sr. Specialist
> >
> >
> > On Fri Jun 28 00:44:47 2024, david.dong wrote:
> > > Hi all,
> > >
> > > Apologies for the delay in following up for this errata; it appears
> > > that this errata affects [e-mail].
> > > As
> > > this is an IETF YANG module, would you be able to submit an errata
> > > against RFC 8782?
> > >
> > > Thank you.
> > >
> > > Best regards,
> > >
> > > David Dong
> > > IANA Services Sr. Specialist
> > >
> > > On Mon May 06 17:24:50 2024, [e-mail] wrote:
> > > > The following errata report has been verified for RFC9132,
> > > > "Distributed Denial-of-Service Open Threat Signaling (DOTS)
> > > > Signal
> > > > Channel Specification".
> > > >
> > > > --------------------------------------
> > > > You may review the report below and at:
> > > > https://www.rfc-editor.org/errata/eid7058
> > > >
> > > > --------------------------------------
> > > > Status: Verified
> > > > Type: Technical
> > > >
> > > > Reported by: Jan Lindblad <[e-mail]> Date Reported:
> > > > 2022-07-29 Verified by: Deb Cooley (IESG)
> > > >
> > > > Section: 5.3
> > > >
> > > > Original Text
> > > > -------------
> > > > uses data-channel:target {
> > > >   when "/dots-signal/scope/conflict-information/"
> > > >      + "conflict-cause = 'overlapping-targets'"; }
> > > >
> > > >
> > > > Corrected Text
> > > > --------------
> > > > uses data-channel:target {
> > > >   when "../conflict-cause = 'overlapping-targets'";
> > > > }
> > > >
> > > >
> > > > Notes
> > > > -----
> > > > The original YANG statements make the "uses" statement apply to
> > > > all
> > > > "list scope" instances as soon as there is at least one "scope"
> > > > instance that has "conflict-cause" set to "overlapping-targets".
> > > > I
> > > > suspect this is not the author's intent.
> > > >
> > > > The corrected YANG statements make the "uses" statement only
> > > > apply to
> > > > the specific "scope" instances that have "conflict-cause" set to
> > > > "overlapping-targets". There are also other ways to fix this
> > > > issue.
> > > >
> > > > --------------------------------------
> > > > RFC9132 (draft-ietf-dots-rfc8782-bis-08)
> > > > --------------------------------------
> > > > Title               : Distributed Denial-of-Service Open Threat
> > > > Signaling (DOTS) Signal Channel Specification
> > > > Publication Date    : September 2021
> > > > Author(s)           : M. Boucadair, Ed., J. Shallow, T. Reddy.K
> > > > Category            : PROPOSED STANDARD
> > > > Source              : DDoS Open Threat Signaling
> > > > Stream              : IETF
> >
> > _______________________________________________
> > Dots mailing list -- [e-mail]
> > To unsubscribe send an email to [e-mail]