![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
David,
I was looking more for an explanation of how and why it was decided to be out of scope.
The arguments for considering it to be in scope would have been:
- the TCP and UDP "pseudo-headers" needed to be changed anyway to accomodate IPv6 addresses (see section 8.1 of RFC 2460);
- the pressure on well-known port numbers was obvious at the time;
- supporting 32-bit port numbers in IPv6 stacks could have been done at very little incremental cost;
- a larger port space would have been an additional incentive to adopt IPv6;
- more ambitious changes to TCP would have a low probability of adoption within a relevant timeframe;
- it makes sense for the port number space to be the same size for UDP-over-IPv6 and TCP-over-IPv6.
Bob
_______________________________________________ Ietf mailing list Ietf at ietf.org https://www1.ietf.org/mailman/listinfo/ietf
Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.