Re: [core] [ipwave] Adaptive RESTful Real-time Live Streaming for Things (A-REaLiST)'

Thank you Carsten for your comments. No one can speak about CoAP better than you!

Alex,
I have uploaded a new version of the draft. The links are given at the end of this mail. I have indeed tried to address your concern in respect to making the draft more "IPv6-relevant".

As Carsten rightly pointed out that the proposal works at the application layer and is built on the foundation of CoAP, so it is Layer-3 agnostic. Also, as we all know, CoAP is designed for IPv6.
However, implementation on IPv6 may influence the process of determining the maximum size of information segments. So, a new subsection has been added as part of the design guidelines. The small addition reads as below:

<Quote>
6.3. Determining the segment size

   Size of the information segment in a CoAP message should be limited by the least
   possible MTU for the end-to-end channel. This is to ensure that there is no
   undesired conversation state at the lower layers of the protocol stack due to
   uncontrolled fragmentation leading to undesired explosion of traffic in the
   network. For IPV6 network, the MTU can be determined using Path MTU Discovery
   (PMTUD) [RFC8201] which bestows the responsibility of determining the path MTU on
   the end-points itself.

   The size of the segment should be guided by the recommendations as specified in
   Section 4.6 of [RFC7252].
</Quote>

I hope this will now satisfy the criterion of finding IPv6 in the draft.

Looping in CoRE list as well to announce the new version to the WG where this draft originates.

Thank you.

URL:            https://www.ietf.org/internet-drafts/draft-bhattacharyya-core-a-realist-01.txt
Status:         https://datatracker.ietf.org/doc/draft-bhattacharyya-core-a-realist/
Htmlized:       https://tools.ietf.org/html/draft-bhattacharyya-core-a-realist-01
Htmlized:       https://datatracker.ietf.org/doc/html/draft-bhattacharyya-core-a-realist
Diff:           https://www.ietf.org/rfcdiff?url2=draft-bhattacharyya-core-a-realist-01

With Best Regards
Abhijan Bhattacharyya
Consultant / Scientist,
{Internet Protocols | 5G | Standardization}, 
TCS Research,
Tata Consultancy Services
Building 1B,Ecospace
Plot -  IIF/12 ,New Town, Rajarhat,
Kolkata - 700160,West Bengal
India
Ph:- +91 33 66884691
Cell:- +919830468972 | +918583875003
Mailto: abhijan.bhattacharyya@tcs.com
Website: http://www.tcs.com
____________________________________________
Experience certainty.	IT Services
Business Solutions
Consulting
____________________________________________

-----"its" <its-bounces@ietf.org> wrote: -----
To: "Alexandre Petrescu" <alexandre.petrescu@gmail.com>
From: "Carsten Bormann" 
Sent by: "its" 
Date: 01/31/2019 06:12PM
Cc: "Abhijan Bhattacharyya" <abhijan.bhattacharyya@tcs.com>, "Michael Richardson" <mcr@sandelman.ca>, its@ietf.org
Subject: Re: [ipwave] Adaptive RESTful Real-time Live Streaming for Things (A-REaLiST)'

"External email. Open with Caution"

> If TCP's state machine was a bottleneck, has one tried to use UDP
> instead?

I think that is indeed one of the advantages CoAP brings go the table here.

> Does CoAP work on Ethernet?

CoAP was designed to be able to run on UDP, which is on IP which in turn works very well on Ethernet.

> Does CoAP work in an end-to-end manner or does it need protocol
> conversion gateways?

I works end-to-end (as long as your network doesn&#8217;t break UDP).

> I want to ask you: please use IPv6 for CoAP and RESTful.

CoAP was designed to work well over IPv6 (but works as well over IPv4).

> Then I searched for the keyword &#8216;IPv6' in the draft.
> [&#8230;]
> If you add &#8216;IPv6' considerations to it, then I will comment on it.

For a CoAP application such as A-REaLiST, IPv6 makes little difference (beyond being able to assign addresses to both ends in the first place), so I don&#8217;t know there is a lot to say.

Grüße, Carsten

_______________________________________________
its mailing list
its@ietf.org
https://www.ietf.org/mailman/listinfo/its
=====-----=====-----=====
Notice: The information contained in this e-mail
message and/or attachments to it may contain 
confidential or privileged information. If you are 
not the intended recipient, any dissemination, use, 
review, distribution, printing or copying of the 
information contained in this e-mail message 
and/or attachments to it are strictly prohibited. If 
you have received this communication in error, 
please notify us by reply e-mail or telephone and 
immediately and permanently delete the message 
and any attachments. Thank you