Re: [Raw] New Version Notification for draft-pthubert-raw-architecture-07.txt

["Pascal Thubert (pthubert)" <[e-mail]>]

Good point, Fabrice

I'll add text saying that ingress and egress serve as Maintenance Entity Group End Points.

Note that the role of ingress covers more stuff like track selection, encapsulation and PSE.

Keep safe!

Pascal

> -----Original Message-----
> From: Fabrice Theoleyre <[e-mail]>
> Sent: lundi 7 juin 2021 17:19
> To: Pascal Thubert (pthubert) <[e-mail]>
> Cc: Greg Mirsky <[e-mail]>; [e-mail];
> [e-mail]; [e-mail]; Carlos J. Bernardos
> <[e-mail]>
> Subject: Re: New Version Notification for draft-pthubert-raw-architecture-
> 07.txt
> 
> Hi Pascal,
> 
> I just read your draft.
> 
> For the ingress / egress end-systems in section 4.3, shouldn’t you use the
> term MEP?
> Besides, I have the feeling that MEP should be the hosts at the border of the
> wireless part: in that way, you focus uniquely on the wireless links to
> collect all the measurements, etc.
> It would be easier to manage.
> 
> What’s your opinion?
> 
> Fabrice
> 
> 
> 
> 
> 
> 
> > Le 4 juin 2021 à 15:49, Pascal Thubert (pthubert) <[e-mail]> a
> écrit :
> >
> > Many thanks for your comments Greg!
> >
> > I added subsections to section 4.3 of draft-pthubert-raw-architecture 07;
> can you please have a look?
> >
> > Coincidently the new text affects the (todo) section 4.3 of draft-ietf-raw-
> oam-support.
> >
> > Fabrice and all, it would be nice that we sync on this. We might also
> exchange pieces of text between the 2 drafts.
> >
> > Keep safe;
> >
> > Pascal
> >
> > -----Original Message-----
> > From: [e-mail] <[e-mail]>
> > Sent: vendredi 4 juin 2021 15:38
> > To: Georgios Z. Papadopoulos <[e-mail]>;
> Georgios Papadopoulos <[e-mail]>; Lou Berger
> <[e-mail]>; Pascal Thubert (pthubert) <[e-mail]>; Rex
> Buddenberg <[e-mail]>
> > Subject: New Version Notification for draft-pthubert-raw-architecture-
> 07.txt
> >
> >
> > A new version of I-D, draft-pthubert-raw-architecture-07.txt
> > has been successfully submitted by Pascal Thubert and posted to the IETF
> repository.
> >
> > Name:		draft-pthubert-raw-architecture
> > Revision:	07
> > Title:		Reliable and Available Wireless Architecture/Framework
> > Document date:	2021-06-04
> > Group:		Individual Submission
> > Pages:		35
> > URL:            https://www.ietf.org/archive/id/draft-pthubert-raw-
> architecture-07.txt
> > Status:         https://datatracker.ietf.org/doc/draft-pthubert-raw-
> architecture/
> > Html:           https://www.ietf.org/archive/id/draft-pthubert-raw-
> architecture-07.html
> > Htmlized:       https://datatracker.ietf.org/doc/html/draft-pthubert-raw-
> architecture
> > Diff:           https://www.ietf.org/rfcdiff?url2=draft-pthubert-raw-
> architecture-07
> >
> > Abstract:
> >   Reliable and Available Wireless (RAW) provides for high reliability
> >   and availability for IP connectivity over a wireless medium.  The
> >   wireless medium presents significant challenges to achieve
> >   deterministic properties such as low packet error rate, bounded
> >   consecutive losses, and bounded latency.  This document defines the
> >   RAW Architecture.  It builds on the DetNet Architecture and discusses
> >   specific challenges and technology considerations needed to deliver
> >   DetNet service utilizing scheduled wireless segments and other media,
> >   e.g., frequency/time-sharing physical media resources with stochastic
> >   traffic.
> >
> >
> >
> >
> > The IETF Secretariat
> >
> >