Re: [BEHAVE] CGN REQ: Port Set Assignment

[Simon Perreault <[e-mail]>]

[e-mail] wrote, on 03/17/2011 03:24 AM:
>    1.  for a new outgoing flow, choose a random port and create a new
>        mapping.  There is a limit on the maximum number of ports.
> 
>    2.  for a new outgoing flow, choose several random ports and create a
>        "bin" of those ports.  This outgoing flow is assigned one of
>        those ports.  Subsequent outgoing flows will be assigned a port
>        from the "bin".  When the "bin" is full, a new flow causes this
>        process to be repeated (i.e., a new bin is created).  A bin is
>        smaller or equal to the user's maximum port limit.
> 
>    3.  Same as (2), but the ports allocated to a "bin" are consecutive
>        public ports.
> 
> Med: I don't know where to put the non-contiguous one single "bin" case (excerpt from (see http://tools.ietf.org/html/draft-bajko-pripaddrassign-02#section-4.1)
> 
>    "a non Continuous Port Range is assigned to a given customer's
>    device. In this example, the Port Range Value defines 128 Continuous
>    Port Ranges, each one with a length of 16 port values.  Note that
>    the two first Port Ranges are both in the well-known ports span
>    (i.e. 0-1023) but these two ranges are not adjacent.

It looks to me like it would be between 2 and 3: somewhat random, but not
completely.

Now, I don't think we need to list all possibilities in the draft. Anyone could
invent a dozen new ones by blending what's already there in varying proportions,
without even trying hard to be creative.

What the text needs to make clear is that this is a continuum, and how the pros
and cons vary as you move along it (as a first step). The next revision will
contain terminology that will work better than numbers for discussion.

Thanks,
Simon
-- 
NAT64/DNS64 open-source --> http://ecdysis.viagenie.ca
STUN/TURN server        --> http://numb.viagenie.ca
vCard 4.0               --> http://www.vcarddav.org