Re: [Teas] WG adoption - draft-nsdt-teas-ietf-network-slice-definition

I support WG adoption.

This draft can be worked further to fine tune and as it stands I believe
it’s mature for adoption.

Thanks

Gyan

On Thu, Jan 14, 2021 at 10:26 PM Rokui, Reza (Nokia - CA/Ottawa) <
reza.rokui@nokia.com> wrote:

> PSF,
>
>
>
> If such a use-cases exist (I am not aware of any use-cases), the current
> draft address them. As Joel mentioned, if (for some use-cases) the network
> decides to create a new “IETF network slice” between various endpoints,
> this request will be find its way to the NBI of “IETF Network Slice
> Controller” (NSC) and whatever mentioned in draft is still valid. How this
> request gets to the NSC NBI is out-of-scope of the draft. Any method can be
> use.
>
>
>
> IMO, such a request from network should not go from NSC SBI to NBI. It is
> not correct. The only information travel from SBI to NBI should be related
> to “IETF network slice” assurance (i.e. monitoring data from the network).
>
>
>
> Cheers,
>
>
>
> Reza
>
>
>
>
>
>
>
> *From: *Teas <teas-bounces@ietf.org> on behalf of "peng.shaofu@zte.com.cn"
> <peng.shaofu@zte.com.cn>
> *Date: *Thursday, January 14, 2021 at 10:06 PM
> *To: *"jmh@joelhalpern.com" <jmh@joelhalpern.com>
> *Cc: *"teas@ietf.org" <teas@ietf.org>
> *Subject: *Re: [Teas] WG adoption -
> draft-nsdt-teas-ietf-network-slice-definition
>
>
>
>
>
> Hi Joel,
>
>
>
> Thanks for your attention.
>
> Here, as the direction of the request is from south to north, do you think
> whether the definition document need to describe this case ?
>
> If so, the request would be very different with that is discribed in the
> current document. In detailed, it is sent through technology-specific
> interface between headend and network controller, then the network
> contoller may continue to request a slice from NSC, or report the created
> slice to NSC through technology-specific interface.
>
>
>
> Regards,
>
> PSF
>
>
>
> 原始邮件
>
> *发**件人：*JoelM.Halpern
>
> *收件人：*彭少富10053815;
>
> *抄送人：*teas@ietf.org;
>
> *日* *期* *：*2021年01月15日 10:18
>
> *主* *题* *：**Re: [Teas] WG adoption -
> draft-nsdt-teas-ietf-network-slice-definition*
>
> Given that station in the case below is making a request, isn't it
> reasonable to assume that the request makes its way to the control
> systems, which then handle the itneraction with the underlay network
> through the mechanisms proposed in the definitions and framework drafts?
>
> Yours,
> Joel
>
> On 1/14/2021 9:08 PM, peng.shaofu@zte.com.cn wrote:
> >
> > A little comment:
> >
> >
> > It seems that the definition document only support that the realization
> > of IETF network slice is triggered by the consumer through the interface
> > to NSC with specific SLO. I think it is not enough. Please see if it is
> > needed to support the case for a network device (the headend) to
> > explicitly request a slice on demand, and request a connection path
> > within the specific slice on demand.
> >
> >
> > Regards,
> >
> > PSF
> >
> >
> > 原始邮件
> > *发件人：*VishnuPavanBeeram
> > *收件人：*TEAS WG;
> > *抄送人：*TEAS WG Chairs;
> > *日 期 ：*2021年01月04日 22:02
> > *主 题 ：**[Teas] WG adoption -
> > draft-nsdt-teas-ietf-network-slice-definition*
> > _______________________________________________
> > Teas mailing list
> > Teas@ietf.org
> > https://www.ietf.org/mailman/listinfo/teas
> >
> > All,
> >
> > This is start of a two week poll on making
> > draft-nsdt-teas-ietf-network-slice-definition-02 a TEAS working group
> > document.
> > Please send email to the list indicating "yes/support" or "no/do not
> > support". If indicating no, please state your reservations with the
> > document. If yes, please also feel free to provide comments you'd
> > like to see addressed once the document is a WG document.
> >
> > The poll ends January 18th.
> >
> > Thanks,
> > Pavan and Lou
> >
> >
> >
> > _______________________________________________
> > Teas mailing list
> > Teas@ietf.org
> > https://www.ietf.org/mailman/listinfo/teas
> >
>
> _______________________________________________
> Teas mailing list
> Teas@ietf.org
> https://www.ietf.org/mailman/listinfo/teas
>
>
> _______________________________________________
> Teas mailing list
> Teas@ietf.org
> https://www.ietf.org/mailman/listinfo/teas
>
-- 

<http://www.verizon.com/>

*Gyan Mishra*

*Network Solutions A**rchitect *

*M 301 502-134713101 Columbia Pike *Silver Spring, MD