Re: [core] [Dots] WG Last Call on draft-ietf-core-new-block

[[e-mail]]

Re-,

The concern is what to put in that paylaod if the resource does not exist:

   If the POST succeeds and results in the target resource being
   deleted, the response SHOULD have a 2.02 (Deleted) Response Code.

Cheers,
Med

> -----Message d'origine-----
> De : Marco Tiloca [mailto:[e-mail]]
> Envoyé : mardi 12 janvier 2021 10:10
> À : BOUCADAIR Mohamed TGI/OLN <[e-mail]>;
> [e-mail]; [e-mail]; [e-mail];
> [e-mail]
> Cc : [e-mail]; [e-mail]
> Objet : Re: [Dots] [core] WG Last Call on draft-ietf-core-new-block
> 
> Hi Med,
> 
> Could you clarify why that part is broken?
> 
> From RFC 7252, Section 5.9.1.2  "2.02 Deleted" says:
> 
>    "This Response Code is like HTTP 204 "No Content" but only used
> in response to requests that cause the resource to cease being
> available, such as DELETE and, in certain circumstances, POST. The
> payload returned with the response, if any, is a representation of
> the action result."
> 
> So, a 2.02 response can follow a POST request, and it can have a
> payload, which might be split using Block2.
> 
> Best,
> /Marco
> 
> On 2021-01-12 08:21, [e-mail] wrote:
> > Hi Marco, all,
> >
> > With regards to 2.02, RFC7959 says the following:
> >
> >    Hence, for the methods defined in [RFC7252], Block1 is useful
> with
> >    the payload-bearing POST and PUT requests and their responses.
> >    Block2 is useful with GET, POST, and PUT requests and their
> payload-
> >    ^^^^^^
> ^^^^^^^^
> >    bearing responses (2.01, 2.02, 2.04, and 2.05 -- see Section
> 5.5 of
> >    ^^^^^^^^                 ^^^^
> >    [RFC7252]).
> >
> > Which we think is broken.
> >
> > We don't echo that part in the new-block.
> >
> > Should we fill an errata against this?
> >
> > Cheers,
> > Med
> >
> >> -----Message d'origine-----
> >> De : Dots [mailto:[e-mail]] De la part de Marco
> Tiloca
> >> Envoyé : lundi 11 janvier 2021 20:23 À : supjps-
> [e-mail];
> >> [e-mail]; [e-mail];
> >> [e-mail]
> >> Cc : [e-mail]; [e-mail]
> >> Objet : Re: [Dots] [core] WG Last Call on draft-ietf-core-new-
> block
> >>
> >> Hi Jon,
> >>
> >> Thanks for the fast reaction. Please, see inline.
> >>
> >> Best,
> >> /Marco
> >>
> >> On 2021-01-11 17:39, [e-mail] wrote:
> >>> Hi Marco,
> >>>
> >>>> response code beside it).
> >>> [Jon] Thanks - added.  Also added in 2.02 and 2.05 as being
> >> expected response codes in 3.3.
> >>
> >> ==>MT
> >> Looks good.
> >> <==
> >>
> >
> ____________________________________________________________________
> __
> > ___________________________________________________
> >
> > Ce message et ses pieces jointes peuvent contenir des informations
> > confidentielles ou privilegiees et ne doivent donc pas etre
> diffuses,
> > exploites ou copies sans autorisation. Si vous avez recu ce
> message
> > par erreur, veuillez le signaler a l'expediteur et le detruire
> ainsi que les pieces jointes. Les messages electroniques etant
> susceptibles d'alteration, Orange decline toute responsabilite si ce
> message a ete altere, deforme ou falsifie. Merci.
> >
> > This message and its attachments may contain confidential or
> > privileged information that may be protected by law; they should
> not be distributed, used or copied without authorisation.
> > If you have received this email in error, please notify the sender
> and delete this message and its attachments.
> > As emails may be altered, Orange is not liable for messages that
> have been modified, changed or falsified.
> > Thank you.
> >
> 
> --
> Marco Tiloca
> Ph.D., Senior Researcher
> 
> RISE Research Institutes of Sweden
> Division ICT
> Isafjordsgatan 22 / Kistagången 16
> SE-164 40 Kista (Sweden)
> 
> Phone: [phone]
> https://www.ri.se
> 


_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.