Looking at drafts, I noticed that draft-ietf-teas-nrp-scalability says
that one is required (? expected? needs to?) use an NRP separate from
the path control information.
However, the Spring adopted draft
draft-ietf-spring-resource-aware-segments puts the NRP selection in the
segment identifier(s).
If you tried to do both, you would have two conflicting representations
for the NRP to be used in the same packet. That seems problematic.
We need to somehow resolve this.
Yours,
Joel
_______________________________________________
spring mailing list -- spring@ietf.org
To unsubscribe send an email to spring-le...@ietf.org
