Hi, Acee,
Thanks for your information.
Let's use iana-routing-types to define AF.
Regarding the camelCase, just follow the RFC 7224 iana-if-type YANG. In
IANA consideration, there is a statement: "The name of the "identity" is the
same as the corresponding enumeration in the
Hi,
Below is part of 1 tree diagram from yang-push-06.
The problem is that is shows the entire RPC, and gives
no indication at all that this module only defines augmentations,
or which nodes in the tree diagram will be found here.
Andy
rpcs:
+---x establish-subscription
| +---w
On Mon, May 22, 2017 at 2:56 PM, Juergen Schoenwaelder <
j.schoenwael...@jacobs-university.de> wrote:
> RFC 7952 says:
>
>4. Annotations sent by a server should not break clients that don't
>support them.
>
> If the client is expected to understand which hash function has been
> used
RFC 7952 says:
4. Annotations sent by a server should not break clients that don't
support them.
If the client is expected to understand which hash function has been
used to generate a hash value, then I think the hash function should
be communicated as proper YANG data and not as
Hi all,
Does anyone see any reasons why RFC7952 annotations couldn't/shouldn't be used
to identify the encryption/hashing format of an encrypted/hashed leaf ?
There are a number of approaches out there for encrypted/hashed leafs (e.g.
RFC7317 crypt-hash which encodes the hash function by
reminder this is happening now...
WebEx: https://ietf.webex.com/ietf/j.php?MTID=m87b080addaf71be419f67f2a893cfe94
Etherpad: http://etherpad.tools.ietf.org:9000/p/notes-2017-may-interim-netmod
On 5/22/2017 10:23 AM, Kent Watsen wrote:
> Some more useful links for today's virtual interim.
>
>
>
Reviewer: Pete Resnick
Review result: Ready
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 wait for direction from your
document shepherd or AD before posting a new version
Some more useful links for today's virtual interim.
* Etherpad: http://etherpad.tools.ietf.org:9000/p/notes-2017-may-interim-netmod
* Slides from Chicago:
https://www.ietf.org/proceedings/98/slides/slides-98-netmod-sessb-schema-mount-00.pdf
K.
-ORIGINAL MESSAGE-
Gentle reminder:
Chin,
These are already defined in iana-routing-types …
https://www.ietf.org/id/draft-ietf-rtgwg-routing-types-04.txt
Furthermore, if you propose future YANG models, let's not bring back
MIB-esque camelCase naming conventions. Like baggy jeans and neon, it was
a fad should rest in peace with
Lou Berger writes:
> On 5/17/2017 3:46 AM, Martin Bjorklund wrote:
>>> Also open issue B.3 says design time mounts are not supported yet but
>>> sec 1 (Intro) says they are out of scope:
>>>
>>>The schema mount mechanism defined in this document provides support
>>>only
10 matches
Mail list logo