> -----Original Message----- > From: Mario Loffredo <mario.loffr...@iit.cnr.it> > Sent: Wednesday, June 17, 2020 1:05 PM > To: Hollenbeck, Scott <shollenb...@verisign.com>; regext@ietf.org; > internet-dra...@ietf.org; i-d-annou...@ietf.org > Subject: [EXTERNAL] Re: [regext] I-D Action: draft-ietf-regext-rfc7483bis- > 00.txt > > Hi Scott, > > please find my comments below.
[snip] > > 6) Section 6 - I would uppercase the word "may" in the following sentence: > > > > Some non-answer responses may return entity bodies with information > > that could be more descriptive. > > > > In addition, which members of an error response are required? > > > > > > > > [SAH] Agreed on the use of MAY. The text says that an error includes all > three fields (error code, title, and description). I believe that means that > all > three are REQIUIRED. > > > In my opinion "errorCode" should be required while "description" should be > optional. About "title", I don't have a clear position. Something else to think about. RFC 7480 describes required error response codes, so for the sake of consistency I think that makes the errorCode a MUST. 7480 also says "Optionally, it MAY include additional information regarding the negative answer in the HTTP entity body". That sounds to me like the title and description can be OPTIONAL. Does that sound reasonable? What have people actually implemented? Scott _______________________________________________ regext mailing list regext@ietf.org https://www.ietf.org/mailman/listinfo/regext
