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

Hi Alex,

> Thank you very much for this valuable action.
My pleasure. 

> It is very worth taking into consideration.

Thanks for you help in improvement of the contents of the proposition.

>  From an implementation standpoint, I would like to learn whether some 
> prototype features RESTful Real-time Live Streaming on IPv6, or not on 
IPv6.
> 

We made a PoC of the concept and the experimentation and outcomes are 
presented in Pages 78-80 of 
https://datatracker.ietf.org/meeting/103/materials/slides-103-core-consolidated-slides-07.pdf
.
But we used IPv4 pipe. While it is worth to do an experiment on how IPv6 
improves the performance (it can only improve I believe). But otherwise 
there should not be much of an impact higher up by a change in the network 
layer because CoAP is designed with 6LowPAN pipe in consideration as 
already emphasised by Carsten. 

May be we can discuss at length if we get an opportunity to present this 
in a physical meeting.

Thank you.

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 on 02/08/2019 09:07:10 PM:

> From: "Alexandre Petrescu" <alexandre.petrescu@gmail.com>
> To: "Abhijan Bhattacharyya" <abhijan.bhattacharyya@tcs.com>, 
> "Carsten Bormann" <cabo@tzi.org>
> Cc: "core@ietf.org" <core@ietf.org>, its@ietf.org
> Date: 02/08/2019 09:08 PM
> Subject: Re: [ipwave] Adaptive RESTful Real-time Live Streaming for 
> Things (A-REaLiST)'
> Sent by: "its" <its-bounces@ietf.org>
> 
> "External email. Open with Caution"
> 
> 
> Le 04/02/2019 à 20:00, Abhijan Bhattacharyya a écrit :
> > 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.
> 
> Thank you very much for this valuable action.
> 
> It is very worth taking into consideration.
> 
>  From an implementation standpoint, I would like to learn whether some 
> prototype features RESTful Real-time Live Streaming on IPv6, or not on 
IPv6.
> 
> Alex
> 
> > 
> > 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 <
mailto:abhijan.bhattacharyya@tcs.com>
> > Website: http://www.tcs.com
> > ____________________________________________
> > Experience certainty. IT Services
> > Business Solutions
> > Consulting
> > ____________________________________________
> > 
> > 
> > -----"its" <its-bounces@ietf.org <mailto:its-bounces@ietf.org>> wrote: 
-----
> > To: "Alexandre Petrescu" <alexandre.petrescu@gmail.com 
> > <mailto:alexandre.petrescu@gmail.com>>
> > From: "Carsten Bormann"
> > Sent by: "its"
> > Date: 01/31/2019 06:12PM
> > Cc: "Abhijan Bhattacharyya" <abhijan.bhattacharyya@tcs.com 
> > <mailto:abhijan.bhattacharyya@tcs.com>>, "Michael Richardson" 
> > <mcr@sandelman.ca <mailto:mcr@sandelman.ca>>, its@ietf.org 
> > <mailto: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’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 ‘IPv6' in the draft.
> >  > […]
> >  > If you add ‘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’t know there is a lot to say.
> > 
> > Grüße, Carsten
> > 
> > _______________________________________________
> > its mailing list
> > its@ietf.org <mailto: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
> > 
> 
> _______________________________________________
> its mailing list
> its@ietf.org
> https://www.ietf.org/mailman/listinfo/its
> 