date:20181101

Re: [netmod] for a future rfc6991bis

2018-11-01 Thread Qin Wu

Agree with this criteria, remember geo location proposal was discussed before 
by ALTO proponents in LMAP, in addition, location service is useful for L3VPN 
sevice placement, see example case in RFC8299 which can select appropriate PE 
based on location info. Acee also provided a valid use case in this e-mail 
thread.

发件人： Juergen Schoenwaelder
收件人： Qin Wumailto:bill...@huawei.com>>
抄送： netmodmailto:netmod@ietf.org>>
主题： Re: [netmod] for a future rfc6991bis
时间： 2018-11-01 20:04:15

I think we need to find a way to limit the update to types that are
known (or expected) to be 'widely' needed. In other words, for every
proposed type, an argument should be made why this should be included
in RFC 6991bis.

/js

On Thu, Nov 01, 2018 at 11:55:25AM +, Qin Wu wrote:
> I am wondering if we can add longitude, latitude in DMS or decimal degree,
> Further we can consider to add
> Postal-code, Country-code like Location type.
>
> -Qin
> -邮件原件-
> 发件人: netmod [mailto:netmod-boun...@ietf.org] 代表 Juergen Schoenwaelder
> 发送时间: 2018年10月31日 20:47
> 收件人: netmod@ietf.org
> 主题: Re: [netmod] for a future rfc6991bis
>
> Here is my list of possible additions. I might have lost some items on a 
> computer that meanwhile is not used anymore, I will have to dig a bit to see 
> what I can recover.
>
> /js
>
> On Wed, Oct 31, 2018 at 01:26:01PM +0100, Ladislav Lhotka wrote:
> > Hi,
> >
> > another update that was discussed recently is a clarification of the
> > XPath context for the xpath1.0 type.
> >
> > Lada
> >
> > Kent Watsen  writes:
> >
> > > NETMOD WG,
> > >
> > > A conversation in NETCONF WG regarding the yang-push noted that it
> > > might be time to update RFC 6991, in particular to introduce a type for 
> > > time-duration.
> > >
> > >
> > > https://mailarchive.ietf.org/arch/msg/netconf/KaUJloIShkLNIXTuHZNwB-
> > > SYBnQ
> > >
> > > In addition, it might be good to introduce [inet?] types for RFC
> > > 5322 (Internet Message Format) including perhaps:
> > >
> > >   - email-address(addr-spec, per Section 3.4.1)
> > >   - named-email-address  (name-addr, per Section 3.4)
> > >
> > >
> > > Kent // contributor
> > >
> > >
> > >
> > > ___
> > > netmod mailing list
> > > netmod@ietf.org
> > > https://www.ietf.org/mailman/listinfo/netmod
> >
> > --
> > Ladislav Lhotka
> > Head, CZ.NIC Labs
> > PGP Key ID: 0xB8F92B08A9F76C67
> >
> > ___
> > netmod mailing list
> > netmod@ietf.org
> > https://www.ietf.org/mailman/listinfo/netmod
>
> --
> Juergen Schoenwaelder   Jacobs University Bremen gGmbH
> Phone: +49 421 200 3587 Campus Ring 1 | 28759 Bremen | Germany
> Fax:   +49 421 200 3103 

--
Juergen Schoenwaelder   Jacobs University Bremen gGmbH
Phone: +49 421 200 3587 Campus Ring 1 | 28759 Bremen | Germany
Fax:   +49 421 200 3103 
___
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod

Re: [netmod] for a future rfc6991bis

2018-11-01 Thread Acee Lindem (acee)

Hi Qin,

On 11/1/18, 10:44 AM, "Qin Wu"  wrote:

That's a good use case for geo-location service. If the geo-location 
information is specified in routing protocol, I think it should also be 
specified by YANG, but need to make sure they are consistent.
For precision of longitude and latitude, why not use DMS (Degree, Minute, 
Second)? 

I'd be happy to reach consensus on this but we're going to solve it in this 
Email thread. 

Thanks,
Acee

-Qin
-邮件原件-
发件人: Acee Lindem (acee) [mailto:a...@cisco.com] 
发送时间: 2018年11月1日 22:18
收件人: Qin Wu ; Juergen Schoenwaelder 
; netmod@ietf.org
主题: Re: [netmod] for a future rfc6991bis

