Re: [Tools-discuss] Idnits-2.16.02 feedback: -latest pattern

[Henrik Levkowetz <[e-mail]>]

Hi Carsten,

On 2019-04-06 18:43, Carsten Bormann wrote:
> Idnits should recognize the -latest pattern that Martin Thomson’s
> template uses and turn these four messages into one (or maybe even
> fix the fourth, because that very much can be figured out based on
> the pattern):

I don't see that from the information given.

 1) If idnits was made more permissive to accept these, and they actually
    occurred in a submitted document by mistake, they would not be flagged

 2) I don't see why idnits should be run on something which hasn't been
    processed all the way through to exact submission state, which seems to
    be what's happening here -- if the processing pipeline is able to produce
    something ready for submission, why is idnits run on something else?


Regards,

	Henrik


> Grüße, Carsten
> 
> 
>   Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt:
>   ----------------------------------------------------------------------------
> 
>   ** Missing revision: the document name given in the document,
>      'draft-ietf-core-multipart-ct-latest', does not give the document
>      revision number
> 
>   ~~ Missing draftname component: the document name given in the document,
>      'draft-ietf-core-multipart-ct-latest', does not seem to contain all the
>      document name components required ('draft' prefix, document source,
>      document name, and revision) -- see
>      https://www.ietf.org/id-info/guidelines#naming for more information.
> 
>   == Mismatching filename: the document gives the document name as
>      'draft-ietf-core-multipart-ct-latest', but the file name used is
>      'draft-ietf-core-multipart-ct'
> 
>   Miscellaneous warnings:
>   ----------------------------------------------------------------------------
> 
>   == Couldn't figure out when the document was first submitted -- there may
>      comments or warnings related to the use of a disclaimer for pre-RFC5378
>      work that could not be issued because of this.  Please check the Legal
>      Provisions document at https://trustee.ietf.org/license-info to determine
>      if you need the pre-RFC5378 disclaimer.
> 
> 
> ___________________________________________________________
> Tools-discuss mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/tools-discuss
> 
> Please report datatracker.ietf.org and mailarchive.ietf.org
> bugs at http://tools.ietf.org/tools/ietfdb
> or send email to [e-mail]
> 
> Please report tools.ietf.org bugs at
> http://tools.ietf.org/tools/issues
> or send email to [e-mail]
>