Opened 7 years ago

Last modified 7 years ago

#1 new enhancement

When is customer-nat-address used?

Reported by: adrian@… Owned by: draft-ietf-l3sm-l3vpn-service-model@…
Priority: minor Milestone: milestone1
Component: l3vpn-service-model Version: 2.0
Severity: Active WG Document Keywords: NAT
Cc:

Description

Issue raised by Aijun Wang (wangaijun@…)

What is the scenario where the leaf "customer-nat-address" will be used?
If the customer being provided one public address, why use NAT? if use NAT, why allocate such "customer-nat-address"?

Change History (3)

comment:1 Changed 7 years ago by wangaj@…

S.Litkowski has given the explanation during IETF Yokohama meeting. This issue can be closed.

comment:2 in reply to: ↑ description Changed 7 years ago by bill.wu@…

Replying to adrian@…:

Issue raised by Aijun Wang (wangaijun@…)

What is the scenario where the leaf "customer-nat-address" will be used?
If the customer being provided one public address, why use NAT? if use NAT, why allocate such "customer-nat-address"?

There was agreement on the list to close this issue. No change is needed.

comment:3 Changed 7 years ago by bill.wu@…

  • Component changed from draft-ltsd-l3sm-l3vpn-service-model to l3vpn-service-model
  • Milestone set to milestone1
  • Owner changed from draft-ltsd-l3sm-l3vpn-service-model@… to draft-ietf-l3sm-l3vpn-service-model@…
  • Severity changed from - to Active WG Document
  • Version set to 2.0
Note: See TracTickets for help on using tickets.