Hi Qin,

We'd tried to converge on geo-coordinates in the protocols and received and 
a rather wide range of opinions as to the precision and what was required. An 
IETF consensus is required and not everyone is going to be happy. However, I'm 
not sure where this work lies and it hasn't been a priority for me. In fact, I 
let my draft expire: 
https://www.ietf.org/archive/id/draft-acee-ospf-geo-location-05.txt. I think 
trying to adding these before this happens could delay the BIS update. 

Thanks,
Acee

On 11/1/18, 7:55 AM, "netmod on behalf of Qin Wu"  wrote:

I am wondering if we can add longitude, latitude in DMS or decimal 
degree,
Further we can consider to add
Postal-code, Country-code like Location type.

-Qin
-邮件原件-
发件人: netmod [mailto:netmod-boun...@ietf.org] 代表 Juergen Schoenwaelder
发送时间: 2018年10月31日 20:47
收件人: netmod@ietf.org
主题: Re: [netmod] for a future rfc6991bis

Here is my list of possible additions. I might have lost some items on 
a computer that meanwhile is not used anymore, I will have to dig a bit to see 
what I can recover.

/js

On Wed, Oct 31, 2018 at 01:26:01PM +0100, Ladislav Lhotka wrote:
> Hi,
> 
> another update that was discussed recently is a clarification of the 
> XPath context for the xpath1.0 type.
> 
> Lada
> 
> Kent Watsen  writes:
> 
> > NETMOD WG,
> >
> > A conversation in NETCONF WG regarding the yang-push noted that it 
> > might be time to update RFC 6991, in particular to introduce a type 
for time-duration.
> >
> >   
> > https://mailarchive.ietf.org/arch/msg/netconf/KaUJloIShkLNIXTuHZNwB-
> > SYBnQ
> >
> > In addition, it might be good to introduce [inet?] types for RFC 
> > 5322 (Internet Message Format) including perhaps:
> >
> >   - email-address(addr-spec, per Section 3.4.1)
> >   - named-email-address  (name-addr, per Section 3.4)
> >
> >
> > Kent // contributor
> >
> >
> >
> > ___
> > netmod mailing list
> > netmod@ietf.org
> > https://www.ietf.org/mailman/listinfo/netmod
> 
> --
> Ladislav Lhotka
> Head, CZ.NIC Labs
> PGP Key ID: 0xB8F92B08A9F76C67
> 
> ___
> netmod mailing list
> netmod@ietf.org
> https://www.ietf.org/mailman/listinfo/netmod

-- 
Juergen Schoenwaelder   Jacobs University Bremen gGmbH
Phone: +49 421 200 3587 Campus Ring 1 | 28759 Bremen | Germany
Fax:   +49 421 200 3103 
___
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod

___
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod

Re: [netmod] for a future rfc6991bis

2018-11-01 Thread Qin Wu

That's a good use case for geo-location service. If the geo-location 
information is specified in routing protocol, I think it should also be 
specified by YANG, but need to make sure they are consistent.
For precision of longitude and latitude, why not use DMS (Degree, Minute, 
Second)?

-Qin
-邮件原件-
发件人: Acee Lindem (acee) [mailto:a...@cisco.com] 
发送时间: 2018年11月1日 22:18
收件人: Qin Wu ; Juergen Schoenwaelder 
; netmod@ietf.org
主题: Re: [netmod] for a future rfc6991bis

Hi Qin,

We'd tried to converge on geo-coordinates in the protocols and received and a 
rather wide range of opinions as to the precision and what was required. An 
IETF consensus is required and not everyone is going to be happy. However, I'm 
not sure where this work lies and it hasn't been a priority for me. In fact, I 
let my draft expire: 
https://www.ietf.org/archive/id/draft-acee-ospf-geo-location-05.txt. I think 
trying to adding these before this happens could delay the BIS update. 

Thanks,
Acee

On 11/1/18, 7:55 AM, "netmod on behalf of Qin Wu"  wrote:

