[Ibnemo] 答复: [Sdn] I-D Action: draft-xia-sdnrg-service-description-language-02.txt

[Xiayinben <[e-mail]>]

Hi Albrecht,

I think you are right. This draft should focus on the requirement and the information which need to describe a service request.
Because Intent is a new philosophy to design network interface. I think it need several drafts to discuss it from different points. Maybe in the future, there should be a working group to cover these topics. So we establish this mail list for detail technical discussion. 
https://www.ietf.org/mailman/listinfo/ibnemo

It seems you interested in this topic and you have lots of related experience as well. It is appreciated if you have any suggestion about the discussion points or how to structure the topics.

Best regards,
Yinben 

-----邮件原件-----
发件人: Ibnemo [mailto:[e-mail]] 代表 Schwarz, Albrecht (Albrecht)
发送时间: 2015年5月9日 0:00
收件人: Zhoutianran; STUART VENTERS; [e-mail]
抄送: [e-mail]
主题: Re: [Ibnemo] [Sdn] I-D Action: draft-xia-sdnrg-service-description-language-02.txt

Terence, et al.,

firstly, the level of languages and level of protocols should be not mixed in the ietf draft.

Secondly, there are even more options:

I) Compilation/interpretation dimension:
O1: in runtime evironment
O2: in advance

II) Signalling (= protocol) dimension (with x= 1, 2):
Ox.1: policy rule explicitly signalled
Ox.2: pointer to policy rule signaled, policy rule then retrieved from a remote, central data base by enforcement element
Ox.3: pointer to policy rule signaled, policy rule retrieved from a local data base

Furthermore:
Ox.1.1: policy rule signaled in a container, i.e., PSL syntax is different to underlying protocol syntax
Ox.1.2: policy rule signaled in native protocol syntax

Regards,
Albrecht

-----Original Message-----
From: sdn [mailto:[e-mail]] On Behalf Of Zhoutianran
Sent: Freitag, 8. Mai 2015 04:56
To: STUART VENTERS; [e-mail]
Cc: [e-mail]
Subject: Re: [Sdn] I-D Action: draft-xia-sdnrg-service-description-language-02.txt

This is interesting. Here is my two cents.

I agree with you that there are two issues.
And for the first one, I think we need a language to easily express the service request or the user intent.

The second one is about the protocol between the controller and applications. I think we have two option.
1. One is to pass the script as content directly to the controller. And all the compilation/parsing done on the controller.
2. The other option is to parse the intent expression on the application side into some well known format, e.g. xml, json, and then transport the content to the controller.

That's what we need to discuss in the community.


Best,
Terence


-----Original Message-----
From: sdn [mailto:[e-mail]] On Behalf Of STUART VENTERS
Sent: Wednesday, May 06, 2015 11:19 PM
To: [e-mail]
Subject: Re: [Sdn] I-D Action: draft-xia-sdnrg-service-description-language-02.txt

There appear to be two, separable technical issues in this draft:

1) What information is needed to represent a service request.
2) How to represent and transport the information for a request.

The first part may be a good area.

For the second part, I wonder if there are not already available methods to declare a schema and represent and transport the information governed by it.
It appears the draft is proposing to invent another mechanism.
It would be nice to understand the reasoning behind this choice.


--------------

On 04-05-15 11:59, [e-mail] wrote:
>
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
>
>
>          Title           : Requirements for a Service Description Language and Design Considerations
>          Authors         : Yinben Xia
>                            Sheng Jiang
>                            Susan Hares
> 	Filename        : draft-xia-sdnrg-service-description-language-02.txt
> 	Pages           : 7
> 	Date            : 2015-05-04
>
> Abstract:
>     The more and more complicated IP networks require a new interaction
>     mechanism between their customers and their networks.  A service
>     description language is needed to enable customers to easily describe
>     their diverse intent.  SDN controller would compile the user intent
>     into device configurations.  This document analyzes requirements for
>     such service description language and gives considerations for
>     designing such service description language.
>
>
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-xia-sdnrg-service-description-l
> anguage/
>
> There's also a htmlized version available at:
> https://tools.ietf.org/html/draft-xia-sdnrg-service-description-langua
> ge-02
>
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-xia-sdnrg-service-description-
> language-02
>
>
> Please note that it may take a couple of minutes from the time of 
> submission until the htmlized version and diff are available at tools.ietf.org.
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>
> _______________________________________________
> I-D-Announce mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/i-d-announce
> Internet-Draft directories: http://www.ietf.org/shadow.html or 
> ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>


--
*****************************************************************
               请记住，你是独一无二的，就像其他每一个人一样

_______________________________________________
sdn mailing list
[e-mail]
https://www.irtf.org/mailman/listinfo/sdn
_______________________________________________
sdn mailing list
[e-mail]
https://www.irtf.org/mailman/listinfo/sdn
_______________________________________________
sdn mailing list
[e-mail]
https://www.irtf.org/mailman/listinfo/sdn
_______________________________________________
Ibnemo mailing list
[e-mail]
https://www.ietf.org/mailman/listinfo/ibnemo