<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif;">
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<div>
<div>On 3/21/15, 9:10 AM, "Salvatore Orlando" <<a href="mailto:sorlando@nicira.com">sorlando@nicira.com</a>> wrote:</div>
</div>
<div><br>
</div>
<blockquote id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style="BORDER-LEFT: #b5c4df 5 solid; PADDING:0 0 0 5; MARGIN:0 0 0 5;">
<div>
<div>
<div dir="ltr">If we feel a need for specifying the relative position of gateway address and allocation pools when creating a subnet from a pool which will pick a CIDR from its prefixes, then the integer value solution is probably marginally better than the
"fake IP" one (eg.: 0.0.0.1 to say the gateway is the first IP). Technically they're equivalent - and one could claim that the address-like notation is nothing bug and octet based representation of a number.
</div>
</div>
</div>
</blockquote>
</span>
<div><br>
</div>
<div>I agree here. An integer is probably clearer.</div>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<blockquote id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style="BORDER-LEFT: #b5c4df 5 solid; PADDING:0 0 0 5; MARGIN:0 0 0 5;">
<div>
<div>
<div dir="ltr">
<div><br>
</div>
<div>I wonder why a user would ask for a random CIDR with a given prefix, and then mandate that gateway IP and allocation pools are in precise locations within this randomly chosen CIDR. I guess there are good reasons I cannot figure out by myself.
</div>
</div>
</div>
</div>
</blockquote>
</span>
<div><br>
</div>
<div>Early in the spec review cycle we talked about some generalizations of these concepts. I would consider the location of the gateway IP to be a reservation; we discussed having subnet templates that (in my mind) are essentially a collection of IP reservations.
This would allow a user to specify the specific locations of various services in a pre-defined manner; routing is just one of those services that is prominent as a specific case for backwards compatibility.</div>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<blockquote id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style="BORDER-LEFT: #b5c4df 5 solid; PADDING:0 0 0 5; MARGIN:0 0 0 5;">
<div>
<div>
<div dir="ltr">
<div>In my opinion all that counts here is that the semantics of a resource attribute should be the same in the request and the response. For instance, one should not have gateway_ip as a relative "counter-like" IP in the request body and then as an actual
IP address in the response object. </div>
</div>
</div>
</div>
</blockquote>
</span>
<div><br>
</div>
<div>So, you are agreeing with an alternate name in the request, as suggested?</div>
<div><br>
</div>
<div>John</div>
<span id="OLK_SRC_BODY_SECTION">
<div>
<div>
<div class="gmail_extra"><br>
</div>
</div>
</div>
</span>
</body>
</html>