Re: [AVTCORE] IDNits issue with draft-ietf-avtcore-multi-party-rtt-mix-12

[Gunnar Hellström <[e-mail]>]

Bernard,

Yes, I can and will resubmit with the issues fixed.

However, one warning was because the nits check found what looks like a 
reference in brackets, but is part of a symbolic screen picture example 
containing a source label for text in brackets.

This was the warning:

==================================================================
  == Missing Reference: 'Bob' is mentioned on line 1427, but not
      defined
'|[mix][Bob] And I on Wednesday evening.        | |...'
===================================================================

May I keep the format of this picture as it is?

Regarding the comment about pre-RFC5378 work, I have the required grants 
to the BCP78 rights.

Thanks,

Gunnar


Den 2021-02-10 kl. 09:01, skrev Bernard Aboba:
> Just ran IDnits on the document and got an error (see below).  Can you 
> fix the issues and resubmit the document?
> idnits 2.16.05
>
>
> tmp/draft-ietf-avtcore-multi-party-rtt-mix-12.txt:
> tmp/draft-ietf-avtcore-multi-party-rtt-mix-12.txt(1351): Unexpected reference format: '...         ...'
> tmp/draft-ietf-avtcore-multi-party-rtt-mix-12.txt(1353): Unexpected reference format: '...         ...'
> tmp/draft-ietf-avtcore-multi-party-rtt-mix-12.txt(1355): Unexpected reference format: '...         ...'
> tmp/draft-ietf-avtcore-multi-party-rtt-mix-12.txt(1358): Unexpected reference format: '...         ...'
> tmp/draft-ietf-avtcore-multi-party-rtt-mix-12.txt(1361): Unexpected reference format: '...         ...'
> tmp/draft-ietf-avtcore-multi-party-rtt-mix-12.txt(1363): Unexpected reference format: '...         ...'
> tmp/draft-ietf-avtcore-multi-party-rtt-mix-12.txt(1365): Unexpected reference format: '...         ...'
> tmp/draft-ietf-avtcore-multi-party-rtt-mix-12.txt(1368): Unexpected reference format: '...         ...'
> tmp/draft-ietf-avtcore-multi-party-rtt-mix-12.txt(1689): Unexpected reference format: '...    |[Bob...'
> tmp/draft-ietf-avtcore-multi-party-rtt-mix-12.txt(1691): Unexpected reference format: '...    |[Eve...'
> tmp/draft-ietf-avtcore-multi-party-rtt-mix-12.txt(1694): Unexpected reference format: '...    |[Bob...'
> tmp/draft-ietf-avtcore-multi-party-rtt-mix-12.txt(1697): Unexpected reference format: '...    |[Eve...'
> tmp/draft-ietf-avtcore-multi-party-rtt-mix-12.txt(1698): Unexpected reference format: '...    |[Bob...'
> tmp/draft-ietf-avtcore-multi-party-rtt-mix-12.txt(1707): Unexpected reference format: '...    |[Ali...'
> tmp/draft-ietf-avtcore-multi-party-rtt-mix-12.txt(1711): Unexpected reference format: '...    |[Eve...'
> tmp/draft-ietf-avtcore-multi-party-rtt-mix-12.txt(1714): Unexpected reference format: '...    |[Ali...'
> tmp/draft-ietf-avtcore-multi-party-rtt-mix-12.txt(1719): Unexpected reference format: '...    |[Eve...'
> tmp/draft-ietf-avtcore-multi-party-rtt-mix-12.txt(1721): Unexpected reference format: '...    |[Eve...'
>
>   - The draft-hellstrom-avtcore-multi-party-rtt-source state file is not from today.
>     Attempting to download a newer one...
>   - Success fetching draft-hellstrom-avtcore-multi-party-rtt-source state file.
>
>   - The draft-ietf-avtcore-multi-party-rtt-mix state file is not from today.
>     Attempting to download a newer one...
>   - Success fetching draft-ietf-avtcore-multi-party-rtt-mix state file.
>
>   - The draft-ietf-mmusic-t140-usage-data-channel state file is not from today.
>     Attempting to download a newer one...
>   - Success fetching draft-ietf-mmusic-t140-usage-data-channel state file.
>
>   - No rfc0007 state file. Attempting to download it...
>     Failure fetching the file, proceeding without it.
>
>   - No rfc006 state file. Attempting to download it...
>     Failure fetching the file, proceeding without it.
>
>   - No rfc009 state file. Attempting to download it...
>     Failure fetching the file, proceeding without it.
>
>   - No rfc0098 state file. Attempting to download it...
>     Failure fetching the file, proceeding without it.
>
>   - The rfc2028 state file is not from today.
>     Attempting to download a newer one...
>   - Success fetching rfc2028 state file.
>
>   - The rfc2198 state file is not from today.
>     Attempting to download a newer one...
>   - Success fetching rfc2198 state file.
>
>   - The rfc3550 state file is not from today.
>     Attempting to download a newer one...
>   - Success fetching rfc3550 state file.
>
>   - The rfc4102 state file is not from today.
>     Attempting to download a newer one...
>   - Success fetching rfc4102 state file.
>
>   - The rfc4103 state file is not from today.
>     Attempting to download a newer one...
>   - Success fetching rfc4103 state file.
>
>   - The rfc4353 state file is not from today.
>     Attempting to download a newer one...
>   - Success fetching rfc4353 state file.
>
>   - The rfc4566 state file is not from today.
>     Attempting to download a newer one...
>   - Success fetching rfc4566 state file.
>
>   - The rfc4575 state file is not from today.
>     Attempting to download a newer one...
>   - Success fetching rfc4575 state file.
>
>   - The rfc4579 state file is not from today.
>     Attempting to download a newer one...
>   - Success fetching rfc4579 state file.
>
>   - The rfc5194 state file is not from today.
>     Attempting to download a newer one...
>   - Success fetching rfc5194 state file.
>
>   - The rfc5630 state file is not from today.
>     Attempting to download a newer one...
>   - Success fetching rfc5630 state file.
>
>   - The rfc5764 state file is not from today.
>     Attempting to download a newer one...
>   - Success fetching rfc5764 state file.
>
>   - The rfc6263 state file is not from today.
>     Attempting to download a newer one...
>   - Success fetching rfc6263 state file.
>
>   - The rfc6429 state file is not from today.
>     Attempting to download a newer one...
>   - Success fetching rfc6429 state file.
>
>   - The rfc7667 state file is not from today.
>     Attempting to download a newer one...
>   - Success fetching rfc7667 state file.
>
>   - The rfc7675 state file is not from today.
>     Attempting to download a newer one...
>   - Success fetching rfc7675 state file.
>
>   - The rfc8634 state file is not from today.
>     Attempting to download a newer one...
>   - Success fetching rfc8634 state file.
>
>   - The rfc8643 state file is not from today.
>     Attempting to download a newer one...
>   - Success fetching rfc8643 state file.
>
>    Checking boilerplate required by RFC 5378 and the IETF Trust (see
>    https://trustee.ietf.org/license-info  <https://trustee.ietf.org/license-info>):
>    ----------------------------------------------------------------------------
>
>       No issues found here.
>
>    Checking nits according tohttps://www.ietf.org/id-info/1id-guidelines.txt  <https://www.ietf.org/id-info/1id-guidelines.txt>:
>    ----------------------------------------------------------------------------
>
>       No issues found here.
>
>    Checking nits according tohttps://www.ietf.org/id-info/checklist  <https://www.ietf.org/id-info/checklist>  :
>    ----------------------------------------------------------------------------
>
>       No issues found here.
>
>    Miscellaneous warnings:
>    ----------------------------------------------------------------------------
>
>    == The copyright year in the IETF Trust and authors Copyright Line does not
>       match the current year
>
>       (Using the creation date from RFC4103, updated by this document, for
>       RFC5378 checks: 2004-06-15)
>
>    -- The document seems to lack a disclaimer for pre-RFC5378 work, but may
>       have content which was first submitted before 10 November 2008.  If you
>       have contacted all the original authors and they are all willing to grant
>       the BCP78 rights to the IETF Trust, then this is fine, and you can ignore
>       this comment.  If not, you may need to add the pre-RFC5378 disclaimer.
>       (See the Legal Provisions document at
>       https://trustee.ietf.org/license-info  <https://trustee.ietf.org/license-info>  for more information.)
>
>       IETF Trust Legal Provisions of 28-dec-2009, Section 6.c(iii):
>          This document may contain material from IETF Documents or IETF
>          Contributions published or made publicly available before
>          November 10, 2008.  The person(s) controlling the copyright in
>          some of this material may not have granted the IETF Trust the
>          right to allow modifications of such material outside the IETF
>          Standards Process. Without obtaining an adequate license from the
>          person(s) controlling the copyright in such materials, this
>          document may not be modified outside the IETF Standards Process,
>          and derivative works of it may not be created outside the IETF
>          Standards Process, except to format it for publication as an RFC
>          or to translate it into languages other than English.
>
>    -- The document date (15 December 2020) is 56 days in the past.  Is this
>       intentional?
>
>
>    Checking references for intended status: Proposed Standard
>    ----------------------------------------------------------------------------
>
>       (See RFCs 3967 and 4897 for information about using normative references
>       to lower-maturity documents in RFCs)
>
>    == Missing Reference: 'Bob' is mentioned on line 1427, but not
>       defined
> '|[mix][Bob] And I on Wednesday evening.        | |...'
>
>    == Outdated reference: draft-ietf-mmusic-t140-usage-data-channel has been
>       published as RFC 8865
>
>    ** Obsolete normative reference: RFC 4566 (Obsoleted by RFC 8866)
>
>    -- Possible downref: Non-RFC (?) normative reference: ref. 'T140'
>
>    -- Possible downref: Non-RFC (?) normative reference: ref. 'T140ad1'
>
>
>       Summary: 1 error (**), 0 flaws (~~), 3 warnings (==), 4 comments (--).

-- 
Gunnar Hellström
GHAccess
[e-mail]