[core] Roman Danyliw's Discuss on draft-ietf-core-groupcomm-bis-15: (with DISCUSS and COMMENT)

[Roman Danyliw via Datatracker <[e-mail]>]

Roman Danyliw has entered the following ballot position for
draft-ietf-core-groupcomm-bis-15: Discuss

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/about/groups/iesg/statements/handling-ballot-positions/ 
for more information about how to handle DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-core-groupcomm-bis/



----------------------------------------------------------------------
DISCUSS:
----------------------------------------------------------------------

(For the IESG to process at the formal telechat)

Idnits points out:
  ** Downref: Normative reference to an Informational RFC: RFC 5110
  ** Downref: Normative reference to an Informational RFC: RFC 7967
  ** Downref: Normative reference to an Informational RFC: RFC 9053

RFC9053 is already in the DownRef Registry
(https://datatracker.ietf.org/doc/downref/)  RFC7967 was called in the IETF
Last Call Message.

==[ from IETF Last Call Message ]==
… snip …
The document contains these normative downward references.

See RFC 3967 for additional information:
    rfc7967: Constrained Application Protocol (CoAP) Option for No Server
    Response (Informational - Independent Submission stream
==[ end IETF Last Call Message ]==

However, RFC5110 was neither announced in IETF Last Call or found the DownRef
registry.  It was used as a normative reference in RFC7390. The IESG needs to
approve this use.


----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

Thank you to Roni Even for the GENART review.