Re: [Softwires] WGLC for draft-ietf-softwire-iftunnel-01

2019-01-08 Thread Rajiv Asati (rajiva) 
Support (as a co-author).

--
Cheers,
Rajiv

From: Softwires  on behalf of "ianfar...@gmx.com" 

Date: Tuesday, January 8, 2019 at 11:48 AM
To: Yong Cui 
Cc: Softwires-wg list 
Subject: Re: [Softwires] WGLC for draft-ietf-softwire-iftunnel-01

HI Yong,

Sorry for the late response. I’m still catching up after the holidays…

As a co-author, I support this document progressing. As you mention below, 
separating out the iftunnels module from draft-ietf-softwire-yang into a new 
draft was requested during the IANA review.  meaning that 
draft-ietf-softwire-yang (currently with the IESG) now has a normative 
reference to this draft.

Regarding the draft itself, the iftunnel module itself has already been through 
the final WGLC for draft-ietf-softwire-yang. As it models the IANA tunnelType 
Definitions registry 
(https://www.iana.org/assignments/smi-numbers/smi-numbers.xhtml#smi-numbers-6), 
we’ve tried to keep the format in line with other, similar documents with YANG 
modules for other IANA registries (e.g. RFC7224).

Thanks,
Ian


On 19. Dec 2018, at 08:26, Yong Cui 
mailto:cuiy...@tsinghua.edu.cn>> wrote:

Dear all,

There were the following progress on Softwire YANG and related work during the 
past couple of months:
• draft-ietf-softwire-yang completed WGLC
• During expert review, a YANG module for the iana-iftunnel registry was 
requested as the softwire module needs to reference it.
• draft-ietf-softwire-yang was updated to include this module and Sheng ran a 
WGLC on the new content. This passed without comment.
• During IANA review, it was requested that the iana-iftunnel YANG module was 
put into a separate document.
• draft-ietf-softwire-yang was updated, removing the iana-iftunnel YANG module, 
and draft-ietf-softwire-iftunnel was published containing just the module (it 
was posted as a WG doc as the content etc. is already under the scope of 
draft-ietf-softwire-yang)

So now, we’d like to issue a WGLC for draft-ietf-softwire-iftunnel-01.
https://datatracker.ietf.org/doc/draft-ietf-softwire-iftunnel/

Considering the coming Christmas and New Year, I would extend the WGLC to 3 
weeks, i.e. Dec. 19, 2018 - Jan. 9, 2019. Please send your comments to our 
softwire mailing list, including your support or concerns.


Merry Christmas and Happy New Year!

Yong & Ian

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

Re: [Softwires] [Gen-art] Genart last call review of draft-ietf-softwire-yang-06

2019-01-08 Thread Alissa Cooper 
Roni, thanks for your reviews. Ian, thanks for your responses. I entered a 
DISCUSS ballot concerning the security considerations.

Best,
Alissa

> On Jan 7, 2019, at 7:42 AM, ianfar...@gmx.com wrote:
> 
> Hi Roni,
> 
> My apologies for the oversight. I’ve just posted -14 which includes the 
> RESTCONF reference in the Introduction.
> 
> Thanks,
> Ian
> 
>> On 9. Oct 2018, at 09:02, Roni Even > > wrote:
>> 
>> Reviewer: Roni Even
>> Review result: Ready with Nits
>> 
>> I am the assigned Gen-ART reviewer for this draft. The General Area
>> Review Team (Gen-ART) reviews all IETF documents being processed
>> by the IESG for the IETF Chair.  Please treat these comments just
>> like any other last call comments.
>> 
>> For more information, please see the FAQ at
>> 
>> .
>> 
>> Document: draft-ietf-softwire-yang-??
>> Reviewer: Roni Even
>> Review Date: 2018-10-08
>> IETF LC End Date: 2018-10-11
>> IESG Telechat date: Not scheduled for a telechat
>> 
>> Summary:
>> The document is ready for publication as a standard track RFC with nits
>> 
>> Major issues:
>> 
>> Minor issues:
>> 
>> Nits/editorial comments:
>> 1. In section 1 it says that the YANG data model can be used with netconf , I
>> noticed that restconf is only mentioned in the security section as network
>> management. why not add restconf to introduction?
>> 
>> 
>> ___
>> Softwires mailing list
>> Softwires@ietf.org 
>> https://www.ietf.org/mailman/listinfo/softwires 
>> 
> 
> ___
> Gen-art mailing list
> gen-...@ietf.org 
> https://www.ietf.org/mailman/listinfo/gen-art 
> 
___
Softwires mailing list
Softwires@ietf.org
https://www.ietf.org/mailman/listinfo/softwires

[Softwires] Alissa Cooper's Discuss on draft-ietf-softwire-yang-14: (with DISCUSS and COMMENT)

2019-01-08 Thread Alissa Cooper 
Alissa Cooper has entered the following ballot position for
draft-ietf-softwire-yang-14: Discuss

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-softwire-yang/



--
DISCUSS:
--

The security considerations do not seem to follow the YANG security guidelines
. They do not
list the specific writeable and readable subtrees/nodes and why they are
sensitive. The fact that all the writeable nodes could "negatively affect
network operations" seems trivially true for most writeable YANG module nodes.
In the case of these modules, there seem to be multiple different threats
relevant to different nodes, including exposure of data about individual
users/customers, potential for disruption of the operations of the BR or CE,
etc.


--
COMMENT:
--

I think "external party" would make more sense than "abuse party."


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

Re: [Softwires] WGLC for draft-ietf-softwire-iftunnel-01

2019-01-08 Thread ianfarrer 
HI Yong,

Sorry for the late response. I’m still catching up after the holidays…

As a co-author, I support this document progressing. As you mention below, 
separating out the iftunnels module from draft-ietf-softwire-yang into a new 
draft was requested during the IANA review.  meaning that 
draft-ietf-softwire-yang (currently with the IESG) now has a normative 
reference to this draft.

Regarding the draft itself, the iftunnel module itself has already been through 
the final WGLC for draft-ietf-softwire-yang. As it models the IANA tunnelType 
Definitions registry 
(https://www.iana.org/assignments/smi-numbers/smi-numbers.xhtml#smi-numbers-6 
),
 we’ve tried to keep the format in line with other, similar documents with YANG 
modules for other IANA registries (e.g. RFC7224).

Thanks,
Ian

> On 19. Dec 2018, at 08:26, Yong Cui  wrote:
> 
> Dear all,
> 
> There were the following progress on Softwire YANG and related work during 
> the past couple of months:
>   • draft-ietf-softwire-yang completed WGLC
>   • During expert review, a YANG module for the iana-iftunnel registry 
> was requested as the softwire module needs to reference it.
>   • draft-ietf-softwire-yang was updated to include this module and Sheng 
> ran a WGLC on the new content. This passed without comment.
>   • During IANA review, it was requested that the iana-iftunnel YANG 
> module was put into a separate document.
>   • draft-ietf-softwire-yang was updated, removing the iana-iftunnel YANG 
> module, and draft-ietf-softwire-iftunnel was published containing just the 
> module (it was posted as a WG doc as the content etc. is already under the 
> scope of draft-ietf-softwire-yang)
> 
> So now, we’d like to issue a WGLC for draft-ietf-softwire-iftunnel-01. 
> https://datatracker.ietf.org/doc/draft-ietf-softwire-iftunnel/
> 
> Considering the coming Christmas and New Year, I would extend the WGLC to 3 
> weeks, i.e. Dec. 19, 2018 - Jan. 9, 2019. Please send your comments to our 
> softwire mailing list, including your support or concerns.
> 
> 
> Merry Christmas and Happy New Year!
> 
> Yong & Ian
> 

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