issues
search
rgwilton
/
YANG-Packages-Draft
IETF Individual Draft for possible YANG Package Solution
Other
0
stars
0
forks
source link
issues
Newest
Newest
Most commented
Recently updated
Oldest
Least commented
Least recently updated
Need to add checksum to the YL reference of a package
#45
rgwilton
closed
4 years ago
0
Tweak text
#44
rgwilton
closed
4 years ago
1
Section 5.2.1.1 needs to be more definitive in how they apply
#43
rgwilton
closed
4 years ago
0
Timestamp or date?
#42
rgwilton
closed
4 years ago
1
Should "supported-features" be hierarchical?
#41
rgwilton
closed
4 years ago
1
Should packages just be in JSON or XML?
#40
rgwilton
closed
4 years ago
1
Be more clear about what is meant by "metadata"
#39
rgwilton
closed
4 years ago
1
Is is import or include package
#38
rgwilton
closed
4 years ago
1
Clean up terminology between package and package instance
#37
rgwilton
closed
4 years ago
1
Can we just use a prefix of the SHA-256 for the checksum?
#36
rgwilton
closed
4 years ago
1
Is it possible for a revision to be implemented and another revision to be import-only?
#35
rgwilton
closed
4 years ago
1
Rework text on Sec 5.3: Client server package conformance
#34
rgwilton
closed
4 years ago
1
YANG package as the schema for an instance data document
#33
rgwilton
closed
4 years ago
1
Define an IANA registry for IETF YANG packages
#32
rgwilton
closed
4 years ago
1
Package tags
#31
rgwilton
closed
4 years ago
1
Ensure that definition of BC vs NBC change is well defined between the documents
#30
rgwilton
closed
4 years ago
1
Package conformance
#29
rgwilton
closed
4 years ago
0
Add NBC leaf?
#28
rgwilton
closed
4 years ago
1
Selecting features
#27
rgwilton
closed
4 years ago
0
Should a package be able to remove modules from an imported package?
#26
rgwilton
closed
4 years ago
1
Semantic versioning draft should include text like the following:
#25
rgwilton
closed
4 years ago
1
Add contact/organization to a package definition?
#24
rgwilton
closed
4 years ago
2
Should a top level package definition contain location/checksum?
#23
rgwilton
closed
4 years ago
1
What should the unique identifier for a YANG package be?
#22
rgwilton
closed
4 years ago
1
Do we enforce that every YANG module in a package has to at least have a revision date?
#21
rgwilton
closed
4 years ago
2
Perhaps change revision-date to date and time
#20
rgwilton
closed
5 years ago
1
Allow multiple package definitions in an instance data document?
#19
rgwilton
closed
4 years ago
3
Add flag to indicate if a package is a top level selectable package
#18
rgwilton
closed
4 years ago
2
Add references to draft-verdt-netmod-yang-semver
#17
rgwilton
closed
4 years ago
1
Should a package include RFC 8199 related metadata?
#16
rgwilton
closed
5 years ago
0
Should a package (or implementation) be able to remove modules from a package?
#15
rgwilton
closed
5 years ago
1
Is disabling features using deviations sufficient?
#14
rgwilton
closed
4 years ago
1
Do packages need namespaces, or are unique package names sufficient
#13
rgwilton
closed
5 years ago
0
Should package definitions differ between YANG library and instance data docs?
#12
rgwilton
closed
4 years ago
2
Augment YANG library, or new version?
#11
rgwilton
closed
4 years ago
1
Should the package definitions be part of YANG library?
#10
rgwilton
closed
4 years ago
1
How do bug fixes work with packages?
#9
rgwilton
closed
4 years ago
1
Is it correct for there to only be a single package per schema?
#8
rgwilton
closed
4 years ago
2
Should features be listed per module, or per package, or globally
#7
rgwilton
closed
4 years ago
1
Add a parent-version field
#6
rgwilton
closed
4 years ago
1
Should partial packages (e.g. not referentially complete) be allowed?
#5
rgwilton
closed
4 years ago
2
Should we be using draft-ietf-netmod-yang-instance-file-format?
#4
rgwilton
closed
4 years ago
1
Remove stale text that talks about package namespaces.
#3
rgwilton
closed
5 years ago
0
Enhance package deviation examples
#2
rgwilton
closed
4 years ago
1
Add support for deviations
#1
rgwilton
closed
4 years ago
2