I am wondering if we can add longitude, latitude in DMS or decimal degree,
Further we can consider to add
Postal-code, Country-code like Location type.

-Qin
-邮件原件-
发件人: netmod [mailto:netmod-boun...@ietf.org] 代表 Juergen Schoenwaelder
发送时间: 2018年10月31日 20:47
收件人: netmod@ietf.org
主题: Re: [netmod] for a future rfc6991bis

Here is my list of possible additions. I might have lost some items on a 
computer that meanwhile is not used anymore, I will have to dig a bit to see 
what I can recover.

/js

On Wed, Oct 31, 2018 at 01:26:01PM +0100, Ladislav Lhotka wrote:
> Hi,
> 
> another update that was discussed recently is a clarification of the 
> XPath context for the xpath1.0 type.
> 
> Lada
> 
> Kent Watsen  writes:
> 
> > NETMOD WG,
> >
> > A conversation in NETCONF WG regarding the yang-push noted that it 
> > might be time to update RFC 6991, in particular to introduce a type for 
time-duration.
> >
> >   
> > https://mailarchive.ietf.org/arch/msg/netconf/KaUJloIShkLNIXTuHZNwB-
> > SYBnQ
> >
> > In addition, it might be good to introduce [inet?] types for RFC 
> > 5322 (Internet Message Format) including perhaps:
> >
> >   - email-address(addr-spec, per Section 3.4.1)
> >   - named-email-address  (name-addr, per Section 3.4)
> >
> >
> > Kent // contributor
> >
> >
> >
> > ___
> > netmod mailing list
> > netmod@ietf.org
> > https://www.ietf.org/mailman/listinfo/netmod
> 
> --
> Ladislav Lhotka
> Head, CZ.NIC Labs
> PGP Key ID: 0xB8F92B08A9F76C67
> 
> ___
> netmod mailing list
> netmod@ietf.org
> https://www.ietf.org/mailman/listinfo/netmod

-- 
Juergen Schoenwaelder   Jacobs University Bremen gGmbH
Phone: +49 421 200 3587 Campus Ring 1 | 28759 Bremen | Germany
Fax:   +49 421 200 3103 
___
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod

___
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod

Re: [netmod] for a future rfc6991bis

2018-11-01 Thread Acee Lindem (acee)

Hi Qin,

We'd tried to converge on geo-coordinates in the protocols and received and a 
rather wide range of opinions as to the precision and what was required. An 
IETF consensus is required and not everyone is going to be happy. However, I'm 
not sure where this work lies and it hasn't been a priority for me. In fact, I 
let my draft expire: 
https://www.ietf.org/archive/id/draft-acee-ospf-geo-location-05.txt. I think 
trying to adding these before this happens could delay the BIS update. 

Thanks,
Acee

On 11/1/18, 7:55 AM, "netmod on behalf of Qin Wu"  wrote:

I am wondering if we can add longitude, latitude in DMS or decimal degree,
Further we can consider to add
Postal-code, Country-code like Location type.

-Qin
-邮件原件-
发件人: netmod [mailto:netmod-boun...@ietf.org] 代表 Juergen Schoenwaelder
发送时间: 2018年10月31日 20:47
收件人: netmod@ietf.org
主题: Re: [netmod] for a future rfc6991bis

Here is my list of possible additions. I might have lost some items on a 
computer that meanwhile is not used anymore, I will have to dig a bit to see 
what I can recover.

/js

On Wed, Oct 31, 2018 at 01:26:01PM +0100, Ladislav Lhotka wrote:
> Hi,
> 
> another update that was discussed recently is a clarification of the 
> XPath context for the xpath1.0 type.
> 
> Lada
> 
> Kent Watsen  writes:
> 
> > NETMOD WG,
> >
> > A conversation in NETCONF WG regarding the yang-push noted that it 
> > might be time to update RFC 6991, in particular to introduce a type for 
time-duration.
> >
> >   
> > https://mailarchive.ietf.org/arch/msg/netconf/KaUJloIShkLNIXTuHZNwB-
> > SYBnQ
> >
> > In addition, it might be good to introduce [inet?] types for RFC 
> > 5322 (Internet Message Format) including perhaps:
> >
> >   - email-address(addr-spec, per Section 3.4.1)
> >   - named-email-address  (name-addr, per Section 3.4)
> >
> >
> > Kent // contributor
> >
> >
> >
> > ___
> > netmod mailing list
> > netmod@ietf.org
> > https://www.ietf.org/mailman/listinfo/netmod
> 
> --
> Ladislav Lhotka
> Head, CZ.NIC Labs
> PGP Key ID: 0xB8F92B08A9F76C67
> 
> ___
> netmod mailing list
> netmod@ietf.org
> https://www.ietf.org/mailman/listinfo/netmod

