issues
search
ietf-wg-idr
/
draft-ietf-idr-5g-edge-service-metadata-14
Editing for the 5G Service Metadata
0
stars
1
forks
source link
issues
Newest
Newest
Most commented
Recently updated
Oldest
Least commented
Least recently updated
Edits and notes from review
#33
jhaas-pfrc
opened
4 days ago
1
Please update IANA section, TLV names should be synced up
#32
muzixing
closed
1 month ago
2
Required Resolution Checks prior to Early Allocation (Summary)
#31
suehares
opened
1 month ago
0
Section 9 - Definition of BGP domain
#30
suehares
closed
1 month ago
1
Section 4.5.2 - Informative rather than normative
#29
suehares
closed
1 month ago
1
Section 5 is Informative
#28
suehares
closed
1 month ago
1
Section 4.4.1
#27
suehares
closed
1 month ago
2
Please list the field description in order in the TLV
#26
muzixing
closed
2 months ago
1
description of length
#25
muzixing
closed
2 months ago
1
Add Resource ID
#24
muzixing
opened
2 months ago
2
Remove A-flag in Service-Oriented Capacity Sub-TLV
#23
muzixing
closed
2 months ago
3
Length fields in section 4.3
#22
suehares
closed
2 months ago
1
Added my revision-18, deleteed the file of revision-14
#21
muzixing
closed
4 days ago
1
Allowing to distribute raw delay info?
#20
muzixing
closed
5 months ago
2
add a utilization TLV for the per-service/service-oriented Capability TLV
#19
muzixing
opened
5 months ago
2
make the TLVs more flexible
#18
muzixing
closed
5 months ago
1
adding a Capability sub-TLV for a service
#17
muzixing
closed
4 months ago
1
Inconsistent Route Selection Considerations:
#16
suehares
closed
2 months ago
2
Route churn
#15
suehares
closed
2 months ago
3
Detail in section 5
#14
suehares
closed
2 months ago
2
Jeff Haas comment: need more clarification for the Site Physical Availability Index Sub-TLV
#13
lindadunbar
opened
5 months ago
2
Need to describe the scale of the prefixes with Metadata Path Attribute attached
#12
lindadunbar
opened
5 months ago
4
Jeff Haas suggested to merge Section 4.1.3 (Metadata Path Attribute Error Handling) with Section 8 (Validation and Error Handling)
#11
lindadunbar
closed
5 months ago
1
The Security Consideration addition to ensure boundary nodes not leaking Metadata on accident
#10
lindadunbar
closed
5 months ago
1
Section 4.3.2 - Routing methodology here is problematic
#9
suehares
closed
5 months ago
4
Section 4.3.1 - Site Index Associated to Routes
#8
suehares
closed
5 months ago
3
Reserved Field in Site Physical Availability Index
#7
suehares
closed
6 months ago
1
Route-Flag-I text needs correction
#6
suehares
closed
6 months ago
1
Metadata Path Attributive - Clear definition that Attribute is non-transitive
#5
suehares
closed
5 months ago
7
Adding a new Route Target code point for constraining Metadata Path Attribute distribution
#4
lindadunbar
opened
6 months ago
2
Jeff Haas original comments on Oc 27, 2023
#3
lindadunbar
opened
6 months ago
4
New Route Target code point for constraining Metadata Path Attribute distribution
#2
lindadunbar
closed
5 months ago
1
comments on the draft-ietf-idr-5g-edge-service-metadata-14 from LinChangWang (inchangwang.04414@h3c.com)
#1
lindadunbar
opened
6 months ago
1