Re: [Teas-ns-dt] REMINDER: TEAS NS DT Recurring Thursday Meeting

[John E Drake <[e-mail]>]

Good, thanks

Yours Irrespectively,

John



Juniper Business Use Only
From: Shunsuke Homma <[e-mail]>
Sent: Sunday, February 9, 2020 8:49 PM
To: John E Drake <[e-mail]>
Cc: John E Drake <jdrake=[e-mail]>; Kiran Makhijani <[e-mail]>; Jari Arkko <jari.arkko=[e-mail]>; [e-mail]
Subject: Re: [Teas-ns-dt] REMINDER: TEAS NS DT Recurring Thursday Meeting

Hi John,

Thank you for elaborating your thought. I got it.

We can add supplementary text explaining follows:
 - the labels in the figure mean just numbering of endpoints.
 - all of endpoints on the same slice may belong to the same address space.
 - there is direct connectivity between any pair

Regards,

Shunsuke


On Sun, Feb 9, 2020 at 12:02 AM John E Drake <[e-mail]<mailto:[e-mail]>> wrote:
Nevermind, that was nonsensical.

Having the labels for the left side endpoints and the right side endpoints come out of the same address space would work.  I.e., there are M endpoints, some on the left and some on the right, and there is direct connectivity between any pair.

Yours Irrespectively,

John



Juniper Business Use Only
From: Teas-ns-dt <[e-mail]<mailto:[e-mail]>> On Behalf Of John E Drake
Sent: Saturday, February 8, 2020 9:53 AM
To: Shunsuke Homma <[e-mail]<mailto:[e-mail]>>
Cc: Kiran Makhijani <[e-mail]<mailto:[e-mail]>>; Jari Arkko <jari.arkko=[e-mail]<mailto:[e-mail]>>; [e-mail]<mailto:[e-mail]>
Subject: Re: [Teas-ns-dt] REMINDER: TEAS NS DT Recurring Thursday Meeting

Hi,

The simplest fix would be to make the labels on the right set of endpoints match the labels on the left set of endpoints.

Yours Irrespectively,

John



Juniper Business Use Only
From: Shunsuke Homma <[e-mail]<mailto:[e-mail]>>
Sent: Friday, February 7, 2020 11:30 PM
To: John E Drake <[e-mail]<mailto:[e-mail]>>
Cc: Jari Arkko <jari.arkko=[e-mail]<mailto:jari.arkko=[e-mail]>>; Kiran Makhijani <[e-mail]<mailto:[e-mail]>>; [e-mail]<mailto:[e-mail]>
Subject: Re: [Teas-ns-dt] REMINDER: TEAS NS DT Recurring Thursday Meeting

Hi John,

Thank you for your comment.

What the figure shows are the following points:
- transport slice provides connectivity fulfilling specific SLOs among endpoints.
- endpoints may be distributed in several networks and transport slice can be established across multiple networks.

The reason why endpoints seems to be separated is that the endpoints are distributed in the underlay networks. There are no other intentions.

If you don't like the figure, can you share your image as ascii or ppt format? Or I can invite you to collaborator to edit xml directly if you prefer.

Regards,

Shunsuke

On Sat, Feb 8, 2020 at 1:00 AM John E Drake <[e-mail]<mailto:[e-mail]>> wrote:
Hi,

I don't think figure 2 is correct because it seems to be making a distinction between the endpoints on the left and the endpoints on the right, like a switch.  I thought the definition was describing a MP2MP construct, i.e., any to any connectivity, with possibly different SLOs between specific endpoint pairs.

Yours Irrespectively,

John



Juniper Business Use Only
From: Teas-ns-dt <[e-mail]<mailto:[e-mail]>> On Behalf Of Shunsuke Homma
Sent: Friday, February 7, 2020 4:21 AM
To: Jari Arkko <jari.arkko=[e-mail]<mailto:[e-mail]>>
Cc: Kiran Makhijani <[e-mail]<mailto:[e-mail]>>; [e-mail]<mailto:[e-mail]>
Subject: Re: [Teas-ns-dt] REMINDER: TEAS NS DT Recurring Thursday Meeting

Hello,

I pushed the latest definition draft which was shared from Kiran to NS-DT github repo.
https://github.com/teas-wg/teas-ns-dt/blob/master/definitions/draft-rokui-teas-transport-slice-definition-00.txt

You can find diffs from the previous version in the following page..
https://github.com/teas-wg/teas-ns-dt/commit/e13258a41772e7ee4f4027710db8f8e2a32e5c30

Your further feedback would be appreciated.

And if you need, I can upload md and xml format files as well.

Regards,

Shunsuke


On Fri, Feb 7, 2020 at 12:41 AM Jari Arkko <jari.arkko=[e-mail]<mailto:[e-mail]>> wrote:
>We have had some good review discussions on definitions document. If you think it's worth going through the document, we (authors) would like to do that in today's meeting:
>1. to show the recent changes (based on comments)
>2. Feedback on level of detail on a particular topic
>3. more importantly to get feedback if something is missing.


That sounds great, thank you. Lets do that!



Jari


--
Teas-ns-dt mailing list
[e-mail]<mailto:[e-mail]>
https://www.ietf.org/mailman/listinfo/teas-ns-dt<https://urldefense.com/v3/__https:/www.ietf.org/mailman/listinfo/teas-ns-dt__;!!NEt6yMaO-gk!XABgEwdEmcdgEu-E0Vw-tYjr__NZ5sPU__2MJYqVT9beHpDVvG-aATHCa5udkYg$>