-- 
Juergen Schoenwaelder   Jacobs University Bremen gGmbH
Phone: +49 421 200 3587 Campus Ring 1 | 28759 Bremen | Germany
Fax:   +49 421 200 3103 
___
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod

___
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod

Re: [netmod] for a future rfc6991bis

2018-11-01 Thread Juergen Schoenwaelder

I think we need to find a way to limit the update to types that are
known (or expected) to be 'widely' needed. In other words, for every
proposed type, an argument should be made why this should be included
in RFC 6991bis.

/js

On Thu, Nov 01, 2018 at 11:55:25AM +, Qin Wu wrote:
> I am wondering if we can add longitude, latitude in DMS or decimal degree,
> Further we can consider to add
> Postal-code, Country-code like Location type.
> 
> -Qin
> -邮件原件-
> 发件人: netmod [mailto:netmod-boun...@ietf.org] 代表 Juergen Schoenwaelder
> 发送时间: 2018年10月31日 20:47
> 收件人: netmod@ietf.org
> 主题: Re: [netmod] for a future rfc6991bis
> 
> Here is my list of possible additions. I might have lost some items on a 
> computer that meanwhile is not used anymore, I will have to dig a bit to see 
> what I can recover.
> 
> /js
> 
> On Wed, Oct 31, 2018 at 01:26:01PM +0100, Ladislav Lhotka wrote:
> > Hi,
> > 
> > another update that was discussed recently is a clarification of the 
> > XPath context for the xpath1.0 type.
> > 
> > Lada
> > 
> > Kent Watsen  writes:
> > 
> > > NETMOD WG,
> > >
> > > A conversation in NETCONF WG regarding the yang-push noted that it 
> > > might be time to update RFC 6991, in particular to introduce a type for 
> > > time-duration.
> > >
> > >   
> > > https://mailarchive.ietf.org/arch/msg/netconf/KaUJloIShkLNIXTuHZNwB-
> > > SYBnQ
> > >
> > > In addition, it might be good to introduce [inet?] types for RFC 
> > > 5322 (Internet Message Format) including perhaps:
> > >
> > >   - email-address(addr-spec, per Section 3.4.1)
> > >   - named-email-address  (name-addr, per Section 3.4)
> > >
> > >
> > > Kent // contributor
> > >
> > >
> > >
> > > ___
> > > netmod mailing list
> > > netmod@ietf.org
> > > https://www.ietf.org/mailman/listinfo/netmod
> > 
> > --
> > Ladislav Lhotka
> > Head, CZ.NIC Labs
> > PGP Key ID: 0xB8F92B08A9F76C67
> > 
> > ___
> > netmod mailing list
> > netmod@ietf.org
> > https://www.ietf.org/mailman/listinfo/netmod
> 
> -- 
> Juergen Schoenwaelder   Jacobs University Bremen gGmbH
> Phone: +49 421 200 3587 Campus Ring 1 | 28759 Bremen | Germany
> Fax:   +49 421 200 3103 

-- 
Juergen Schoenwaelder   Jacobs University Bremen gGmbH
Phone: +49 421 200 3587 Campus Ring 1 | 28759 Bremen | Germany
Fax:   +49 421 200 3103 

___
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod

Re: [netmod] for a future rfc6991bis

2018-11-01 Thread Qin Wu

I am wondering if we can add longitude, latitude in DMS or decimal degree,
Further we can consider to add
Postal-code, Country-code like Location type.

-Qin
-邮件原件-
发件人: netmod [mailto:netmod-boun...@ietf.org] 代表 Juergen Schoenwaelder
发送时间: 2018年10月31日 20:47
收件人: netmod@ietf.org
主题: Re: [netmod] for a future rfc6991bis

Here is my list of possible additions. I might have lost some items on a 
computer that meanwhile is not used anymore, I will have to dig a bit to see 
what I can recover.

/js

On Wed, Oct 31, 2018 at 01:26:01PM +0100, Ladislav Lhotka wrote:
> Hi,
> 
> another update that was discussed recently is a clarification of the 
> XPath context for the xpath1.0 type.
> 
> Lada
> 
> Kent Watsen  writes:
> 
> > NETMOD WG,
> >
> > A conversation in NETCONF WG regarding the yang-push noted that it 
> > might be time to update RFC 6991, in particular to introduce a type for 
> > time-duration.
> >
> >   
> > https://mailarchive.ietf.org/arch/msg/netconf/KaUJloIShkLNIXTuHZNwB-
> > SYBnQ
> >
> > In addition, it might be good to introduce [inet?] types for RFC 
> > 5322 (Internet Message Format) including perhaps:
> >
> >   - email-address(addr-spec, per Section 3.4.1)
> >   - named-email-address  (name-addr, per Section 3.4)
> >
> >
> > Kent // contributor
> >
> >
> >
> > ___
> > netmod mailing list
> > netmod@ietf.org
> > https://www.ietf.org/mailman/listinfo/netmod
> 
> --
> Ladislav Lhotka
> Head, CZ.NIC Labs
> PGP Key ID: 0xB8F92B08A9F76C67
> 
> ___
> netmod mailing list
> netmod@ietf.org
> https://www.ietf.org/mailman/listinfo/netmod

-- 
Juergen Schoenwaelder   Jacobs University Bremen gGmbH
Phone: +49 421 200 3587 Campus Ring 1 | 28759 Bremen | Germany
Fax:   +49 421 200 3103 
___
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod

Re: [netmod] for a future rfc6991bis

2018-11-01 Thread Balázs Lengyel


  
  
Hello,
We do see a need for the following types:

  date (in the earlier debate as I remember Martin wanted to
include timezone)
  
  time
  node-instance-identifier from netconf-acm. We found that this
is a useful type used not just in acm, so it would be nice to
have it defined in 6991.
  
  email
  

regards Balazs

On 2018. 10. 31. 13:46, Juergen
  Schoenwaelder wrote:


  Here is my list of possible additions. I might have lost some items on
a computer that meanwhile is not used anymore, I will have to dig a
bit to see what I can recover.

/js

On Wed, Oct 31, 2018 at 01:26:01PM +0100, Ladislav Lhotka wrote:

  
Hi,

another update that was discussed recently is a clarification of the
XPath context for the xpath1.0 type.

Lada

Kent Watsen  writes:



  NETMOD WG,

A conversation in NETCONF WG regarding the yang-push noted that it might be 
time to update RFC 6991, in particular to introduce a type for time-duration.

  https://mailarchive.ietf.org/arch/msg/netconf/KaUJloIShkLNIXTuHZNwB-SYBnQ

In addition, it might be good to introduce [inet?] types for RFC 5322 
(Internet Message Format) including perhaps:

  - email-address(addr-spec, per Section 3.4.1)
  - named-email-address  (name-addr, per Section 3.4)


Kent // contributor



___
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod



-- 
Ladislav Lhotka
Head, CZ.NIC Labs
PGP Key ID: 0xB8F92B08A9F76C67

___
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod

  
  

  
  
  ___
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod


-- 
Balazs Lengyel   Ericsson Hungary Ltd.
Senior Specialist
Mobile: +36-70-330-7909  email: balazs.leng...@ericsson.com 

  




smime.p7s
Description: S/MIME Cryptographic Signature
___
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod

Re: [netmod] for a future rfc6991bis

Re: [netmod] for a future rfc6991bis

Re: [netmod] for a future rfc6991bis

Re: [netmod] for a future rfc6991bis

Re: [netmod] for a future rfc6991bis

Re: [netmod] for a future rfc6991bis

Re: [netmod] for a future rfc6991bis

7 matches

Site Navigation

Mail list logo

Footer information